[TOS] Guidelines on launching an open source project?
allen at bowdoin.edu
Tue Jun 26 05:59:20 UTC 2012
Hi T. F.,
A popular and simple approach is to set up a Google project at code.google.com, which you can configure with a Mercurial repository and control access in the ways that you identify below. (Before setting up this project, you would need to create a Google id for yourself if you don't have one already.)
The code in your Mercurial repository can then can be cloned over to this new repository for others to access and your committers to maintain as they do now.
Let me know if you need help with any of the details.
On Jun 25, 2012, at 11:55 PM, <pawlicki at cs.rochester.edu> <pawlicki at cs.rochester.edu> wrote:
> I been asked to help take a fairly extensive body of code and
> release it as an open source project.
> I'm wondering if someone can point me to some resources that
> might guide us along this process?
> My collaborators have a body of code used for physics simulation.
> It's all under Mercurial for internal management. They want to
> distribute it under an open source model, while maintaining control
> of the "official" version.
> Any pointers, guidelines, or advice would be appreciated.
> T. F. Pawlicki
> Dept. Computer Science
> University of Rochester
> tos mailing list
> tos at teachingopensource.org
More information about the tos