Hi Etienne,
What about the contribution guide ? I think it's covered in the IntelliJ and
Eclipse setup sections.
Regards
JB
On 04/24/2017 02:12 PM, Etienne Chauchot wrote:
Hi all,
I definitely agree with everything that is said in this thread.
I might suggest another good to have:
to ease the work of a new contributor, it would be nice to have some sort of
programming guide but not oriented to pipeline writers but to sdk/runner/io/...
writers.
I know that new contributors have the docs available in the google drive, the
ML, the code base, and the availability of beamers, but maybe having key points
in a common place (like FAQ for sdk/runner/io/... writers, for example) would be
interesting.
Best,
Etienne
Le 24/04/2017 à 09:14, Jean-Baptiste Onofré a écrit :
Hi,
I think we already tag the newbie jira ("low hanging fruit" ;)).
Good idea for domain of interest/concept.
Regards
JB
On 04/24/2017 09:01 AM, Ankur Chauhan wrote:
Might I suggest adding tags to projects based on area of intetest, concept
and if it's a good "first bug".
Sent from my iPhone
On Apr 23, 2017, at 23:03, Davor Bonaci <da...@apache.org> wrote:
1. Have people unassign themselves from issues they're not actively
working on.
2. Have the community engage more in triage, improving tickets
descriptions and raising concerns.
3. Clean house - apply (2) to currently open issues (over 800). Perhaps
some can be closed.
+1 on all three of these, and will do my part shortly!
Also, it is worth noting that we have improved as a project in tracking
issues in the last 1-2 months. There are more resolved issues than opened
in this period, whereas in the past we'd have a hundred more opened than
resolved.
I would also propose to not assign new Jira automatically: now, the Jira is
automatically assigned to the Jira component leader.
Imagine a user discovering an issue and filing a new JIRA issue. It
wouldn't be assigned to anyone, significantly reducing the chance somebody
will actually help.
Of course, somebody could search for new issues periodically, etc. -- but
that just won't happen. The final outcome would be -- instead of a lot of
issues assigned to component leads, we'd have (much) more unassigned
issues, which were *never* looked at. Assigning an issue just sets a
community expectation that a committer should look -- and it does help move
things along!
I think a better approach of addressing the current state would be increase
the number of components / component leads. With more people involved and
lower per-person load, I think we'd be more effective.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
