If I wanted to checkout the trunk of the Edit-SFS program, I would do this:Lobster wrote:Reporting bugs - easy
checking out code - did not seem easy
- in fact I could add a comment to code but not check out
this was with Jeremys code (Pizzasgood)
- eh did you lock it so crazy cructaceans can not check it out
or am I just incompetent? (probably incompetent)
Code: Select all
svn checkout http://puppy-development.googlecode.com/svn/trunk/edit-sfs/trunk edit-sfs_trunk
Code: Select all
svn checkout http://puppy-development.googlecode.com/svn/trunk/edit-sfs edit-sfs
Both of those examples are for people who don't intend to commit changes back to SVN, i.e. users or package makers who just want to grab the latest version. Developers who intend to commit changes can use very similar commands, except that instead of http:// they would use https://, and they would also need to add the --username youremail@gmail.com option. So, if I were a developer with an address of amadeus@gmail.com, I would do this:
Code: Select all
svn checkout https://puppy-development.googlecode.com/svn/trunk/edit-sfs edit-sfs --username amadeus@gmail.com
People should observe some form of etiquette when committing to somebody else's project, such as making their own branch (in /trunk/<project-name>/branches/) so they don't step on anybody's toes, unless they've talked to those in charge of that particular project and gotten permission to commit to the trunk or official branches. Different people and projects might have different workflows, so contributors should also be aware of that. For example, on Edit-SFS I'm just doing all the work in the trunk, and occasionally I might tag a release version. For more complex projects, I might prefer to use a development branch and consider the trunk the stable branch, so that at any time somebody could checkout the latest snapshot of the trunk and have a working, if unfinished, version of the code.