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.

Sign up for GitHub

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

Jump to bottom

Convening teams + planning issues for Outreachy/Summer of Code #5684

Closed
jywarren opened this issue May 8, 2019 · 43 comments
Closed

Convening teams + planning issues for Outreachy/Summer of Code #5684

jywarren opened this issue May 8, 2019 · 43 comments
Labels
discussion gsoc outreachy planning Planning issues! summer-of-code

Comments

@jywarren
Copy link
Member

jywarren commented May 8, 2019

Hi, all! We have some more guidance coming for folks in our summer programs #5667 -- but I also want to encourage people to begin getting to know one another, and looking at who will be working together this summer.

Some of you are pretty much on a team together on one project, like @alaxalves and @kaustubh-nair -- although how you share the work needs to be planned out -- and others will be working on parts that link up with each other, like @ananyaarun and @CleverFool77 and @gautamig54, for one example (@ananyaarun's work on maps will be featured on several of the pages on PublicLab.org the others will be working on!)

So, this kind of thing needs some discussion, planning, and coordination. Please consider starting to transfer your proposal tasks into "planning issues" with checklists, as outlined in the "Modularity" blog post on https://publiclab.org/software-outreach -- and people can start to organize tasks among team members in such planning issues.

Some working in parallel may be necessary and helpful! Someone could work on the front-end, while someone else works on the controllers. Or one person could develop re-usable templates that the other plugs into overall page designs! Our UI teams have some to digest in our new Style Guide draft!

@CleverFool77 @ananyaarun @IshaGupta18 @namangupta01 @sidntrivedi012 @divyabaid16 @Divy123 @MargaretAN9 @ViditChitkara @aashna27 @gautamig54 @kaustubh-nair @rexagod @alaxalves

Mentors - I've assigned people more projects, just because I hadn't heard from everyone. I'm happy to change, add, reduce your projects, so please feel free to contact me; we can use the 'reviewers' Gitter room to coordinate. I'm sorry if you got lots of notifications, i don't mean to imply you /have/ to take on more projects, just wanted to get the ball rolling, and we can readjust now. Thanks! 🙌

Mentors so far: @jainaman224 @ebarry @sagarpreet-chadha @harshithpabbati @siaw23 @Souravirus @gauravano @Mridul97 @sashadev-sky @SidharthBansal
@jywarren
Copy link
Member Author

jywarren commented May 8, 2019 •
edited
Loading

And noting I've just added everyone above to @publiclab/soc - mentors and participants -- and will soon create the mentors list too!

Update: done -- for reviews, please see @publiclab/reviewers, but if you really need /just/ mentors, you can now use @publiclab/mentors. Thank you!

@jywarren jywarren mentioned this issue May 8, 2019
Closed
11 tasks
@SidharthBansal
Copy link
Member

Thanks Jeff. Let's plan things out.

@SidharthBansal
Copy link
Member

Hi @publiclab/soc team, all the participants are requested to open Planning issues like we did last summer.
For one project we can open up one planning issue. Example for MK Rails Upgrade we will have one planning issue in the MK repository where @kaustubh-nair and @alaxalves will coordinate.
We can follow this approach for all the projects.
Like Naman and Gautami for Notification System
Naman and Isha for the Sensor Data Project
Vidit and @divyabaid16 for MK synchronous editing project
and so on.
We can use the assign feature at the planning issue for assigning all the mentors and all the participants on those issues.
This will make us work highly managable and modular.
In case we will create gitter rooms then there are people who uses other IRC channel which does not provide ability to save the previous messages. This can create problem. So i think best approach will be to create planning issues which we did each year.

@kaustubh-nair
Copy link
Member

Sounds awesome.
@alaxalves and I will have a discussion over the weekend and put up the schedule and division of work on the planning issue accordingly.

@SidharthBansal
Copy link
Member

That will be simply awesome!!!
You can discuss and interact at the planning issue. Update the header of the issue as you progress through out the project

@SidharthBansal
Copy link
Member

@publiclab/soc also, we used the Milestones. Milestones are used to acertain the progress of the project. So, please add all your issues/prs/ftos into the milestone so that we can evaluate your progress by just reading the milestones.
You can use gsoc or outreachy label on the issues and prs.
Don't forget to break the planning issue into individual issues and link them to the main planning issue
Thanks

@SidharthBansal
Copy link
Member

SidharthBansal commented May 9, 2019 •
edited
Loading

#2676 and #2388 can help you folks for understanding how we do planning issues at pl. Thanks

@CleverFool77
Copy link
Member

Hi @jywarren and @SidharthBansal
I had a question.
Me and @gautamig54 will be working on UI.
So Should I open an issue containing all the division of works in checklists where we will look into the matter regarding coordination ?

@sagarpreet-chadha
Copy link
Contributor

Hi @CleverFool77 ,
Yes please go ahead . I also did the same during my gsoc :) #2671

@asquare14
Copy link
Member

asquare14 commented May 10, 2019 via email •
edited
Loading

@SidharthBansal
Copy link
Member

@asquare14 thanks for the suggestion. I think that feature requires things to be given by mentors. We need to give rights to create projects to the students if we want them to be listed under projects. @jywarren what you think is better option
Milestones/Projects?

@asquare14
Copy link
Member

asquare14 commented May 10, 2019 via email

@SidharthBansal
Copy link
Member

SidharthBansal commented May 10, 2019 via email

@asquare14
Copy link
Member

@SidharthBansal Found this great answer on stackoverflow ! Do give it a read https://stackoverflow.com/questions/39591795/what-is-the-difference-relationship-between-github-projects-and-milestones

@SidharthBansal
Copy link
Member

SidharthBansal commented May 10, 2019 via email

@grvsachdeva
Copy link
Member

Yeah, using GitHub projects is a better option. We already have many projects - https://github.com/publiclab/plots2/projects 😃.

@CleverFool77
Copy link
Member

Hi everyone.
So Should I create project under the name Outreachy 2019, In which I'll open various tasks like people section , questions section etc ?

@grvsachdeva
Copy link
Member

grvsachdeva commented May 11, 2019 via email

@gautamig54
Copy link
Contributor

gautamig54 commented May 11, 2019 •
edited
Loading

@CleverFool77 The idea sounds great. You can open issue saying "UI improvements - Summer 2019" or something like this and we can start the discussions and divide the work for different webpages.
@namangupta01, I can open an issue for "Notification System" and start the discussion and divide the work accordingly. Thanks!

@SidharthBansal
Copy link
Member

SidharthBansal commented May 11, 2019 via email

@CleverFool77
Copy link
Member

CleverFool77 commented May 11, 2019 •
edited
Loading

Hi @gautamig54 and everyone
I just opened the project for UI improvements. Now all the new cards and checklists will be added there.
@gautamig54 I guess we can start off with our checklists.
Now all the issues for UI improvements in summer of code would added there.
How do we divide them ?
Should I divide the whole project into sections of people, question, dashboard , tags etc.
And every section into further todos parts?
It would be great to hear some suggestions regarding the protocol followed in projects as I never used one before.
Thank You.

@SidharthBansal
Copy link
Member

SidharthBansal commented May 11, 2019 via email

@namangupta01
Copy link
Member

namangupta01 commented May 11, 2019 via email

@SidharthBansal
Copy link
Member

Best Of Luck Naman.

@SidharthBansal
Copy link
Member

Please link milestone/projects/planning issues here.

@SidharthBansal
Copy link
Member

publiclab/mapknitter#305

@SidharthBansal
Copy link
Member

publiclab/mapknitter#593
@divyabaid16 @vidit here is issue for you. You asked me to open for you. Please feel free to make it as per your project requirements.
Best of luck

@sidntrivedi012
Copy link
Member

sidntrivedi012 commented May 13, 2019 •
edited
Loading

@jywarren @SidharthBansal Opened the Planning issue in Spectral-workbench.js for the Spectral Workbench Capture project. Please review. publiclab/spectral-workbench.js#92

I will be adding more sub-tasks in a detailed format to the issue shortly. I am currently somewhat busy due to my university exams which will be ending on 22nd May. Though, I will try to keep up with the work to be done and going on here.

Thanks 🙂

@SidharthBansal
Copy link
Member

Awesome!!!
Best of luck to you all!!!
I have my exams till 19th(on Sunday too!!!).
My university wants us to study even at weekends.. lol...hahaha

@jywarren
Copy link
Member Author

This is looking great, folks! I've been trying to go in and give deeper comments on each project's planning issues every couple days. I just did this here: publiclab/leaflet-environmental-layers#168

Actually i'm noticing that there are a lot of projects this year which will be getting started in a separate repo outside plots2 but with the intention of re-integrating later. This is cool and it's a great approach. I've started trying to connect folks who are working in this way. I know @IshaGupta18 @namangupta01 have just gone through this process quite quickly! This may be relevant to @Rishabh570 as well, in terms of how to architect a stand-alone JS library.

Note that folks like @gautamig54 @CleverFool77 don't need to do this - your work will be right in plots2. But for those working on satellite libraries or general purpose libraries or like @sidntrivedi012 or @rexagod on a satellite library to another codebase, you can rely on each other a lot for guidance and ideas and helpful critique on how to structure your projects.

Awesome to see everyone getting organized and ready! 🎉 🎉 🎉

@gautamig54
Copy link
Contributor

@CleverFool77 Thanks for opening a project for UI improvements. I think it is better to have a separate issue for each page which can be added in the to-do list for the project. Also, I will open up an issue which will list down the pages which we need to focus on or any other UI improvements and we can discuss our summer plan there. It will be helpful for an organised start to the project as our entire summer plan will be at a single place.

@jywarren
Copy link
Member Author

jywarren commented May 16, 2019 via email

@gautamig54
Copy link
Contributor

I have opened a project for the Notification System. @namangupta01 Can you have a look at it and add if I missed something. Also, should I create an issue for the Notification System project for discussions?

@SidharthBansal
Copy link
Member

SidharthBansal commented May 17, 2019 via email

@Divy123
Copy link
Member

Divy123 commented May 17, 2019

@aashna27 , @publiclab/mentors I have added the project for Image Sequencer here:
https://github.com/publiclab/image-sequencer/projects/2
Aashna you can add your set of issues as well by breaking them up as suitable for you. Also we can collaborate upon and keep on breaking some issues as suitable.

@CleverFool77
Copy link
Member

@CleverFool77 Thanks for opening a project for UI improvements. I think it is better to have a separate issue for each page which can be added in the to-do list for the project. Also, I will open up an issue which will list down the pages which we need to focus on or any other UI improvements and we can discuss our summer plan there. It will be helpful for an organised start to the project as our entire summer plan will be at a single place.

Hi @gautamig54 .
That's exactly what I followed. I tried keeping different issue for each section.
And In each section , I added further checklists based on division of work.
We'll be adding these issues in todos of projects. It would make the process convenient and easy
Thanks !!!

@namangupta01
Copy link
Member

Hi @gautamig54, I have added some tasks in the project and will add some soon.

@SidharthBansal
Copy link
Member

SidharthBansal commented May 21, 2019 via email

@asquare14
Copy link
Member

@SidharthBansal Can you please add me to the reviewers chat on gitter so that I can discuss a few things with you all ! :)

@jywarren
Copy link
Member Author

jywarren commented May 28, 2019 via email

@grvsachdeva
Copy link
Member

@jywarren actually the reviewers' group is an invite-only group. I just added you @asquare14 to the group. Welcome 🎉 !!

@asquare14
Copy link
Member

asquare14 commented May 29, 2019 via email

@jywarren
Copy link
Member Author

jywarren commented Sep 4, 2019

Great work everyone!!!!

@jywarren jywarren closed this as completed Sep 4, 2019
@jywarren jywarren mentioned this issue May 5, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion gsoc outreachy planning Planning issues! summer-of-code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests