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

Welcome Google Code In Students #3698

Closed
SidharthBansal opened this issue Oct 13, 2018 · 34 comments
Closed

Welcome Google Code In Students #3698

SidharthBansal opened this issue Oct 13, 2018 · 34 comments
Labels
gci-candidate outreach issues involve community involvement and helping people who're stuck somewhere
Projects
Google Code-In

Comments

@SidharthBansal
Copy link
Member

SidharthBansal commented Oct 13, 2018 •
edited by jywarren

Hello folks from Google Code In - I realised we don't have a main place for you all to ask questions and get support, so I wanted to say WELCOME and create this issue as a discussion zone. Please leave a comment to say hello, in part so we know who's interested in the program! @publiclab/mentors please keep an eye open for opportunities to welcome and support our Google Code In students! 👍 🎉

First contribution

It's so great to see that several of you have made your first contribution. 🙌 This should really help as all our contributions follow this workflow. If you haven't yet, please see this page to get started:

https://code.publiclab.org#r=all

Students are advised to do 2 first-timer-only or fto-candidate issues as their primary task at Public Labs. They are considered as beginner task on Public Lab.

What next?

If you're looking for a next project, I might recommend one which starts to involve multiple files in the application code, so you can start to get a better understanding of the application's workings. Are you familiar with how a Rails application works, in terms of how the model accesses the database, the controller performs the logic, and the views display the actual web pages? If not, we can help you start to pick apart how our system works one piece at a time.

You can find a lot of relatively small but not completely documented issues here:

fto-candidate issues which are meant to be solved by first timers but aren't well-formatted yet

If you choose one, please leave a comment and we can do our best to help find any missing information or help guide you through the next steps. Don't hesitate to ask questions!

Larger collections of tasks can often be found under the break-me-up label, which you can go through to find smaller projects to "break off" and solve:

break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration

We also have many other projects on Node js and Javascript. You can see the complete collection on https://github.com/publiclab . They are also part of Google Code In Program.

Supporting tasks

Another area you might be interested in contributing is in supporting other new people to the project. This is an often unrecognized part of a healthy collaborative project, so we've made these issues to encourage people to take part in this crucial activity. We'd love your help, and as a newcomer yourself, you know exactly what it feels like to be new, so you know how important it is to be welcoming and supportive!

https://github.com/publiclab/plots2/wiki/Google-Code-In-Tasks
These tasks are multiple use tasks

Help wanted tasks

These are a little tougher tasks than the beginner level tasks. But don't worry @publiclab/mentors are there to help you out whenever you get stuck. All the tasks which have gci-candidate label on them but don't have fto-candidate nor first-timers-only tag are considered as help-wanted tasks.
These tasks include design, documentation, support, testing, coding, adaptability, code enhancements etc.

There are many tasks which are present on github but due to lack of time we are not able to publish them on GCI dashboard. They are a part of GCI and will be considered under evaluation. So, please search the tasks from github rather than from GCI task list for Public Labs.

Thanks and we're happy to answer questions!!
@SidharthBansal SidharthBansal added outreach issues involve community involvement and helping people who're stuck somewhere gci-candidate labels Oct 13, 2018
@SidharthBansal SidharthBansal mentioned this issue Oct 13, 2018
Closed
@vishalka98
Copy link
Contributor

hello, i'm interested in this program

@Dayitva
Copy link

Dayitva commented Oct 24, 2018

Hello from Indonesia. Hoping to have great fun participating in GCI this year.

@ho-dor
Copy link

ho-dor commented Oct 26, 2018

Hello. I am a first-time contributor. Help me to get started with rails and open-source.

@avsingh999
Copy link
Member

@ho-dor great, welcome to you in publiclab
here https://code.publiclab.org/ find the issue and solve it
thanks :)

@SidharthBansal
Copy link
Member Author

Some support tasks are available here
https://codein.withgoogle.com/dashboard/tasks/5765666616377344/
https://codein.withgoogle.com/dashboard/tasks/5108091688321024/
https://codein.withgoogle.com/dashboard/tasks/5313931938627584/
https://codein.withgoogle.com/dashboard/tasks/5897760814399488/
Claim the tasks which you have not yet. Please tell the work done on the GCI dashboard itself.
@okonek @oorjitchowdhary @kevinzluo and all other GCI students are requested to take them if they have not yet.

@SidharthBansal
Copy link
Member Author

Many of the GCI folks will be joining the University/College next year. So, if you are willing for internships like GSoC, Outreachy, RGSoC etc. you can plan for next year with Public Lab by contributing even after GCI.

@kevinzluo
Copy link
Collaborator

Unfortunately the first 2 tasks are marked as beginner (GCI students are only allowed to complete 2 beginner tasks), so I and many others are currently unable to complete them. I will try to do the rest 👍 .

@SidharthBansal
Copy link
Member Author

@kevinzluo thanks for reporting.
@jywarren I have created two tasks so that non beginners can also help us. They are INTENTIONALLY duplicate tasks
https://codein.withgoogle.com/dashboard/tasks/5464186466336768/
https://codein.withgoogle.com/dashboard/tasks/6406765190053888/

@SidharthBansal
Copy link
Member Author

Whenever any GCI student does any of the following task the student will get credit
https://github.com/publiclab/plots2/wiki/Google-Code-In-Tasks
So, if you can't find these support tasks on GCI we will be happy to create an issue for you.

Also, there is a nice list of fto-candidate issues on the plots2. You can earn credits by converting it to the first-timers-only issue by using first timers template.
Thanks

@SidharthBansal
Copy link
Member Author

@dinaelhanan @publiclab/mentors @JonathanXu1 @uzorjchibuzor @oorjitchowdhary @kevinzluo @champagnepappi @ValentinaTironi @okonek @shubhscoder and others. Sorry if I could not add your name here.

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 7, 2018 •
edited

Here is list to ftos https://github.com/publiclab/plots2/issues?q=is%3Aopen+is%3Aissue+label%3Afto-candidate
Only convert those which are required and are not well formatted with code links, potential solution and problem statement.

@SidharthBansal SidharthBansal mentioned this issue Dec 8, 2018
Closed
20 tasks
@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 10, 2018 •
edited

I think deadline has passed.
Well done guys.
You are all awesome. 🎉 🛩️ 😄
No more tasks can be claimed. Students are requested to work on their pending tasks

@oorjitchowdhary
Copy link
Member

oorjitchowdhary commented Dec 10, 2018 •
edited by SidharthBansal

GCI is almost over...
So I request all the students @ValentinaTironi @JonathanXu1 @kevinzluo @dinaelhanan @CodeSarthak @thesparks @okonek to please give a great round for applause for all our mentors who have helped us in every task, every little thing and have taught extraordinary new things..
So this one's for the mentors, @publiclab/mentors @publiclab/reviewers !!!

🎉 🎉 💯

@SidharthBansal
Copy link
Member Author

Thanks all of you

@SidharthBansal
Copy link
Member Author

Sorry for those whose names are not included but they did participate in the contest.
The 🎉 emoticons are having dynamic behaviour. Nice to catch them in your last comment.

@vatbq
Copy link
Contributor

vatbq commented Dec 10, 2018

Thank you too much! I was so scared when it started, I thought I couldn't do this but now we are here!! That's really amazing 💯 This is my last opportunity to participate on GCI, my 18th year is near but It was a fantastic experience! Thank you thank you all! 🎉 🎉

@digitaldina
Copy link
Collaborator

I loved it too! It was my first time writing and ruby code and the help from the community was fantastic, but what was even more fantastic was working on a project that makes an impact on the environment, loved every minute!

@jywarren
Copy link
Member

jywarren commented Dec 10, 2018 via email

@jonxuxu
Copy link
Member

jonxuxu commented Dec 10, 2018

Thank you so much for this wonderful experience. This was my first time contributing to open-source and it was absolutely eye-opening. I really appreciate the mentors' swift and helpful support, as well as the friendliness of all the other collaborators.

You guys have made this an event to remember :)

@kevinzluo
Copy link
Collaborator

Yes, a big thanks goes out to all of the mentors who have helped make GCI an incredible experience this year!

You all have taught me that through collaboration and a positive spirit, we can accomplish great things. Not once in this past 1 and a half months have I seen a mentor post anything negative or insulting. I will forever cherish this event in memory 😃 .

@jywarren
Copy link
Member

We'd love to thank people via the Public Lab Twitter account (https://twitter.com/publiclab) as well, or any other social media you have if you'd like to paste it in here 👍 We always want to celebrate our great community members 🎉

@grvsachdeva
Copy link
Member

Awesome work everyone 🎉 ! We really enjoyed working with all of you and would love to continue working. I guess all of you have got the real taste of Open Source by collaborating with each other for creating something big.

GCI might get over soon, but we would love to have you as a part of Public Lab ❤️.

@tsparksh
Copy link
Member

Thank you! This is a wonderful experience for me. I really enjoyed solving tasks and writing issue, I will never forget these days

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 11, 2018 via email

@kevinzluo
Copy link
Collaborator

@SidharthBansal Sorry to bother, but are you referring to the deadline posted on gitter (You all are informed that me, gaurav, sagarpreet will not be available from 9:30 IST today. Get your stuff done before it.), or the deadline of December 12 on the GCI website?

Thank you,
Kevin Luo

@kevinzluo kevinzluo mentioned this issue Dec 11, 2018
Merged
20 tasks
@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 11, 2018 via email

@kevinzluo
Copy link
Collaborator

Alright, thank you for the clarification!

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 11, 2018 via email

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 11, 2018 via email

@SidharthBansal
Copy link
Member Author

@jywarren as GCI deadline to claim task is over, I have removed gci-candidate labels from plots2.

All GCI students who are working on the issues taken up(by a comment on GitHub or claimed at GCI website, etc) can continue to work on them until the deadlines.
If you have done some work, then it will be judged for sure. Each and every work will be judged.

Many of the students will be stressed about the results. Somebody wrote yesterday, that he is stressed a lot. I will like to suggest that you should be happy instead of being stressful. You all did a very nice job this year. As we have a limited number of slots for prizes, so we cannot give you all prizes.
For those who will win the prizes it means they are currently having great capabilities 🎉 👍 💯 Winners are suggested to keep bringing changes in themselves so that they will become better day by day.
Those who will not win the prizes: They did a great job. They were opened to open source. They contributed to real time software. Isn't this big? You can learn from your mistakes. You learnt what git is. Git is a tough subject. You learnt rails, html, css, and a lot of stuff. You came to know how to interact with people globally. You came to know how to collaborate on a large scale. You came across the different phases of Life Cycle Model for the Software through following
Requirements: You all learnt how to raise issues and brainstorm them. Find different ways to elaborate on different ideas and notions. You to create checklists. How to break down stuff into smaller pieces.
Design and Implementation: You learnt how to apply changes to get the code work what we discussed in the requirement phase.
Testing: Many students worked at different types of test unit tests, controller tests, integration tests, etc.
Maintenance phase: You learnt how to enhance the existing code. We enhanced the existing login system to have better UI. It can't be achieved without you all. Bug fixing comes into play here. We came across so many bug fixes. Great to see your work.
Be leaders for the organisation: You created First timer issues. They were meant to teach you lessons of mentoring, collaborating etc. At Public Lab, we teach collaborators from beginner level.
I think the above plan for the GCI was completed. You all did all types of tasks. So, why are you stressed up? Learning is a continuous curve and will never reach an end. It is a starting. You will fall, then you have to rise up again. If you will never fall then how can you rise?
I hope that you all enjoyed learning all above things.
In case even if you will feel dishearted about the result, then you can try again next year. We are there to help you always. We want no one to be stressed. Be cool. Have fun. You are children and stress word should not appear within you ever.
In case you are ineligible for GCI next year, then you can think to participate into Open Source through other means, like GSoC, Outreachy, RGSoC etc. We run all the three programs. Don't ever lose hope. Continue coding and be happy.

@vatbq
Copy link
Contributor

vatbq commented Dec 11, 2018

OH, It was so beautiful @SidharthBansal, Thank you for support us! I'm so stressed, nervous, and scared too. Also, I'm sick now and I can't be looking for a long time the computer because I've a headache and It hurst a lot.
I think all of us did an awesome work here, everyone is really great :) Continue like this and you're going to get very far! It was a pleasure ❤️

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Dec 11, 2018 via email

@vatbq
Copy link
Contributor

vatbq commented Dec 11, 2018

Yes, I'll do that when I finish some pending here :) I almost finish, don't worry. Thank you ❤️

@jywarren
Copy link
Member

jywarren commented Dec 11, 2018 via email

@jywarren jywarren closed this as completed Jan 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
gci-candidate outreach issues involve community involvement and helping people who're stuck somewhere
Projects
No open projects
Google Code-In
Awaiting triage
Milestone
No milestone
Development

No branches or pull requests