On 11/03/15 23:53, Andreas Kupries wrote:
On Wed, Mar 11, 2015 at 11:16 AM, jungle Boogie <jungleboog...@gmail.com> wrote:
Hi Andreas,
On 11 March 2015 at 10:58, Andreas Kupries <andre...@activestate.com> wrote:
On Wed, Mar 11, 2015 at 10:34 AM, Richard Boehme <rboe...@gmail.com> wrote:
I would be strongly in favor of presets in Fossil as everyone has outlined
"open source" - everyone can read
"corporate" - only registered users can read, and new users have
minimal permissions
"private" - I'm unsure what this means. Comments?
Single user with total access, nobody else.
The repo at
http://core.tcl.tk/akupries/lspace/
should be an example. Locked down entirely, to myself.
So the difference between private and corporate is the number of
people who have access?
Private = 1 user all permissions
.. but the developer and reader privileges still exist so the initial
user can easily add collaborators,
the effect would not be very different from a Github private repo
Corporate = many users & different permissions
Something like:
1) nobody can read the wiki and tickets, but has no access to code (or
whatever else may be stored in a fossil repo)
2) users who register themselves can edit the wiki and open or comment
on tickets, but have no access to code
Open source = ability to clone view code on site
This is my view, yes. With corporate more open than private, and more
closed than OSS in the default perms.
Is that correct?
Thanks.
Richard
-------
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
