-
Notifications
You must be signed in to change notification settings - Fork 158
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
Weekly Community Check-in #20 - What You Have Learnt #451
Comments
@Marieram @swiatek7 @gauravano @publiclab/reviewers @publiclab/is-reviewers @publiclab/community-reps @subhahu123 @An0u @Jaya738 @mgroovyank @shreyateeza @TANGL3SIT3S @nazeem1988 @karunagoyalk @Nirvikalpa108 @cassianoblonski @EngrEric @Anjalizi @GettyOrawo @coderbeetle @corbettbw @govindjeevan @gautamig54 @daddyjab @emestabillo @letnewKid @srujana121 @jazdao @chinwendusilvia @aggarwal19 @Jenniline @madelinejones @helenatxu @richa031 @FabSar @kuja24 @megha070 @Aarabhi2017 @Manvi07 @siddhishree @Julius26 @VinneyJ @sonali9696 @rarrunategu1 @coreytegeler @labseven @milomacphail @CleverFool77 @ananyaarun @ananya @divyabaid16 @publiclab-mimi @shubhi2000 |
Hi everyone! Great check-in @harshkhandeparkar 👍 Contributing to Public Lab has surely made me a better developer, I learned testing, Git, understanding of diff. frameworks, being a good team player, collaboration skills, mentorship and many more. Although there is still a long way to go, there's always something to learn from every issue/PR/discussion/project. I think I am also a bit more organized now, improved time-management skills(but still a lot more improvement needed :P), a good communicator, my typing and email reading speed have increased 😅, increase in confidence and most importantly a better person. I would be slow in responding to issues/PRs till May 16, due to my exams, so if your PR is ready for review then please mention @publiclab/plots2-reviewers and if it's ready for merging then mention @jywarren @SidharthBansal. Thanks! |
Again, another great topic! It strikes me as funny that I never thought I would learn how to make a contribution, (pull request, testing, revisions, etc). I had just never considered it in the first place. Plots2 is a place where I've mainly contributed through ideas but it's just never been on my list of things to do. I also learned that the developer community is like any other community at Public Lab and that was a really crucial finding for me because it meant that I also learned that there was a good place for me to fit in which has been harder in recent years for their own interesting and necessary reasons. I think that's partly due to the way people conceive of websites in general. When I hold an actual newspaper (which sadly, I do not) the printers are journalists. It's where (I assume) "the press" comes from. At a news website, developers disappear. They don't produce news, instead they "maintain". So, I think previously I've had the erroneous sense that Public Lab developers make the thing Public Lab does possible, instead of a thing which is made possible by Public Lab. We too work on tools, research, activism, and so on. I hope that in the future, we can find ways to interface in a more front facing way with the main website. |
Hi all!!! |
Awesome theme @harshkhandeparkar. Wow, where do I start? I have learnt so much here.
|
Hi! I am going to go for one learning point instead of attempting to enumerate all the things i've learned from PL: I wanted to remove the ability to "click spam" the like button on notes in plots2 and @jywarren taught me about debouncing in JS by pointing me to this PR for a usage reference: I chose this one because it has proved to be a really useful and versatile JS skill, and I ended up learning so much beyond the original issue about optimizing client / server interactions. |
Is anyone interested in opening the next check-in tomorrow? |
Yes please, I want to!! |
Yeahh, I would like to volunteer to do it tomorrow.
…On Sat, May 4, 2019, 1:13 PM Sasha Boginsky ***@***.***> wrote:
Is anyone interested in opening the next check-in tomorrow?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#451 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGKQ7SFHENSAPXQ43BZGHIDPTU5CPANCNFSM4HJEOMHQ>
.
|
Thanks @sashadev-sky. I will be opening it tomorrow if it's okay to @aashna27? |
Hey everyone , |
@sashadev-sky @Divy123 @aashna27 If it's not a problem, I actually communicated my interest in opening the next check-in a while back to @gauravano, so can I proceed with this? |
Sure please go ahead!! |
Yes @sagarpreet-chadha, it's at 12:00 am IST |
Okayy! Cool 😀
…On Sat, May 4, 2019, 3:51 PM Sasha Boginsky ***@***.***> wrote:
@rexagod <https://github.com/rexagod> sorry I didn't realize! No problem
it's all you. @Divy123 <https://github.com/Divy123> @aashna27
<https://github.com/aashna27> you guys get next two weeks :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#451 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGKQ7SH5FYX72RFBC6P6G5LPTVPRRANCNFSM4HJEOMHQ>
.
|
Sorry for the late response. |
New check-in open at publiclab/inline-markdown-editor#72. Thanks everyone! |
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 please comment a Hello message below, we 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 page.
This Week's Theme:
What You Have Learnt: We all have experienced open source from the day we started our journey with PublicLab. PublicLab is known for welcoming new contributors so there is no doubt that your open source journey has been very interesting and got to learn many new things, especially about open source.
Apart from learning to contribute to open source projects, I learnt many other things and concepts (mostly mathematical concepts) which I had never expected to learn. I had never thought that a simple open source journey would teach me so many other things which are not at all related to programming.
This week, you can share what you have learnt that you never expected to learn:
Hope everyone has an awesome week!
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!!
cc
@mohitRJranjan @milaaraujo @kevinzluo @Rishabh570 @sashadev-sky @geekychaser @shubhscoder @sidntrivedi012 @SidharthBansal @cesswairimu @stefannibrasil @ViditChitkara @tech4GT @mridulnagpal @IshaGupta18 @coderjolly @namangupta01 @sagarpreet-chadha @Souravirus @MayankKashyap @siaw23 @ryzokuken @icarito @steviepubliclab, @ebarry, @jywarren, @sagarpreet-chadha, @JonathanXu1, @uzorjchibuzor, @eli6, @rexagod, @divyabaid16, @dinaelhanan, @oorjitchowdhary, @wanzulfikri, @mohitRJranjan @publiclab/mentors @publiclab/image-sequencer-guides @publiclab/leaflet-environmental-layers-guides @Paarmita @publiclab/reviewers @Divy123 @bhavayAnand9 @Mridul97 @avsingh999 @romanrodriguez @Dhiraj240 @codeIriss @rishabhc32 @chirag-singhal @IgorWilbert @dhruvgupta167 @vrk99 @pdurbin @harshkhandeparkar @aashna27 @Harshithpabbati @marieram @swiatek7
@niravasher
Thanks and keep contributing! Contributing to Public Lab means contributing to the Environment.
People who did the check-ins-
Have a great week everyone 🎈 🎉 🎇
The text was updated successfully, but these errors were encountered: