Short description of your project. Max 10 sentences. This SHOULD NOT be a copy of the project idea text.
Long description of the project. Must include all technical details of the project, like libraries involved.
Here it is also important to document previous conversations with your prospective mentors. You can show relevant pieces of code that you want to change. You can link to literature you used during the research.
Write a subsection which lists your contributions so far to DSC NSEC or the project. This may include:
- Issues, PRs
- Resources Review
- Preliminary Attempts Provide links whenever possible.
Here you should provide a list of your milestones. Below are a series of suggested sub-sections based on the different phases of WoC. You can use it as a template, but you can/should add more details for each phase, e.g. by breaking it down into weeks or setting specific targets for each phase. Each target should be split into sub-tasks with time estimates. Work breakdown structures may be helpful here.
This phase is to get to know the community better. Check that your build environment is setup. This time should also be used to discuss your project in more detail with the community, including introducing yourself and beginning to vet your ideas.
Deliverables
Deliverables
At this stage you should finish up your project and ensure that you have code submitted to your organization. Our main criteria to define your project as a success is submission of code advancements before the end of WoC.
Do you have code on github? Can you show previous contributions to other projects? Did you do other code-related projects or university courses?