TubeTK/Development: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
Line 27: Line 27:
* TubeTK git policy is being converted to promote a branchy workflow.
* TubeTK git policy is being converted to promote a branchy workflow.
** We will be basing the TubeTK policy on the workflow described at http://nvie.com/posts/a-successful-git-branching-model
** We will be basing the TubeTK policy on the workflow described at http://nvie.com/posts/a-successful-git-branching-model
** [[TubeTK/GITBranchingUsage | Git Usage and Procedures:]]  How to get, edit and contribute back to TubeTK
** [[TubeTK/Development/GITBranchingUsage | Git Usage and Procedures:]]  How to get, edit and contribute back to TubeTK
** [[TubeTK/GITConfiguration | Git Configuration:]]  Setup your git environment, including your name, email, and git hooks (scripts that run at certain points, for example when committing or pushing changes)
** [[TubeTK/GITConfiguration | Git Configuration:]]  Setup your git environment, including your name, email, and git hooks (scripts that run at certain points, for example when committing or pushing changes)
** Extra Git info:
** Extra Git info:

Revision as of 04:46, 14 December 2010

Collaborative TubeTK Development

Please follow these steps to build and extend TubeTK

1. View the software over the web

2. Check on the status of TubeTK

3. Download the software via git

  • Read-only access
  • Read and write access (assume you have an existing and approved gitorious account)
    • git clone git@gitorious.org:tubetk/tubetk.git
    • git push git@gitorious.org:tubetk/tubetk.git master

4. Setup your development environment

5. Build the toolkit

6. Read, learn, and follow the development guidelines

7. Read the FAQ

8. Contribute Code

9. Contribute Dashboard Clients

Integrating TubeTK

TubeTK and Slicer

TubeTK and ImageJ