-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Help with Project proposal for Outreachy internship #3896
Comments
Thanks for opening your first issue! This space is protected by our Code of Conduct - and we're here to help. |
Let's start with #3498 , as you can see on this issue that the project is already somewhat divided into parts. Now, what you have to do is design your timeline by considering these:-
Its upto you which points you like to consider. @jywarren @sagarpreet-chadha @SidharthBansal please add more points. Thanks! |
For starting, you can copy the project parts here as given and then assign a week to each part. |
Hi Outreachy Applicants, we will really appreciate if you can get involved the general contributors to your project by creating |
Hi @gauravano thanks again for this detailed guide. Can I claim #3498 and work on it throughout or do I have to add more to it? |
Actually, the issue #3498 is the outreachy project which would be solved by
the selected intern. But, you can add the steps on solving the issue in
your application if you have given thought about implementation.
Gaurav Sachdeva
…On Mon 5 Nov, 2018, 7:12 PM love-opensource, ***@***.***> wrote:
Let's start with #3498 <#3498>
, as you can see on this issue that the project is already somewhat divided
into parts. Now, what you have to do is design your timeline by considering
these:-
1. you could further subdivide a part as per your convenience
2. At public lab we follow modularity, so we prefer the method of
solving a part of project per week and then its testing and then proceeding
to other part
3. Considering buffet time so that if your strategy goes wrong you
would have time to correct it
Its upto you which points you like to consider.
@jywarren <https://github.com/jywarren> @sagarpreet-chadha
<https://github.com/sagarpreet-chadha> @SidharthBansal
<https://github.com/SidharthBansal> please add more points. Thanks!
Hi @gauravano <https://github.com/gauravano> thanks again for this
detailed guide. Can I claim #3498
<#3498> and work on it
throughout or do I have to add more to it?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3896 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT6S9h_5J_UkeIA8rXi2GE8Nx28gV26pks5usEAygaJpZM4YOCPx>
.
|
I have approved your proposal on https://publiclab.org , so you can
continue to edit it. Thanks!
…On Mon, Nov 5, 2018 at 11:00 PM love-opensource ***@***.***> wrote:
Hello, please while writing my proposals, I mistakenly submitted it while
it was incomplete. Right now I can't edit it as it's under review.
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3896 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT6S9ho44oV60wb2I3xp-DFUjlrCQPENks5usHWZgaJpZM4YOCPx>
.
|
I think we can close this issue as we have met outreachy proposal submission deadline. |
Please describe the problem (or idea)
As an Outreachy intern, one is required to submit a timeline of the work an intern plans to accomplish during the internship. In that regard and as a new contributor, I need some guids and help from the mentors.
This is a call to help for the accomplishment of the last phase of the application process.
@gauravano
Please show us where to look
https://publiclab.org/ ...
What's your PublicLab.org username?
Browser, version, and operating system
Thank you!
Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.
To learn how to write really great issues, which increases the chances they'll be resolved, see:
https://publiclab.org/wiki/developers#Contributing+for+non-coders
The text was updated successfully, but these errors were encountered: