One repository per project, or subfolders?
Newbie question. I have a slew of existing projects which are strictly local (no SVN at all). Most are web projects, some XCode. They are scattered all over my hard drive (organized by client) I now have Versions, and a hosted subversion account. I'd like to get all my projects under SVN. I'm the only coder on any of these projects. What are the pros/cons of: -Having one hosted repository, with folders for each of my projects -Many hosted repositories, each for one of my projects? Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
I think the best will be one project = one repository. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
As you have things already organized by client, I would say that it would be better to go for the repository per client. This would be dependant on how much versioning/rollbacks/merges required is required. So in effect you would have a subfolder for each project you have done for a client in their Repository. Obviously YMMV and you have to make a decision on how much you will be relying on the versioning system for what you need and changes you will be making per project on a regular basis. Kieren On 07/07/2009, at 7:42 PM, Mitch Cohen wrote: > > Newbie question. I have a slew of existing projects which are > strictly local (no SVN at all). Most are web projects, some XCode. > They are scattered all over my hard drive (organized by client) I now > have Versions, and a hosted subversion account. I'd like to get all > my projects under SVN. I'm the only coder on any of these projects. > > What are the pros/cons of: > > -Having one hosted repository, with folders for each of my projects > > -Many hosted repositories, each for one of my projects? > > Thanks! > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
I'd vote for the same, (one repository per client, not per project) especially if you have a hosted SVN account — you may run out of free repositories, depending on your host. Adding a directory to a repository is easier than setting up a new repository each time a new project comes along, and it makes more sense to group project for a client in a repository regardless of how they "scattered all over [your] hard drive" — you can check out directories as different working copies in whatever location you like. - Quinn On Jul 8, 2009, at 3:31 AM, Kez wrote: As you have things already organized by client, I would say that it would be better to go for the repository per client. This would be dependant on how much versioning/rollbacks/merges required is required. So in effect you would have a subfolder for each project you have done for a client in their Repository. Obviously YMMV and you have to make a decision on how much you will be relying on the versioning system for what you need and changes you will be making per project on a regular basis. Kieren On 07/07/2009, at 7:42 PM, Mitch Cohen wrote: Newbie question. I have a slew of existing projects which are strictly local (no SVN at all). Most are web projects, some XCode. They are scattered all over my hard drive (organized by client) I now have Versions, and a hosted subversion account. I'd like to get all my projects under SVN. I'm the only coder on any of these projects. What are the pros/cons of: -Having one hosted repository, with folders for each of my projects -Many hosted repositories, each for one of my projects? Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~--- smime.p7s Description: S/MIME cryptographic signature
Re: One repository per project, or subfolders?
Thanks everyone! I hadn't thought about the one client per repository notion, but that makes a lot of sense. Thanks again! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
The setup I use is a single repository with folders for each client underneath a folder for each project for that client. No need for multiple repositories. You can check out a working copy of any project anywhere you'd like. Network congestion, e.g. checking status, can be limited if you do this verses checking out the entire repository. There are plenty of options for arrangement, none are wrong, some maybe more usable than others for various reasons with various pros/ cons for each. Jamie On Jul 8, 9:57 am, Mitch Cohen wrote: > Thanks everyone! I hadn't thought about the one client per repository > notion, but that makes a lot of sense. > > Thanks again! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
On Jul 7, 7:42 am, Mitch Cohen wrote: > They are scattered all over my hard drive (organized by client) Wow, you let your client organize your hard drive? :) Oh, yes, I'd vote for one client = one repo, too. That's how we do it; keeps a balance between too many and too few. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
That also works. The reason that use separate repositories is so that work for separate clients is never intermingled together, and it's simple to control access to a particular client's work. (Companies tend to not like their IP to be freely available to other clients, competitor or otherwise.) I doubt that network congestion would necessarily be reduced by using a single repository, since Versions checks for each working copy individually anyway. - Quinn On Jul 9, 2009, at 6:09 AM, Jamie wrote: The setup I use is a single repository with folders for each client underneath a folder for each project for that client. No need for multiple repositories. You can check out a working copy of any project anywhere you'd like. Network congestion, e.g. checking status, can be limited if you do this verses checking out the entire repository. There are plenty of options for arrangement, none are wrong, some maybe more usable than others for various reasons with various pros/ cons for each. Jamie On Jul 8, 9:57 am, Mitch Cohen wrote: Thanks everyone! I hadn't thought about the one client per repository notion, but that makes a lot of sense. Thanks again! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~--- smime.p7s Description: S/MIME cryptographic signature
Re: One repository per project, or subfolders?
+1 for repo per client. Some of my clients want access to their code, so this makes sense. However, sometimes I have projects for which I need to provide access to outside contractors. In such cases, I set up a repo per project. -- Kevin Powick --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: One repository per project, or subfolders?
One example for using a single repository is sandboxing. This repository is separate from the client's, may utilize a different SCM, access is limited, it may or may not be local but is always under your control. Regarding network congestion, my point wasn't that it would be reduced using a single repository but that a single repository can lead to sluggish response as SVN determines status, e.g. creating a working copy of trunk/ and therefore all projects below it. As you correctly point out and apparently not clear in my statement, it's is not necessarily a result of a single repository but poor working practice. On a side note, with Xcode 3+ sandboxing can be achieved using the "Make Snapshot" feature. Jamie On Jul 9, 1:09 pm, Quinn Taylor wrote: > That also works. The reason that use separate repositories is so that > work for separate clients is never intermingled together, and it's > simple to control access to a particular client's work. (Companies > tend to not like their IP to be freely available to other clients, > competitor or otherwise.) > > I doubt that network congestion would necessarily be reduced by using > a single repository, since Versions checks for each working copy > individually anyway. > > - Quinn --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
