Team Chat Logs

May 9, 2010

2010 4
Mo Tu We Th Fr Sa Su
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31            
<< <   > >>

[00:48:19.609467]<vlt>jamesw: Where do you want it to appear?
[00:48:59.154527]<jamesw>on the home wiki page, wikistart
[00:49:20.930340]<jamesw>via a macro i guess, i was expecting something like [[TimelineHistory(5)]]
[00:49:45.457229]<jamesw>i like the display on the timeline page, but i would like it more inline with other wiki content
[00:50:50.637204]<vlt>jamesw: Aah, you want it inside the wiki part ... ok ...
[00:52:03.209129]<jamesw>so people can easily tell who is committing what, when, and see it right when they log in
[01:27:12.338868]<macmaN>why dont you make timeline the default handler
[01:28:06.513931]<macmaN>even though i wouldnt do that myself, since i have a dashboard wikipage template
[01:28:19.910854]<macmaN>you can get reports from all basic modules
[01:28:30.806785]<macmaN>wiki has RecentChanges
[01:29:02.032146]<macmaN>source has ChangeLogMacro
[01:29:04.931295]<macmaN>from th
[01:30:26.869038]<macmaN>blog has RecentBlog macro
[01:31:04.513294]<macmaN>so you can assemble your timeline view on wikipage yourself
[01:34:38.320021]<jamesw>hmmm
[01:34:50.955144]<jamesw>i would appreciate more details
[01:42:04.632001]<macmaN>i really have given all you need
[01:56:37.306375]<jamesw>ok well thank you macmaN, i'll do my best
[01:57:20.773889]<macmaN>WikiMacros page is your friend
[01:58:38.543291]<jamesw>ty
[04:12:20.178850]<ychaouche>re-test ?
[04:20:39.326760]<ychaouche>Hello, is there a way to insert a link in from wiki to the last version of a particular line in a source file ? I want that link to point to the same line even if the line number has changed over time (source modifications). Is this doable ?
[04:29:13.258510]<webczat>hey.
[04:29:32.796718]<webczat>Is this ok if user has ticket chgprop permission? he can then change any ticket.
[04:51:43.732646]<webczat>I have trac 0.12
[05:06:04.058359]<webczat>?
[05:43:47.344306]<webczat>I'm not sure......
[06:22:19.148857]<Xeross>I just gave someone TICKET_ADMIN permissions on my trac installation but he still can't edit the tickets
[06:24:26.805476]<Xeross>Any idea what's wrong ?
[06:37:28.819991]<webczat>Xeross: are you sure you wrote a good username?
[06:37:56.884449]<Haegin>hi, I've setup Trac with the authentication module as the trac guide recommends and have registered a user but can't find out how to set permissions for that user. should they appear in the list on the Permissions page in trac admin?
[06:40:59.509217]<Haegin>essentially I want to have one user who can do all the admin stuff, a group for all the other registered users who can create new tickets and add to tickets and then anyone else can only view stuff
[07:01:04.062662]<Xeross>webczat: Yes, I typed it as it showed in the user list of the auth mod I'm using, and it works for me and another guy but not for this guy
[07:08:54.752985]<Xeross>somehow the guys name ended up with a capital R
[07:34:03.425895]<webczat>reff
[07:36:46.988102]<webczat>can i have multiple repos in trac 0.11?
[07:57:17.236949]<webczat>wrrrrrrr
[07:58:19.253041]<webczat>on the wiki, there is a description of an example workflow making it possible to send something for testing to the reporter. but if i'll add the ticketchgprop to the reporter he will be able to modify all tickets, if i won't, he won't be able to modify any. wtf?
[08:02:44.963994]<webczat>what is that?
[08:02:58.841038]<retracile>webczat: Why is it surprising? Granting someone permissions to change tickets gives them permission to change tickets.
[08:04:08.194331]<retracile>webczat: Restricting individual tickets isn't something Trac does out of the box. There is a PrivateTickets plugin on trac-hacks that can restrict on a per-ticket basis
[08:04:58.698963]<webczat>retracile: yeah, but if i will use this workflow example and will send ticket for the testing to the reporter, and reporter won't have chgprop, he won't be able to do anything even if i defined workflow actions
[08:05:18.902219]<webczat>and from the other side if i will give him that permission, he will be able to modify many parameters of all bugs
[08:05:59.219221]<webczat>both are bad
[08:06:28.188309]<retracile>no, they aren't bad.
[08:06:58.689848]<webczat>retracile: if i want to be able to send things for testing to the bug reporter where reporter is an ordinary registered user then it is
[08:07:25.185823]<retracile>Either the reporter can be trusted to make modifications to tickets, or he can't.
[08:07:42.008538]<retracile>webczat: Then you want to use PrivateTickets.
[08:07:42.799417]<webczat>retracile: this is reporter's own ticket!
[08:08:51.755967]<retracile>webczat: The person reporting a ticket does not have special permission access to that ticket in stock Trac. If you want that, go look at the PrivateTickets plugin.
[08:09:35.325930]<webczat>retracile: as i see, privateticket restricts ticket viewing, not modification. and, privateticketpermissions restricts workflow but not priority/etc modifications.
[08:11:15.431405]<webczat>retracile: what i want is to allow reporters to modify ticket state when reporter has valid permissions specified in a workflow, for example i want reporter to be able to reject test request from developer.
[08:11:29.437273]<webczat>but i don't want reporter to modify ticket in any other way
[08:13:27.746071]<webczat>retracile: else this example is useless unless you will allow only developers to have this bug send for testing.
[08:14:19.201781]<retracile>webczat: it's not useless; it's changing the owner of the ticket to the right person
[08:14:59.509046]<webczat>retracile: and the right person must have TICKET_CHGPROP to respond to the change by accepting or rejecting, that gives the person access to all bugs too
[08:15:08.781497]<retracile>yep
[08:15:26.257748]<webczat>and that is not okay
[08:16:05.906899]<webczat>unless i will send tickets to developers
[08:16:23.016596]<webczat>is there discussionplugin for trac 0.12?
[08:17:18.961375]<retracile>webczat: you have a single use-case in your head that you think is so obvious it must be the way things have to work. Well, it's not. Stop saying it's "bad", "not okay", "wtf", etc.
[08:17:30.738380]<webczat>like trachacks tells that it is but plugin description tells that it is not
[08:18:31.124638]<webczat>also can i use urls in git plugin?
[08:18:56.000454]<retracile>source repositories must be local to the machine.
[08:19:28.048463]<webczat>honestly why it differentiates that?
[08:19:56.967593]<retracile>webczat: give it 30 seconds of thought.
[08:20:28.693683]<retracile>latency
[08:21:08.135048]<webczat>git itself supports urls and filenames
[08:22:08.896104]<retracile>Trac needs fast access to the repository, so it needs to be local. Setup a system outside of Trac to pull changes to a local git repo.
[08:23:10.537170]<webczat>yeah
[10:40:29.505947]<webczat>hey.
[10:40:42.114580]<webczat>i don't fully understand what are tasks and trac milestones.
[11:02:13.516464]<hasienda>webczat: milestone = bundle of tickets + duedate, but tasks?
[11:06:23.622014]<webczat>hasienda: ticket type named task that is the default.
[11:06:59.717490]<webczat>and, is it like milestone is "build a large part of software or a module or what" and tickets are like assigning tasks to developers or resolving bugs before it's done?
[11:15:38.101461]<hasienda>webczat: yes, anything that may be achieved by solving some tasks (and maybe bugs). The association is done on a per ticket basis, the milestone selector has all currently defined and unfinished milestones available for assiciating a given ticket to them
[11:27:28.167330]<webczat>can all users associate a milestone or a permission is required?
[11:27:44.167518]<webczat>like ordinary users should not be able to create tasks or assign bugs to milestones
[11:28:06.804717]<webczat>first one can be fixed by developers marking that as invalid, what about the second one?
[11:56:55.775043]<hasienda>webczat: did you have a look at http://trac.edgewall.org/wiki/TracPermissions#TicketSystem ?
[11:59:03.655031]<webczat>do they have that? ;o
[11:59:06.270952]<webczat>will check later
[12:07:06.897349]<hasienda>webczat: in short: TICKET_VIEW is for anonymous, anything else is not for "all users" by default, but in general you could achive by clever mapping of permissions to user(groups)
[12:07:43.557609]<hasienda>webczat: ... a lot of things
[15:03:55.315285]<mstrzele>hi all
[15:06:57.675512]<mstrzele>If anyone had a problem with installing plugins on Debian? I'm trying to install SvnAuthzAdmin, but I'm getting an error message: 'Skipping "svnauthz.admin_ui = svnauthz.admin_ui": (can't import "ImportError: cannot import name get_module_path")'. Trac 0.11.7 from unstable repository.
[15:51:17.422575]<hasienda>mstrzele: np here, but did never try to install from Debian packages but all built from source (=repo checkout) on the target system
[15:52:47.966564]<hasienda>mstrzele: running trac-012dev-r9478 with a number of plugins right now, but certainly had to fix some code for changes between 0.11 and 0.12
[16:55:29.621239]<unlord>crazy
[16:55:35.029012]<unlord>now /Timeline works fine