Weekly Community Check-In #6 - "Expand Your Horizons"

[sashadev-sky]

Hi 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 🎯. 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.

We're SO EXCITED to have your help!

Is there anything, you would like to share with us from past 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 📟.

This Week's Theme

I thought of making this week's theme around the idea of Expanding Your Horizons. As code contributors to Public Lab software, it's easy to get focused in on one specific project. While this is great, there is so much more to see and learn! This weekly check-in can be a great place to write about which code base you have been contributing to and something that interests you about it specifically, code related or greater picture, so that everyone can learn a little bit about all of the projects circulating.

I was inspired to make this the theme when I learned that there is a wealth of new information to be found in the Public Lab index of Wiki's, where code contributors are also welcome to share their knowledge and create research notes and wikis regarding new features, integrations, their work and relevant exciting things. Take a look! .

Summer of Code

@jywarren has started a brainstorming post for the ideas page for Summer of Code 2019 -It would be best get some ideas into discussion from the fellow community member before time. People have been brainstorming already - let's do it together!
https://publiclab.org/notes/warren/01-02-2019/brainstorming-for-summer-of-code-2019

Software Contributors Survey

This survey is conducted on a yearly basis to improve our experience.

The form will remain open until early March, but don't wait to respond!

People who did the check-ins

• Gaurav Sachdeva (@gauravano )
• Sidharth Bansal (@SidharthBansal )
• Cess (@cesswairimu )
• Harman Jolly (@coderjolly )
• Rishabh Rawat (@Rishabh570 )
• Sasha Boginsky (@sashadev-sky)

Have a great week everyone 🎉 🎆 🎈

[SidharthBansal]

Hi, last week around 10 issues/PRS resolved in login sequence project. We have completed multiple tag subscription project also. Nowadays focussing on some minor fixes. Regarding expanding the horizon, a great theme, this winter I took two projects and was able to complete them with help of community bonding. Shifting from a student to a leader this winter was a great experience. I realised leading different people with different mindset and time zones is difficult and interesting. Greater projects can be implemented in collaboration.: tada:

…

On Mon, Jan 21, 2019, 8:55 AM Sasha Boginsky ***@***.*** wrote: Hi 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 🎯. 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. We're SO EXCITED to have your help! Is there anything, you would like to share with us from past 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, please request help here OR leave a comment with @publiclab/mentors <https://github.com/orgs/publiclab/teams/mentors> @publiclab/reviewers <https://github.com/orgs/publiclab/teams/reviewers> for some input. 🙌 This Week's Theme I thought of making this week's theme around the idea of Expanding Your Horizons. As code contributors to Public Lab software, it's easy to get focused in on one specific project. While this is great, there is so much more to see and learn! This weekly check-in can be a great place to *write about which code base you have been contributing to and something that interests you about it specifically, code related or greater picture*, so that everyone can learn a little bit about all of the projects circulating. I was inspired to make this the theme when I learned that there is a wealth of new information to be found in the *Public Lab index of Wiki's, where code contributors are also welcome to share* their knowledge and create research notes and wikis regarding new features, integrations, their work and relevant exciting things. Take a look! <https://publiclab.org/wiki/>. cc @thesparks @faithngetich <https://github.com/faithngetich> @DakshGondaliya <https://github.com/DakshGondaliya> @mohitRJranjan <https://github.com/mohitRJranjan> @milaaraujo <https://github.com/milaaraujo> @kevinzluo <https://github.com/kevinzluo> @stefannibrasil <https://github.com/stefannibrasil> @gauravano <https://github.com/gauravano> @ViditChitkara <https://github.com/ViditChitkara> @tech4GT <https://github.com/tech4GT> @mridulnagpal <https://github.com/mridulnagpal> @namangupta01 <https://github.com/namangupta01> @sagarpreet-chadha <https://github.com/sagarpreet-chadha> @Souravirus <https://github.com/Souravirus> @jywarren <https://github.com/jywarren> @MayankKashyap <https://github.com/MayankKashyap> @siaw23 <https://github.com/siaw23> @ryzokuken <https://github.com/ryzokuken> @ccpandhare <https://github.com/ccpandhare> @icarito <https://github.com/icarito> @steviepubliclab <https://github.com/steviepubliclab> @ebarry <https://github.com/ebarry> @jywarren <https://github.com/jywarren>, @sagarpreet-chadha <https://github.com/sagarpreet-chadha>, @icarito <https://github.com/icarito>, @JonathanXu1 <https://github.com/JonathanXu1>, @uzorjchibuzor <https://github.com/uzorjchibuzor>, @eli6 <https://github.com/eli6>, @kevinzluo <https://github.com/kevinzluo>, @ValentinaTironi <https://github.com/ValentinaTironi>, @rexagod <https://github.com/rexagod>, @sashadev-sky <https://github.com/sashadev-sky>, @IshaGupta18 <https://github.com/IshaGupta18>, @milaaraujo <https://github.com/milaaraujo>, @dinaelhanan <https://github.com/dinaelhanan>, @cesswairimu <https://github.com/cesswairimu>, @dependabot <https://github.com/dependabot>[bot], @oorjitchowdhary <https://github.com/oorjitchowdhary>, @okonek <https://github.com/okonek>, @wanzulfikri <https://github.com/wanzulfikri>, @mohitRJranjan <https://github.com/mohitRJranjan> @publiclab/mentors <https://github.com/orgs/publiclab/teams/mentors> @publiclab/image-sequencer-guides <https://github.com/orgs/publiclab/teams/image-sequencer-guides> @publiclab/leaflet-environmental-layers-guides <https://github.com/orgs/publiclab/teams/leaflet-environmental-layers-guides> @Paarmita <https://github.com/Paarmita> @vishalka98 <https://github.com/vishalka98> @publiclab/reviewers <https://github.com/orgs/publiclab/teams/reviewers> @Divy123 <https://github.com/Divy123> @pomyo <https://github.com/pomyo> @bhavayAnand9 <https://github.com/bhavayAnand9> @ovipa017-xamk <https://github.com/ovipa017-xamk> @Mridul97 <https://github.com/Mridul97> @avsingh999 <https://github.com/avsingh999> @Rishabh570 <https://github.com/Rishabh570> @subhahu123 <https://github.com/subhahu123> @asquare14 <https://github.com/aSquare14> @Radhikadua123 <https://github.com/Radhikadua123> @quinn-codes-synthesis <https://github.com/quinn-codes-synthesis> @amychan331 <https://github.com/amychan331> @mardelvalle <https://github.com/mardelvalle> @narnt @hydro-m @love-opensource @romanrodriguez @shubhangi-chauhan @Dhiraj240 @geekychaser @codeIriss @CoderJolly Summer of Code @jywarren <https://github.com/jywarren> has started a brainstorming post for the ideas page for Summer of Code 2019 -It would be best get some ideas into discussion from the fellow community member before time. People have been brainstorming already - let's do it together! https://publiclab.org/notes/warren/01-02-2019/brainstorming-for-summer-of-code-2019 Software Contributors Survey This survey <https://docs.google.com/forms/d/e/1FAIpQLSdGoRWXD79h1qMthwA41R1Kf76iajhqwYIC4A05gH2XvCflLQ/viewform> is conducted on a yearly basis to improve our experience. Please fill out it if you haven't already. I believe it will be open until the end of January, please correct me if i'm wrong and I will update accordingly :) People who did the check-ins - Gaurav Sachdeva ***@***.*** <https://github.com/gauravano> ) - Sidharth Bansal ***@***.*** ) - Cess ***@***.*** <https://github.com/cesswairimu> ) - Harman Jolly ***@***.*** ) - Rishabh Rawat ***@***.*** <https://github.com/Rishabh570> ) - Sasha Boginsky ***@***.*** <https://github.com/sashadev-sky>) Have a great week everyone 🎉 🎆 🎈 — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#4676>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUACQ-15TmC3u7c1OV2iSmWqL-Bv2YbUks5vFTMjgaJpZM4aKClZ> .

[SidharthBansal]

Who will be doing the next checkin? On Mon, Jan 21, 2019, 10:30 AM Sidharth Bansal < [email protected] wrote:

