Switching from CVS to Subversion: test svn repo available

[Josh Sled]

On Tue, Oct 25, 2005 at 11:16:51AM +0100, Neil Williams wrote:

| developers on code management. Some method of clearly attributing branches to 
| particular goals beyond a short, cryptic, branch name.

"short, cryptic, branch name[s]" such as? 


| 3. More acceptance that new developers don't necessarily know the unwritten 
| conventions of code management in GnuCash. Encourage such developers to use 
[deletia]
| and how to check it out. Clearly, our documentation needs improving - it 
| appears to be pitched at a level of background knowledge that is higher than 
| the people being attracted to development.

Yes.  Our web site needs 50-75% less words, and more appropriate ones.


| 4. Has anyone seriously considered using the SourceForge project more? SF is 
| sticking with CVS but we don't have to use it. Other projects successfully 
| use the SF Trackers for patches and the SF documentation is much better than 
| our own. Currently, no SF trackers are available. SF Tasks could also help by 
| making out-of-tree work visible to everyone. Again, not enabled. Ideally, 
| everyone with commit access should have membership of the SF project and be 
| able to at least update the trackers, tasks and documentation.

SF--.  It's been slow and painful to use over many years.  I don't find
the features compelling.  I'd rather have someone mail -devel saying
they're working on stuff.  I don't see the advantage of pathes-on-SF
vs. patches-in-bugzilla or patches-to-gnucash-patches.


| 5. More write access to online information outside the mailing list archives. 
| The gnucash.org website is not being updated, new documentation has to go on 
| other websites and isn't always linked from the gnucash site. At least if we 
| used SF more, all listed developers could correct, update and submit 
| documentation on *code management* issues. Using News and/or Docs on SF could 
| dramatically increase the ease of drafting new developers into the fold.

I don't think SF is the right solution, but certainly www.gnucash.org
should have more correct info.  A good consolidating run-through of the
existing (scattered, incomplete, sometimes obsolete) documentation is
required, too.


| Which is why, IMHO, we need more publication of code. "out-of-tree" code 
| should be banished. All code related to gnucash present or future should be 
| visible to all developers, no matter what state it is in. I desperately want 
| people to have a chance to see cashutil, even in it's current state.

So create a branch in CVS.  It's not that hard.

...jsled
-- 
http://asynchronous.org/jsled/ | a=jsled; b=asynchronous.org; echo ${a}@${b}