Skip to content

RailsGoat Summer of Code Type Project Information

Jump to bottom
Al Snow edited this page Mar 24, 2018 · 49 revisions

3/24/2018: STUDENTS: Please do not forget and do not hesitate to upload a final copy of the proposal (in PDF format) ASAP. Later you can upload another modified final proposal, if needed, and it will override the first one. So, a final proposal is not final yet, until the submission time expires (on March 27). If you have not submitted a final proposal yet by that time (March 27), you will be automatically disqualified by the GSOC system.

Students Getting Started with RailsGoat SOC Initiative

  1. We really appreciate your interest in the RailsGoat SOC Initiative. As Google has open up the GSOC student proposal submit time-period (March 12-27, 1018), we encouraged you to read up about the RailsGoat SOC Initiative on this wiki page and follow the links under OWASP/GSOC 2018 Initiative.
  2. We see that OWASP applied to GSOC 2018 and has been selected. We do not know yet how many students "slots" Google will give OWASP or if we will get any of the given slots.
  3. We hope to be a part of the OWASP GSOC Initiative and currently working to staff the ideas listed below with mentors.
  4. Start thinking about the project "idea" or ideas you want to work on. You can pick one of the ones listed at the end of this page: OWASP/GSOC Project Ideas or come up with one yourself. You will be creating a proposal based on the"idea" and submitting it to Google between March 12-27, 2018.
  5. Here is your OWASP Slack invite: https://owasp.herokuapp.com . Introduce yourself in the RailsGoat Slack channel. Feel free to ask questions in the RailsGoat Slack channel.
  6. Get involve in RailsGoat community. Comment on a RailsGoat issue or submit a RailsGoat Pull Request.
  7. Suggestion for First Issues: I would suggest that while you are setting up your RailsGoat environment and reading the RailsGoat repo's documentation that you write up things (one thing per ticket) that are confusing or out-of-date. Then we can work them one-by-one to improve the initial experience of working with this project. Also remember to work on your "GSOC Student Application/Proposal" if you want be be officially part of GSOC 2018. You can add comments/questions/show interest to any GitHub issue with a GSOC tag.

Our current Idea List for RailsGoat SOC Initiative

We are collecting RailsGoat Summer of Code-Type project ideas. Please feel free to add more. Don't hesitate to send your original ideas as well! Our current ideas have been posted to the OWASP GSOC Idea wiki page

Main 2018 GSOC Milestones

  • NOTE: As of today (1/30/2018), GSOC and RGSOC organization submit deadlines have passed. Hopefully we can be part of another SOC program. See possibles below.
  • Feb.12: OWASP and "Rails" projects were accepted to Google Summer of Code (GSOC).
  • Feb.15-Mar.11: Get Mentors for Railsgoat ideas. Students start to be involved in RailsGoat Community.
  • Mar.12-Mar.27: Students Apply for GSOC
  • Apr.23: Accepted GSOC Student Announced
  • Apr.23-May.13: GSOC Community Bonding Period
  • May.14: GSOC Coding Begins
  • Aug.21: GSOC Mentors submit final student evaluations
  • October: Mentor Summit at Google

Mentors Getting Started with RailsGoat SOC Initiative

  1. Here is your OWASP Slack invite: https://owasp.herokuapp.com . Introduce yourself in the RailsGoat Slack channel. I encourage you to ask questions/give suggestions in RailsGoat Slack channel so we can get ready for student proposals in the near future.
  2. Ask the OWASP org administrator to send you an invitation to set up a GSOC account before you can log in to the GSOC website.
  3. Register on OWASP/GSOC Google Group as specified in OWASP/GSOC wiki.
  4. Feel free to ask questions in the RailsGoat Slack channel.
  5. Get involve in RailsGoat community.
  • Read GSOC Mentor email
  • Bulletproof Rails setup instructions for GSOC Mentors or Students
  • Add more ideas from GSOC Mentors or Students
  • Add easy issues for GSOC Students
  • Recruit GSOC students
  • Help with GSOC student proposals
  • Practice top 10
  • Trying external tools with GSOC program
  • Participating in/monitoring RailsGoat Slack channel.

Contribute to project by:

  • Comment on RailsGoat issues
  • Assigning yourself to issues
  • Working issues
  • Submitting a RailsGoat Pull Request
  • Writing up a new RailsGoat issue

Ways to Communicate: (Sorted by preference)

MORE ADMINISTRATIVE

Possible programs to be part of

Past GSOC Projects: https://summerofcode.withgoogle.com/archive/

SOC/RailsGoat Roles

Ways to Publicize

Sections are divided by their OWASP Top Ten label (A1-A10) and marked as R4 and R5 for Rails 4 and 5.

Clone this wiki locally