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 #7 - "Commitment" #4711

Closed
7 tasks done
Rishabh-Kumar-Bothra opened this issue Jan 27, 2019 · 26 comments
Closed
7 tasks done

Weekly Community Check-In #7 - "Commitment" #4711

Rishabh-Kumar-Bothra opened this issue Jan 27, 2019 · 26 comments
Labels
community check-in outreach issues involve community involvement and helping people who're stuck somewhere

Comments

@Rishabh-Kumar-Bothra
Copy link
Contributor

Rishabh-Kumar-Bothra commented Jan 27, 2019

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 @publiclab/reviewers for some input 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 Commitment. The idea behind this theme is that there are lots of pending issues which are being claimed. So, this week we will try to complete a maximum of our pending issues before claiming new ones. Approach mentors if you face any difficulty while solving them.

This week I am working on creating mockups for a tour of Publiclab.org and some previously claimed issues.

cc
@mohitRJranjan @milaaraujo @kevinzluo
@stefannibrasil @gauravano @ViditChitkara @tech4GT @mridulnagpal @namangupta01 @sagarpreet-chadha @Souravirus @MayankKashyap @siaw23 @ryzokuken @icarito @steviepubliclab @ebarry @jywarren, @sagarpreet-chadha, @JonathanXu1, @uzorjchibuzor, @eli6, @ValentinaTironi, @rexagod, @sashadev-sky, @IshaGupta18, @dinaelhanan, @cesswairimu, @dependabot[bot], @oorjitchowdhary, @okonek, @wanzulfikri, @mohitRJranjan @publiclab/mentors @publiclab/image-sequencer-guides @publiclab/leaflet-environmental-layers-guides @Paarmita @publiclab/reviewers @Divy123 @bhavayAnand9 @Mridul97 @avsingh999 @Rishabh570 @asquare14 @Radhikadua123 @quinn-codes-synthesis @amychan331 @mardelvalle @narnt @hydro-m @love-opensource @romanrodriguez @shubhangi-chauhan @Dhiraj240 @geekychaser @codeIriss @CoderJolly @rishabhc32 @chirag-singhal @Saurabh19126848_twitter @IgorWilbert @dhruvgupta167 @vrk99 @pdurbin @dave-light

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)
  • Rishabh Kr Bothra (@geekychaser)

Have a great week everyone 🎉 🎆 🎈

@grvsachdeva grvsachdeva added outreach issues involve community involvement and helping people who're stuck somewhere community check-in labels Jan 27, 2019
@grvsachdeva
Copy link
Member

grvsachdeva commented Jan 27, 2019

Thanks for awesome check-in @geekychaser!

Upcoming week's goal :

  1. I would try to do maximum issues I have assigned myself in past
  2. Getting more familiar with Mapknitter codebase, reviewing issues, documentation updates, integration, etc.
  3. Working on the Translation project, specifically, transferring directory system to file specific system for each language.

Wish you all happy week ahead, keep coding, contributing and be happy!

@sagarpreet-chadha
Copy link
Contributor

Hi all 😄 !

I will be working on adding latitude and longitude support to PL.editor's map module - which will pan location on map instead of showing default location , to given input location .
Also reminding myself here to update Readme as well to update API documentation :P .

Thank you all and have a great week ahead 💃 🎉 !

@IgorWilbert
Copy link
Member

IgorWilbert commented Jan 27, 2019

Hello everyone 😄! I'm very happy for being part of this project!

Upcoming week's goals:
1- Final touches on the PRs I opened for the Editor, so that they can be merged;
2- Investigate old open issues and if possible turn them into FTO-issues;
3- Continue planning on plots2 mobile version for GSoC, pointing out the most important functionalities and how to implement them;
4 - Get familiar with Image Sequencer codebase;

Hope you all have a great week! Let's do this 🚀 !

@SidharthBansal
Copy link
Member

SidharthBansal commented Jan 28, 2019 via email

@Dhiraj240
Copy link
Member

Hello everyone,
I am going to work on Mapknitter and SpectralWorkbench projects.
Initially i will do their setup on my local machine.
For this week my end result should be to understand the codebase of Mapknitter and solve the issues, if i unable to solve it then i will report at least two code specific fto issues.

@ebarry
Copy link
Member

ebarry commented Jan 28, 2019

Hi Everyone,
This week I am interestedly following @cesswairimu's work on #4693 (if you have ideas on the readability of graphs, let us know!), also the tag visualization going on here with @skilfullycurled #1502, and the conversations on Community-Reps channel: https://github.com/orgs/publiclab/teams/community-reps

@skilfullycurled
Copy link
Contributor

skilfullycurled commented Jan 28, 2019 via email

@ebarry
Copy link
Member

ebarry commented Jan 28, 2019

Hmmm, can you see if you are in the "public lab organization"? https://github.com/orgs/publiclab/people

@jywarren
Copy link
Member

@skilfullycurled - maybe they're not publicly readable? but i think they are, i just don't know the link. 2 things to think about - first, we'd love to have you join that group, as it's purpose is: Be the voice of the Public Lab community in feature/bugfix discussions! -- but also, let's all remember that the "teams" feature is useful for some coordinating but is always to be balanced with the more public/inclusive option of simply posting an issue. In this case, I believe it was a place to have a discussion about an important design change without having to do it all right in front of a new contributor... very much appreciate the sensitivity! Thanks, all!

@jywarren
Copy link
Member

Also just to re-surface this call for a co-review process as our community grows here at plots2! #4707
-- Seeking reviewers!

Thanks everyone and great job posting the check-in this week, @geekychaser !!!

@skilfullycurled
Copy link
Contributor

skilfullycurled commented Jan 29, 2019 via email

@jywarren
Copy link
Member

I'd also like to request some help with breaking this issue down and getting it resolved. I don't think it'll be too hard and it'll make a big difference for oauth users.

Thanks all!!!

#4691

@cesswairimu
Copy link
Collaborator

Hi all,
This week am committed to get my open three PRs finished and merged.

@Yugandhartripathi
Copy link
Member

Hello everyone,
This week I plan to dive into PL.editor codebase and participate in brainstorming for soc 2019.

@IshaGupta18
Copy link
Collaborator

Hey Everyone, this week I plan to get my PRs for #4632 and #4413 merged. I will have to work on #4632 more to get it in place. Apart from this, I would love to solve more issues, here and and at mapknitter, and brainstorm on SOC ideas for 2019. Thanks for your constant efforts with my PRs @SidharthBansal and @jywarren . I would also like to pitch some ideas to you regarding SOC. Thanks a lot everyone!

@sashadev-sky
Copy link
Member

Hi all,

This week I have been working on standardizing the community check-in process #4718 #4692. It's moving along pretty well, comment on the first linked issue if you want to see any other changes :)
As per this weeks theme, I have also been going through open issues to review and offer help.

Thank you!

@Rishabh570
Copy link

Hello everyone,
My main goal for this week is to analyse and plan out the enhancements for code.publiclab.org (looking for the possibilities of different ideas). Also, as I'm currently working on MVC structure of community-toolbox, I'm getting lots of conflicts because of the recent changes in the code, just making my way through them 😅

Hope everyone is having an awesome week 🙌
Thanks!!!

@jywarren
Copy link
Member

Hi, everyone! Chiming in again to say that I added a new section to the gsoc page here:

https://publiclab.org/wiki/gsoc#How+to+apply

This just outlines the steps a bit and offers a bit more guidance. But don't worry, the big call for proposals as in previous years will be almost the same, and is not yet open.

Also noting that I helped @IshaGupta18 on #4413 but we weren't able to figure out why it's not matching in the test we've written! We're close to giving up and leaving the test out, but that's not so nice. If anyone would like a nice puzzle, any help appreciated!!!

@SidharthBansal
Copy link
Member

SidharthBansal commented Jan 31, 2019 via email

@jywarren
Copy link
Member

jywarren commented Feb 1, 2019

Hi, all! I'm also starting to put together a new Code Community Report, like this one from the start of the month, but summing up the whole year of 2018. If folks have statistics, big picture observations, other things like that which you'd like to suggest for the report, please chime in!

https://publiclab.org/notes/warren/01-02-2019/public-lab-code-community-report-jan-2019

@grvsachdeva
Copy link
Member

Hi @shubhscoder, you expressed interest in opening the check-in last week. So, would you be opening check-in for next week?

Thanks!

@shubhscoder
Copy link
Contributor

shubhscoder commented Feb 2, 2019 via email

@grvsachdeva
Copy link
Member

Great! You can open check-in on Monday too, there is no hurry. Also, @sashadev-sky @rexagod and I have prepared some guidelines for opening Check-in, please try to follow them - https://github.com/publiclab/plots2/pull/4718/files?short_path=5d68667#diff-5d686670ad182a95f3af0779f9940834

Thanks!

@shubhscoder
Copy link
Contributor

shubhscoder commented Feb 2, 2019 via email

@sashadev-sky
Copy link
Member

@geekychaser I made a mistake in my last check-in about the date the survey closes and I think you had already opened this issue by the time I updated it. I updated it here so that the correct date carries over from this week. Hope thats ok!

@shubhscoder please note the small change for your check-in :)

@grvsachdeva
Copy link
Member

New Check-In at #4757 . Thank you 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