Skip to content
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 #2 - "Everybody Struggles"! #4369

Closed
SidharthBansal opened this issue Dec 23, 2018 · 26 comments
Closed

Weekly Community Check-In #2 - "Everybody Struggles"! #4369

SidharthBansal opened this issue Dec 23, 2018 · 26 comments
Labels
community check-in outreach issues involve community involvement and helping people who're stuck somewhere

Comments

@SidharthBansal
Copy link
Member

SidharthBansal commented Dec 23, 2018

Hi everybody 😃 !

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. We have a Community Check-In each week, where every community member can 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 ☑️ .

We believe in collaborative efforts to support our community. We are running a learning platform which helps a newcomer to become master of tomorrow. 💯

If you're new here, welcome, and please comment a Hello message below, we would 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!

The coming weeks will be absolutely full of code 💻 , tasks 🗒️, fun 🎉 and excitement 😃!!

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 @publiclab/reviewers for some input. 🙌

This week's theme

This week we are having outreachy theme Everybody Struggles. So if you are struggling on any issue or have struggled on any issue then feel free to comment below here. We are not going to judge you on it. We want to showcase that BEST THINGS TAKES TIME AND LABOUR.

Have a GREAT week 🎉 !

Thank you !

/cc
@kunalvaswani123 @thesparks @faithngetich @DakshGondaliya @mohitRJranjan @milaaraujo @kevinzluo
@stefannibrasil @gauravano @ViditChitkara @tech4GT @mridulnagpal @namangupta01 @sagarpreet-chadha @Souravirus @jywarren @MayankKashyap @siaw23 @ryzokuken @ccpandhare @icarito @steviepubliclab @ebarry @jywarren, @sagarpreet-chadha, @icarito, @JonathanXu1, @uzorjchibuzor, @eli6, @kevinzluo, @ValentinaTironi, @rexagod, @sashadev-sky, @IshaGupta18, @milaaraujo, @dinaelhanan, @cesswairimu, @dependabot[bot], @oorjitchowdhary, @okonek, @wanzulfikri, @mohitRJranjan @publiclab/mentors @publiclab/image-sequencer-guides @publiclab/leaflet-environmental-layers-guides @Paarmita @vishalka98 @publiclab/reviewers @Divy123 @pomyo @bhavayAnand9 @ovipa017-xamk @Mridul97 @avsingh999 @Rishabh570 @subhahu123 @asquare14 @Radhikadua123 @faithngetich @quinn-codes-synthesis @amychan331 @mardelvalle @narnt @hydro-m @love-opensource @romanrodriguez @shubhangi-chauhan

Feel free to mention names of those contributors in comment below who have been missed.

@SidharthBansal
Copy link
Member Author

Here is @jywarren's struggle from #4327 (comment).

This past week I have been continuing to try to remove the old DrupalUsers code in #2857, and no matter how many errors I solve, another dozen or more appear -- it can be pretty frustrating! Never-ending, even. I'm getting closer though! Each time I open the Travis logs and hunt through for clues. We'll get there eventually, and hopefully this will dramatically simplify a lot of our users code by finally getting rid of the duplicated code of having 2 user models.

As he is busy. I am pasting it from his comment.

@SidharthBansal
Copy link
Member Author

Here is my struggle. 🔬 When we were building the OAuth project the main struggle was the absence of Devise gem at plots2. Almost all the documentation on the web have the solution of devise gem. So, there was a need to create our own system to incorporate AuthLogin library with the OAuth. The real struggle was to make the system in a state that it will never fail in the future. Initially we arrived at many corner cases(aka edge cases). As we were exploring new corner cases were arising. So, initially it was very hard to develop such a system. Once we completed the main system logic with all the corner cases. The system was so fast in accepting the providers that we included each provider within a week.
Now when the Google+ provider is not supported any longer after Mar'19. We need to migrate to the Google provider. The amount of struggle for this work will be too less. Our struggle paid off. The system will remain in a consistent state. All the users will remain intact even after this migration.
This was a struggle from past. 🔨
Let's talk about the current struggle. We recently made the login and signup modal. The whole website is so much linked to the login/signup functionality that as we explore a single issue and provide a fix we came across two or more subissues of equal priority. The issue is exploring exponentially over last two months. But as all the mentors are helping. We are able to catch up these issues and find a potential fix to these problems.

About the december work: ⛑️
In the subscription project, we did a quite lot this week. @IshaGupta18 is helping a lot. Thanks. The notes' sidebar subscription functionality is under progress. Multiple tag subscription feature is also under progress and is almost completed. The comment+subscription flow project needs to be tackled as soon as these two prs are merged.
Regarding the Login Sequences project: We have completed over 10+ issues and prs last week. Some more issues have come. We are trying to fix them. 💯 🔢
Thanks all.
Happy Holidays 🎄 🎅 🎉 🇨🇽 Merry Christmas all of you!!! 👍

@IshaGupta18
Copy link
Collaborator

Hey everyone! First of all thank you so much @SidharthBansal for the appreciation. It means a lot to me and you have been putting a ton of effort to get the functionality right. I have recently started here and enjoy it a lot. Right now, I am working on the multiple tag subscription feature and I hope to finish it soon.
My semester is about to start very soon, however I would love to keep working here and learn a lot more stuff! Thank you all very much!

@sagarpreet-chadha
Copy link
Contributor

Hi 😄 !

I was trying to get the spinner work in Leaflet.blurred 🗺 library today and i got stuck 🙈 at one point :

How do i install different versions of same package in package.json ?

What i tried before reaching to a solution :

  • The issue here is that leaflet-spinner has peer dependencies of leaflet@0.7.3 .

  • Peer dependencies are not installed automatically after npm 3 !

  • I have tried npm i npm-install-peers but this is not working .

  • Had faced same problem while integrating with mapknitter but there we use Bower which has concept of Resolutions to install multiple versions of same package .

  • Finally tried installing 2 versions of leaflet : one using npm name and another using git url , which also is not working 😥 .

  • Finally used cdn links to install the package and now it seems to work smoothly 😃 😌 !

Thank you 🎅 🎄 🤶 🎆 !

@jywarren jywarren changed the title Weekly Community Check-In #2 Everybody Struggles Weekly Community Check-In #2 - "Everybody Struggles"! Dec 23, 2018
@jywarren
Copy link
Member

Hi, all! I am traveling this week and doing my best to keep up with the fast pace. So one additional struggle is being sure that, even in a limited amount of time, I look carefully at big project plans like those of @milaaraujo (on the API and especially latitude/longitude storage in the Node model! #4292) and @cesswairimu (on the community stats project, 📊 📈 #4302). I don't want to misread or miss something that will cause trouble later!

Also wanting to mention @edieblu who continues to make progress on the Dashboard redesign, and has shared some great progress -- please check it out and offer your feedback to help improve our dashboard! https://publiclab.org/notes/edie_blues/12-13-2018/public-lab-dashboard-new-design-ideas#c21559

Thanks, everyone!!!

@grvsachdeva grvsachdeva added outreach issues involve community involvement and helping people who're stuck somewhere community check-in labels Dec 23, 2018
@grvsachdeva grvsachdeva pinned this issue Dec 25, 2018
@cesswairimu
Copy link
Collaborator

Hi everyone 👋 ,
A couple of struggles on my side especially on the ui, styling and basic layout.

  • One specific thing that I struggled with was date-picker positioning..sounds pretty simple but it was a pain to get it to appear where I wanted, asked for help from the community though the suggestions I got did not solve it I had to make some comprises.

  • Another major struggle was a brakeman issue User controlled method execution it looked critical to ignore. I tried to tweak it a couple of times and much much later solved it by making the method a private method 🎉 .

Thanks all for the support 😃 !!

@jywarren
Copy link
Member

Just a note also that this week many people are on holiday or vacation. Please be patient and activity will pick up a bit as people return over the next week or so!

@Dhiraj240
Copy link
Member

Hello everyone,
I have not been active since 3 months and i only worked on reviewing PRs.Although i solved few issues in plots-2 My main focus in this week will be to take up the new issues and work on pending issues too.Now my performance from this week will be consistent to get some edge in other projects. especially on solving issues.

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 26, 2018 via email

@Rishabh-Kumar-Bothra
Copy link
Contributor

Hello everyone,
This week I am working on some /tags related issues and some UI related problems and will try to complete them as soon as possible and will try to form some more issues.
Special thanks to @SidharthBansal @oorjitchowdhary for lots of support and helping out to make things more clear

@SidharthBansal
Copy link
Member Author

Who is willing to do next week checkins? We do this process in rotations so that each one will get an opportunity to do checkins. You need to just create a similar issue on Monday like this and close previous weeks issue.
Thanks

@cesswairimu
Copy link
Collaborator

@SidharthBansal I would love to do next week's checkins

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 26, 2018 via email

@codeIriss
Copy link

Hey everyone, I was trying to do open source contributions and i came across public lab and the plots2 project and i felt that contribution to plots2 will be helpful for me.but starting to contribute to such a large code base is never easy, i get started with my first issue and @jywarren @SidharthBansal helped me alot and after some days i solved that particular issue and thankyou so much @SidharthBansal @jywarren for helping me . Please help me in moving further and contributing more to the organisation. :)

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 27, 2018 via email

@grvsachdeva
Copy link
Member

I struggled a lot while completing my first PR with Public Lab. Why because I got scared from the huge codebase, I tried to go through the whole repo at once, but was it really the right way? I think No. Because, I was not a superhero that I would just read the project and all features understood, it took time for me in getting familiar. I started with small issues, focussed only on that part which is relative to a particular issue like see only those routes, models, controllers, tests required at that time.

So, start small but with each subsequent issue try to up your game and remember to utilize practices you learnt from last PR experiences.

The case may be different if the contributor is experienced in RoR. I was just at beginner level when I started.

@codeIriss this might help. Thanks!

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 27, 2018 via email

@Souravirus
Copy link
Member

Hi everyone, hope everyone is enjoying their holidays. I am currently working on upgrading to bootstrap4 in #3937 and hoping to complete by the next week.
Thank you!!

@coderjolly
Copy link
Member

Who is willing to do next week checkins? We do this process in rotations so that each one will get an opportunity to do checkins. You need to just create a similar issue on Monday like this and close previous weeks issue.
Thanks

I am willing

@grvsachdeva
Copy link
Member

Hi @coderjolly, for next check-In @cesswairimu has already shown interest but you could surely do the check-In for next to next week. How does it sound?

@SidharthBansal
Copy link
Member Author

@cesswairimu please link it to the new weekly check in after forming it.
Don't forget to close this issue.
Thanks in advance.

@sashadev-sky
Copy link
Member

Hi all! I am traveling this week and won’t be back online until after nye, but I look forward to continue contributing in 2019. Happy new year!

@digitaldina
Copy link
Collaborator

Hey everyone! I struggled a lot at first, with this being a codebase bigger than any I have every worked with, especially since I've never written a line of ruby before working on plots2, but I am started to feel more at ease because of the great help from the community, and taking a deep breath! I am working on a few small tasks and closing up loose ends with the login modals, and hope to continue with this. Thanks to everyone that helped me out!

@shubhscoder
Copy link
Contributor

Hello everyone! According to my experience the initial setup of the project was the most difficult part of my first PR. So, in order to facilitate a newcomer, we should automate the process of setup. I had opened a issue regarding the same #3259 but later forgot about it. I think some basic shell scripting is required or we can write a python script to automate the process. Anyone with any experience in this, please provide some guidance regarding the same. Thank you so much!

@coderjolly
Copy link
Member

Hi @coderjolly, for next check-In @cesswairimu has already shown interest but you could surely do the check-In for next to next week. How does it sound?

Sure, feel free to mention as now I am free from my exams

@cesswairimu
Copy link
Collaborator

Moved to #4476 Thanks everyone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community check-in outreach issues involve community involvement and helping people who're stuck somewhere
Projects
None yet
Development

No branches or pull requests