| | 1 | = Lessons Learned from GSoC 2017 |
| | 2 | |
| | 3 | - Umesh and Zero presented their projects and what went well and not so well during GSoC 2017. |
| | 4 | - We should use some sort of issue tracking to make progress more visible and measurable. A good idea might be Trello or GitHub projects |
| | 5 | - Some projects do a lot of planning beforehand and use a burndown chart to track student progress. We don't think this will work very well for us, since our projects often change after they start. |
| | 6 | - Mojca and Clemens attended the Mentor Summit |
| | 7 | - We asked for a period after the initial submission deadline where students can improve their proposals but no new proposals can be added. There used to be a button to enable editing in the application review period that could be used to achieve this. Let's see whether this will be the case this year, and if it is, use it. |
| | 8 | - Clemens sent a mail to the list with a report: https://lists.macports.org/pipermail/macports-dev/2017-October/036720.html |
