Writing C4GT Proposal — my experience on getting selected

In this article, I’ll explain everything I have mentioned in my proposal for C4GT. As new contributors, you must have different projects that you wish to contribute to, so don't refer to somebody’s entire proposal to craft yours or it can influence your creativity (basically stop asking me to send my proposal😂). I have written this as a guide to what sections should be included. This contains a general format and tips you should follow to craft a good proposal. All the best to this year’s contributors!

Section 1 :- Introduction

Keep it straight to point without any flowery introductions, let your projects/profile speak for yourself. Keep links to your GitHub, LinkedIn, Personal portfolio. Make sure they’re working. One addition I would make is to include a drive link to my updated resume here that I didn't do earlier. Also add your discord Id link.

Section 2:- Synopsis

Include topics for project summary such as :-

• Need of the project — your understanding of its impact.
• Understanding of the project — what have you understood from the problem statement .
• Features to be implemented — what have you figured out are the major features to be implemented from the problem statement and talking to your mentors .
• Tech Stack Chosen and Reason of Choice — Can be a good point to include that shows you’ve done research on the topic.

Tip :- Need is often written by mentors in project description- research that well. Choose open sourced technologies as its an open source program :) Some easy to scale, develop and use technologies can be named. If you’re confused about the exact milestones, talk to your mentors.

Section 3 :- Plan of Action

I used this section to provide a concise diagram of my exact design for the project. Its a great way to make a good impression on the reviewer as they can directly understand your thinking process. I used excalidraw for it.

Mostly C4GT Mentors are looking if you can grasp the needs of the project and can come up with a plan for implementing it. The design, plan and course of action is decided in the first week with the mentor and this is definitely not the final design, but can be a good inclusion in the proposal.

Section 4 :- Code Flow

This can be the thing that separates your proposal from everybody. Looking back it doesn’t get implemented according to plan when you actually start, but its a great section to showcase that you’re working on designing the project well. With 1000s of proposals being received in C4GT, it is important to include these sections to stand apart. It also helps in the coding period as you’ve done the research before. My project was going to be made from scratch, if yours isn't like that just mention the structure of files you’re going to add or the changes you will make to the project.

Section 5 :- Technical Implementations Examples

Add code excerpts, sample designs, mockups relevant to your projects. Add links to contributions you’ve made to that project already.

• If its an already existing project and you’ve made PRs, include links to those.
• If you haven't made any PR till now, please do! Its a great way to interact with mentors and understand /setup the project. In the mean time, you might be under time constraint to submit the proposal before making a PR — in that case go to the project repository and search your github username in Open PRs and provide the link to that. Then when the mentors open it in the future, it’ll be updated with latest pushes. This can also work if you’ve made only 1/2 PR but are working right now to make more after the proposal deadline.

• If in case its a completely new project that needs to be built from scratch( Like it was for me) provide sample code mock ups that can be implemented in coding period.

Something like this customized to your project. Make sure to add comments to explain it. Provide 1–2 simple short examples for this don't go overboard, this is not the coding period :)

Section 6 :- Schedule of Deliverables

Divide the work flow in milestones/deliverables. Label each deliverable as either required or optional. Make it precise using bullet points. Always keep buffer room for any unforeseen errors or difficulties . Keep the mid-point and end point demo showcase weeks clear as it generally gets used up in making good demos and presentations. Keep the 1st week for Blog setup, interacting with fellow contributors and attending the sessions that C4GT team organizes. Deliverables should cover investigation, coding, and documentation.

Tip:- Make it in a table format in 1 page, its easier to read.

Section 7:- Previous Development and Community Experience

Include a brief summary of Open Source Experience and Community Participation. If you don't have any that's completely fine. Include some good group projects or hackathons then. The point to understand is that C4GT is a open source program where community building plays a major role. So its good to showcase if you’ve experience with that. If not, include your contribution in a team of SDE interns for example.

Please give links to projects built on similar tech stack to what’s required for the project you’re submitting the proposal to. They must be deployed!

Section 8 :- Contribution in C4GT’s open community:-

In this section answer the questions about your participation in C4GT’s open community tickets,

provide the screenshot of the leaderboard with your GitHub ID and DPG points earned (if any).

Have you contributed to tickets in C4GT’s open community? (Mandatory to answer)

Yes/ No

Have you successfully completed C4GT’s GitHub Classroom Assignment? (Mandatory to answer)

Yes/ No

Enter your DPG points (Mandatory to answer, Enter 0 if not applicable)

Screenshot of leaderboard with your GitHub ID (Mandatory to answer, enter 0 if not applicable)

Section 9:- Conclusion

For this include topics on :-

• Commitment to C4GT :- hours you can devote to this, be honest about it and mention prior commitments that you have.
• Why C4GT :- research well, read up blogs then write it.
• Why Choose me ? :- Write it depicting how you’ll be a good fit for the project according to your skills. Don't write things like I am good leader, methodical worker etc etc. Make it concise to why you have the skills for this project.
• Community Outreach :- Are you planning to write blogs? Participate in C4GT college chapter? Post on LinkedIn about your journey/project? Write about how will you help spread the word about your project and C4GT
• Post C4GT :- Keep contributing to the project even after C4GT is over!! Its for the spirit of open source and not just internship :) You can write about this.
• Conclusion :- Prolly say thanks for reading this haha :)

Some Tips from my side :-

1. Keep usage of Chat GPT, Bard, Copilot to the minimum. Use it only for spell checks/grammar errors.
2. Use one font only with consistent sizing of headlines and content.
3. Add header and footer, make it clean and short.
4. Spell Check before submitting and check if all the links are working
5. Use bullet points , keep it short. 13–14 pages should be the maximum. Mentors are busy and don't have time to read a long proposal.
6. Keep contributing to the project and interacting with mentors between the proposal submission date and final result date.
7. Get a review of your proposal from the mentors if possible.
8. Please use numbered bullet points for a better flow in the proposal.

Also read the official guide here: https://docs.google.com/document/d/1D2pLc_eP-8-waBnRuj57Tc_jQT7_-ZWRQCDjv6qtPTY/edit

I hope this helps everyone, note this is not one size fits all. You all must have different projects and approaches so customize this to your own project. Stop watching tutorials on how to make proposals😂 and stop reading multiple blogs too (oops kinda hurt my own blog views from that). Stop seeking advice and start doing! Once you’ll start writing it, you’ll yourself come up with sections you should include to make it better.

If you’ve enough time, send to previous selected contributors and get it reviewed. All the best !! Don't stress after submitting it keep working hard, the result is only in the hands of Krishna. If this blog helps you and you get selected, do send me a message on LinkedIn :)