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.

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.

Thank you, Sidharth. Folks - we're just trying to be sure you don't miss out on this! Many thanks for your interest in working with us 😃 🎉

Hi, all! Just added one more item, which I'd like to see incorporated; it should be relatively easy to add in:

• script to go back through posts and tag first-timer posts with first-time-poster tag, retroactively so they show up at https://publiclab.org/tag/first-time-poster, to improve stats on first-time posting

Does this make sense? Thank you! @radhikadua @quinn-codes-synthesis @cess

Also, as @sagarpreet has noted elsewhere, we are on the extended Nov 6th deadline, so you still have a bit of time!

And, @gauravano has joined our mentoring team! Welcome!

Hi @warren,

script to go back through posts and tag first-timer posts with first-time-poster tag, retroactively so they show up at https://publiclab.org/tag/first-time-poster, to improve stats on first-time posting

Sounds good to me. Also, along with that, I think all the new posts which are created by new contributors, they should automatically be tagged to keep the stats correct.

Thanks!

I believe the second part is already complete! We implemented it a few weeks ago :-)

Thanks!

On Thu, Nov 1, 2018 at 5:41 PM \<notifications@publiclab.org> wrote:

Hi! You were mentioned by radhikadua in a comment on the research note Call for Outreachy 2018-19 proposals!. You can reply to this email or visit this link:

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

radhikadua wrote:

---

Hi @warren, script to go back through posts and tag first-timer posts with first-time-poster tag, retroactively so they show up at https://publiclab.org/tag/first-time-poster, to improve stats on first-time posting Sounds good to me. Also, along with that, I think all the new posts which are created by new contributors, they should automatically be tagged to keep the stats correct. Thanks!

---

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

Report abuse to: moderators@publiclab.org

Check out the blog at https://publiclab.org/blog | Love our work? Become a Public Lab Sustaining Member today at https://publiclab.org/donate
Reply with the email you use at PublicLab.org and your comment will be posted to the website.

Was trying to submit my proposal but the button keep getting stuck in the spinning position, so I thought it wasn't submitted and I had something like a wifi issue. I just check my dashboard and realized that they are in pending. Sorry about the repeat submission!

Hi, everyone - thanks for your proposals -- one thing I mentioned in a couple places that I think may be useful --

I think it would be great to see a few links to different areas of the existing codebase - to give a better sense of where these features and new code segments would be implemented, and how they relate to existing code. What would go into a model, a controller, a view? Are you familiar with the MVC model and how to break up code among these parts?

These are key and useful questions which can help to give better detail to your proposals and help you break up your work into smaller, more easily tested and maintained parts. It's also great for debugging because if each pull request you make does only one thing, it's easier to review and merge in piece by piece, without the worry that changing one function will break or affect another.

For more on modularity and why it's helpful, check out the piece I wrote on modularity on our software outreach page! https://publiclab.org/software-outreach

Thanks everyone as we approach our Nov 6th deadline!

@cess @quinn-codes-synthesis @faithngetich188 @radhikadua @amychan331 @thayshi @bansal_sidharth2996 @gauravano @sagarpreet

Also, just a reminder to @thayshi and @faithngetich188 and anyone else interested - i don't see your final proposals on the Outreachy dashboard, so be sure to get them submitted before Nov 6th! Thanks!! 🎉

Hi, folks -- as you may know, we've accepted Cess to be our Outreachy intern this session (congratulations, Cess!). I wanted to write to thank everyone for their incredible work over the past several weeks. If we had the capacity, we would have loved to accept more people. Our community is growing and perhaps this will be possible in the future.

I want to wish everyone the best whether you were accepted for another project, or if you have other projects of your own coming up in your life, and to make sure you all know you are always welcome here in our community. You're all amazing and I'm confident you all have amazing things in store in the future!!

THANK YOU for everything!!! 🎉 ❤️

Good luck!