You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m really glad improving the contributor (especially for new contributors) experience is a top priority in our 2019 community roadmap. Curious if there are any efforts post Q1 that we can define (ex “implement 2 tools that identify new contributors and expedite quick feedback” / “define and initiate a protocol for enabling fast feedback loops for contributor PRs”) that are targeted at the contributor experience. One way would be to open up a space to get feedback on painpoints and reach out to some current/lapsed contributors, and then do some initiatives Q2/3 to patch the most harmful bugs in our community protocols.
Similarly, putting together status updates and recognition for the community of engaged contributors who are pushing the project forward seems like it would fall in this team’s responsibilities, right?
The text was updated successfully, but these errors were encountered:
Ref https://github.com/ipfs/community/blob/master/ROADMAP.md
I’m really glad improving the contributor (especially for new contributors) experience is a top priority in our 2019 community roadmap. Curious if there are any efforts post Q1 that we can define (ex “implement 2 tools that identify new contributors and expedite quick feedback” / “define and initiate a protocol for enabling fast feedback loops for contributor PRs”) that are targeted at the contributor experience. One way would be to open up a space to get feedback on painpoints and reach out to some current/lapsed contributors, and then do some initiatives Q2/3 to patch the most harmful bugs in our community protocols.
Similarly, putting together status updates and recognition for the community of engaged contributors who are pushing the project forward seems like it would fall in this team’s responsibilities, right?
The text was updated successfully, but these errors were encountered: