Applying for SageMath Coding Sprints at the IMA
Coding sprints are designed for teams 2-8 participants to spend 3-5 days at the IMA. Interested applicants should first initiate a trac ticket (or describe an existing one) on the SageMath trac server, explaining the proposed code. (Proof-of-concept code is not necessary at this stage, but welcome.) This will allow developers and users to comment on proposed changes and is the first, important step in the git workflow.
Applicants should then complete a short online application and email a 1-2 page proposal to firstname.lastname@example.org. The proposal should include a description of the design proposals for any code to be written and how the potential functions of the code or materials to be developed will impact researchers in academia and industry and/or educators. Proposals should discuss prior history of related code in SageMath, or other open-source software, and a brief description of the relevant mathematical and coding background of the proposers.
Please note only one participant of the coding sprint team needs to fill out the online application and submit the proposal to email@example.com. The submitted proposal should include name, affiliation, and email address of all collaborators.
Each proposal will be evaluated by the scientific board according to the following three criteria:
- Effectiveness – does the proposed functionality successfully address an important development opportunity in Sage?
- Feasibility – can sufficient progress be made on the proposed functionality during the coding sprint?
- Interest from the community – is there a pressing need for the code?
Applications will be accepted on a rolling basis according to the following schedule:
- June 1, 2017—Deadline for initial round of decisions (Notification by July 1)
- Sept. 1, 2017—Deadline for second round of decisions, sprints must occur after Nov. 1 (Notification by Oct. 1)
- Nov. 1, 2017—Deadline for third round of decisions, sprints must occur after Jan. 1 (Notification by Dec. 1)
- Feb. 1, 2018—Final deadline for coding sprint applications, sprints to occur after April 1 (Notification by March 1)
Please contact the organizers with additional inquiries.