[mapguide-internals] Request for submission

Tom Fukushima tom.fukushima at autodesk.com
Tue Mar 27 13:56:46 EDT 2007


1) I think that the discussion should be on the mailing list; and then
any relevant parts should be copied to the trac defect after discussion
is completed. The reason for having the discussion on the mailing list
is so that we can all see what a submitters submissions are like; then
when it comes time to vote on whether to accept the patch submitter as
someone with actual commit rights, we will all have know the
capabilities of the person.

2) I like the idea of attaching the patch to the trac defect.


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Robert
Sent: Tuesday, March 27, 2007 8:31 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Request for submission

According to the book Producing FOSS by Karl Fogel discussion should not
take place in the tracker. To date I've been using that book to guide
many of our open source efforts. In the end I am not sure it is a big
deal but I'll let the rest of the PSC voice their thoughts.

I do like the idea of new tickets showing up in a number of peoples
inbox to give them visibility, so in the meantime I'll look into how to
go about that.


Jason Birch wrote:
> Hmm.  
> That approach would work well also.  I agree that new tickets don't 
> really get enough visibility.  If we do this, we should also make sure

> that we either set up something like Akismet to block spam, or require

> a login for a ticket submission.
> Jason
> -----Original Message-----
> From: Paul Spencer
> Subject: Re: [mapguide-internals] Request for submission
> I personally think all patches should be filed as enhancements and all

> discussion related to the patch should take place in the ticket so 
> that everything related to that issue is in one place and can easily 
> be found.
> This is what we have done in the past and it is very effective, no 
> information is lost.  The reason it works is because the default owner

> of new issues is a mailing list of people that are interested in new 
> issues.  In this case, it would be very useful if new tickets could be

> assigned to a default owner that is, in effect, the mapguide- 
> internals list.  While the issue is not reassigned, all discussion 
> would be tracked in both the bug and on the list.  Once assigned (i.e.

> someone is going to do something about it), the mailing list user can 
> be removed and anyone that is interested in following further can cc 
> themselves to the bug.
> One thing that I have found with the current setup is that bugs just 
> seem to disappear when filed.  No-one else seems to get notified that 
> a new bug was created etc.  Perhaps that's not the case?
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list