Josh Buchanan wrote: > First, > > Great project you folks have going here. I just paid the Paypal piper :)
I agree. :-) bsag, lukemelia (et. all) are kickin' out some amazing work! > Second, I'd like to help. I'm a total hack (not in the good sense), but > I'm really not all that familiar with CVS, let alone Subversion. There > are lots of new features I'd love to play with, but I'm not comfortable > with the mechanics of checking it out (I do have a pull of the latest > stable version via SVN). I too have wanted to help for a while but find, while in school, I don't have the time to do much. Helping you get started with Open Source development is something I can do quickly (I hope). SVN is not something to be afraid of... Think of it as a web server that adds some extra capabilities to normal HTTP GET and HTTP POST -- it supports versions (among other things). For a full book on SVN: http://svnbook.red-bean.com/ If you want to develop I could probably offer more guidance if I knew what you were developing on. There are a variety of tools for all the different platforms. Everything from command line tools (svn) to GUI environments (http://rapidsvn.tigris.org/). If you want to do some real fun stuff you probably want to get to installs going. [1] your stable release (for your real life) [2] your devel release (to break and fix) Goto http://dev.rousette.org.uk/browser and you'll be able to poke through the code. When I looked, it appeared as though the latest trunk is 537. svn co --username=guest http://www.rousette.org.uk/svn/tracks-repos/trunk tracks That pulled the latest trunk for me. CVS and SVN (and most other SCM systems) use the idea of source code being a tree. The 'trunk' is the mainline that is growing. People 'branch' off and do other work. At key points (ie. releases) people will 'tag' a series of files together so that there is a name they can later refer to to get another copy of it. If you are just developing at home you won't need to worry about any of this now. When it comes to 'merging' your changes in ... cross that bridge when you come to it. :-) > I'm happy to help myself--but I'd like the experts to give a little > guidance before I hose my production instance ;) Guidance: --------- Don't play in production land! Make a sandbox to play in (doesn't hurt when you fall ... remember your childhood). Copy your current production DB into place and use a copy of the tracks DB you've pulled out. When you have tested your changes then (maybe) look at adding them to your production release. I don't know how many times I've pooched lots of hard work this way. :-D > Again, great project. I'm looking forward to the future. Agreed. I too look forward to the future. Cheers, .cpb ----- Colin Bell <[EMAIL PROTECTED]> http://www.techknowlogic.net _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
