Bugzilla – Full Text Bug Listing
| Summary: | Add Individual WGPA Agreement to Committer Paperwork Documentation in accounts.eclipse.org | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Shawn Kilpatrick <shawn.kilpatrick> | ||||
| Component: | Accounts.eclipse.org | Assignee: | Eric Poirier <eric.poirier> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | chris.guindon, eric.poirier, sharon.corbett, wayne.beaton, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 10 | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 567720 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Shawn Kilpatrick
Hi Shawn, Is it correct for us to assume that this bug is for Jakarta EE and AsciiDoc only? We need to scope this since we need to create Hellosign templates for each one. Sharon did mention that this is something that you can do. Please let me know once these templates are created. I will then login to fetch the information that we need in order to automate this. We also need to standerzise on WGIPA vs IWGPA since it's confusing. Sharon and I have been using IWGPA but you are WGIPA, which one is correct? Finally, when should someone sign the Employer Consent form? Is it for committers who are employed by a member company that did not sign the WGPA? Shawn/Chris; Please refer to these documents as Individual Working Group Participation Agreements (IND WGPA). I've adjusted the Summary accordingly. Lets leave the Employer Consent Agreement for Spec Projects to a later date. The reason for this is that this needs more thoughtful consideration. Its not an individual who signs this but their employer and when it is returned, it is filed specifically to reflect the consent for the related spec project eg; Employer Consent Agreement - Jakarta EE. The Employer Consent Agreement for Spec Projects (Not to be confused with old Employer Consent Agreements) is included in the IND WGPA as a URL and there are instructions on what needs to happen. Therefore, the individual will pass this PDF along to their employer outside of Hello Sigh. Clunky but that's fine for now. To that end... Shawn: Can you please create templates for the following Individual WGPA's we currently have: WGPA - IND-AsciiDoc https://www.eclipse.org/org/workinggroups/wpga/asciidoc-individual-participation-agreement.pdf WGPA - IND-Jakarta EE https://www.eclipse.org/org/workinggroups/wpga/jakarta_ee_individual_working_group_participation_agreement.pdf WGPA - IND-MicroProfile https://www.eclipse.org/org/workinggroups/wpga/microprofile-working-group-participation-agreement-individual.pdf All: Please note these agreements will be updated soon to AISBL versions. As a result, they will have to be templated again in the near future. However, I understand this is not a large amount of effort and I'd like to get this in place as soon as possible to avoid provisioning a committer to a spec project with only an ICA. This also means each time a new spec project is created, a new hello sign template will need to be created for the relevant IND WGPA for that spec and it will then need to be tied into the provisioning component for that spec project as WPGA's generally are tied to the related working group... Please let me know if there are any other questions. I hope this makes sense. Happy to jump on a call to clarify further. Regards, Sharon Created attachment 284457 [details]
Specification project paperwork requirements flow chart
Presented in all of its glory, here's the decision flow that sorts out what documents we require from a user.
(In reply to Wayne Beaton from comment #3) > Created attachment 284457 [details] > Specification project paperwork requirements flow chart > > Presented in all of its glory, here's the decision flow that sorts out what > documents we require from a user. Thanks Wayne. > Presented in all of its glory, here's the decision flow that sorts out what
> documents we require from a user.
Just to make sure that this detail doesn't get lost over time... this flow starts from an assumption that an individual has been elected to a *specification* project. The existing workflow for regular old Eclipse open source software projects (ROEOSS) remains unchanged.
Let's never use the ROEOSS acronym.
My changes are now live on production. It is now possible to create IWGPA documents for Microprofile, AsciiDoc and Jakarta EE. Please reopen this bug if there's any issues created the following documents. Thanks. (In reply to Eric Poirier from comment #6) > My changes are now live on production. > > It is now possible to create IWGPA documents for Microprofile, AsciiDoc and > Jakarta EE. > > Please reopen this bug if there's any issues created the following documents. > > Thanks. Did Shawn confirm that all is well before closing this bug? (In reply to Christopher Guindon from comment #7) > (In reply to Eric Poirier from comment #6) > > My changes are now live on production. > > > > It is now possible to create IWGPA documents for Microprofile, AsciiDoc and > > Jakarta EE. > > > > Please reopen this bug if there's any issues created the following documents. > > > > Thanks. > > Did Shawn confirm that all is well before closing this bug? He does not have any documents to review at the moment. He will reach out to me whether or not the changes are working when he does have documents to review. In case there is something wrong, I will reopen this bug or create a new one. |