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

SoC Ladder Documentation #3319

Closed
SidharthBansal opened this issue Sep 14, 2018 · 12 comments
Closed

SoC Ladder Documentation #3319

SidharthBansal opened this issue Sep 14, 2018 · 12 comments
Labels
big for Google Code-In documentation feature lacks proper documentation or needs more documents gci-candidate

Comments

@SidharthBansal
Copy link
Member

SidharthBansal commented Sep 14, 2018

Write documentation on how to start contributing to Public Labs for SoC.
Make a list of repositories included in Public Labs. Explain the steps included in the program.
We are preparing to participate in Google Code-in, and have reserved this issue for participants in GCI - but we'd love to have your help with another one! Please check out https://code.publiclab.org to see more.

@SidharthBansal SidharthBansal added the documentation feature lacks proper documentation or needs more documents label Sep 22, 2018
@SidharthBansal SidharthBansal changed the title GSoC Ladder Documentation SoC Ladder Documentation Oct 22, 2018
@SidharthBansal
Copy link
Member Author

We participate in Outreachy, GSoC and RGSoC every year.
We need to tell how to start contributing to Public Labs by helping them at each step. How nice would it be if we can aggregate all the code links, repository links, installation, first timer issue, help wanted issues, pr reviews into a single document so that the new aspariant can follow that ladder and can climb it to have a sure chance in SoC program.
This can result in reducing the mentors effort a lot. Because people will know what is going to be their next step.
This is a big issue.

@SidharthBansal SidharthBansal added the big for Google Code-In label Oct 22, 2018
@SidharthBansal
Copy link
Member Author

This task is published on GCI dashboard. Thanks all.

@oorjitchowdhary
Copy link
Member

Can you explain more about this issue... where is the document to be created? in a pull request? or somewhere else

@SidharthBansal
Copy link
Member Author

@oorjitchowdhary the task is no longer needed.

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Nov 10, 2018 via email

@oorjitchowdhary
Copy link
Member

@oorjitchowdhary the task is no longer needed.

Okay.. No problem..

@oorjitchowdhary
Copy link
Member

The /gsoc page is updated in accordance to the issue at time of Outreachy applications. Now it is not needed. I have given you credits on GCI dashboard. Thanks

On Sat, Nov 10, 2018 at 7:12 PM Oorjit Chowdhary @.***> wrote: Can you explain more about this issue... where is the document to be created? in a pull request? or somewhere else — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#3319 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AUACQ6fH9mvToruBKbZ2CNSewk3BkOtdks5uttfhgaJpZM4Woq1y .

How do you give credits to me? Is it like a bonus task?

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Nov 10, 2018 via email

@oorjitchowdhary
Copy link
Member

Oh.. so I just have to claim it at the GCI website then right? Coz I'm doing another task right now and wanted to do this task simultaneously...

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Nov 10, 2018 via email

@oorjitchowdhary
Copy link
Member

oorjitchowdhary commented Nov 10, 2018

Ohk.. Thanks a lot.. I appreciate it..

@SidharthBansal
Copy link
Member Author

SidharthBansal commented Nov 10, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big for Google Code-In documentation feature lacks proper documentation or needs more documents gci-candidate
Projects
None yet
Development

No branches or pull requests

2 participants