| Re: [jakarta.ee-community] Guide to Contributing to Jakarta EE 10 |
No doubt there are many possible interpretations and nuances but as I said, I would like to see if it is reasonable to stick to a simple one. This one seems rather simple and sensible to me: https://www.agilejava.eu/2020/01/30/contributing-to-jakarta-ee/.
"You can now start contributing by submitting Pull Requests to the projects you are interested in, including Jakarta EE specification projects. It doesn’t cost anything. No signatures from your employer are necessary. Just the ECA. The only thing you need in order to contribute to Jakarta EE specifications is a signed ECA!"
If it is best to stick to the verbiage close to the one quoted above, I think that is a fine outcome.
That said, the reason for double checking is to understand what the right folks in the Eclipse Foundation that have to manage all this really think. To state the obvious, employer permission is a big deal for many people - even if it is informal, verbal permission that the Eclipse Foundation does not actually verify/track through signed paperwork.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual
community member and do not reflect the views of my employer.
Then probably make sure you work for an employer that doesn't ;-)
Especially the ECA as the smallest agreement is more simple than e.g. the ICLA at Apache (there is no difference between Committer or Contributor Agreement at Apache) which also states4. You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to the Foundation, or that your employer has executed a separate Corporate CLA with the Foundation.
So if you are employed you have to sign the corporate CLA https://www.apache.org/licenses/cla-corporate.pdf and if you change employer or your employer changes his mind then you're stuck in a lot more paperwork with the Apache agreement or at least the situation is very similar.
Werner
On Tue, Jul 14, 2020 at 7:24 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:
Reza,
long story short: Yes.
But reality is more complex: It is the *EF* that wants some paperwork, but
it is a different story what *you* want to hold in hands for the times when
your employer changes his mind.
The ECA (i. e. the smalles possible paperwork for CONTRIBUTOS) is found
here: https://www.eclipse.org/legal/ECA.php, quote: "By making a
contribution to this project, I certify that the contribution was created in
whole or in part by me and I have the right to submit it under the open
source license indicated in the file or". This means, you don't need to have
your employer sign anything as the EF trusts you that your employer *would*
agree that you submissions may be open sourced *if* he would be asked. But
still, you *should* ask him before you sign that line.
The full COMMITER paperwork concept is outlined in
https://www.eclipse.org/projects/handbook/#contributing-committers, quote:
"When a contributor becomes a committer, they must be covered by a committer
agreement (either a Member Committer and Contributor Agreement (MCCA) or an
Individual Committer Agreement (ICA). Committers on specification projects
must be covered by additional agreements. As the last step in the committer
election process, the Eclipse Foundation systems will determine which
agreement applies and engage a committer paperwork workflow with the new
committer to ensure that everything is in place.".
-Markus
-----Ursprüngliche Nachricht-----
Von: jakarta.ee-community-bounces@xxxxxxxxxxx
[mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] Im Auftrag von Reza Rahman
Gesendet: Dienstag, 14. Juli 2020 03:49
An: Jakarta EE community discussions; Jakarta EE Ambassadors
Betreff: Re: [jakarta.ee-community] Guide to Contributing to Jakarta EE 10
I have one more issue in this context I would like to clarify once again
(the reason is that there seems to be various contradictory ideas on
this topic from people with perhaps different perspectives).
My understanding is that becoming a contributor has a lot lower
paperwork bar than being a committer. In general for a contributor it
appears to be sufficient to just sign the ECA - which in general does
not seem to require any kind of paperwork from an employer. On the other
hand, becoming a committer seems to in most/some cases require some kind
of employer involvement even if effectively signing an "IP waiver" for a
given employee contributing on their own time. Is this a good layman's
view of things? Can the right folks (Wayne, Mike, Tanja, Ivar, etc)
please clarify? I know there are corner cases, but is this a fair
characterization for most people that will likely contribute using the
guide (non-vendors, people that probably don't work for member
companies, contributing individually). Can things be stated in an even
simpler way?
Again, the objective here is to make the on-ramp for new contributors
(that may one day become committers, but probably not) as friendly,
simple and enticing as possible. Having something akin to a verbal logic
diagram that attempts to cover every corner case is virtually guaranteed
to confuse and put off people...
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community
member and do not reflect the views of my employer.
P.S.: I really thought we did this once for the Jakarta EE 9
contribution guide already, but I guess not given the ongoing confusion
going in various directions.
On 7/11/2020 11:53 PM, Reza Rahman wrote:
> The first draft is now complete, could folks kindly take a look:
>
https://docs.google.com/document/d/1uZFBoIujXCc-gQhCzh_ZdlKEsrsV0yVVIHzBTI3u
sF8/edit?usp=sharing?
>
> Obviously there are a lot of possible things across the platform and
> ecosystem, but I do believe it is best to focus on a simple, brief,
> end-user focused and mostly self-contained resource (to be ultimately
> part of the Jakarta EE Ambassadors website).
>
> If possible, I would like to finalize this by next weekend.
>
> Reza Rahman
> Jakarta EE Ambassador, Author, Blogger, Speaker
>
> Please note views expressed here are my own as an individual community
> member and do not reflect the views of my employer.
>
> On 7/5/2020 11:16 PM, Reza Rahman wrote:
>> Just a quick heads up that as promised I started drafting the guide
>> this weekend:
>>
https://docs.google.com/document/d/1uZFBoIujXCc-gQhCzh_ZdlKEsrsV0yVVIHzBTI3u
sF8/edit?usp=sharing.
>> I was planning to get a draft done by today but holiday family
>> obligations got in the way.
>>
>> I hope to get it ready for review by next weekend.
>>
>> Reza Rahman
>> Jakarta EE Ambassador, Author, Blogger, Speaker
>>
>> Please note views expressed here are my own as an individual
>> community member and do not reflect the views of my employer.
>>
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________ jakarta.ee-community mailing list jakarta.ee-community@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community