IshaGupta18
commented
4 years ago Hey! Would love to be a mentor! I think i fulfill all the criterias, and I have a couple of ideas for Google Summer of Code for simple-data-grapher, maybe we could take that into account? Thanks a lot, can't wait for Summer of Code this year! On Mon, Jan 27, 2020, 11:03 PM Jeffrey Warren notifications@github.com wrote:
With Outreachy https://outreachy.org and Google Summer of Code http://summerofcode.withgoogle.com 2020 coming up, we're looking ahead to who may be interested in mentoring for these programs. We have participated in both during the past few years https://publiclab.org/notes/warren/08-21-2018/congratulations-on-a-great-2018-summer-of-code, and while we are not guaranteed spots, we are planning to apply as an organization.
Read some previous year's proposals here https://publiclab.org/tag/call-for-proposals, and participate in project idea brainstorming here. If one of the project ideas strikes your interest, please mention it!
We especially welcome people from groups underrepresented in free and open source software!
It's very important to us to have diverse representation in our mentor group just as in our participant group. And remember -- our community aspires to be a respectful place. Please read and abide by our Code of Conduct https://publiclab.org/conduct. To participate:
This year, we're asking that mentors have taken some of the following steps to be part of our community:
- Solve a first-timers issue https://code.publiclab.org#r=all. Provide the link to the first timer issue's pull request (PR) once it's merged. In case, you are not able to find any first-timer issue, solve issue marked as fto-candidate or support, these issues may require little more work, but we'll try to help.
- Solve a help-wanted issue https://github.com/publiclab/plots2/labels/help-wanted. Help wanted issues are issues which are not labelled as gci-candidate neither as fto-candidate nor as first-timer-only. Provide link to such issues' merged PR. (Make sure you claim the issue first by commenting on issue you are planning to solve)
- make a first-timers issue. Use the extra friendly template https://publiclab.org/n/13667 which we generally use for creating our first timer issues. Provide the link to the first timer issue which is created by you.
Mentors check in with a student at least once per week roughly from May-August, and offer some project management guidance and encouragement... while relying on the chatroom https://publiclab.org/chat and the @publiclab/reviewers https://github.com/orgs/publiclab/teams/reviewers group to provide code-specific input, so that we share the burden of specific technical support. We have weekly Check-Ins on GitHub (#4548 https://github.com/publiclab/plots2/issues/4548) as well, and mentors are expected (along with students!) to be in the rotation to post these occasionally.
Remember that to be a mentor you don't necessarily need to know how to code -- we also need mentors who know Public Lab's community and practices well, and who can encourage students to speak up when they get stuck, and to ask the community for input and testing of their work. Students often get stuck when they don't know how something should look, or how a feature might be used by the community -- contextual info! Priorities this year
This year we are aiming to bring some focus on high-priority projects to the program, and we’d like all mentors to help to encourage these new priorities. Some are highlighted in our ideas list https://publiclab.org/wiki/gsoc-ideas, which lists our top community projects. We’re much more likely to accept projects that source from this list, although we’re happy to provide input on other suggested ideas too!
Others are covered in our [ROADMAP]) https://publiclab.org/notes/warren/05-22-2019/draft-of-a-public-lab-software-roadmap-comments-welcome), which emphasizes code stability, testing, maintainability, and reducing technical debt.
However, it does note that new projects can be developed in a “satellite” format, where they first achieve stability as separate repositories, before being proved out and integrated into PublicLab.org. With lots of people proposing React projects last year (for example), we really want to see such a project developed separately with a limited scope (like, just the commenting system, or just the dashboard), and proved out before being considered for integration.
Finally, we have a new Style Guide this year, which we are strongly encouraging people to read carefully before proposing design changes or refinements: https://publiclab.org/notes/warren/05-07-2019/introducing-a-draft-style-guide-for-public-lab
Thanks!
If you're interested in being a mentor, leave a comment here -- and read over our software outreach resources https://publiclab.org/software-outreach to get an idea of how we work!
Some key resources on mentoring:
- read over our Summer of Code workflow here https://publiclab.org/wiki/gsoc#How+we+work
- read these extra notes on our approach here https://opensource.googleblog.com/2016/12/google-summer-of-code-2016-wrap-up_21.html
- read different ways to mentor in this post https://publiclab.org/notes/warren/11-08-2016/help-public-lab-s-software-grow-by-joining-a-supportive-team -- we need various types!
- read about what reviewers do day-to-day on Public Lab code projects https://publiclab.org/wiki/developers#Reviewers
- read about our commitment to modularity https://publiclab.org/notes/warren/01-18-2018/software-outreach-modularity-is-great-for-collaboration, very important in how we ask contributors to work
- check out our growing list of software outreach strategies https://publiclab.org/software-outreach
Thanks a lot, and we're happy to answer questions!
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/publiclab/plots2/issues/7360?email_source=notifications&email_token=AJXHQZ2V4LXRYGPPDNNESVDQ74LIJA5CNFSM4KMFGTLKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4II7WM2Q, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJXHQZ5CGJB3JHDVI2WKCEDQ74LIJANCNFSM4KMFGTLA .
Divy123
SidharthBansal
govindgoel
debck
ananyaarun
vinitshahdeo
DevanshCodes
theOpetunde
This is greater than SoC programs we had earlier. 💯 This is just for plots2.
Similar progress for other repositories like leaflet, LDI, Editor, MK, SWB, IS and many more.
We are proud to have you all this winter. We have already filled the results for students. Google will be announcing them on 10 February.
Regarding mentors, we will be happy to announce them now 🎉 🎉 🎉
@keshav234156 GCI GRAND PRIZE SUMMIT + PL KIT
@ananyaarun GSOC SUMMIT(If GCI mentor is invited, in 2019 gci mentor was invited. We hope this year also, GCI mentor is invited) + PL Kit
Following mentors will be awarded a PL Kit for their contribution at Public Lab
Ananya, Keshav, Debashish, Mayank Pathela, Sasha, Isha, Sudipto and Harman Jolly. 🥇
I have sent an email for the PL kits. Kindly order that using the coupon code I emailed you all.
Thanks and let's start with GSoC and outreachy 🚀
Let's make it more encouraging and collaborative than past years
starkblaze01
harshithpabbati
alaxalves
pydevsg
ataata107
VladimirMikulic
Uzay-G
sssash18
In the above given image we could convert the left image into the style of the right image to get the bottom image.
NitinBhasneria
saurabhkanswal
sagarpreet-chadha
Tlazypanda
StlMaris123
With Outreachy and Google Summer of Code 2020 coming up, we're looking ahead to who may be interested in mentoring for these programs. We have participated in both during the past few years, and while we are not guaranteed spots, we are planning to apply as an organization.
Read some previous year's proposals here, and participate in project idea brainstorming here. If one of the project ideas strikes your interest, please mention it!
We especially welcome people from groups underrepresented in free and open source software!
It's very important to us to have diverse representation in our mentor group just as in our participant group. And remember -- our community aspires to be a respectful place. Please read and abide by our Code of Conduct.
To participate:
This year, we're asking that mentors have taken some of the following steps to be part of our community:
fto-candidateorsupport, these issues may require little more work, but we'll try to help.gci-candidateneither asfto-candidatenor asfirst-timer-only. Provide link to such issues' merged PR. (Make sure you claim the issue first by commenting on issue you are planning to solve)Mentors check in with a student at least once per week roughly from May-August, and offer some project management guidance and encouragement... while relying on the chatroom and the @publiclab/reviewers group to provide code-specific input, so that we share the burden of specific technical support. We have weekly Check-Ins on GitHub (#4548) as well, and mentors are expected (along with students!) to be in the rotation to post these occasionally.
Remember that to be a mentor you don't necessarily need to know how to code -- we also need mentors who know Public Lab's community and practices well, and who can encourage students to speak up when they get stuck, and to ask the community for input and testing of their work. Students often get stuck when they don't know how something should look, or how a feature might be used by the community -- contextual info!
Priorities this year
This year we are aiming to bring some focus on high-priority projects to the program, and we’d like all mentors to help to encourage these new priorities. Some are highlighted in our ideas list, which lists our top community projects. We’re much more likely to accept projects that source from this list, although we’re happy to provide input on other suggested ideas too!
Others are covered in our ROADMAP, which emphasizes code stability, testing, maintainability, and reducing technical debt.
However, it does note that new projects can be developed in a “satellite” format, where they first achieve stability as separate repositories, before being proved out and integrated into PublicLab.org. With lots of people proposing React projects last year (for example), we really want to see such a project developed separately with a limited scope (like, just the commenting system, or just the dashboard), and proved out before being considered for integration.
Finally, we have a new Style Guide this year, which we are strongly encouraging people to read carefully before proposing design changes or refinements: https://publiclab.org/notes/warren/05-07-2019/introducing-a-draft-style-guide-for-public-lab
Thanks!
If you're interested in being a mentor, leave a comment here -- and read over our software outreach resources to get an idea of how we work!
Some key resources on mentoring:
Thanks a lot, and we're happy to answer questions!
Kindly fill https://docs.google.com/forms/d/1OFjj_2d4BnntXEy6bddWoKNOeBqvnJCLeGwOFORajZI/edit before 30th March 2020