|Subject:||[Monotone-devel] How will policy branches work?|
|Date:||Tue, 05 Feb 2008 13:45:41 +0200|
|User-agent:||Opera Mail/9.22 (Win32)|
Coming from the requirements side I think I would need something like this: I create a monotone database and make someone (like myself) administrator. The administrator can then set read-/write-permissions for branches. For example I could allow developers to use the branch "sourcecode" while the documentation team will use the branch "documentation". Once a file is checked into the branch "sourcecode" it must remain in this branch. The settings would be stored in the database and can not be changed by anyone except the administrator(s). If now a developer and someone from the documentation team synchronize their databases the developer would not get the "documentation" branch and the other one not the "sourcecode" branch. Other branches with read/write access for everyone would be transferred.
I don't know if policy branches in monotone will work like this and if my idea makes actually sense (maybe there are some problems I'm not aware of). The basic idea is that I want to continue to benefit from a distributed version control system while I need more control over who will get and use what. I understand that I can not prevent team members from distributing files in another way. However I would prefer if files are not spread to everyone automatically or accidently by the version control system.
|[Prev in Thread]||Current Thread||[Next in Thread]|