On Feb 2, 2009, at 06:15, HKS wrote: > Hi, I'm fairly new to GCode and SVN and I'm wondering whats the best > way to organise my projects. I have a handful of projects for a > variety of web development resources (eg jQuery, MooTools, > Joomla, ...). Subversion's intro book recommends having a folder > structure like > > proj1/trunk > proj1/tag > proj1/branches > proj2/... > proj3/... > > Should I create separate projects on GCode or reorganise the folder > structure manually? Ideally I would share the wiki and other > resources for some of them. What happens if I need more than 10?
If you create separate Google Code projects, they will have separate repositories, issue trackers and wikis. Since discussion lists are not integrated with Google Code projects, you could have a single discussion group for all projects if desired. Code from one repository cannot be svn cp'd to another, so it's more difficult to share code. If your projects are related, that may be a reason not to separate. For my project (canviz) I found it easier to have a single project. My repository also contains a second project (path) which grew out of the first and could be useful on its own, but it was easier to keep both projects together. YMMV. With Subversion you can easily reorganize the structure within a repository at any time using svn mv so you're not locked into anything. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
