Re: [birt-pmc] Trivial Tickets Idea

[Michael Fox <foxm@xxxxxxxxxx>]

HI Scott,

I think we're just approaching this
from opposite sides.  The new bugzilla field will help the BIRT team
track these items, and they have to be in bugzilla to track the work flow.
 My thought on the wiki based sign up sheet is intended to make it
easier for the outside world to find these work items and register interest
in them, and perhaps link up with other people who have also expressed
interest.  Maybe I'm interested in working on an item, but can't commit
to doing all the work.  If I put that on the wiki, hopefully somebody
else with an interest will see it and we can collaborate.  Bugzilla
is essential, but I don't see it fostering that kind of signup.

        Mike

Scott Rosenbaum <scottr@xxxxxxxxxxxxxxxxxxxxx>
Sent by: birt-pmc-bounces@xxxxxxxxxxx

04/10/2008 05:46 PM

Please respond to
"BIRT PMC communications \(including coordination, announcements,        and Group discussions\)" <birt-pmc@xxxxxxxxxxx>

To	"BIRT PMC communications \(including coordination, announcements,        and Group discussions\)" <birt-pmc@xxxxxxxxxxx>
cc
Subject	Re: [birt-pmc] Trivial Tickets Idea

Mike,

My fear is that if we maintain a separate list some place, that list will
be out of date as soon as we publish it.  I would prefer to have a
field that we could set in bugzilla with a query that we could run to see
the items.  I have asked Bjorn if any of the other Eclipse projects
maintain a similar mechanism.  I'll let you know what he says, hopefully
at Monday's PMC.

Scott

Michael Fox wrote: 

Scott, 

I think I see what you are getting at here, but I'm not sure what it will
accomplish. I assume the purpose of this is to get committed work items
implemented by people outside the current committer base.  I can only
think of 2 reasons why somebody would pick up one of these:  they
want to establish credibility towards becoming a committer, or they need
that item for their own business reasons.  In either case they would
likely try to proceed independent of the "trivial" flag.

Customer submitted bugzilla entries with this flag set will presumably
contain the necessary implementation code.  However, it will still
have to be reviewed/accepted by a committer.  What will that person
do differently based on this flag?   

I'm not against this, I think I would just structure it a bit differently.
 How about maintaining a list  on the web site (or wiki) of "desirable
but unstaffed work items" and solicit volunteers.  These could
vary in scope/complexity, maybe rated as such.  People sign up to
work on them, collaborate if multiple people are interested, and submit
their results through the normal bugzilla process. BIRT team involvement
would be minimal or none until the bugzilla submission.  Its much
more visible on the front page of the web site, with a link to the signup
wiki page. 

        Mike

"Wenfeng Li" <wli@xxxxxxxxxxx>
Sent by: birt-pmc-bounces@xxxxxxxxxxx

04/09/2008 01:33 PM

Please respond to
"BIRT PMC communications \(including coordination, announcements,        and Group discussions\)" <birt-pmc@xxxxxxxxxxx>

To	"BIRT PMC communications \(including coordination, announcements,        and Group discussions\)" <birt-pmc@xxxxxxxxxxx>
cc
Subject	RE: [birt-pmc] Trivial Tickets Idea

Scott 
  
+1 fot his idea.    How does this OSS project spread the word
about their “trivial tickets”? 
  
WEnfeng

---

From: birt-pmc-bounces@xxxxxxxxxxx
[mailto:birt-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Scott Rosenbaum
Sent: Wednesday, April 09, 2008 8:18 AM
To: BIRT PMC communications (including coordination, announcements,and
Group discussions)
Subject: [birt-pmc] Trivial Tickets Idea 
  
Guys,

I was reviewing a different OSS project and noticed that they have the
idea of Trivial Tickets, which are relatively simple tasks that they open
up to contributions from other people.  I was wondering if it makes
sense to create something similar for BIRT where some of our Bugzilla entries
are flagged in a way that allows people to realize that these are considered:
   a) valued contributions to BIRT
   b) relatively low priority
   c) relatively few dependencies
   d) open for contributions

Basically it is a way to solicit community contributions on non-critical
wish list items.  

Thoughts?

Scott_______________________________________________
birt-pmc mailing list
birt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/birt-pmc

---

_______________________________________________
birt-pmc mailing list
birt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/birt-pmc
  _______________________________________________
birt-pmc mailing list
birt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/birt-pmc