| Re: [ee4j-pmc] CONTRIBUTING Issue coming your way... |
I would add the following: The reason why we didn't want to add this to the ECA is because this text only really applies to specification projects hosted at GitHub, not all EF open source projects generally. Invalidating everyone's ECA's yet again for something which is basically a Jakarta-EE-specific issue didn't seem to make sense on a community-wide perspective.Hi,
The short answer to why this information is added to the CONTRIBUTING.md rather than the ECA is for practical reasons. Adding it to the ECA would require board approval and it would affect projects where it is not necessarily needed.For a longer, more precise answer, please contact the EMO.
HTH
Ivar
On Sun, May 10, 2020 at 3:39 AM Aislan Nadrowski <aislan.nadrowski@xxxxxxxxx> wrote:
Markus :)
Em sáb, 9 de mai de 2020 04:54, Markus KARG <markus@xxxxxxxxxxxxxxx> escreveu:
Thanks for clarifying this. I understand the common benefit of a CONTRIBUTING file in general, but as always, I'd like to know the legal reason for each "MUST" anybody imposes on a subproject. :-)
-Markus
Von: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] Im Auftrag von Ivar Grimstad
Gesendet: Freitag, 8. Mai 2020 06:40
An: EE4J PMC Discussions
Betreff: Re: [ee4j-pmc] CONTRIBUTING Issue coming your way...
Hi Markus,
That's a good point. I don't know actually. I'll check with Wayne. There is p robably a good reason for it.
Ivar
On Thu, May 7, 2020 at 9:41 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
I wonder why this has to be added to the Contributing.md file of all projects: Shouldn't this simply be part of the ECA?
Von: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] Im Auftrag von Kevin Sutter
Gesendet: Mittwoch, 6. Mai 2020 23:09
An: EE4J PMC Discussions
Betreff: Re: [ee4j-pmc] CONTRIBUTING Issue coming your way...
For completeness, we also have this document which is the approved proposal which precipitated the non-assert amendment to the CONTRIBUTING docs..
https://docs.google.com/document/d/1VMXVzdfBflKfhW0rmTJXI2sRAdECaVTXnElZ_RSrUME/edit#heading=h.5ku0nbahp5wg(everyone should have read access via this link...)
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: "Kevin Sutter" <sutter@xxxxxxxxxx>
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Date: 05/06/2020 13:41
Subject: [EXTERNAL] Re: [ee4j-pmc] CONTRIBUTING Issue coming your way...
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
Hi Markus,
This item was initially discussed at the Jakarta EE Steering Committee on March 24 (search for "non assert"):
https://jakarta.ee/meeting_minutes/steering_committee/minutes-march-24-2020.pdf
Once the wording was properly reviewed and approved, then it was sent to the PMC for their "approval" and action. I (as a member of the PMC) volunteered to communicate this need to the Project Leads via Issues for easy tracking. Hope that's sufficient. If you need more justification, I would suggest contacting the Eclipse EMO. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
To: "'EE4J PMC Discussions'" <ee4j-pmc@xxxxxxxxxxx>
Date: 05/06/2020 12:39
Subject: [EXTERNAL] Re: [ee4j-pmc] CONTRIBUTING Issue coming your way...
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
It would be fine if the PMC could also tell us the reason WHY all projects MUST add that text. :-)
-Markus
Von:ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] Im Auftrag von Kevin Sutter
Gesendet: Dienstag, 5. Mai 2020 23:36
An: JakartaEE Spec Project Leadership discussions
Cc: EE4J PMC Discussions
Betreff: [ee4j-pmc] CONTRIBUTING Issue coming your way...
Hi,
Just a heads up that I will be creating (on behalf of the PMC) an Issue against each Specification Project to update/create a CONTRIBUTING file in each of your respective specification-related github repos. We need this update for all of our Specification Projects. The Issue description will have the detail that needs to be specified. We're asking you to do this at your earliest convenience. This would actually be an easy "first issue" for anybody that is looking to get started on a project...
Thanks!