|
There is no formality required in this project. You can pitch in at any time and help.
You can do the following:
- Create an issue in github and assign it to yourself
- or just drop a note in the mailing list and then create a PR
The Core spec document is converted to Jakarta and is available in master branch. This requires some more work for it to be ready for review for the 4.0 release.
You can go through the 4.0 release plan, create issues for each task and start a discussion thread and create PRs with the required changes.
Occasionally I drop a note in here on what I am currently doing and what needs to be done. The what needs to be done is always a future task that I have not started. You or anybody else can pick it up and assign it to yourself.
Thanks
Hussain
From: ejb-dev-bounces@xxxxxxxxxxx <ejb-dev-bounces@xxxxxxxxxxx> on behalf of Edwin Derks <ederks85@xxxxxxxxx>
Sent: Wednesday, May 6, 2020 01:13 PM
To: ejb developer discussions <ejb-dev@xxxxxxxxxxx>
Subject: Re: [ejb-dev] [jakartaee-spec-project-leads] CONTRIBUTING Issue coming your way...
Hi Hussain,
Thanks for getting back to me. I know how the process technically works so your summary is clear to me. However, if I just follow these steps, it would be the second time that I started work that is already being done by somebody else, while this is not
clear (for me) based on communication within the project.
I'm looking at how to "own" work for the ejb project, or any other project in ee4j for that matter, in order to not concurrently doing work that is going to be dismissed because somebody else is doing the same thing, but creates a PR earlier.
Maybe I'm doing something wrong or don't understand how this works, but then I'm also here to learn how to contribute. So any guidance you can offer would be greatly appreciated.
Edwin
Hi Edwin,
Contributing to the project is simple,
- You create a fork of the repository
- Clone your fork
- Create a branch from master (e.g., update-contributing)
- Make the required changes
- Make sure to commit with Signed-off-by footer (email should match with the one you have signed in the Eclipse Contributor Agreement)
- Create a pull request from the repository
- Describe the pull request and refer to the issue it fixes and submit it
Review, approval and merge will be done by Committers of the repository.
You can watch the repository to get notifications if new issues or pull requests are created.
Thanks
Hussain
[External]
Hi,
Never mind, I see it has already been done.
Edwin
Hi,
Please see Kevin Sutter's message below:
"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!"
I would like to do this task as an easy first step to actually get involved contributing to the project. What is the best way to do this, should I create a Github issue for this first?
Kind regards,
Edwin Derks
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original
message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law,
this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance
on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
_______________________________________________
ejb-dev mailing list
ejb-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ejb-dev
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original
message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law,
this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance
on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
|
