Hello Everyone! π β
We all at Public Lab π learn, grow, work, brainstorm ideas, contribute together so why not share about our weekly goals and the awesome work we have done at Public Lab with each other, so we can support and collaborate with each other better. The goal of our Community Check-In is for every community member to share something about their work from the past week and about their current week's goal dart. You are also welcome to share fun-fact π, new ideas π‘, your learning goals. βοΈ
If you're new here, welcome π and don't forget to say hi β below, we'd love to work with you! If you're looking for new issues, please try some of our first-timers-only issues.
You can find them at https://code.publiclab.org/#r=all π
We're SO EXCITED to have your help! π€
Is there anything, you would like to share with us from last week's work? What is your plan for this week? π
If you have not planned yet, just leave a Hello! so that we know that you are in sync with us π and doing well!
As always, if you're waiting for a review, or if you're stuck, you can request help here, leave a comment on your issue with @publiclab/reviewers mentioned, or ask the community in our Gitter chatroom. π
Gitter
Gitter is an active chatroom in our community and we'll be sending weekly reminders about check-ins there. Be sure to sign up there for these updates or just to join the conversation. You can also join us through http://publiclab.org/chat π¬
This Week's Theme: "Motivate"
A bit of context first. Before I started contributing to PublicLab back in November, I drifted a while between different organizations, trying to find the right one, trying to fit in, trying to do something amazing. I was well acquainted with JS concepts back then as well, but lacked a driving force to keep me going. I would go on hours of formatting the code according to their linting rules, proper indentation, using the latest APIs and double checking anyone of those that might be deprecated, just to be neglected off since I was a newer contributor, and hadn't been around that much, so those repositories, more or less, always had the same people that reviewed, pushed, and merged the PRs. Always.
This would really put me off. I would decide to checkout a new organization the next day, and hopefully make some progress there, with little or no luck, until eventually, I came across an organization that actually had a label for first-timers-only
and the welcoming atmosphere seemed too good to be true. I don't know if other organizations do this too now or not, but initially this really got my spirits up, and I pushed some commits. After that I was suggested to complete a fto-candidate
, so I did that as well, and immediately moved to PublicLab's Editor, a JS lib, that interested me back then, and still does.
I honestly did not expect any of the humongous support I got along the way. My PRs were reviewed the same day, enabling me to put in as much work as I wanted to, maybe even push my limits, which I enjoyed every second of. Before you know it, I was opening fto
issues welcoming newer contributors just like me to the repository! How @jywarren, @gauravano, @sashadev-sky, or anyone else managed to do the brilliant work they did, while welcoming newer contibutors like me, while solving my doubts on Gitter, while providing insightful reviews on my PRs, and so much more, was out of my ability to comprehend, and I was in fact, motivated.
I will always be thankful for the environment PublicLab enabled me to work in, so that I can contribute with the same energy from back when I completed my fto
to this day, it's really been an amazing journey.
Go ahead, volunteer!
Fighting my temptation to keep going on with the storytelling, I will get down to the point now. In order to help make PublicLab the welcoming and progressive community it is and has been, I'm volunteering to help open fto
for similar folks, looking for a place to start and continue as well. I will also be helping folks across as many repositories, in as many areas as possible, so that they, in the near future, may hopefully repeat the loop.
I would love any and all the help I can get with this, and if you could spare some time to do the same, doesn't matter how long a member you've been, please comment below to volunteer. To summarize, you can open new fto
s or fto-candidates
, help people (not only first-timers) complete their PRs, clear doubts on Gitter, etc. To further clarify, this will be different from the normal workflow in the fact that the volunteer will be doing these tasks in a greater frequency this week, if at all possible, than they do usually. There will not be any judgement, and you are free to do the above tasks as a volunteer at your own pace or even attend to your own issues whenever you feel like it.
Below are a few fto
s and one fto-candidate
I managed to spin up today, so if you're reading this, and haven't yet contributed to any of PublicLab's repositories, pick one (comment here and check them out after completion)! Also, since the check-in is in this repo, I thought of doing the same with the fto
s.
You can find our list of previous check-ins here. π
Community Survey
@ebarry has compiled the results of the community survey, which was open from January 14 to March 21, into a comprehensive code community report. Please add your comments here to this thread for what we are inspired to do/change as a result of reading:https://publiclab.org/notes/liz/04-15-2019/report-2019-software-contributors-survey
This is a really unique opportunity to contribute to open source from a greater scope, and a reminder of the greater meaning behind the work all of you have been doing!
Thanks and keep contributing! Contributing to Public Lab means contributing to the Environment!
Previous Check-ins π
Gaurav Sachdeva (@gauravano) publiclab/plots2#4327
Sidharth Bansal (@SidharthBansal) publiclab/plots2#4369
Cess (@cesswairimu) publiclab/plots2#4476
Harman Jolly (@coderjolly) publiclab/plots2#4548
Rishabh Rawat (@Rishabh570) publiclab/plots2#4607
Sasha Boginsky (@sashadev-sky) publiclab/plots2#4676
Rishabh Kr Bothra (@geekychaser) publiclab/plots2#4711
Shubham Sangamnerkar (@shubhscoder) publiclab/plots2#4757
Siddhant N Trivedi (@sidntrivedi012) publiclab/plots2#4784
Isha Gupta (@IshaGupta18) publiclab/plots2#4844
Gaurav Sachdeva (@gauravano) publiclab/plots2#4879
Harshith Pabbati (@harshithpabbati) publiclab/plots2#4917
Gaurav Sachdeva (@gauravano) publiclab/plots2#5034
Harshith Pabbati (@harshithpabbati) publiclab/image-sequencer#883
Harman Jolly (@coderjolly) publiclab/mapknitter#447
Divya Baid (@divyabaid16) publiclab/PublicLab.Editor#317
Gautami Gupta (@gautamig54) publiclab/leaflet-environmental-layers#164
Sasha Boginsky (@sashadev-sky) publiclab/Leaflet.DistortableImage#215
Sagarpreet Chadha (@sagarpreet-chadha) publiclab/leaflet-blurred-location#198
Harsh Khandeparkar (@harshkhandeparkar) publiclab/spectral-workbench#451
Pranshu Srivastava (@rexagod) #61
Have a great week everyone! πβ€οΈπ