This is meant as a temporary page for the darcs application to be a Google Summer of Code mentoring organisation, due 2009-03-09 -------------- 1. Describe your organization. - Darcs is a free, open source source code management system. It is based on an advanced 'theory of patches' and is written in Haskell. - The darcs team consists entirely of volunteer programmers from the darcs community. (TODO: well, Eric is on 20% time with UoB; maybe "volunteer" is no longer quite right?). The team supports the continued development of darcs by hosting the official darcs repository, website and bugtracker; and by organising regular darcs coding sprints, performing fundraising and otherwise seeking ways to increase the participation of darcs users in development. We will soon be joining the Software Freedom Conservancy (''TODO: stitch this in, gut says it's relevant, but why?'') 2. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating? - Time. Since 2003, darcs has run exclusively on the free time and enthusiasm of David Roundy and other volunteers. But the darcs community has grown and enthusiasm alone is not enough for us to do the kind of work we want. - We are excited about darcs because we feel that its theory of patches is unique and offers an kind of smoothness and flexibility that isn't possible with less principled revision control systems. While darcs uses a very elegant underlying theory, it has not been sufficiently optimised for large, real world repositories. This kind of work requires a lot of time, for which a dedicated worker would ideal. - Our goal is to create as much space as possible for us to work on darcs, for example, a "20% time" arrangement between Eric Kow and his employer, regular darcs hacking sprints twice a year, and active participation in programs like Google Summer of Code. In the bigger picture, we hope that the darcs project can be a regular participant in the Google Summer of Code program. 3. Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. - No. But we have had a successful project under the umbrella of the Haskell.org, Jason Dagit, 2007 mentored by David Roundy 4. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? 5. No 6. What license(s) does your project use? The GPL. We are also interested in spinning out or rewriting some of our our code as standalone libraries, for which we may decide that the BSD license is most appropriate. 7. What is the URL for your ideas page? `http://wiki.darcs.net/index.html/GoogleSummerOfCode `_ 8. What is the main development mailing list or forum for your organization? - `darcs-users@darcs.net `_ - `http://lists.osuosl.org/mailman/listinfo/darcs-users `_ 9. What is the main IRC channel for your organization? #darcs on irc.freenode.net 10. Does your organization have an application template you would like to see students use? If so, please provide it now. Can be inspired from `http://hackage.haskell.org/trac/summer-of-code/wiki/StudApply2008 `_ 11. Who will be your backup organization administrator? Please include Google Account information. Ganesh Sittampalam 12. Who will your mentors be? Please include Google Account information. 13. Eric Kow 14. Ganesh Sittampalam 15. ??? 16. What criteria did you use to select these individuals as mentors? Please be as specific as possible. 17. Eric: (TODO) 18. darcs - project maintainer 19. Haskeller 20. Ganesh: 21. darcs - helped invent type-witnesses idea for darrs - wrote some quickCheck tests - reworking some of slurpy code. 22. very experienced (commercial!) Haskeller 23. has had students (as a postdoc), and interns and junior at jobs 24. What is your plan for dealing with disappearing students? 25. What is your plan for dealing with disappearing mentors? 26. What steps will you take to encourage students to interact with your project's community before, during and after the program? 27. Before 28. #darcs ; get help tour of source code (as needed) 29. During 30. encourage blogging of progress ; planet.darcs.net 31. darcs weekly news editor will keep in touch with students 32. After 33. if have money: invite student to darcs hacking sprints? 34. encourage them to participate more in the community, for example, by joining the Review Team 35. What will you do to ensure that your accepted students stick with the project after GSoC concludes? See also -------- - `http://code.google.com/opensource/gsoc/2009/faqs.html `_ - `http://groups.google.com/group/google-summer-of-code-announce/web/notes-on-organization-selection-criteria `_