- Submitting proposals
- Proposal Status
- Benefits to Community
- Having an idea on related works being done
- Biographical Information
- Submit a Draft Proposal early
- Outside the ideas List
Create an account on https://git.fosscommunity.in (if you don't have one already)
Create a new wiki page at https://git.fosscommunity.in/community/camp/-/wikis/home ('New page' button on the top right corner of main/middle column)
Title of the page should be
Proposals/<title of your proposal>/<your nickname>
Follow the guidelines below for writing the proposal.
You must submit the camp sessions feedback form before submitting the proposal. If you haven't provided feedback yet, make sure to contact the camp organizers using any of the communication channels mentioned in the <yet to add> [FIXME].
Put your full name on the proposal.
Your title should be short, clear and interesting.
You must mention whether the proposal is Draft or Final.
It can be mentioned below the title as
Proposal Status:Draft or
Start proposal with a short summary, designed to convince the reviewer to read the rest of the proposal.
Benefits to Community
Explain how your work can benefit the larger community, not just to yourself.
Include a brief, clear work breakdown structure with milestones and deadlines. Make sure to label deliverables as optional or required. If you are unsure about the milestones you can work with the mentors for planning the same. It's fine to include thinking/research time and learning time in your work schedule. Remember that the goal of the camp is to help you become contributors and any contribution counts.
Having an idea on related works being done
If there's an existing discussion or a discussion you have opened for the proposed task with upstream community, please reference the discussion in the proposal.
You should understand and communicate with other people’s work that may be related to your own when working on the proposed project. Do your research, and make sure you understand how the project you are proposing fits into the target organization.
Keep your personal info brief. Be sure to add personal experiences and skills that might be relevant to the project. Summarize your education, work, interests and Free Software experience. Any published work, blog, Free Software projects/communities and the like should definitely be mentioned.
Submit a Draft Proposal early
Submit your draft proposal early so that the mentors can review it and ask you questions or request more detail on aspects of your proposal before the final deadline.
The earlier you submit a well written draft proposal, the more time they have to give you feedback on it so you can make it stronger and understand more of what they are looking for.
Follow the instructions from your mentor on the content and format of your proposal. You must mention the proposal status as
Draft and write an abstract before sharing the draft with the organization.
You can edit the draft as many times as you wish before the application deadline.
Outside the ideas List
You can also propose work that is not on the Ideas List. Reviewers tend to get excited about a learner that goes beyond a direct response and enthusiastically adds reasoning and idea behind the proposal.
However, original proposals are also riskier; their flaws will be much more apparent. Here’s some of the ways that such proposals fail:
Projects without a mentor
Try to make sure that some mentors of the camp would be available to work with you. If you feel that project proposal do not require mentorship but general help and advice on how to proceed, mention about the same in the proposal. Projects that represent too large a scope
The time flies by quickly. If you have a large project, break it into small, coherent pieces and propose to get the first couple of them done. That way the mentor can be confident that they will get at least one good piece of work out of you.
The mentor needs to see a clearly delimited, contained piece of work. If the mentor can’t understand or define the work, the proposal may be rejected.
Projects that are “inappropriate” for legal or social reasons
If your proposal is near the boundary of what is acceptable for the upstream project, make sure you clear it with your target mentor in advance. Also make sure that your proposal does not violate the <yet to add> [FIXME] (CoC).
Guidelines Courtesy: https://google.github.io/gsocguides/student/writing-a-proposal