|
Size: 1645
Comment:
|
← Revision 13 as of 2010-10-22 18:27:33 ⇥
Size: 1713
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Mercurial and Google's Summer of Code 2006 == BryanOSullivan is interested in having Mercurial participate in the 2006 [http://code.google.com/summerofcode.html Google Summer of Code]. == Volunteers == If you are interested in volunteering as a mentor, please add your name here. Volunteer duties may include the following: reviewing student applications, monitoring and mentoring students as they work, and writing up an evaluation of the student's work at the end. * BryanOSullivan |
## page was renamed from SummerOfCode2006 Mercurial does not participate in the 2006 [[http://code.google.com/summerofcode.html|Google Summer of Code]], but nevertheless here is a list of ideas one could implement. |
| Line 14: | Line 7: |
| * Extension: fast, incremental, native Subversion importer using Subversion's Python bindings. | * (./) Add support for storing symbolic links. * Support push over HTTP, using SSL, in a way that is friendly to both users and web admins. * (./) Extension: fast, incremental, native Subversion importer using Subversion's Python bindings. |
| Line 17: | Line 12: |
| * Add support for date/time ranges to all Mercurial commands that can currently accept revision range. * Develop a distributed bug tracking system. Allow people to maintain their bugs and code in the same repo or in decoupled repos. Provide web interface for easy administration. (See [http://www.panoramicfeedback.com/opensource/ Bugs Everywhere] for an example.) * Convert commit comments between UTF-8 and current locale. |
* (./) Add support for date/time ranges to all Mercurial commands that can currently accept revision range. * Develop a distributed bug tracking system. Allow people to maintain their bugs and code in the same repo or in decoupled repos. Provide web interface for easy administration. (See [[http://www.panoramicfeedback.com/opensource/|Bugs Everywhere]] or [[http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-3a410db622d55b4dd88d91437d2c953f6b730542|grit]] for some examples.) * (./) Convert commit comments between UTF-8 and current locale. |
| Line 22: | Line 17: |
| * Stuff from CategoryNewFeatures ---- CategoryGsoc CategoryHistorical |
Mercurial does not participate in the 2006 Google Summer of Code, but nevertheless here is a list of ideas one could implement.
Project ideas
- Write a set of "drop-in" web hosting code, so that people can create projects, upload repositories, create server-side branches, see how much branches are diverging, and manage all of these.
Add support for storing symbolic links. - Support push over HTTP, using SSL, in a way that is friendly to both users and web admins.
- Extension: fast, incremental, native Subversion importer using Subversion's Python bindings.
- Extension: export changes to git repositories.
- Extension: let git clients pull changes from Mercurial servers using "git://" wire protocol.
- Add support for date/time ranges to all Mercurial commands that can currently accept revision range.
Develop a distributed bug tracking system. Allow people to maintain their bugs and code in the same repo or in decoupled repos. Provide web interface for easy administration. (See Bugs Everywhere or grit for some examples.)
- Convert commit comments between UTF-8 and current locale.
- Store file names internally as UTF-8, and convert to current locale/code page on disk.
- Find a high-performance way to do localised text strings in Python, and use this to add complete i18n support for at least one non-English language.
Stuff from CategoryNewFeatures