From: Yann L. <ya...@le...> - 2005-08-10 01:48:59
|
> > Why not simply making a CVS branch. This exactly what it does... > > Of course you can do that with CVS, but in my opinion it is something of a > hassle when you are just doing quick and dirty stuff. In the case of the > documentation, I might have just one file changed that I want to put up > where everyone one can get at it. Perhaps I will get numerous feedback > about typos and such which can be updated quickly, but serve little purpose > in CVS for revision control. > > The sourceforge project file web interface just seems a little more > accessible for this purpose. One issue is to allow multiple people to update the documentation in a way that might make it temporarily inconsistent, without messing up the main CVS version. As Leon suggests, a new CVS branch is exactly what we need for that. CVS is by far the simplest mechanism for making quick updates available to others: edit a thefile, do "cvs commit thefile", that's it. Everyone who does "cvs update" in their local copy of the branch directory will get the changes. > I am not trying to complicate issues by my suggestion and perhaps this is > not the way things have traditionally been done. Maybe a little change in > packaging/file management/availability will open things up to more > participation. There is definitely a need for opening things up to participation, particularly when it comes to documentation.... -- Yann |