| *** Joins: kirillka (~Miranda@global01.vester.ru) | 00:53 | |
| dhx_m | nuclear_eclipse: hi | 01:13 |
|---|---|---|
| dhx_m | nuclear_eclipse: regarding bug #11394 I don't like the proposed solution in the comments | 01:16 |
| dhx_m | nuclear_eclipse: actually now I look at it... it seems OK I guess | 01:17 |
| dhx_m | nuclear_eclipse: I think the issue here is that we can't log the user in under the anonymous account because an anonymous account may not exist | 01:18 |
| dhx_m | nuclear_eclipse: thus we have to integrate auth_is_user_authenticated() checks all over the plan | 01:18 |
| dhx_m | *place | 01:18 |
| *** Quits: wolog (~wolog@AOrleans-152-1-29-130.w90-21.abo.wanadoo.fr) (Read error: Connection reset by peer) | 01:50 | |
| *** Joins: giallu (~giallu@fedora/giallu) | 02:29 | |
| *** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 02:39 | |
| *** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 02:44 | |
| *** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 02:45 | |
| *** Joins: fanno (~b3g@193.3.95.240) | 03:03 | |
| *** Joins: wolog (~wolog@195.6.104.193) | 03:07 | |
| *** Joins: davidinc (~d5374b13@gateway/web/freenode/x-zbrqegyqylmwgokc) | 03:20 | |
| *** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 03:40 | |
| *** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 03:42 | |
| *** Quits: kirillka (~Miranda@global01.vester.ru) (Ping timeout: 276 seconds) | 05:19 | |
| *** Joins: kirillka (~Miranda@global01.vester.ru) | 05:49 | |
| *** Quits: kirillka (~Miranda@global01.vester.ru) (Read error: Connection reset by peer) | 07:02 | |
| *** Joins: kirillka (~Miranda@global01.vester.ru) | 07:03 | |
| *** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 07:25 | |
| nuclear_eclipse | dhx_m: I guess my biggest question is what made it stop working in the first place? have you tried doing a `git bisect` on it at all? | 08:23 |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 09:18 | |
| dhx_m | nuclear_eclipse: I haven't been able to reproduce the problem ever | 09:33 |
| *** Quits: davidinc (~d5374b13@gateway/web/freenode/x-zbrqegyqylmwgokc) (Ping timeout: 248 seconds) | 09:47 | |
| *** Quits: kirillka (~Miranda@global01.vester.ru) (Quit: kirillka) | 10:02 | |
| *** Quits: fanno (~b3g@193.3.95.240) (Remote host closed the connection) | 10:16 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 258 seconds) | 11:10 | |
| *** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 276 seconds) | 11:36 | |
| *** Quits: AceSMcCloud (~acesmcclo@cpc4-craw6-2-0-cust461.croy.cable.virginmedia.com) (Ping timeout: 276 seconds) | 12:04 | |
| *** Joins: AceSMcCloud (~acesmcclo@cpc4-craw6-2-0-cust461.croy.cable.virginmedia.com) | 12:05 | |
| *** Joins: jack_spratt (~jack@78.33.217.161) | 12:12 | |
| jack_spratt | Hi, I'm coordinator of a team of editors, and I'm looking for software to manage tasks and revisions and to a small degree control workflow. I don't think that bugzilla is ideally suited to this task, but does anyone know of similar software that is? I've looked at trac and processmaker and mantis and they don't seem ideal. As one of the most popular bug tracking systems I figured mantis users might know | 12:13 |
| CIA-29 | Mantisbt: jreese * r2b20ecf75b7e /core/ (error_api.php event_api.php): Fix potential error loop with output plugins | 12:18 |
| CIA-29 | Mantisbt: jreese master-1.2.x * rbc978309531b /core/ (error_api.php event_api.php): Fix potential error loop with output plugins | 12:18 |
| nuclear_eclipse | jack_spratt: if Mantis can't be configured to do what you want, then you probably won't find any other bug trackers that do =\ | 12:19 |
| *** Joins: AzaToth (~azatoth@wikipedia/AzaToth) | 12:19 | |
| nuclear_eclipse | most other bugtrackers have less flexibility than Mantis when it comes to fitting into alternate workflows or usecases | 12:20 |
| nuclear_eclipse | jack_spratt: definitely try to take some time to look at config_defaults_inc.php and the manage configuration pages, there are a *lot* of ways to change how MantisBT works | 12:21 |
| jack_spratt | nuclear_eclipse: ok, good tip. Is there any kind of modular structure that would allow me to write a plugin that would work with future mbt releases? | 12:22 |
| nuclear_eclipse | yep | 12:22 |
| jack_spratt | is it good/usable (I'm a php dev)? | 12:22 |
| nuclear_eclipse | most of the plugin system is geared more towards adding features to MantisBT, rather than modifying existing functionality though, mainly because it's already so configurable | 12:23 |
| jack_spratt | hmm | 12:23 |
| nuclear_eclipse | well, I'm biased since I wrote it :P | 12:23 |
| jack_spratt | heh | 12:23 |
| nuclear_eclipse | http://docs.mantisbt.org/master/en/developers/dev.plugins.html | 12:23 |
| jack_spratt | you wrote the plugin architecture? | 12:23 |
| nuclear_eclipse | yep | 12:23 |
| jack_spratt | are there many plugins already? | 12:24 |
| nuclear_eclipse | quite a few, but only a handful of mature ones, mostly ones I've written in the course of working on features for my employer | 12:25 |
| nuclear_eclipse | http://git.mantisforge.org/ | 12:25 |
| jack_spratt | they look groovy | 12:25 |
| jack_spratt | well, definitely worth a look, thanks. | 12:26 |
| nuclear_eclipse | if you need any help regarding plugins, feel free to ask | 12:26 |
| nuclear_eclipse | always happy to help others jumpstart the plugin community :) | 12:27 |
| jack_spratt | ok, great. I use mantis for another project for bug tracking and it works very, very well. but this project is different - I'm coordinating a team of editors for the Free Software Foundation Europe and the needs are a bit different to normal bugtracking. | 12:27 |
| jack_spratt | do you know if its possible to tell if an issue has been read by a user or not in a vanilla mantis install? | 12:28 |
| nuclear_eclipse | no, it's not, but that would definitely be possible to implement with a plugin | 12:29 |
| nuclear_eclipse | just hook the bug view events and add a row to a table, and then hook events or create new pages to see | 12:29 |
| nuclear_eclipse | ... to see who's read what | 12:30 |
| jack_spratt | so there is already a bug view event? thats very useful. Do you know if it notes the viewerid? | 12:30 |
| nuclear_eclipse | it doesn't but that's trivial to get from the MantisBT API's | 12:31 |
| nuclear_eclipse | auth_get_current_user_id() | 12:31 |
| jack_spratt | do you think that this would be best suited to a plugin rather than adding it to core? | 12:31 |
| nuclear_eclipse | depends on exactly what you need from it | 12:31 |
| jack_spratt | hmm | 12:31 |
| jack_spratt | how about whether it supports links in emails to refuse to accept assignment of a new issue - like there is a hierarchy of users to whom issues get automatically assigned, and in the email notification a reply or link could be used to automatically refuse to accept the issue, in which case its assigned to someone else? | 12:32 |
| nuclear_eclipse | could always get feedback from the dev team on the mailing list | 12:32 |
| jack_spratt | yes... | 12:32 |
| nuclear_eclipse | the email thing, probably not | 12:32 |
| jack_spratt | pluginable again? | 12:33 |
| nuclear_eclipse | the weakest part of Mantis is email handling IMO | 12:33 |
| jack_spratt | are there sufficient events etc. to work with and add to the email side? | 12:33 |
| nuclear_eclipse | perhaps | 12:33 |
| nuclear_eclipse | depends on how creative you want to get :) | 12:34 |
| jack_spratt | heh | 12:34 |
| nuclear_eclipse | you could hook the text processing event for emails to add a message at the bottom of it, and then create new pages to handle the specific behavior you want | 12:34 |
| jack_spratt | so mantis is OO? | 12:35 |
| nuclear_eclipse | unfortunately we don't yet support features like email templates | 12:35 |
| jack_spratt | OK | 12:35 |
| nuclear_eclipse | only in small parts | 12:35 |
| jack_spratt | for the most part function driven then? | 12:35 |
| nuclear_eclipse | basically, Mantis was created long before PHP really supported OOP abilities, so much of it is still written in a procedural format with global functions | 12:35 |
| nuclear_eclipse | some of the API's have been updated to an OOP format, but not many | 12:36 |
| jack_spratt | OK | 12:36 |
| nuclear_eclipse | lack of developer time is another huge factor =\ | 12:36 |
| jack_spratt | but you're prepared to work with it so the code can't be atrocious? | 12:36 |
| nuclear_eclipse | other than some spots of tight coupling between API's it's actually quite a well laid out application | 12:37 |
| jack_spratt | well that's promising | 12:38 |
| jack_spratt | does it have any kind of support for milestones or releases so that things can be tagged and required and some kind of percentage overview generated? like trac does for instance | 12:38 |
| nuclear_eclipse | and it all follows a relatively sane code standard | 12:38 |
| jack_spratt | hehe, not relative to wordpress I hope | 12:38 |
| nuclear_eclipse | projects can have versions defined in them, and then issues can be set as found-in, targetting, or fixed-in those versions, and then you can use the roadmap and changelog to track that | 12:39 |
| jack_spratt | ah ok, I havent seen the roadmap funtionality, I'll have to investigate that. | 12:42 |
| jack_spratt | Well you've done a good job of selling me mantis as a solution | 12:42 |
| jack_spratt | with a little work it looks like I can do what I want | 12:42 |
| jack_spratt | I guess that there is no 'off the shelf' solution for editors workflow and content management | 12:43 |
| jack_spratt | so I'll probably have to write a little extra functionality nomatter what I use | 12:43 |
| jack_spratt | and I already like mantis - I think its best feature is its relative simplicity. right now I have totally non-technical people submitting and editing bug reports on two continents, and I never thought they would be capable of using bt software | 12:44 |
| nuclear_eclipse | hehe | 12:44 |
| *** Joins: cobexer (~cobexer@188-23-1-5.adsl.highway.telekom.at) | 12:46 | |
| nuclear_eclipse | and if you have a usecase that the plugin system doesn't yet support, I'm more than happy to add new events to the core system | 12:47 |
| *** Joins: moto-moi (~hylke@cara.xs4all.nl) | 12:49 | |
| jack_spratt | are you often in here? | 12:50 |
| nuclear_eclipse | well, my server keeps me logged in here 24/7, so feel free to ping me any time, and I'll get back to you the next time I reattach to Irssi :P | 12:51 |
| jack_spratt | spot on! Thanks again for your help, it was very fortunate that you were here, I may be in touch. Cya | 12:51 |
| *** Quits: jack_spratt (~jack@78.33.217.161) (Quit: Leaving) | 12:51 | |
| *** Quits: wolog (~wolog@195.6.104.193) (Remote host closed the connection) | 13:01 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 13:04 | |
| paul__ | moo | 13:19 |
| nuclear_eclipse | hi paul__ | 13:35 |
| *** Joins: fanno (~Morten@90.184.93.233) | 13:41 | |
| *** Joins: wolog (~wolog@AOrleans-152-1-42-42.w90-21.abo.wanadoo.fr) | 14:36 | |
| *** Joins: siebrand (~beis@sm.xs4all.nl) | 14:44 | |
| *** cobexer is now known as \cobexer|away | 14:47 | |
| *** Joins: cobexer (~cobexer@188-23-97-217.adsl.highway.telekom.at) | 16:01 | |
| *** Quits: \cobexer|away (~cobexer@188-23-1-5.adsl.highway.telekom.at) (Ping timeout: 248 seconds) | 16:04 | |
| *** Quits: cobexer (~cobexer@188-23-97-217.adsl.highway.telekom.at) (Remote host closed the connection) | 17:10 | |
| *** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) | 17:33 | |
| *** Quits: moto-moi (~hylke@cara.xs4all.nl) (Quit: Ex-Chat) | 17:57 | |
| *** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Quit: daryn) | 18:03 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 260 seconds) | 18:35 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 18:52 | |
| *** Quits: AzaToth (~azatoth@wikipedia/AzaToth) (Remote host closed the connection) | 19:40 | |
| *** Quits: scribe9343423 (~scribe934@mantisforge.org) (Remote host closed the connection) | 20:00 | |
| *** Joins: scribe9343423 (~scribe934@mantisforge.org) | 20:00 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 264 seconds) | 20:31 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 21:44 | |
| *** Quits: fanno (~Morten@90.184.93.233) (Read error: Connection reset by peer) | 22:00 | |
| *** Joins: hoover_ (~hoover@97-83-163-61.dhcp.stpt.wi.charter.com) | 23:10 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!