Mat Schaffer on 6 Feb 2007 22:03:17 -0000

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PhillyOnRails] PhillyOnRails Rubyforge Project, Started!

On Feb 6, 2007, at 2:54 PM, Mark Chadwick wrote:

I propose to keep things semi-organized in svn, we use the kind of organization found in Pragmatic Version Control ( ) ...or at least follow the projectname/trunk convention to keep it clean?  Thoughts?

stolen from 

This is definitely a good way to do things.  But I think if people want to have their own systems in their own sub-projects that's fine too.  I don't want to stifle creativity on account of textbook SCM practices.  But now may be a good time to start brainstorming ground rules.  Here's how I'd draft them:

1. Create a directory in subversion with your sub-project name before comitting any new projects
  (e.g., The 'texas holdem' project would go into 'svn://'

2. Be _very_ careful when releasing gems.  Once a gem is released it will propagate to mirror servers.  Choose a good name and respect your users.

3. Our homepage points to, use this wiki for project information.

To unsubscribe or change your settings, visit: