search

publiclab / plots2

a collaborative knowledge-exchange platform in Rails; we welcome first-time contributors! :balloon:
https://publiclab.org
GNU General Public License v3.0
961 stars 1.83k forks source link

Call for Outreachy Proposals!!! #3726

Closed SidharthBansal closed 6 years ago

SidharthBansal commented 6 years ago

We are having Planning for expanded community stats system as our Outreachy Project this winter. Refer #3498

Folks are requested to post the plan for the fellowship program in form of proposal. They can brainstorm project related ideas here.

Update

We now have an official call for proposals posted at PublicLab.org, here:

https://publiclab.org/notes/warren/10-23-2018/call-for-outreachy-2018-19-proposals

I need to check the exact requirements in Outreachy but these have some of the kind of information that will be helpful in framing out a proposal: https://publiclab.org/notes/warren/02-28-2017/call-for-proposals

I hope this is helpful! A few tips for making awesome proposals:

These tips are general tips. Are you tensed? No need to worry!!! :smile: We all are there to help you at each stage of proposing the proposal to the manufacturing of the end product. So just be happy and code.

Best of luck folks. :tada: Hope we will have great time this year with you all. :+1: Here's the one for this last year's program! :1st_place_medal: :1234: :100: https://publiclab.org/notes/warren/02-15-2018/call-for-summer-of-code-2018-proposals

Thanks and more soon! :smile: :tada:

We are participating in Outreachy for the first time. Hoping you all will have awesome experience!!!

quinn-codes-synthesis commented 6 years ago

What's the best way to go about this if we're not really sure what timeline to expect of ourselves? i.e. I'm generally a very fast learner, but I haven't yet had the opportunity to see how quickly I pick things up when I'm coding full-time (currently in an unrelated full-time job, coding whenever I can carve out some free time in my schedule). I'm also thinking I should build in some buffer time for things like getting stuck on an issue, debugging, research for how best to tackle a problem, etc etc.

I guess what I'm asking is -- should I be stressing about figuring out an exact schedule and sticking to it, or is this more about making a rough statement of goals and priorities broken down by week?

SidharthBansal commented 6 years ago

We want an expected schedule so that we can check your progress. No strict schedule needed. Just we want to introduce modularity into the big project so that the project can be reviewed in pieces and can be merged in pieces. The timeline helps us to help you in different phases of the project.

Yes it is a good idea to plan out some time for bug fixes, documentation, testing etc.

SidharthBansal commented 6 years ago

Hi Quinn, Glad to see you. We are looking for an expected timeline so that we can see your progress throughout the project. With help of the timeline, we introduce modularity into the project so that each piece of code is reviewed thoroughly and merged.

Yes it is great idea to include testing, bug fixes, documentation into the proposal.

No strict deadlines are needed. Just give how you want to break down the project into different weekly tasks.

Best of luck for proposal.

On Mon, Oct 22, 2018, 12:49 PM Quinn notifications@github.com wrote:

What's the best way to go about this if we're not really sure what timeline to expect of ourselves? i.e. I'm generally a very fast learner, but I haven't yet had the opportunity to see how quickly I pick things up when I'm coding full-time (currently in an unrelated full-time job, coding whenever I can carve out some free time in my schedule). I'm also thinking I should build in some buffer time for things like getting stuck on an issue, debugging, research for how best to tackle a problem, etc etc.

I guess what I'm asking is -- should I be stressing about figuring out an exact schedule and sticking to it, or is this more about making a rough statement of goals and priorities broken down by week?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/publiclab/plots2/issues/3726#issuecomment-431757235, or mute the thread https://github.com/notifications/unsubscribe-auth/AUACQ1iR9jtcQRd8uQ8UWh78QgolqG1Jks5unXFmgaJpZM4XyK0H .

SidharthBansal commented 6 years ago

rough statement of goals and priorities broken down by week?

Is OK.

On Mon, Oct 22, 2018, 12:57 PM Sidharth Bansal < bansal.sidharth2996@gmail.com> wrote:

Hi Quinn, Glad to see you. We are looking for an expected timeline so that we can see your progress throughout the project. With help of the timeline, we introduce modularity into the project so that each piece of code is reviewed thoroughly and merged.

Yes it is great idea to include testing, bug fixes, documentation into the proposal.

No strict deadlines are needed. Just give how you want to break down the project into different weekly tasks.

Best of luck for proposal.

On Mon, Oct 22, 2018, 12:49 PM Quinn notifications@github.com wrote:

What's the best way to go about this if we're not really sure what timeline to expect of ourselves? i.e. I'm generally a very fast learner, but I haven't yet had the opportunity to see how quickly I pick things up when I'm coding full-time (currently in an unrelated full-time job, coding whenever I can carve out some free time in my schedule). I'm also thinking I should build in some buffer time for things like getting stuck on an issue, debugging, research for how best to tackle a problem, etc etc.

I guess what I'm asking is -- should I be stressing about figuring out an exact schedule and sticking to it, or is this more about making a rough statement of goals and priorities broken down by week?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/publiclab/plots2/issues/3726#issuecomment-431757235, or mute the thread https://github.com/notifications/unsubscribe-auth/AUACQ1iR9jtcQRd8uQ8UWh78QgolqG1Jks5unXFmgaJpZM4XyK0H .

quinn-codes-synthesis commented 6 years ago

Fantastic, thank you!

(the below is crossposted at #3498)

Woops, Github was being finicky yesterday and I ended up asking basically the same question here and in the other thread (it wasn't showing me that the post went through).

Thanks for the response! What is the best way to submit a proposal work-in-progress? Email to you and the other mentors, posting it here, something else? Through the Outreachy site directly?

SidharthBansal commented 6 years ago

We will have public conversation always so as to have open source environment as Outreachy is open source. You need to create research notes on publiclab.org Tag the mentors with their names.

quinn-codes-synthesis commented 6 years ago

Ah, research notes. That's the tidbit I was missing. Thank you so much!

SidharthBansal commented 6 years ago

Don't forget to fill the proposal on main outreach website before the deadline.

We want to help you with your application so we are reviewing it on publiclab research notes section.

Actual evaluation will be based on the final application ie proposal submitted to Outreachy website. So don't forget to submit them on the Outreachy website.

Does this makes sense?

On Tue, Oct 23, 2018, 1:37 PM Quinn notifications@github.com wrote:

Ah, research notes. That's the tidbit I was missing. Thank you so much!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/publiclab/plots2/issues/3726#issuecomment-432140914, or mute the thread https://github.com/notifications/unsubscribe-auth/AUACQ9C8dgMI91yRL6cbIE7_IUsh6V_Gks5uns49gaJpZM4XyK0H .

quinn-codes-synthesis commented 6 years ago

Yep, perfect!

What is the appropriate method for tagging a user on Public Lab? I see the syntax [username](/profile/username) is mentioned here as a method to link a user's profile -- but I thought that perhaps you meant writing warren, bansal_sidharth2996 et al. in the tags section, so I figured I'd clarify. :)

SidharthBansal commented 6 years ago

Yeah you are right. Jeff has @warren username. You just need to list the names by seeing them on their profiles

On Tue, Oct 23, 2018, 2:22 PM Quinn notifications@github.com wrote:

Yep, perfect!

What is the appropriate method for tagging a user on Public Lab? I see the syntax username is mentioned here https://publiclab.org/wiki/authoring-help as a method to link a user's profile -- but I thought that perhaps you meant writing warren, bansal_sidharth2996 et al. in the tags section, so I figured I'd clarify. :)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/publiclab/plots2/issues/3726#issuecomment-432157227, or mute the thread https://github.com/notifications/unsubscribe-auth/AUACQ2juGzGFRZvDQOtUD3yPdq4x7ahoks5untjKgaJpZM4XyK0H .

jywarren commented 6 years ago

(@quinn-codes-synthesis this should help you post!)

Hi, everyone! I'm sorry there was some confusion -- since, unlike in our other Summer of Code programs, we have a single project we've submitted, we weren't sure we needed a call for proposals page. But although we'd love to see group discussion and collaboration around refining the proposals, it does seem helpful to ask each applicant to post a draft proposal (in addition to the one you'll send to Outreachy.org).

So I've posted a call for proposals here, where I'd like to ask each of you to open a draft proposal and get some comments on it! Thank you!!

https://publiclab.org/notes/warren/10-23-2018/call-for-outreachy-2018-19-proposals

ghost commented 6 years ago

University and college students who are applying are requested to provide information about their school calendar and class credits. We will ask for your current term and your next term. Please have that information before starting the process.

SidharthBansal commented 6 years ago

All the participants of Outreachy are requested to submit the application before October 30 at 4pm UTC on the main Outreachy website. Failure to do so will result in failure from the Outreachy program.

Applicants who create an application can edit it until the project application deadline. After your project's application deadline, applicants will NOT be able to create a new application. Applicants who have submitted an application cannot edit their application, but they will be able to continue recording and editing their contributions on the Outreachy website until the intern announcement deadline on Nov. 16, 2018 at 4pm UTC. Applicants who have not submitted an application will not be able to record or edit their contributions.

quinn-codes-synthesis commented 6 years ago

Phew! Proposal posted.

I am a little confused on whether the application needs to be finalized on the 30th or on the 6th -- I had thought the deadline had been postponed, but I'm still seeing some comments (like the one just above) that say the 30th.

Anyway, I welcome feedback so I can polish it in whatever time we have left!

sagarpreet-chadha commented 6 years ago

Hi ! The deadline is Nov 6 , 4 PM UTC 🕓 ⏳ .

SidharthBansal commented 6 years ago

We have extended it. So that you can work on your proposals well. :smile:

SidharthBansal commented 6 years ago

No more new applicants can submit the idea for project. The deadline is over.