|
Size: 1666
Comment: Generalizing SummerOfCode information.
|
Size: 1672
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| 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. | 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 13: | Line 13: |
| * 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.) | * 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.) |
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