Please enable JavaScript.
Coggle requires JavaScript to display documents.
GSOC - Coggle Diagram
GSOC
doubts
First and foremost, make sure you meet Google’s formal requirements for participation in Summer of Code. Also be sure you are eligible to participate in a program like GSoC with your visa, etc. Hopefully, you have already checked this by now, but be sure to double-check before you waste time and energy on a proposal.
Deliverables
Include a brief, clear work breakdown structure with milestones and deadlines. Make sure to label deliverables as optional or required. You may want your plan to start by producing some kind of white paper, or planning the project in traditional Software Engineering style. It’s OK to include thinking time (“investigation”) in your work schedule. Deliverables should include investigation, coding and documentation.
depth??Biographical Information
Keep your personal info brief. Be sure to communicate personal experiences and skills that might be relevant to the project. Summarize your education, work, and open source experience. List your skills and give evidence of your qualifications. Convince your organization that you can do the work. Any published work, successful open source projects and the like should definitely be mentioned
Submit your draft proposal early during the application period so that the organization mentors can review it and ask you questions or request more detail on aspects of your proposal before the final deadline
-
important
This program is the Google Summer of Code. If you are less than fluent in the programming languages that your target organization uses, you might want to skip the work of writing an application. If you do decide to proceed, be clear about your level of ability, so that the organization can make an informed decision.
Follow the instructions from the organizations on the content and format of your proposal and use the GSoC program site instructions on successfully submitting and sharing a draft to the organization. You must create the draft and write an abstract before sharing the draft with the organization
The “Pencils Down” deadline for your project to be complete is usually sometime in mid-August. This will come sooner than you think.
There are also many non-code ways you can contribute to software. If you’re interested in documentation, graphic design, release testing, public relations or marketing, most projects welcome contributions in these areas. Taking on small non-code projects can be a great way to stay connected and build a reputation in a community.
-
-
steps
1
Contact the project, introduce yourself and ask questions related to your project.
2
For each organization, take some time to learn more about what they do (i.e., Google them!). The organization’s mission, it’s size and range of applications may all influence your interest in working with them. Realize that through GSoC you will be joining an open source community. Ideally, you’ll find an organization that you are enthusiastic to be a part of for many years to come!
No matter what, don’t wait until the application period to initiate contact - really! Engage with multiple communities once the participating organizations are chosen to get a feel for how different groups work and find the one or two that fit your interests/personality.
-
Pro Tip: Don’t be afraid to apply to projects where you only meet 51% of the listed requirements. Include a section on how you’ll compensate for or learn the missing skills - and demonstrate during the application process that you are working on acquiring those new skills.
-