|Re: [jakarta.ee-community] Guide to Contributing to Jakarta EE 10|
Thanks Ivar for providing your perspective. For the purposes of the guide, it would be helpful to have a canonical way for folks to expect to engage.
Looping in the Jakarta EE Ambassadors Google Group as well. Would love to hear a few more opinions on this, especially from folks that would like to be more deeply engaged but are not today.
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.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Date: 7/13/20 1:21 AM (GMT-05:00)
To: Jakarta EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-community] Guide to Contributing to Jakarta EE 10
On Mon, Jul 13, 2020 at 2:11 AM reza_rahman <reza_rahman@xxxxxxxxx> wrote:
I think it is up to each project to choose how they communicate as long as it is inclusive and transparent.
My 2 cents on suggested guidelines:
- Project mailing lists should be the primary channel of communication.
- Decisions, voting and such should be done on the mailing lists
- Discussions on the mailing list could typically result in GitHub issues
- Hammering down the details of a particular issue is probably best to do by commenting on the issue directly
- Channels like Slack, Gitter, etc. are fine to use for sync ad-hoc discussions and clarifications.
- It could be a good practice to post the results of these discussions on the mailing list if relevant for the broader community
Back to the top