RE: [PHP] I need ideas for things to code -- Roach vs Bugzilla
-Original Message- Sent: Friday, April 24, 2009 4:31 PM Subject: Re: [PHP] I need ideas for things to code how about: a better bugzilla replacement in php I got that one done for you: http://www.daevid.com/content/examples/roach.php p.s. the PHP code is absolute crap by the way. I inherited the start of this and just had to keep building on top of it, so i never got time to re-write it properly, only fix as I went. It's a dead project at this point, so someone is free to pick up where I left off as Lockdown is no more. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla
On Mon, Apr 27, 2009 at 2:47 PM, Daevid Vincent dae...@daevid.com wrote: I got that one done for you: http://www.daevid.com/content/examples/roach.php p.s. the PHP code is absolute crap by the way. I inherited the start of this and just had to keep building on top of it, so i never got time to re-write it properly, only fix as I went. It's a dead project at this point, so someone is free to pick up where I left off as Lockdown is no more. Well, thanks for that; it seems like it's got a lot of features. A big one to examine would be looking at its integration with svn. But I like the triage assignment by default. It's a little disappointing though if you're selling it with the note of the code is crap ... :) I'll toss it over to my boss who is the one messing around with trac/redmine/etc and see what he has to say. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] I need ideas for things to code -- Roach vs Bugzilla
-Original Message- From: Michael Shadle [mailto:mike...@gmail.com] Sent: Monday, April 27, 2009 2:59 PM To: Daevid Vincent Cc: php-general@lists.php.net Subject: Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla On Mon, Apr 27, 2009 at 2:47 PM, Daevid Vincent dae...@daevid.com wrote: I got that one done for you: http://www.daevid.com/content/examples/roach.php p.s. the PHP code is absolute crap by the way. I inherited the start of this and just had to keep building on top of it, so i never got time to re-write it properly, only fix as I went. It's a dead project at this point, so someone is free to pick up where I left off as Lockdown is no more. Well, thanks for that; it seems like it's got a lot of features. A big one to examine would be looking at its integration with svn. But I like the triage assignment by default. It's a little disappointing though if you're selling it with the note of the code is crap ... :) I'll toss it over to my boss who is the one messing around with trac/redmine/etc and see what he has to say. I just didn't want someone to think this was the caliber of code I wrote! ;-) I cleaned up what I could, when I could, but we're not in the business of writing a CR tracker -- so it got a small percentage of my time. I am using Trac personally, but I'm not a fan of Trac's ticket system. Roach is way more powerful in that respect, but the overall Wiki/SVN/Ticket/Plugin integration outweighs the lacking Ticket system. Roach is the best ticket system I've ever used -- and I say that honestly. I'm stuck with FogBugz here at work and really don't like it. I hated Bugzilla. I've tried a few others as well and didn't like them either. For sure Roach isn't as polished or pretty or fancy-pants web 2.0 ajaxy. But it is solid. it works well and shows the info you want when/where you want it. It's fast. It's flexible. And IMHO it works the way developers work. Like I said, 6 years of daily use by 25 developers really helped to refine what mattered and what didn't. The hooks with SVN are also great. For example someone couldn't commit to SVN without the corresponding CR in Roach in the commit message. I thought I had the SVN pre-commit and post-commit hooks in the tarball, but apparently not. They were written in Ruby, so maybe not so useful to you anyways. I'm sure i have them somewhere if you really wanted them. d -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla
On Mon, Apr 27, 2009 at 3:27 PM, Daevid Vincent dae...@daevid.com wrote: I just didn't want someone to think this was the caliber of code I wrote! ;-) totally understood. i don't like people getting the wrong idea of my code too :) I am using Trac personally, but I'm not a fan of Trac's ticket system. Roach is way more powerful in that respect, but the overall Wiki/SVN/Ticket/Plugin integration outweighs the lacking Ticket system. Me too. The whole wiki style is a bit funky for ticketing. I think bugzilla is nasty and I hate supporting old CGI programs. It just seems like they never change design-wise, definately UI but also conceptually for the most part. The hooks with SVN are also great. For example someone couldn't commit to SVN without the corresponding CR in Roach in the commit message. I thought I had the SVN pre-commit and post-commit hooks in the tarball, but apparently not. They were written in Ruby, so maybe not so useful to you anyways. I'm sure i have them somewhere if you really wanted them. Sure, you should include them in the package. Worst case if we wind up doing something with hooks I can use them as a cue on how to reject without including a ticket ID for example, etc. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla
Michael Shadle wrote: On Mon, Apr 27, 2009 at 5:46 PM, Shawn McKenzie nos...@mckenzies.net wrote: #1 Which one are we talking about? Tickets/trackers (Bugzilla, Mantis, Roach, you name it) and SCM integration tools (Redmine, Trac) OK, so geared towards software bugs I assume (I haven't used any)? #2 Having rarely used either, what are the main (must have) features? For general purpose ticketing engine, it would need custom field support. For specifically designed solutions it depends. For us we only need a few fields, really. I've hacked together bits and pieces in only a few minutes, we're using a custom one right now, but one with active development would be nice - APIs and plugins for extensibility, XML/RSS feeds, etc. Those aren't required but should come standard nowadays... OK, so I am not familiar with the bug tracking software or anything that it needs to do, but I find it hard to believe that at the top of the list would be APIs, plugins, RSS. These don't sound like main features of a bug tracking app. #3 What are the needed features that other OSS solutions don't offer? Clean interface, easy reporting, integration with SCM (i.e. svn) - various apps do various combinations of these. If it was done in PHP it would be perfect as we could bolt on our custom authentication into it. Trac is written in Python and Redmine in Ruby; we'd have to re-code our authentication integration into one of those languages for it. Oh, and multiple project support. Trac does not support this. Redmine claims to. (as in, multiple svn repositories as well) I can dig it... #4 What are the great features missing from free and commercial apps? I am not sure I've seen a commercial PHP app that does this. Doesn't matter PHP or other. What is not available in any other product that would be awesome to have (wish list)? -Shawn -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla
Michael Shadle wrote: On Mon, Apr 27, 2009 at 3:27 PM, Daevid Vincent dae...@daevid.com wrote: I just didn't want someone to think this was the caliber of code I wrote! ;-) totally understood. i don't like people getting the wrong idea of my code too :) I am using Trac personally, but I'm not a fan of Trac's ticket system. Roach is way more powerful in that respect, but the overall Wiki/SVN/Ticket/Plugin integration outweighs the lacking Ticket system. Me too. The whole wiki style is a bit funky for ticketing. I think bugzilla is nasty and I hate supporting old CGI programs. It just seems like they never change design-wise, definately UI but also conceptually for the most part. The hooks with SVN are also great. For example someone couldn't commit to SVN without the corresponding CR in Roach in the commit message. I thought I had the SVN pre-commit and post-commit hooks in the tarball, but apparently not. They were written in Ruby, so maybe not so useful to you anyways. I'm sure i have them somewhere if you really wanted them. Sure, you should include them in the package. Worst case if we wind up doing something with hooks I can use them as a cue on how to reject without including a ticket ID for example, etc. OK, so I'm just now jumping into the conversation, not because I use or need a ticketing system, quite the opposite. I have rarely used a ticketing system and wonder whether this discussion is more about a ticketing system (I have a problem with this service/widget and need help) or bug tracking (software has bug, from user or dev)? #1 Which one are we talking about? #2 Having rarely used either, what are the main (must have) features? #3 What are the needed features that other OSS solutions don't offer? #4 What are the great features missing from free and commercial apps? -- Thanks! -Shawn http://www.spidean.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla
On Mon, Apr 27, 2009 at 5:46 PM, Shawn McKenzie nos...@mckenzies.net wrote: #1 Which one are we talking about? Tickets/trackers (Bugzilla, Mantis, Roach, you name it) and SCM integration tools (Redmine, Trac) #2 Having rarely used either, what are the main (must have) features? For general purpose ticketing engine, it would need custom field support. For specifically designed solutions it depends. For us we only need a few fields, really. I've hacked together bits and pieces in only a few minutes, we're using a custom one right now, but one with active development would be nice - APIs and plugins for extensibility, XML/RSS feeds, etc. Those aren't required but should come standard nowadays... #3 What are the needed features that other OSS solutions don't offer? Clean interface, easy reporting, integration with SCM (i.e. svn) - various apps do various combinations of these. If it was done in PHP it would be perfect as we could bolt on our custom authentication into it. Trac is written in Python and Redmine in Ruby; we'd have to re-code our authentication integration into one of those languages for it. Oh, and multiple project support. Trac does not support this. Redmine claims to. (as in, multiple svn repositories as well) #4 What are the great features missing from free and commercial apps? I am not sure I've seen a commercial PHP app that does this. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] I need ideas for things to code -- Roach vs Bugzilla
On Mon, Apr 27, 2009 at 6:09 PM, Shawn McKenzie nos...@mckenzies.net wrote: OK, so geared towards software bugs I assume (I haven't used any)? Web site development, a little system administration. But yes, basically software bugs. OK, so I am not familiar with the bug tracking software or anything that it needs to do, but I find it hard to believe that at the top of the list would be APIs, plugins, RSS. These don't sound like main features of a bug tracking app. APIs for bug insertion, deletion, reporting, etc. is not far off from a core product. Especially in web 2.0 land nowadays. We have multiple installations of bugzilla and other tracking mechanisms in and outside of the company feeding off each other, with no clean interfaces. Of course there are hundreds of generic bug tracking programs out there. Anyone with a PHP book can make one. We'd like to align with an industry standard type one, or one with an active community, but there is no real big one I am aware of other than Bugzilla (if not factoring in language) or Mantis (for PHP), or with SCM interaction Redmine and Trac. Trac won't work for us because we have multiple repositories/projects. We'd have to hack together some sort of solution to manage all of them from one, or install a bunch of instances, and then we'd have bugs in multiple systems to track. Each developer on our team handles code for at least one project, just FYI. Redmine may work, but we need more time to determine if we can hack our own auth layer on top of it. Even then I am not sure if it will meet our needs 100% or not. We have not evaluated it enough yet. Doesn't matter PHP or other. What is not available in any other product that would be awesome to have (wish list)? Most products are bloated. Part of my wish list would be that it is written in PHP, so our team can extend it without writing beginner insert language here code to try to customize the couple things we'd need to tweak (like the auth layer) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
