Bugzilla – Full Text Bug Listing
| Summary: | Add EF AISBL Documents on our Governance Documents page | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Sharon Corbett <sharon.corbett> | ||||||
| Component: | Website | Assignee: | Christopher Guindon <chris.guindon> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | chris.guindon, mike.milinkovich, Paul.White, wayne.beaton, webmaster, yi.liu | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 10 | ||||||||
| See Also: |
https://git.eclipse.org/r/c/www.eclipse.org/org/+/170848 https://git.eclipse.org/c/www.eclipse.org/org.git/commit/?id=c555b300bcb2ddacc600b7d2d144f2493fbc55ef |
||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 566455 | ||||||||
| Attachments: |
|
||||||||
|
Description
Sharon Corbett
The existing URL for the existing Bylaw will be deprecated when we go live with the others! (In reply to Sharon Corbett from comment #1) > The existing URL for the existing Bylaw will be deprecated when we go live > with the others! I was thinking of using the existing url for Eclipse Foundation AISBL and create a new url for EF US. If deprecated the current URL, we will probably want to create a redirect to the Eclipse Foundation AISBL document to avoid broken links on the site. What do you think of this: https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf => EF BE https://www.eclipse.org/org/documents/eclipse_foundation-us-bylaws.pdf => EF US If we want a unique URL for EF BE, I would propose: https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf (In reply to Christopher Guindon from comment #3) > What do you think of this: > > https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf => EF BE > https://www.eclipse.org/org/documents/eclipse_foundation-us-bylaws.pdf => EF > US > > If we want a unique URL for EF BE, I would propose: > https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf Sharon, could you tell us what is your preference here? Mike (and I have to agree), prefer consistency: https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf https://www.eclipse.org/org/documents/eclipse_foundation-us-bylaws.pdf Hope that helps. Sharon (In reply to Christopher Guindon from comment #3) > What do you think of this: > > https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf => EF BE > https://www.eclipse.org/org/documents/eclipse_foundation-us-bylaws.pdf => EF > US > > If we want a unique URL for EF BE, I would propose: > https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf Here is my two cents: For consistency put the documents here: https://www.eclipse.org/org/documents/eclipse_foundation-us-bylaws.pdf https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf (and if you want to replace the "_" above to "-" we could do that. For backwards compatibility can we redirect https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf >>> https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf I do realize that redirecting PDFs are a complete pain in the backside, relying on a 301 redirect, so if this not the way that you want to go just say so and I will try again. (In reply to Mike Milinkovich from comment #6) > (In reply to Christopher Guindon from comment #3) > Here is my two cents: > > For consistency put the documents here: > https://www.eclipse.org/org/documents/eclipse_foundation-us-bylaws.pdf > https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf > > (and if you want to replace the "_" above to "-" we could do that. +1 let's replace the _ to -. https://www.eclipse.org/org/documents/eclipse-foundation-us-bylaws.pdf https://www.eclipse.org/org/documents/eclipse-foundation-be-bylaws.pdf > For backwards compatibility can we redirect > https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf > >>> https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf > > I do realize that redirecting PDFs are a complete pain in the backside, > relying on a 301 redirect, so if this not the way that you want to go just > say so and I will try again. The idea would be to redirect the old document to the BE version? +1 for redirect. Some might say it's a pain because it's the same amount of work to create 1 redirect or 5. This is not a problem here given the scope of what we are changing. I think we are in an agreement on how we should be name these documents. I would like to re-purpose this bug to include documents from /org/documents/ that will have a EF-US and EF-BE version. Please confirm my list: 1. Bylaws 2. Membership Agreement 3. Affiliates Membership Guidelines 4. Intellectual Property Policy 5. Antitrust Policy Once confirm, I will provide a list of new URL for these documents. I will also provide a list to webmaster so that we can prepare the redirect rules. I created a spreadsheet to document these URL changes: https://docs.google.com/spreadsheets/d/1BVUP3wjKhkXiqeDkeyYDZ9xEzp8rlWvkri9ZEXG7b8k/edit#gid=0 Sharon, please let me know what you think! (In reply to Christopher Guindon from comment #7) > > For backwards compatibility can we redirect > > https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf > > >>> https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf > > > > I do realize that redirecting PDFs are a complete pain in the backside, > > relying on a 301 redirect, so if this not the way that you want to go just > > say so and I will try again. > > The idea would be to redirect the old document to the BE version? Yes. Perhaps not immediately, but yes. The idea being that once we have made the transition if someone (including our own web pages) has that URL hard coded somewhere they are going to land at our new and relevant Bylaws. > Please confirm my list: > > 1. Bylaws > 2. Membership Agreement > 3. Affiliates Membership Guidelines > 4. Intellectual Property Policy > 5. Antitrust Policy It's actually only #1 and #2. #3 should not be on that list. Actually, it would by my preference if the link to those affiliate guidelines was moved down on that page to be included in the list of all of those policies below. #4,5 are actually going to be word-for-word identical between the EF-US and EF-BE. So they will be maintained as the same document. So they will have the same URLs. HTH (In reply to Mike Milinkovich from comment #9) > (In reply to Christopher Guindon from comment #7) > > > For backwards compatibility can we redirect > > > https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf > > > >>> https://www.eclipse.org/org/documents/eclipse_foundation-be-bylaws.pdf > > > > > > I do realize that redirecting PDFs are a complete pain in the backside, > > > relying on a 301 redirect, so if this not the way that you want to go just > > > say so and I will try again. > > > > The idea would be to redirect the old document to the BE version? > > Yes. Perhaps not immediately, but yes. The idea being that once we have made > the transition if someone (including our own web pages) has that URL hard > coded somewhere they are going to land at our new and relevant Bylaws. > > > Please confirm my list: > > > > 1. Bylaws > > 2. Membership Agreement > > 3. Affiliates Membership Guidelines > > 4. Intellectual Property Policy > > 5. Antitrust Policy > > It's actually only #1 and #2. > > #3 should not be on that list. Actually, it would by my preference if the > link to those affiliate guidelines was moved down on that page to be > included in the list of all of those policies below. > > #4,5 are actually going to be word-for-word identical between the EF-US and > EF-BE. So they will be maintained as the same document. So they will have > the same URLs. > > HTH Thanks Mike, I did a prototype for the /org/documents page while you were in the middle of replying to me. I will adjust tomorrow but for now this is my first pass at this: https://staging.eclipse.org/org/documents/ username: testuser password: plaintext There is a few issues with some of these links and that's expected. For example, DOWNLOAD those not make sense for a link to an HTML page. The goal of my prototype is for us to agree on a look and feel. I will clean this up once we agree on a way forward. I will put on my rusty designer hat on and explain why I decided to go with a table :) I decided to use a <table> in my mockup because I wanted to create something that allowed our users to quickly understand which document is shared across foundation (big orange button) and which are not(ef-us/ef-be). I also created some space between each document to make the page easier to read and consume. If we decide to move forward with this design, I would recommend that we also update the Eclipse Foundation Policies section so that we are consistent across this page. I like the look of the page design. It's well laid out and readable. I have lots of comments on the content, but will have to provide that later/separately. (Example: it's been a long time since the EPL was the license of *all* of our projects.) The URL naming convention was discussed today in a meeting. The idea, if approved would be to use "eclipse-foundation-aisbl" and "eclipse-foundation-inc" as a prefix for new documents. For example, for the bylaws document the filename would be: https://www.eclipse.org/org/documents/eclipse-foundation-aisbl-bylaws.pdf https://www.eclipse.org/org/documents/eclipse-foundation-inc-bylaws.pdf We also consider replacing "eclipse-foundation" with "eclipsefdn". My concern with this is that eclipsefdn is not really a term that people use to search for us on google. I think we would be better off using eclipse-foundation in regards to SEO. The benefit of using "eclipsefdn" is that it's shorter. The staging server was updated today to reflect the latest changes to the Eclipse Foundation Governance Documents page: https://staging.eclipse.org/org/documents/ username: testuser password: plaintext The links to the Membership Agreement and Bylaws don't work since we still need to upload these documents. Looks good. A few comments: - given the EPL links directly to a PDF, should be "Download" rather than "Read More". - Bylaws, Membership Agreement, and EFSP - each link give 404 (perhaps related to being on staging). Agree, looks good and much of an improvement from the page today! The URL linked for the Bylaws for AISBL hasn't been adjusted (but you probably know that). From a visual perspective, I find the Download and Read Me buttons large and the focus of the page (but that could be just me)... Regards, Sharon (In reply to Paul White from comment #16) > Looks good. A few comments: > - given the EPL links directly to a PDF, should be "Download" rather than > "Read More". You are right! I will make the change. On that note, Mike did propose that we should remove it from the page. Should we do that? > - Bylaws, Membership Agreement, and EFSP - each link give 404 (perhaps > related to being on staging). Bylaws & Membership Agreement are missing since I am still waiting for someone to post these new documents on this bug! EFSP will work on production. That page simply does not exist on our staging server at the moment. https://www.eclipse.org/projects/efsp/ (works) https://staging.eclipse.org/projects/efsp/ (does not) (In reply to Sharon Corbett from comment #17) > From a visual perspective, I find the Download and Read Me buttons large and > the focus of the page (but that could be just me)... The button width is responsive in order to make this looks nice and properly aligned. (In reply to Christopher Guindon from comment #18) > (In reply to Sharon Corbett from comment #17) > > > From a visual perspective, I find the Download and Read Me buttons large and > > the focus of the page (but that could be just me)... > > The button width is responsive in order to make this looks nice and properly > aligned. I pushed a new version a few seconds ago with smaller download/read more buttons. Should "Delaware incorporated" be hyphenated? i.e., "Delaware-incorporated" (In reply to Wayne Beaton from comment #20) > Should "Delaware incorporated" be hyphenated? > > i.e., "Delaware-incorporated" No. (In reply to Christopher Guindon from comment #18) > (In reply to Paul White from comment #16) > > Looks good. A few comments: > > - given the EPL links directly to a PDF, should be "Download" rather than > > "Read More". > > You are right! I will make the change. On that note, Mike did propose that > we should remove it from the page. Should we do that? Yes. Please delete the reference/row for the EPL from this page. Thanks. (In reply to Mike Milinkovich from comment #22) > (In reply to Christopher Guindon from comment #18) > > (In reply to Paul White from comment #16) > > > Looks good. A few comments: > > > - given the EPL links directly to a PDF, should be "Download" rather than > > > "Read More". > > > > You are right! I will make the change. On that note, Mike did propose that > > we should remove it from the page. Should we do that? > > Yes. Please delete the reference/row for the EPL from this page. Thanks. Done! The change should be on staging in about 5min. Personally, I do not think *any* of the links should say/do "Download". They should all be "Read More". We've never required a download for people to read our Bylaws or membership agreement before. They should be able to just click to see the PDF. (In reply to Mike Milinkovich from comment #24) > Personally, I do not think *any* of the links should say/do "Download". They > should all be "Read More". We've never required a download for people to > read our Bylaws or membership agreement before. They should be able to just > click to see the PDF. I can definitely change the default. I was simply marking the distinction between an HTML page and a file (pdf). Howerver, it is true that the default behavior for all modern browser is to simply render the pdf in the browser. I will make that text change now. *** Bug 566457 has been marked as a duplicate of this bug. *** We need to publish our new Membership Agreement tomorrow on the website. Here's my plan: I will update my patch to remove the text for the bylaws and membership agreement that says: The XYZ for our Delaware incorporated US organization can be found HERE. This will allow us to push our new design to production tomorrow and allow us to make incremental changes to the page such as adding the Belgiums documents on October 20. With my update, I plan on updating/replacing https://www.eclipse.org/org/documents/eclipse_membership_agreement.pdf with the newest version for our US entity. We currently have a lot of redirects to this file, it's important that we keep this URL alive. I am not using our new naming convention now since I think we should setup the redirects with webmaster on October 20 once we are ready to go live with the Membership Agreement and Bylaws for EF Belgium. Does this sounds like a good plan? Any suggestions? My previous proposal is now on staging: https://staging.eclipse.org/org/documents/ Please review since the plan is to push this page as-is to production tomorrow! Hello, I made the changes according to the doc (https://docs.google.com/document/d/1MLOqhgBcrDBYPk3BiJYC9573-15P8qaBHr27aTuMK-8/edit?ts=5f747dc4#) , and I update them on staging, please check and let me know if there are more changes needed. https://staging.eclipse.org/membership/ user: testuser pass: plaintext Thanks! Yi (In reply to Yi Liu from comment #29) > Hello, > I made the changes according to the doc > (https://docs.google.com/document/d/1MLOqhgBcrDBYPk3BiJYC9573- > 15P8qaBHr27aTuMK-8/edit?ts=5f747dc4#) , > and I update them on staging, please check and let me know if there are more > changes needed. > > https://staging.eclipse.org/membership/ > user: testuser > pass: plaintext Thanks for these changes! We should discuss your updates on https://bugs.eclipse.org/bugs/show_bug.cgi?id=566459 I would like to keep the focus on the /org/documents page for this issue. Created attachment 284342 [details]
Membership Agreement Eclipse Foundation Inc. Version 6.0 Oct 1/2020
(In reply to Sharon Corbett from comment #31) > Created attachment 284342 [details] > Membership Agreement Eclipse Foundation Inc. Version 6.0 Oct 1/2020 Chris; As per our discussion on the call today, please use this PDF for the Eclipse Foundation Inc. Membership Agreement (Version 6.0) effective Oct. 1/2020. Thanks, Sharon (In reply to Sharon Corbett from comment #32) > (In reply to Sharon Corbett from comment #31) > > Created attachment 284342 [details] > > Membership Agreement Eclipse Foundation Inc. Version 6.0 Oct 1/2020 > > Chris; As per our discussion on the call today, please use this PDF for the > Eclipse Foundation Inc. Membership Agreement (Version 6.0) effective Oct. > 1/2020. > I made the change, staging should serve the new document shortly. Created attachment 284344 [details]
Eclipse Foundation Inc. Bylaws Version 4.0 Oct 1/20
I've attached the Eclipse Foundation Inc. Bylaws Version 4.0 (effective Oct 1/20) as well. Please push prime time. Thanks, Sharon These changes are ready to go. Thanks to all involved. Chris: We have uncovered a new requirement with respect to the AISBL Bylaws. There is a requirement to provide the AISBL Bylaws in two languages; namely French and English. Mike is not opinionated on how you implement this; we defer to your knowledge and judgement. It is noteworthy that French is one of the official languages of Belgium amongst Dutch and German. Thanks, Sharon One additional point: Our Bylaws need to be available in French. In fact, it is the French version which are our official Bylaws, as French is one of the two official languages of Belgium. However, it is only the Bylaws which have this bilingual requirement. All of our other documents (policies, membership agreement, etc.) can be in English only. (In reply to Mike Milinkovich from comment #38) > One additional point: Our Bylaws need to be available in French. In fact, it > is the French version which are our official Bylaws, as French is one of the > two official languages of Belgium. However, it is only the Bylaws which have > this bilingual requirement. All of our other documents (policies, membership > agreement, etc.) can be in English only. I am thinking that we need to add a bit of text to explain this. People will expect to download the Eclipse version if they click on the orange button. Maybe something like this: The Bylaws lay out the basic rules of governance of the Eclipse Foundation. The official version of our Bylaws is in French but an English version is available here. The Bylaws of our Delaware incorporated US organization can be found <a href="eclipse-foundation-inc-bylaws.pdf">here</a>. I will push this up as a starting point. New Gerrit change created: https://git.eclipse.org/r/c/www.eclipse.org/org/+/170848 (In reply to Christopher Guindon from comment #39) > (In reply to Mike Milinkovich from comment #38) > > One additional point: Our Bylaws need to be available in French. In fact, it > > is the French version which are our official Bylaws, as French is one of the > > two official languages of Belgium. However, it is only the Bylaws which have > > this bilingual requirement. All of our other documents (policies, membership > > agreement, etc.) can be in English only. > > I am thinking that we need to add a bit of text to explain this. People will > expect to download the Eclipse version if they click on the orange button. > > Maybe something like this: > > The Bylaws lay out the basic rules of governance of the Eclipse Foundation. > The official version of our Bylaws is in French but an English version is > available here. > > The Bylaws of our Delaware incorporated US organization can be found <a > href="eclipse-foundation-inc-bylaws.pdf">here</a>. > > I will push this up as a starting point. This is now on staging: https://staging.eclipse.org/org/documents/ u: testuser p: plaintext Please discuss! I made an update today to include the text changed that was discussed last week in a meeting with Sharon and Mike. https://staging.eclipse.org/org/documents/ u: testuser p: plaintext I do understand that the default behavior for most browsers is to render a pdf in a browser but I would say "Telecharger / Download" when we are linking to a PDF instead of "Lire la suite" / "Read more". However, I defer to the team on the correct text to use here. Please note that you are expected to see a 404 when clicking on any of the bylaws and membership document links. I will work with our webmaster in order to define the proper redirects but only once this page is approved. Please discuss! We could say English / Français instead of Lire la suite / Read more. (In reply to Christopher Guindon from comment #43) > We could say English / Français instead of Lire la suite / Read more. +1 Chris for this option as we just worked through in our discussion via the call with Mike moments ago... Thanks, Sharon (In reply to Sharon Corbett from comment #44) > (In reply to Christopher Guindon from comment #43) > > We could say English / Français instead of Lire la suite / Read more. > > +1 Chris for this option as we just worked through in our discussion via the > call with Mike moments ago... > > Thanks, > Sharon +1 I already made the change to staging: https://staging.eclipse.org/org/documents/ u: testuser p: plaintext Please confirm that all is well! Hi Chris: We would like to use the following URLs for the AISBL Bylaws: https://staging.eclipse.org/org/documents/eclipse-foundation-be-bylaws-fr.pdf https://staging.eclipse.org/org/documents/eclipse-foundation-be-bylaws-en.pdf Regarding the US Version either: https://staging.eclipse.org/org/documents/eclipse-foundation-us-bylaws.pdf OR https://staging.eclipse.org/org/documents/eclipse-foundation-us-bylaws-en.pdf I'm inclined to drop the "en" because there is only version. Mike is happy with either of these so its your call :-) Perhaps go with industry standard on this. Apologies in advance if this is a change we had agreed upon before...new year, fresh eyes and all that! Thanks as usual, Sharon Hi Chris: Looking at Staging, can we tighten up the space slightly between the English and French buttons. In my browser, the French one looks like its almost the link to the US Bylaws... Thanks, Sharon (In reply to Sharon Corbett from comment #47) > Hi Chris: > > Looking at Staging, can we tighten up the space slightly between the English > and French buttons. In my browser, the French one looks like its almost the > link to the US Bylaws... > > Thanks, > Sharon Can you share a screenshot? I don't have that problem on my end. The buttons are on 2 different lines. (In reply to Christopher Guindon from comment #48) > (In reply to Sharon Corbett from comment #47) > > Hi Chris: > > > > Looking at Staging, can we tighten up the space slightly between the English > > and French buttons. In my browser, the French one looks like its almost the > > link to the US Bylaws... > > > > Thanks, > > Sharon > > Can you share a screenshot? I don't have that problem on my end. The buttons > are on 2 different lines. I could but I can't because its no longer on staging :-) They are on two lines for me also but the French button looks below the wording... This is now ready for review. All the changes, including request submitting to Infrazilla are now on staging. This includes all the required redirects: https://staging.eclipse.org/org/documents/ u: testuser p: plaintext New Bylaws URLs: https://staging.eclipse.org/org/documents/eclipse-foundation-be-bylaws-fr.pdf https://staging.eclipse.org/org/documents/eclipse-foundation-be-bylaws-en.pdf https://staging.eclipse.org/org/documents/eclipse-foundation-us-bylaws.pdf Bylaws Redirect to latest version: FROM: https://staging.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf TO: https://staging.eclipse.org/org/documents/eclipse-foundation-be-bylaws-en.pdf New Membership Agreement URL: https://staging.eclipse.org/org/documents/eclipse-foundation-membership-agreement.pdf https://staging.eclipse.org/org/documents/eclipse-foundation-us-membership-agreement.pdf Membership Agreement redirect to latest version: FROM: https://staging.eclipse.org/org/documents/eclipse_membership_agreement.pdf TO: https://staging.eclipse.org/org/documents/eclipse-foundation-membership-agreement.pdf To be noted, once live, the "staging." part of these urls will be replace with www. once live! Gerrit change https://git.eclipse.org/r/c/www.eclipse.org/org/+/170848 was merged to [master]. Commit: http://git.eclipse.org/c/www.eclipse.org/org.git/commit/?id=c555b300bcb2ddacc600b7d2d144f2493fbc55ef (In reply to Eclipse Genie from comment #51) > Gerrit change https://git.eclipse.org/r/c/www.eclipse.org/org/+/170848 was > merged to [master]. > Commit: > http://git.eclipse.org/c/www.eclipse.org/org.git/commit/ > ?id=c555b300bcb2ddacc600b7d2d144f2493fbc55ef Done! Thanks all! |