Call for Reviewers 🎉

[grvsachdeva]

Hi everyone, our community is growing fast 🚀 ⚡. Thanks to the number of contributions each one of you has made. With the growth of new contributors to the Mapknitter and so many new and exciting projects, we want your help with reviewing and so we invite people to step up and volunteer to be the part of reviewers group 😃. Also, we are preparing the software community roadmap at https://publiclab.org/notes/warren/05-22-2019/draft-of-a-public-lab-software-roadmap-comments-welcome so comments and suggestions are welcome!!

Community growth

This is especially important as our community around Mapknitter has grown so much in the past few months!

Check out some of these pages to see how many people have helped build mapknitter, since we really started doing welcoming and outreach:

• Community Toolbox: https://code.publiclab.org/#r=mapknitter
• GitHub Pulse: https://github.com/publiclab/mapknitter/pulse/monthly
• Contributors graphs: https://github.com/publiclab/mapknitter/graphs/contributors

What's next: co-review workflow

To build on this community strength 🤝, we'd like to ask for people to sign up as reviewers, to help get pull requests ready for merging. In the new workflow, we'd like each PR to have:

• ✅ 2 reviews by people from the @publiclab/mapknitter-reviewers group
• ✅ a ready label, once ready for final review by someone with merge permissions (@jywarren)
• ✅ tests if possible (not mandatory but preferred) with each PR - although for first-timers this is less critical.

This doesn't mean that we should stop helping each other solve problems even if we're not in the reviewers' group -- We've seen a lot of great welcoming and cooperation! But at least we'll be able to get things ready and merged faster. 👍 🙌

Reviewers team

So, this new @publiclab/mapknitter-reviewers team -- we'd like to ask folks to join it if you're interested! Many of you already play this role -- THANK YOU! 🎉 We'd like folks to consider, as a prerequisite to joining:

• ✅ having 2 PRs merged
• ✅ having helped someone else troubleshoot a PR or issue
• ✅ having made a first-timers-only issue and welcomed in a new person to make their own first contribution (this is how our community grows!)

If you've completed these, please ask here and we'll be sure to add you the new reviewers' group. You'll get notifications when people request a review from you, or mention @publiclab/mapknitter-reviewers.

Also, we welcome reviews by folks not in the reviewers' group, of course! This will be a group to help coordinate co-reviews, but it's not meant to be exclusive. And we encourage people to join!

Managing too many emails!

Just a note - your inbox can become quite a mess as the community grows! Consider turning off notifications for /every event/ and just listening to if you're mentioned! 📬

THANK YOU for making this part of the Public Lab coding community a warm, welcoming, and wonderful place!!! ⚡️ 🙌 👍 🎉 🎉 🎉

[jywarren]

@publiclab/mapknitter-reviewers how do we feel about the above "policy" of 2+ approving reviews, with tests preferred, and using this policy to expand the group with merge privileges?

[cesswairimu]

Sounds good to me

[kaustubh-nair]

@publiclab/mapknitter-reviewers how do we feel about the above "policy" of 2+ approving reviews, with tests preferred, and using this policy to expand the group with merge privileges?

Sounds like a good idea @jywarren

[sashadev-sky]

Hi I completed the tasks :)

1. FTO: Fix singularization case for "images" #636
2. PRs Merged: Create Status.json #483, Add remote_url to export model #552
3. Troubleshooting: Adding rubocop sample config #547

[sagarpreet-chadha]

I would also love to join this team as well :-)

[cesswairimu]

I guess we can keep this open a little longer for other folks who would like to join. Thanks

[jywarren]

Yes, good idea!

…

On Wed, Jun 19, 2019 at 6:28 AM Cess ***@***.***> wrote: I guess we can keep this open a little longer for other folks who would like to join. Thanks — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#634?email_source=notifications&email_token=AAAF6JYXZL7TVHF25SAROALP3ICZZA5CNFSM4HPT2NOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYBNRXQ#issuecomment-503503070>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J6NDZ33FUO473JNAWLP3ICZZANCNFSM4HPT2NOA> .