…

Hi, last week around 10 issues/PRS resolved in login sequence project. We have completed multiple tag subscription project also. Nowadays focussing on some minor fixes. Regarding expanding the horizon, a great theme, this winter I took two projects and was able to complete them with help of community bonding. Shifting from a student to a leader this winter was a great experience. I realised leading different people with different mindset and time zones is difficult and interesting. Greater projects can be implemented in collaboration.: tada: On Mon, Jan 21, 2019, 8:55 AM Sasha Boginsky ***@***.*** wrote: > Hi 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 🎯. 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. > > We're SO EXCITED to have your help! > > Is there anything, you would like to share with us from past 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, please > request help here OR leave a comment with @publiclab/mentors > <https://github.com/orgs/publiclab/teams/mentors> @publiclab/reviewers > <https://github.com/orgs/publiclab/teams/reviewers> for some input. 🙌 > This Week's Theme > > I thought of making this week's theme around the idea of Expanding Your > Horizons. As code contributors to Public Lab software, it's easy to get > focused in on one specific project. While this is great, there is so much > more to see and learn! This weekly check-in can be a great place to *write > about which code base you have been contributing to and something that > interests you about it specifically, code related or greater picture*, > so that everyone can learn a little bit about all of the projects > circulating. > > I was inspired to make this the theme when I learned that there is a > wealth of new information to be found in the *Public Lab index of > Wiki's, where code contributors are also welcome to share* their > knowledge and create research notes and wikis regarding new features, > integrations, their work and relevant exciting things. Take a look! > <https://publiclab.org/wiki/>. > > cc > @thesparks @faithngetich <https://github.com/faithngetich> > @DakshGondaliya <https://github.com/DakshGondaliya> @mohitRJranjan > <https://github.com/mohitRJranjan> @milaaraujo > <https://github.com/milaaraujo> @kevinzluo <https://github.com/kevinzluo> > @stefannibrasil <https://github.com/stefannibrasil> @gauravano > <https://github.com/gauravano> @ViditChitkara > <https://github.com/ViditChitkara> @tech4GT <https://github.com/tech4GT> > @mridulnagpal <https://github.com/mridulnagpal> @namangupta01 > <https://github.com/namangupta01> @sagarpreet-chadha > <https://github.com/sagarpreet-chadha> @Souravirus > <https://github.com/Souravirus> @jywarren <https://github.com/jywarren> > @MayankKashyap <https://github.com/MayankKashyap> @siaw23 > <https://github.com/siaw23> @ryzokuken <https://github.com/ryzokuken> > @ccpandhare <https://github.com/ccpandhare> @icarito > <https://github.com/icarito> @steviepubliclab > <https://github.com/steviepubliclab> @ebarry <https://github.com/ebarry> > @jywarren <https://github.com/jywarren>, @sagarpreet-chadha > <https://github.com/sagarpreet-chadha>, @icarito > <https://github.com/icarito>, @JonathanXu1 > <https://github.com/JonathanXu1>, @uzorjchibuzor > <https://github.com/uzorjchibuzor>, @eli6 <https://github.com/eli6>, > @kevinzluo <https://github.com/kevinzluo>, @ValentinaTironi > <https://github.com/ValentinaTironi>, @rexagod > <https://github.com/rexagod>, @sashadev-sky > <https://github.com/sashadev-sky>, @IshaGupta18 > <https://github.com/IshaGupta18>, @milaaraujo > <https://github.com/milaaraujo>, @dinaelhanan > <https://github.com/dinaelhanan>, @cesswairimu > <https://github.com/cesswairimu>, @dependabot > <https://github.com/dependabot>[bot], @oorjitchowdhary > <https://github.com/oorjitchowdhary>, @okonek <https://github.com/okonek>, > @wanzulfikri <https://github.com/wanzulfikri>, @mohitRJranjan > <https://github.com/mohitRJranjan> @publiclab/mentors > <https://github.com/orgs/publiclab/teams/mentors> > @publiclab/image-sequencer-guides > <https://github.com/orgs/publiclab/teams/image-sequencer-guides> > @publiclab/leaflet-environmental-layers-guides > <https://github.com/orgs/publiclab/teams/leaflet-environmental-layers-guides> > @Paarmita <https://github.com/Paarmita> @vishalka98 > <https://github.com/vishalka98> @publiclab/reviewers > <https://github.com/orgs/publiclab/teams/reviewers> @Divy123 > <https://github.com/Divy123> @pomyo <https://github.com/pomyo> > @bhavayAnand9 <https://github.com/bhavayAnand9> @ovipa017-xamk > <https://github.com/ovipa017-xamk> @Mridul97 > <https://github.com/Mridul97> @avsingh999 <https://github.com/avsingh999> > @Rishabh570 <https://github.com/Rishabh570> @subhahu123 > <https://github.com/subhahu123> @asquare14 <https://github.com/aSquare14> > @Radhikadua123 <https://github.com/Radhikadua123> @quinn-codes-synthesis > <https://github.com/quinn-codes-synthesis> @amychan331 > <https://github.com/amychan331> @mardelvalle > <https://github.com/mardelvalle> @narnt @hydro-m @love-opensource > @romanrodriguez @shubhangi-chauhan @Dhiraj240 @geekychaser @codeIriss > @CoderJolly > Summer of Code > > @jywarren <https://github.com/jywarren> has started a brainstorming post > for the ideas page for Summer of Code 2019 -It would be best get some ideas > into discussion from the fellow community member before time. People have > been brainstorming already - let's do it together! > > https://publiclab.org/notes/warren/01-02-2019/brainstorming-for-summer-of-code-2019 > Software Contributors Survey > > This survey > <https://docs.google.com/forms/d/e/1FAIpQLSdGoRWXD79h1qMthwA41R1Kf76iajhqwYIC4A05gH2XvCflLQ/viewform> > is conducted on a yearly basis to improve our experience. Please fill out > it if you haven't already. > > I believe it will be open until the end of January, please correct me if > i'm wrong and I will update accordingly :) > People who did the check-ins > > - Gaurav Sachdeva ***@***.*** <https://github.com/gauravano> ) > - Sidharth Bansal ***@***.*** ) > - Cess ***@***.*** <https://github.com/cesswairimu> ) > - Harman Jolly ***@***.*** ) > - Rishabh Rawat ***@***.*** <https://github.com/Rishabh570> ) > - Sasha Boginsky ***@***.*** <https://github.com/sashadev-sky>) > > Have a great week everyone 🎉 🎆 🎈 > > — > You are receiving this because you are on a team that was mentioned. > Reply to this email directly, view it on GitHub > <#4676>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AUACQ-15TmC3u7c1OV2iSmWqL-Bv2YbUks5vFTMjgaJpZM4aKClZ> > . >

