[Monotone-devel] Intented organization of projects/databases

[Peter Schuller]

Hello,

what is the intended way to organize multiple projets with monotone?

On the one hand, the monotone database seems designed to be pretty
general, such that instead of having one database per project one could
choose to have a single database per "administrative unit" (local user,
server, etc). But on the other hand the granting of write permissions
seems to be user-global rather than per database (~/.monotone), while
public keys are kept in the database rather than in ~/.monotone where
the permissions are specified.

What is the "preferred" organizational structure in a situation with
multiple unrelated projects which in turn has multiple branches each?

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <address@hidden>'
Key retrieval: Send an E-Mail to address@hidden
E-Mail: address@hidden Web: http://www.scode.org

signature.asc
Description: OpenPGP digital signature