-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call for reviewers group and new co-reviewing workflow #656
Comments
@jywarren I have fulfilled all the conditions as mentioned to join this wonderful team . |
@jywarren Checked the prerequisite checkboxes here as well. Having a lot of fun with Image Sequencer, would absolutely love to be a part of the co-reviewing group! |
@jywarren I would love to be in this team, have checked all the conditions. Thanks! 😄 |
Thank you all! I've added you four. 🎉 Awesome! |
I'd like to also note that reviewers, like any community member, have a responsibility to support and uphold our code of conduct! This is part of what makes our community a respectful and fulfilling place. Please give it a careful read! http://publiclab.org/conduct 🎉 |
I would have liked to join this too but I will be super busy for the next 2 years and won't be able to do anything. Can I still join and be redundant for 2 years? |
I think that's fine, @harshkhandeparkar! I'll add you too --have you also completed the prerequisites? Thank you! |
@jywarren I'd like to be in this team, too. Can I join? |
It's really nice to see our community grow here, our efforts definitely paid off! 🎉❤️ |
Yes I have completed the prerequisites. Thanks! |
Adding @harshkhandeparkar. I believe @rexagod has completed these although for other Public Lab projects in some cases, but they are similarly structured JS libs. So I think it translates pretty well! Adding you both. Thanks! If folks can explicitly click "Approve" on PRs that would be great. If you need reviews, please use the |
I can be a reviewer, @jywarren! :) |
Thanks, @milaaraujo ! I'll add you to the matching |
Can I be the part of the reviewers team. |
You need to have one more merged PR, review one PR to completion and open an FTO in this repo. |
Hello |
@gauravano can you check it out now!! |
Please paste the links. Thanks! |
Harshith, are you well acquainted with the codebase? Will you be able to help other contributors if needed? |
@harshkhandeparkar yeah i will help other contributors. |
Added you to the @publiclab/is-reviewers @harshithpabbati 🎉 Thank you! |
@jywarren @gauravano can i be a reviewer ? ( A member of publiclab/is-reviewers) |
@subhahu123 I have deleted your comments in the other pr. |
Hi @subahu123, I can't see your issues and PRs from https://github.com/publiclab/image-sequencer/issues/. Could you please list them below? Thanks! |
@jywarren I want to join into the maintainers team. How can I do that ??? Are there any prerequisites to complete??? |
Hi Harshith - i'm trying to go through all the SoC and Outreachy proposals
now, so i'm sorry to ask but could you copy in my comment from your PR
where I mentioned some next steps to formalize the process a bit? Thank you
so much and I'm so grateful for your interest in helping maintain the
project!!!
…On Mon, Apr 1, 2019 at 2:49 PM Harshith pabbati ***@***.***> wrote:
@jywarren <https://github.com/jywarren> I want to join into the
maintainers team. How can I do that ??? Are there any prerequisites to
complete???
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#656 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJyWtES42eCVpFUfQJKlUO8nZrtT_ks5vclSygaJpZM4Z77JG>
.
|
Hi @jywarren ! |
Hi! Thank you, can you link to your PRs and issues as above? Thanks, and awesome!! |
Fantastic, thank you! Adding you now. |
Great, adding you! Thank you! |
Fixes #173 (😆 🎉)
One year ago, I posted #173 - Building out a contributor community for Image Sequencer, and talked a lot with @tech4GT about how to do this. As you can now see, with your help, we now have a lively community around this library!
Community growth
Check out some of these pages to see how many people have helped build Image Sequencer, since @ccpandhare and I started the project ~3 years ago:
43 people have now committed code to the project, and even more have participated! 😄 🎉
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:
ready-to-merge
label, once ready for final review by someone with merge permissions (currently @tech4GT and I, although we are interested in expanding this group soon)This doesn't mean that we should stop helping each other solve problems even if we're not in the reviewers group -- i'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/is-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:
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/is-reviewers.
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 corner of the Public Lab coding community a warm, welcoming, and wonderful place!!! ⚡️ 🙌 👍 🎉 🎉 🎉
@aashna27 @harshkhandeparkar @Divy123 @sashadev-sky @MargaretAN9 @ROODAY @VibhorCodecianGupta @Mridul97 @KusioDev @okonek @JonathanXu1 @Rishabh570 @bhavayAnand9 @oorjitchowdhary @roshniRam @publiclab/reviewers @publiclab/image-sequencer-guides @Ankit-Singla @rexagod
The text was updated successfully, but these errors were encountered: