GSoC Project Ideas for 2016

Here are some ideas of possible 2016 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.

$/!\$ All potential GSoC candidates should visit our SummerOfCode/2016 page, which contains more information on everything GSoC for this year.

Contents

Please add GSoC ideas here
Other ideas?

1. Please add GSoC ideas here

1.1. Example

Project description: This is an example project. Please add a clear description with some details about the idea.
Skills: Specific programming languages, domain-specific knowledge... For example: Python, network programming
Difficulty level: Easy/Intermediate/Difficult
Related reading/Links: Useful links to wiki pages, specific relevant mailing list discussions or patches, ...
Further details: Additional detail about the idea
Potential mentors: mentors likely to be involved with this project

1.2. Improved handling of merge conflicts

Project description: Improve the user-friendliness of merge conflicts
Skills: Python
Difficulty level: Easy/Intermediate/Difficult ?
Related reading/Links: http://bz.mercurial-scm.org/show_bug.cgi?id=29
Further details: Merge conflicts between files and directories are not handled in a user-friendly way. Similarly, largefiles conflicts are also not handled very well.
Potential mentors: ?

1.3. Modernize hgweb's graph rendering

Project description: Modernize hgweb's graph rendering
Skills: Python, JavaScript
Difficulty level: Intermediate/Difficult
Related reading/Links: https://bz.mercurial-scm.org/show_bug.cgi?id=4020 (not limited to this bug)
Further details: Current graph rendering code in hgweb is pretty clunky and not very extensible or efficient. We could update it to today's standards, include more things (e.g. phases, hidden changesets, also look at TortoiseHg's graph for more examples) and render graph more efficiently and in a nicer-looking way.
Potential mentors: ?

2. Other ideas?

Come talk to us on IRC.

CategoryGsoc