[Rishabh-Kumar-Bothra]

@SidharthBansal I would love to do check-in for next week.
Thank you

[SidharthBansal]

Great

…

On Mon, Jan 21, 2019, 11:05 PM Rishabh Bothra ***@***.*** wrote: @SidharthBansal <https://github.com/SidharthBansal> I would love to do check-in for next week. Thank you — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4676 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUACQzEl7YWmy0X5FHWErYJzGbKaOFGWks5vFfpigaJpZM4aKClZ> .

[rexagod]

Greetings everyone! It's always amazing to see all the efforts and hard work everyone is putting around here, even in other repositories as well. I would however, like to take this opportunity to promote an idea that sparked over at the Image Sequencer. The idea basically focuses on creating a pinned issue that advises the newcomers to look the codebase, find any refactor opportunity, and submit their first PublicLab PR for the same! This way they don't have to wait for new ftos and the codebase gets refactored too. I'd like you all to give your inputs on this, and whether we can implement it across all the repositories?

Also, I made some ftos for the first-timers reading this 😉

PLOTS2: #4681 #4680
Editor: #246
Leaflet Blurred-Location: #168

Cheers PL. Let's do this! 💯

[sashadev-sky]

@rexagod I think that would be a good idea for a 2nd or so on issue, like @jywarren has that checklist of the workflow 1) finish an FTO 2) Solve a help-wanted 3) Write your own FTO... we could put somewhere in there to find any problems, open an issue regarding them and challenge yourself to solve it.

