[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-pmc] CONTRIBUTING Issue coming your way...
|
On 2020-05-11 12:41 p.m., Markus KARG
wrote:
Hello
EMO,
can
you plese provide a longer, more precise answer please?\
Markus,
Please refer to my additional response posted today at 11:28am
EDT. Thanks.
In
particular I do not see how a CONTRIBUTING.md could be
legally binding, why it is impractical to change the ECA,
and why not all projects need this but just the Jakarta
projects.
Thanks
-Markus
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.
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
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.
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?
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!
