|
Size: 2723
Comment: style edits, decrease repetition
|
Size: 2700
Comment: replace selenic.com URL with mercurial-scm.org one
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| * [[http://selenic.com/hg|Main repository]] — browse or clone the source (see [[DeveloperRepos]] for other repositories) | * [[https://www.mercurial-scm.org/repo/hg|Main repository]] — browse or clone the source (see [[DeveloperRepos]] for other repositories) |
| Line 20: | Line 20: |
| * [[http://bz.selenic.com/buglist.cgi?keywords=easy%2C%20&keywords_type=allwords&list_id=6549&resolution=---&query_format=advanced|Easy bugs]] — tasks flagged as easy, a good entry point for new contributors * [[UIGuideline]] — how to make consistent UI choices |
* [[https://bz.mercurial-scm.org/buglist.cgi?quicksearch=easy&list_id=9019| Some easy bugs]] — tasks flagged as easy, a good entry point for new contributors * [[UIGuideline|UI guidelines]] — how to make consistent UI choices |
| Line 40: | Line 40: |
| * [[DevelopmentProcess|Development process]] — an overview of our development and release workflow | |
| Line 43: | Line 44: |
| ## * [[DevelopmentProcess|Development process]] — an overview of our development and release workflow |
Note:
This page is primarily intended for developers of Mercurial.
Developer Info
Information on working on the Mercurial code base.
Contents
1. Start hacking
Main repository — browse or clone the source (see DeveloperRepos for other repositories)
Theming Mercurial's web interface
Translating Mercurial — how to translate Mercurial into your own language
2. Contributing code
Some easy bugs — tasks flagged as easy, a good entry point for new contributors
UI guidelines — how to make consistent UI choices
Help style guide — how to write nice help
Compatibility rules — how we keep our existing users from crying
Review process — how you can help get patches in
3. Internals
Design - Mercurial's data structures and how it uses them
File formats - list of Mercurial's disk file formats
What goes where - the project architecture
Wire protocol - the push/pull changegroup protocol
Debugging features - how to poke around in Mercurial's internals
4. Working with the community
Managing bugs — how to work with the bug tracker
Developer repositories — where to find various public repositories of Mercurial work
Development process — an overview of our development and release workflow
IRC — where most of the developers hang out
Meetings — When we get the community together (about every 6 months)
Project infrastructure — A list of project infrastructure and who administers it
5. Feature proposals
6. Developer tips
MacOSXTools — Installing the tool chain on Mac OS X.
Using Wine to test Windows support under Linux
Easy way of starting Mercurial hacking on Windows with HackableMercurial