yt_analysis is sharing code with you
Bitbucket is a code hosting site. Unlimited public and private repositories. Free for small teams.
Don't show this againyt_analysis / yt http://yt-project.org/
yt is a python package for analyzing and visualizing astrophysical simulation output from a couple simulation platforms. Check out the homepage (there's a link just above!) where we have documentation, a cookbook, and some user community information.
hg clone https://bitbucket.org/yt_analysis/yt
hg clone ssh://hg@bitbucket.org/yt_analysis/yt
hg clone https://bitbucket.org/yt_analysis/yt/wikiGetting Involved in yt
yt is http://yt.enzotools.org/principles.html fully open source and we welcome and encourage contributions! To that end, we'd also like to lower the barrier to entry for contributing to yt. This page has some tips and tricks for how to get involved and ideas for projects or patches that would be fun or useful to implement in yt.
How is yt developed?
YT has three main areas of development:
- stable -- this is the current stable branch. As of writing, this is yt-1.6. It is located in subversion under
branches/yt-1.6. Changes to this branch are made sparingly, and only for bugfixes. - trunk -- this is the staging area for the next major stable release. No main development occurs here, and it is expected to be relatively stable. Changes are backported from the unstable repo in bulk. This is located in
trunk/. - mercurial -- this is the place where things are developed. It is not guaranteed to be stable. Multiple branches live at http://hg.enzotools.org/yt/
How can you contribute to yt?
If you want to just get going, clone the main mercurial repository at http://hg.enzotools.org/yt/ and start committing! (For more information about mercurial, you can see either the http://hgbook.red-bean.com/read/ hgbook or http://hginit.com/ hginit. Be careful not to commit in either the "yt-1.x" or "trunk" branches, as those are markers for future SVN mirroring. If you're going to be doing a lot of development on a single feature, maybe you could make your own named branch. The main branch is just called yt, and it's where we have most of our fun, but there are a couple other named branches for features and whatnot.
Once you've gotten something you'd like to share, you can either request "push" privileges, submit an `hg bundle` up to one of the other developers, or even submit a unified diff that can be supplied.
If you're going to be developing for yt, you should consider signing up for the http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org developers mailing list. Let us know what you're up to, and if we can help in any way. We're eager to increase participation!
Project Ideas
If you're interested in developing, contributing, helping out, but aren't quite sure how to get started, there's a list of fun things that some of the developers have been thinking about over on the [[wiki:WishList]] page.
This revision is from 2012-01-27 18:31