You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2003/12/08 15:45:18 UTC

Bugzilla as project management tool

After a discussion between Andrew, Betrand and me I started to use
Bugzilla as project management tool for CocoonForms and Flowscript. We
have the hope that Bugzilla makes it easier for us to get an overview of
all open tasks and this should also give our users a sense of when they
can expect a certain new feature.

I started with CocoonForms and Flowscript but other roadmap components
(e.g. Portal engine, ...) would be more than welcome. Please have a look
at http://wiki.cocoondev.org/Wiki.jsp?page=ProjectManagement where you
find some links to the roadmap and you'll also find information
concerning the way we manage our project (at least all the things I'm
aware of ;-)


So what does this mean for you?
-------------------------------
Of course nobody is forced to do anything but if you want to support our
initiative

 - enter all the things you're working on into Bugzilla
   and connect them with the target issue
   e.g. I work on intercepted flowscript so I entered a new
   issue: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25325
   and selected "Flowscript" as the component it belongs to.

   Then I added issue 25284 as issue which is blocked by my issue.
   (issue 25284 is "[Roadmap] Flowscript - FUTURE releases")
    --> this means I don't know when it will be finished ;-)

 - if you don't find an appropriate component in Bugzilla (like core,
   CocoonForms, Flowscript, ...) ask Carsten, Giacome, Betrand or
   me to create a new one

 - if you want to comment on a certain issue don't use the mailing list
   but enter your comments directly into Bugzilla
   (for software design e.g. the way we developed Blocks the mailing
    list is still the way to go, at least IMHO)


If you wonder why we need this?
-------------------------------
I hope it's not (too much) bureaucracy but

 - gives much better overview
 - reduces the danger of duplication of our efforts
   because two people are working on the same issue
 - people who don't follow the dev-list very closly
   can also get an overview of the current project status
   without having to subscribe
 - our users can vote on a feature they really need 
   (every user can vote on 30 features now)
 - good ideas don't get lost in the mail archives


There is always room for improvment so I'm waiting curious for your
comments!

Cheers,
Reinhard


Re: Bugzilla as project management tool

Posted by Sylvain Wallez <sy...@apache.org>.
Reinhard Poetz wrote:

>After a discussion between Andrew, Betrand and me I started to use Bugzilla as project management tool for CocoonForms and Flowscript. We have the hope that Bugzilla makes it easier for us to get an overview of all open tasks and this should also give our users a sense of when they can expect a certain new feature.
>  
>

I found an Eclipse plugin for Bugzilla at 
http://www.cs.ubc.ca/labs/spl/projects/hipikat/
(easy intall by pointint the update manager to 
http://www.cs.ubc.ca/labs/spl/projects/hipikat/updates).

Unfortunately, it throws an OutOfMemoryError when trying to update the 
search window... (Eclipse 2.1)

Can somebody else try this too?

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com



Re: Bugzilla as project management tool

Posted by David Crossley <cr...@indexgeo.com.au>.
Bertrand Delacretaz wrote:
> Reinhard wrote:
> >
> > ...Of course nobody is forced to do anything but if you want to 
> > support our initiative...
> 
> So hopefully people will use this and don't let it slip into
> the "good idea never used it" category. I'm optimistic;-)

To lead by example is all that we can do. When the issue tracker
becomes something that we cannot do without, then it is working.

--David
(getting lonely talking to myself while the rest of the world sleeps)


RE: Bugzilla as project management tool

Posted by David Crossley <cr...@indexgeo.com.au>.
Reinhard Poetz wrote:
> Bertrand Delacretaz wrote:
> 
> > Hi Reinhard,
> > 
> > Thanks very much for setting this up!
> 
> You're welcome

Thanks to everyone involved in getting our issue tracking
into better shape.

<snip/>
> Big +1 for your precise explanation, this is exactly what I meant. I
> think we (as project) have to learn to find the balance and I'm very
> optimistic we'll find it!

Yes, this is all good progress in the management of such
an enormous project. I hope that someone finds time to turn
that into a guidelines document.

--David


RE: Bugzilla as project management tool

Posted by Reinhard Poetz <re...@apache.org>.
From: Bertrand Delacretaz [mailto:bdelacretaz@apache.org]

> Hi Reinhard,
> 
> Thanks very much for setting this up!

You're welcome

> If people here "bite" (*and* do the underlying
> implementations ;-) I'm 
> sure this will be a big help for project coordination.
> 
> Basically what you suggest is "if you're working on something it must
> be an issue in bugzilla" - I like this rule, it helps a lot in 
> answering the "projects questions" that we discussed at the GT.

Yep

> 
> But as you say
> > ...Of course nobody is forced to do anything but if you want to 
> > support our initiative...
> 
> So hopefully people will use this and don't let it slip into
> the "good 
> idea never used it" category. I'm optimistic;-)

I'm optimistic too :-)

> But I think we must be careful about this:
> 
> > ... - if you want to comment on a certain issue don't use
> the mailing
> > list
> >    but enter your comments directly into Bugzilla
> >    (for software design e.g. the way we developed Blocks the mailing
> >     list is still the way to go, at least IMHO)...
> 
> I know there is reluctance to move discussions from the
> mailing list to 
> bugzilla, and having one more "discussion place" (besides lists, wiki 
> and IRC) might fragment discussions.
> 
> Maybe we should:
> a) Keep discussions on the list, unless they are very specific to a
> particular bugzilla issue.
> 
> By "very specific" I mean "of no interest to people who are
> not working 
> on this issue". Hard to decide for sure, it's a question of balance. 
> People can add themselves in CC to specific issues anyway if 
> they want 
> to be sure to follow the discussions.
> 
> b) Document in bugzilla the *outcome* of discussions, with
> links to the 
> mail archives.
> This is already happening and I like it, see issues 25286 and 
> 25285 for 
> example.
> 
> c) In mailing list discussions, include the bugzilla issue
> number like 
> [23454] for cross-referencing.
> 
> It is certainly hard to find a balance between "everything in the
> lists" and "everything in bugzilla", basically, what I 
> suggest is "free 
> talk on the lists" and "documented decisions in bugzilla".
> 
>  From what you wrote, I think you agree but wanted to make
> sure we're on 
> the same page.

Big +1 for your precise explanation, this is exactly what I meant. I
think we (as project) have to learn to find the balance and I'm very
optimistic we'll find it!

--
Reinhard


Re: Bugzilla as project management tool

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Reinhard,

Thanks very much for setting this up!
If people here "bite" (*and* do the underlying implementations ;-) I'm 
sure this will be a big help for project coordination.

Basically what you suggest is "if you're working on something it must 
be an issue in bugzilla" - I like this rule, it helps a lot in 
answering the "projects questions" that we discussed at the GT.

But as you say
> ...Of course nobody is forced to do anything but if you want to 
> support our
> initiative...

So hopefully people will use this and don't let it slip into the "good 
idea never used it" category. I'm optimistic;-)

But I think we must be careful about this:

> ... - if you want to comment on a certain issue don't use the mailing 
> list
>    but enter your comments directly into Bugzilla
>    (for software design e.g. the way we developed Blocks the mailing
>     list is still the way to go, at least IMHO)...

I know there is reluctance to move discussions from the mailing list to 
bugzilla, and having one more "discussion place" (besides lists, wiki 
and IRC) might fragment discussions.

Maybe we should:
a) Keep discussions on the list, unless they are very specific to a 
particular bugzilla issue.

By "very specific" I mean "of no interest to people who are not working 
on this issue". Hard to decide for sure, it's a question of balance. 
People can add themselves in CC to specific issues anyway if they want 
to be sure to follow the discussions.

b) Document in bugzilla the *outcome* of discussions, with links to the 
mail archives.
This is already happening and I like it, see issues 25286 and 25285 for 
example.

c) In mailing list discussions, include the bugzilla issue number like 
[23454] for cross-referencing.

It is certainly hard to find a balance between "everything in the 
lists" and "everything in bugzilla", basically, what I suggest is "free 
talk on the lists" and "documented decisions in bugzilla".

 From what you wrote, I think you agree but wanted to make sure we're on 
the same page.

-Bertrand