Re: [Hyperledger SIG Chairs] SIG Request for Support from Technical Community: Technical contributors
Thanks for bringing this up to everyone. I think #1, in particular, is a big issue. Most projects have their own specific PR requirements that can be difficult to get right on the first time. Maintainers also tend to respond to and deal with PRs from people that they know more quickly, and PRs from unknown contributors that are useful but maybe do a couple of things wrong because the contributors are new can get "black holed." I guess this plays into #3 as well.
Two things that I've recommended for these problems in some of the projects I've worked on are as follows:
I think these rules help reduce discouragement for new people trying PRs. I don't think we want to regulate things at a Hyperledger level, but I did want to share things that seem to work for projects that I work on/follow closely.
Thanks a lot for your time, and have a great day.
From: tsc@... <tsc@...> on behalf of Arun S M <arun.s.m.cse@...>
Sent: Saturday, February 6, 2021 5:20 AM
To: David Boswell <dboswell@...>
Cc: Tracy Kuhrt <tracy.a.kuhrt@...>; tsc@... <tsc@...>; SIG-Chairs@... <SIG-Chairs@...>
Subject: Re: [Hyperledger TSC] [Hyperledger SIG Chairs] SIG Request for Support from Technical Community: Technical contributors
Adding onto this discussion,
The entry barriers that I have found while asking the developer community to get involved are
1. First time contributors think that they need to spend a significant amount of time before making attempts to contribute. They are unsure of their code acceptance by a project.
2. Lack of awareness on available opportunities to get involved.
3. Number of reworks on a PR. due to lack of information on better practices followed at Hyperledger.
Building upon the idea of aggregating contribution opportunities at one place, and similar discussions I have had with another project in Hyperledger.
How about also categorizing those opportunities into different verticals?
- Documentation efforts for those who wish to help out there.
- Porting efforts, if somebody is new to a programming language or doesn't know about a project. Here are low hanging fruits/easy picks.
- Adding to the test coverage, implementing fully designed modules. For a slightly mature developer.
- A section for specific requirements. For example, call out need for help on expertise from verifiable credentials use cases, call out need to work on a setting up a test network, call out need to work on a backend. This way specific people interested in a domain can even subscribe to available opportunities.
- Influencing the roadmap of a project. This is where the passionate developers/organizations join by themselves.
Weekly dev letters can be used to publish a link to this page. Also, highlight new opportunities added upon here.
On Sat, Feb 6, 2021 at 4:19 AM David Boswell <dboswell@...> wrote: