[fossil-users] limited ticketing
Hi, is it possible to configure fossil server so, that some clients will be able only submit tickets (and even not see other tickets or maybe see only tickets that they have submitted)? This mode would be useful for customers whom you want to submit bug reports without being able to observe the whole development process. Thank you, ST ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Nested check-outs
Hi Will, fossil open --nested allows opening a fossil within an existing checkout. This question came up earlier this week as well; it may be worth looking at the archives. Solutions included fossil open --nested and scripting a checkout of external dependencies. Cheers, Gareth On Thu, 17 Nov 2011 04:38:49 -, Will Duquette w...@wjduquette.com wrote: Howdy! Is there a document that describes the best practices for a project that involves components from multiple fossil repositories? For example, suppose I've got an infrastructure library that is in its own fossil repository. And I've got an application that uses that infrastructure library. With Subversion, I'd do an svn:external to pull the infrastructure library into my working area as a subdirectory. Is there an equivalent way to do this with fossil that won't get me into trouble? Thanks very much! Will Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Nested check-outs
On Nov 17, 2011, at 2:04 AM, Gareth Roberts wrote: Hi Will, fossil open --nested allows opening a fossil within an existing checkout. This question came up earlier this week as well; it may be worth looking at the archives. Solutions included fossil open --nested and scripting a checkout of external dependencies. Thanks, Gareth. I knew I'd seen something, but I couldn't remember enough about what it was to even go looking for it. If I understand it correctly from the previous posts to the list, using fossil open --nested just allows a nested checkout to live within a parent checkout without confusing fossil; but the two checkouts are essentially separate. In other words, it's like a Subversion svn:external, except that fossil doesn't check it out for you automatically; you have to do that yourself (i.e., by make getmydependencies or something like that). Thanks! Cheers, Gareth On Thu, 17 Nov 2011 04:38:49 -, Will Duquette w...@wjduquette.com wrote: Howdy! Is there a document that describes the best practices for a project that involves components from multiple fossil repositories? For example, suppose I've got an infrastructure library that is in its own fossil repository. And I've got an application that uses that infrastructure library. With Subversion, I'd do an svn:external to pull the infrastructure library into my working area as a subdirectory. Is there an equivalent way to do this with fossil that won't get me into trouble? Thanks very much! Will Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] A little self-promotion
And, most of all, for users it makes documentation just a click away. Cheers, Jacek 2011/11/16 Steve Havelka smh...@gmail.com: On 11/16/11 4:11 PM, Ron Wilson wrote: On Wed, Nov 16, 2011 at 4:15 PM, Jacek Całajacek.c...@gmail.com wrote: and wonder why fossil is by default so humble to not include a link to its web site in the footer. Maybe to encourage users to contact their project leader first? In my team, I've been handling the questions. For public-facing repos, this is a great idea. It's like how Wordpress has its link at the bottom of the default theme, a cheap and easy way to bring more people to the project. I'm not sure if anyone would actually be confused about whose project it is, just by the presence of that link. ___ 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
Re: [fossil-users] limited ticketing
On Nov 17, 2011, at 11:01 AM, ST wrote: is it possible to configure fossil server so, that some clients will be able only submit tickets (and even not see other tickets or maybe see only tickets that they have submitted)? This mode would be useful for customers whom you want to submit bug reports without being able to observe the whole development process. Have you looked into permissions page in the admin section of the web interface? IIRC this is perfectly possible. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] limited ticketing
On Thu, 2011-11-17 at 14:34 +0100, Remigiusz Modrzejewski wrote: On Nov 17, 2011, at 11:01 AM, ST wrote: is it possible to configure fossil server so, that some clients will be able only submit tickets (and even not see other tickets or maybe see only tickets that they have submitted)? This mode would be useful for customers whom you want to submit bug reports without being able to observe the whole development process. Have you looked into permissions page in the admin section of the web interface? IIRC this is perfectly possible. as far as I understand one can enable/disable ticket viewing completely, but I don't see a way for a user to be able to see/comment/append _only_ to tickets submitted by him... Thank you ST ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] limited ticketing
On Thu, Nov 17, 2011 at 6:02 PM, ST smn...@gmail.com wrote: as far as I understand one can enable/disable ticket viewing completely, but I don't see a way for a user to be able to see/comment/append _only_ to tickets submitted by him... Fossil doesn't offer that level of granularity. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] limited ticketing
On Thu, Nov 17, 2011 at 12:28 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Nov 17, 2011 at 6:02 PM, ST smn...@gmail.com wrote:
as far as I understand one can enable/disable ticket viewing completely,
but I don't see a way for a user to be able to see/comment/append _only_
to tickets submitted by him...
Fossil doesn't offer that level of granularity.
I think this could be done with TH1 scripting. From the Fossil web UI,
Admin-Tickets. On that page, you can select which of the ticket
related pages to edit..
Assuming your ticket schema has a submitter field, you could have
something like:
if {$login eq $submitter} {
things that only the submitter is allowed to do
}
You could do similar with an assignedto field, as well.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] limited ticketing
On Nov 17, 2011, at 6:28 PM, Stephan Beal wrote: On Thu, Nov 17, 2011 at 6:02 PM, ST smn...@gmail.com wrote: as far as I understand one can enable/disable ticket viewing completely, but I don't see a way for a user to be able to see/comment/append _only_ to tickets submitted by him... Fossil doesn't offer that level of granularity. But it should have, as this seems to be a really reasonable (and perfectly doable) thing to have. Thus I open a ticket (sorry, not time to donate for it): https://fossil-scm.org/index.html/tktview/620506c3b211ff839d11230a6e2a31128de94bf4 Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] limited ticketing
If we have granular permissions for tickets, then we should probably also have it for the wiki (view attachments, view history), we should also separate attach and delete for wiki and tickets, and maybe even throw in permissions related to the timeline and files (such as view newest view hitsory, view patch, view diff) and maybe even download zip instead of tar file. Don't forget about tags and even open and closed names. You could EVEN create permissions for each artifact! That would just be easier, because you wouldn't need to worry about the type. OR We could realize that to do this properly would require a good CMS, which fossil is not, and keep it simple. As you can imagine, my vote's for the latter. Tomek On Thu, Nov 17, 2011 at 8:17 PM, Ron Wilson ronw.m...@gmail.com wrote: On Thu, Nov 17, 2011 at 6:56 PM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: On Nov 17, 2011, at 6:28 PM, Stephan Beal wrote: Fossil doesn't offer that level of granularity. But it should have, as this seems to be a really reasonable (and perfectly doable) thing to have. Thus I open a ticket (sorry, not time to donate for it): https://fossil-scm.org/index.html/tktview/620506c3b211ff839d11230a6e2a31128de94bf4 As I posted earlier, this could be done in TH1. ___ 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
