Well, I grabbed all kinds of solutions to my problems with issues such as the Recommended DVCS engine for hosting many independent patches and Using the Mercurial patch queue repository on BitBucket for many users and patches , but hopefully this will be the last question I need to ask. how to set initial control for my project described in https://sourceforge.net/p/iotabuildit/wiki/Home/ . Then I can accept some answer to other questions and continue.
Requirements that I try my best to fulfill:
- Making changes to the source code (patches) should be very easy for the user. This means that they do not need to download the version control client.
- Any version of the code should be easily hosted on the network, because it doesn’t work in Chrome when running from a local file set due to W3C security requirements (which IE apparently ignores but respects Chrome).
- Users should be able to independently register and automatically receive permissions to make patches that can be played and viewed by any other person (for example, Little Big Planet, but more integrated), allowing you to change something, and not just add content).
The paths I've tried so far have failed for the following reasons:
- Mercurial Patch Queue - after studying this for a short time, I found it to be too complicated for the average player / user with whom he can participate. We are talking about potential non-developers here.
- Github BitBucket. - DVCS . , , , - . , .
, , , -, - . PHP- SourceForge, :
- / , ""
- .
- , PHP script, HTTP.
- .
- . ( , , - , )
- PHP script, , -. , ( , ).
, , . , , , PHP script . DVCS, , -, , , , . , , . , .
, , - DVCS, DVCS . ? ( SourceForge? Dreamhost, ( ) Mercurial .)