Another way for this to be done is using bzr and store the mainline in LP, register the cookbook as a product and add the created branch. This would entail those involved to be part of a team that is reponsible for the product. The advantage of this is everyone gets a copy of all revisions of the project at the same time have a central place to push changes to their respective branches (via sftp).
On the other hand, since all documentation work is centralised on one svn server, the project will gain the advantage of having everything in one repository as well as automatic publishing of changes to the development documentation pages, not to mention matt can easily create translation templates then upload it to rosetta. Best, Jerome -- Jerome Gotangco [EMAIL PROTECTED] Mobile: +639196555242 GPG: 0x9E379FC6 -- edubuntu-devel mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
