PageRenderTime 3ms CodeModel.GetById 1ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

Plain Text | 24 lines | 18 code | 6 blank | 0 comment | 0 complexity | 98d34224f10b5967654e33df02c309ad MD5 | raw file
 1Developing Silver Lining Itself
 4You should read and consider the `design notes <design>`_ of course.
 6Version Control
 9Generally I like to use forks for feature additions, and only use hg
10branches for things like a stable branch.  So if you want to add a
11feature, you should fork/clone the repository and make those changes.
12I appreciate some note (in the description field) about what your
13fork's purpose is.  It might simply be "to mess around with
14Silver Lining", but I still appreciate the note.
16The main repository is for integration.  I'm not shy about giving out
17write access to this repository, if you are making consistent
18contributions it's easier for both of us if you can simply push
19directly to the main branch.  This doesn't remove the utility of
20forks; if you are doing something that will take a while to complete
21or you aren't sure if it's in line with Silver Lining's design, it's
22still reasonable to do your own fork.