On Fri, Mar 02, 2007 at 08:50:11PM +0100, Eric Y. Kow wrote: > On Fri, Mar 02, 2007 at 11:44:40 -0800, David Roundy wrote: > > I'd like darcs to be a mentor for the google summer of code this year, and > > the applications are next week. So I'm asking for ideas and volunteers to > > be mentors. The latter is as important as the former. > > Some catch-all projects? > > * A Windows project: not sure what this would entail, but darcs on > Windows might need a bit of special attention > > * General robustness: maybe not to do with patch theory stuff, but > things like the HalFs thing (no more worrying whenever your > supervisor uses Unison to synch with her laptop), improved error > messages, blowing up in as graceful and helpful a manner as possible.
Yeah, here are a couple more inspired by your suggestions: (one's just a clarification of what you suggested) * A single-file database pristine cache, which should be faster and more robust than our directory-based approach. e.g. a halfs filesystem. * Keeping track of which patches affect which files, to speed up query operations that affect only certain files (e.g. changes, diff, etc, when given a filename argument). I'm not sure error messages is quantifiable, in the sense that they need projects that can be measured in terms of whether or not the student succeeded. A new error message framework *might* be doable, but it'd take some sort of explanation. -- David Roundy Department of Physics Oregon State University
signature.asc
Description: Digital signature
_______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