For the idea of it being instead of an FTO, though, you would have to consider some factors like the new contributor could choose a very unfriendly 1st issue, they wouldn't get the opportunity to be guided one on one by the issue creator, they wouldn't get familiarized with the PL workflow. That small bit of structure really helped me get acclimated when I first started. I think the size of the code base makes a big difference too. For smaller ones like image-sequencer it could work much better than in plots2.

what are your thoughts?

[cesswairimu]

Hello everyone 👋,
I have been working on expanding the statistics project. What excites me about this project is the amount of data on the website and how it is can be used to track trends so I am just trying to make it easier to track the trends and the people doing data analysis easy for them to retrieve the data.
Nice theme @sashadev-sky,

[oorjitchowdhary]

Hello all 👋
I haven't been online lately -- sorry for that.

Hope I'm just in time to ask this...
As per GCI rules, a Grand Prize Winner can ask for a Letter of Recommendation. I had asked the GCI Program Manager but she insisted to ask the mentors to write it out as they've worked with me.

So, @publiclab/reviewers can I ask for a Letter of Recommendation for me for my work and contributions to the organization.

This will be great help..
Thanks. 😄

[SidharthBansal]

Whom did you ask? There are multiple program manager at different locations. Can you please name her? Yeah sure we can help you with LORs. You can ask us whenever you have to submit it anywhere. We will help you with it

…

On Fri, Jan 25, 2019, 9:31 PM Oorjit Chowdhary ***@***.*** wrote: Hello all 👋 I haven't been online lately -- sorry for that. Hope I'm just in time to ask this... As per GCI rules, a Grand Prize Winner can ask for a Letter of Recommendation. I had asked the GCI Program Manager but she insisted to ask the mentors to write it out as they've worked with me. So, @publiclab/reviewers <https://github.com/orgs/publiclab/teams/reviewers> can I ask for a Letter of Recommendation for me for my work and contributions to the organization. This will be great help.. Thanks. 😄 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4676 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUACQ-f1aZCD2nVy002pGSehhLZubh2mks5vGypPgaJpZM4aKClZ> .

[oorjitchowdhary]

I asked GCI support and Stephanie Taylor replied to that thread. I don't really have to submit it anywhere yet but I'd like to have it.

[SidharthBansal]

Thanks Oorjit for quick response. You have to contact mentor from which you want LOR. LOR is given by mentor. Thanks

…

On Fri, Jan 25, 2019, 9:42 PM Oorjit Chowdhary ***@***.*** wrote: I asked GCI support and Stephanie Taylor replied to that thread. I don't really have to submit it anywhere yet but I'd like to have it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4676 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUACQ_yR8bYsXdDXbM6ZOuwsMSWsSvcNks5vGyz1gaJpZM4aKClZ> .

[shubhscoder]

I would like to do the community check in the next to next week after @geekychaser has done it. Thank you!

[oorjitchowdhary]

Thanks Oorjit for quick response. You have to contact mentor from which you want LOR. LOR is given by mentor. Thanks

@SidharthBansal, I'm okay with any mentor as we all have contributed to PL. I'd just like @jywarren to review the letter once (if possible) ..
Thanks again

[grvsachdeva]

Reminder for @geekychaser: Please open the community check-In on Monday (or Sunday evening). Also, please drop a message in Gitter channel (tagging @ALL) after opening a check-In. As using Gitter channel we can try to reach max people. You can take more ideas from here - #4692 (comment)

Also, we are discussing more ideas here - #4692. Thanks @sashadev-sky for thinking about community outreach.

[grvsachdeva]

Hi @oorjitchowdhary feel free to drop a mail to @jywarren as he's busy with workshop and so may ignore this message. Thanks!

[grvsachdeva]

New weekly check-in opened at #4711. Thanks all of you!

[jywarren]

I missed chiming in this past week, so I just wanted to say I really loved the theme and all the ideas shared here. Lots of growth in our community and this is how we achieve it! @rexagod we have a few pinned issues in this repo along with those at the "support" label. Maybe these could be generalized for other repos or copied?