|
Size: 1854
Comment:
|
Size: 1333
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| == Work on generic templating support == See GenericTemplatingPlan |
|
| Line 13: | Line 17: |
| * Improve HTML rendering in hgweb view ([[http://selenic.com/hg/help|see here]]) | |
| Line 32: | Line 35: |
| * Optimizing revlog parsing and indexing with a C index class extension * Improving performance of the status command * Eliminating unnecessary checks of unknown files in merge/update |
|
| Line 37: | Line 37: |
| == Command server == Mercurial's primary stable API is its command line interface. Creating a tool and library to communicate with this API over a pipe or a socket will help improve performance for third-party tools that use Mercurial. ([[https://bitbucket.org/wbruna/hgrpc/|here]] is a previous incomplete effort) |
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.
Contents
1. Work on generic templating support
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.