On 09/02/2015 17:22, Guillaume Hoffmann wrote: > 1. HTTP system overhaul, a.k.a. "switch to wreq and see what happens". > This would involve having wreq (http://www.serpentine.com/wreq/) as > default download system, while leaving the current libcurl and HTTP > code for benchmarking purposes.
My feeling is that we shouldn't leave the current code. It's a real mess and it'll be very hard to both keep it and add a nice interface to wreq. In fact, I'd also be inclined to write a standalone "download manager" library, rather than integrating wreq directly into darcs. > * https support under windows (somehow we can't have libcurl under windows?) I think you _can_ have libcurl, it's just a real pain to install. > 2. Work towards Darcsden as a local UI and other improvements > * plain files backend (vs current CouchDB) > * other stuff to help Darcsden be a local UI (without actually > involving any UI work)? any idea? I think the plain files backend is the main thing here, wherever possible it should read existing metadata from the _darcs repository or the user's home directory. I think some UI work is the other natural part to consider, e.g. a UI for record/revert etc. > * unauthenticated patch submission via darcs send and http I think we have most of the pieces in place for this, but we need to get them all working together properly. Darcsden supports 'patches' but they're not on yet, darcs send can use http URLs already. I think that mostly leaves filling in any remaining gaps in the darcsden code such as authentication/anti-spam. > Apart from opinions about these project ideas, if someone thinks there > are more worthwile projects to do, please tell. I'd still be happy with any of the things proposed by me on http://darcs.net/GSoC and would be willing to mentor them, given an appropriate student. Cheers, Ganesh _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
