Source-Forge and how to get your copy

[alpaca]

It was a simple enough task to adapt the EB guide .


I hope you know what you're doing here. You personally will get lots of work to manage this (depending on the rate submissions come in, of course). While I'm not entirely sure how the patch system works, I think you'll also have to manage concurrent updates, merging submissions from several people manually, which SVN otherwise would do automatically. I hope I'm mistaken though. The patch system might understand which changes are made from the revision in question, rather than overwrite any changes made by others when a new file is patched in.

As I understood it the patch system takes into account the revision the patch was generated for. I know it's more work but, well, I don't expect we'll have too many people doing small things in the files themselves. If it's a large bunch of stuff applying patches doesn't happen so often and if it's a regular participant he can request write access which will of course make things easier.
The reason why I don't want anonymous write access is that often enough people don't properly test what they do and then I have to revert the head revision, etc.

I'll check if it's possible to create an anonymously writable branch which would probably be the best solution - if somebody screws something there it at least doesn't disturb other people's work on the current revision.

[bovi]

Anonymous access to only parts should work fine, at least you can specify access for each folder when using svnserve. Not sure about sourceforge but highly likely.

[alpaca]

Anonymous access to only parts should work fine, at least you can specify access for each folder when using svnserve. Not sure about sourceforge but highly likely.

The problem is that I don't think I can access the config files for the project. I'll write to the SF staff.

It's possible with CVS anyways I think.