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?
Thanks. Richard On 3/11/15, Ron W <[email protected]> wrote: > On Wed, Mar 11, 2015 at 1:49 AM, Graeme Pietersz <[email protected]> > wrote: >> >> On 11/03/15 00:45, Ron W wrote: >>> >>> I'm thinking he wants 2 sets of default settings: The existing one >>> (which >>> he perceives as being open source oriented) and another set that are >>> more >>> appropriate for use by software teams within a "corporate environment". >>> >>> It would be nice to have, and not just for corporate teams. It is bit >>> of >> a pain to set up a repo that has nothing publicly accessible - i.e. only >> logged in users see anything. It is not a huge problem, but it is a mild >> annoyance for those of us who regularly set up new repos. It would be >> nice >> to just click a button or run a command that sets sensible defaults for a >> private repo. > > > I just remembered 2 things that partially mitigate the absence of this: > > 1. "fossil new" has a "--template" option to obtain settings from. It > claims to require a path to the repo file. > > 2. "fossil config" has "export", "import", "merge" and other commands to > save/load settings to/from a file or even another Fossil server. > -- Thank you. Richard Boehme Email: [email protected] Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
