Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2013-03-18 17:12:47
Size: 292
Editor: beast
Comment: init
Revision 4 as of 2013-03-18 21:26:33
Size: 1333
Editor: mpm
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#pragma section-numbers 2

= GSoC Project Ideas for 2013 =
Line 2: Line 6:

<<TableOfContents>>

== Work on generic templating support ==

See GenericTemplatingPlan

== Improved built-in help ==

Mercurial's built-in help is quite good, but could be better. Here are some things that could be done:

 * improve crosslinking between help topics
 * migrate remaining contents from manpages into built-in help
 * add example usage to verbose sections in help
 * improve the glossary

== Advanced Hgweb support ==

Our web interface is very handy, but there are a number of features that could be improved:

 * Add functions and conditionals to the templating language
 * Add basic AJAX functionality to make history browsing more dynamic
 * Add some basic web admin functionality

== Performance tuning ==

Mercurial is fast but could always be faster. Possible areas include:

 * Optimizing startup performance
 * Optimizing performance on Windows
 
== Other ideas? ==

Come talk to us on [[IRC]].

----
CategoryGsoc

GSoC Project Ideas for 2013

Here are some ideas of possible 2013 summer project ideas for Mercurial. Your own ideas are welcome. You may decide to work on these ideas or use them as a starting point for your own. Either way, come talk to us in #mercurial in Freenode or on the mercurial-devel@selenic.com mailing list.

1. Work on generic templating support

See GenericTemplatingPlan

2. Improved built-in help

Mercurial's built-in help is quite good, but could be better. Here are some things that could be done:

  • improve crosslinking between help topics
  • migrate remaining contents from manpages into built-in help
  • add example usage to verbose sections in help
  • improve the glossary

3. Advanced Hgweb support

Our web interface is very handy, but there are a number of features that could be improved:

  • Add functions and conditionals to the templating language
  • Add basic AJAX functionality to make history browsing more dynamic
  • Add some basic web admin functionality

4. Performance tuning

Mercurial is fast but could always be faster. Possible areas include:

  • Optimizing startup performance
  • Optimizing performance on Windows

5. Other ideas?

Come talk to us on IRC.


CategoryGsoc

SummerOfCode/Ideas2013 (last edited 2013-04-15 22:31:05 by Pierre-YvesDavid)