Hi Aislan,
Fully agree with
your assessment. I don't think Markus is arguing against the policy
of having a CONTRIBUTING file. That is still a requirement of every
Project within the Eclipse Foundation. Markus is questioning why
this latest "non-assert" update needed to be in the CONTRIBUTING
file instead of just becoming part of the ECA. Ivar is following
up on that question. Hope this helps.
---------------------------------------------------
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:
Aislan
Nadrowski <aislan.nadrowski@xxxxxxxxx>
To:
EE4J
PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Date:
05/08/2020
06:21
Subject:
[EXTERNAL]
Re: [ee4j-pmc] CONTRIBUTING Issue coming your way...
Sent
by: ee4j-pmc-bounces@xxxxxxxxxxx
Hi
Markus/All,
IMHO
it is nice that the projects have a Contributing.md file, because it helps
mainly beginners to contribute. Sometimes, when you are a beginner and
you are not a native English speaker you look for some standard things
like a Contributing.md file. Also, when you do not speak English well is
not easy to understand what the ECA is.
On Fri, May 8, 2020 at 1:40 AM Ivar Grimstad
<ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
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!
---------------------------------------------------
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_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--
Ivar
Grimstad
Jakarta
EE Developer Advocate | Eclipse
Foundation, Inc.
Community.
Code. Collaboration.
Join
us at our virtual event: EclipseCon
2020- October 20-22_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc