The handbook is not intended for contributors. It's meant as a resource for committers and project leads. I am, however, authoring a "how to contribute" section targeting contributors that I hope to have ready by the end of the quarter.
The ECA is the only paperwork that is required for contributors. We have workflows that take new committers through their paperwork process. I recommend that a getting started guide focus on contributors/ECA.
The CONTRIBUTING file in the repository root should provide at least basic information (e.g., ECA) for would-be contributors.
In slides, I outlined the steps for a Jakarta EE update session
last year, here
(Section that starts on slide 11). I also covered this very
briefly in my CodeOne session. GlassFish Contributing.md
contains some of this.
One concern is -- for someone just starting, we don't want to
make the "how to" look so arduous that everyone just walks away.
So, pointing immediately to the resources or project handbook is
probably not the best approach.
First things needed are: Eclipse
Account and/or a GitHub account. With these
two, you can get on the dev lists, create and comment on issues,
even track PRs and issues against repositories.
If you want to contribute, you need to sign the ECA and agree
to the DCA terms (on
the ECA form).
This is probably as far as most folks will need to go, in my
opinion.
Becoming a committer requires more work and possibly even
physical paperwork -- and you need nomination and a successful
election. But, that can be far down the road for someone just
starting out.
If anyone would like to consolidate this to a wiki, or project
page -- I'm certain it would be beneficial.
I'm not sold on which is better -- the Eclipse Wiki, or a web (or
wiki) page on GitHub.
-- Ed
On 1/22/2020 3:18 PM, Reza Rahman
wrote:
If you don't need paperwork in place
for this, this is something I would be happy to help with if it
helps accelerate matters. I can work with someone that has gone
through the paperwork process already (since I really haven't
and can't) or someone that knows the process well.
Also, I might have missed this, but
is there an initiative to document what is required in relative
generic terms to transition a given specification to Jakarta?
Reza Rahman
Jakarta EE Ambassador, Author, Speaker, Blogger
Please note views expressed here are my own as an individual
community member and do not reflect the views of my employer.
On 1/22/2020 5:59 PM, Kevin Sutter
wrote:
Hi fellow
PMC members, Do we have
a wiki or doc that explains the simple steps required to get
started with developing in EE4J (Jakarta EE)? Things like
establishing your Eclipse ID, accepting the ECA (personal or
corporate), associating your github id with your Eclipse
account, etc? I've been looking and can't find anything.
With all of the work that is required for Jakarta EE 9,
having something to point at for new people to get involved
might be helpful.
If we have
something, Great! I just need a pointer to it. If we don't
have it, where would the best location be for something like
this? The Eclipse Wiki isn't the friendliest, but it's
workable. Or, should we create a gihub page for it? At the
Platform? PMC? Thanks for any ideas or suggestions!
---------------------------------------------------
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
--
Reza Rahman
Principal Program Manager
Java on Azure
Please note that views here are my own as an individual community member and do not represent the views of my employer.