On Tue, 2006-10-31 at 22:06 +0100, Nicolas Maufrais wrote:
> We could now start collaborating on the manual. To do so we have to be > able to share our work, that is why we need SVN accounts for people > working on the documentation. At the beginning, there will be a lot of > revisions on the manual, and we don't want to commit our changes > everyday into the "main" SVN branch. Isn't it possible to set up a > documentation-specific SVN branch? Why not using some of distributed version control systems (i use darcs, but git, bzr, mercury are also, afaik, in the same category) where patches can be easily distributed amongs doc-contributors before applying them to (most probably) central svn server? I recommend usage of Tailor (http://progetti.arstecnica.it/tailor) which enables everyone to use his/her preferred vcs and exchange with others' systems. > That way, we would commit our work into that branch, and commit major > changes less often into the official SVN branch. When there will be > less changes made to the manual, we could decide to merge the > development branch into the main SVN branch. I also agree that separate repository for documentation would be nice, so that all work is done there and only 'final' patch is pushed to the main Cinelerra. > I could create one shell script to do all of these tasks. But I don't > think that's the way to go. I assume make should handle the process. Can > someone help me with that issue? That would avoid me to RTFM about > makefiles, and I could concentrate my efforts on working on the manual's > contents. I was working a little bit with autoconf tools and can try to take a look, but it has to wait some days before I'll get some time. > > Since we are almost ready to collaborate on the manual, who is > interested in contributing to the manual? I am. > BTW, should we use American English, or Great-Britain English in the > manual? What's your opinion? Being not native English speaker, I don't have preference here. Sincerely, Gour
signature.asc
Description: This is a digitally signed message part
