How many active tickets do we have on sourceforge? How many developers do we have working on tickets? How many tickets/issues are worked on by several people without broader community input?
My sense is that the same handful of developers respond to a half dozen real bugs/issues per year. Half the time we discover that the bug is in an old or patched version of AOLserver. A ticket tracker sounds like a great place to let serious issues with AOLserver go unaddressed by the whole community, not some great tool for organizing a rapidly changing software project. I have one observation of how our email-list based development cycle works, and a possible fix requiring minimal to no organizational effort. On the last adp bug I did a little bit of work, came up with some working updates and then dropped the ball with submitting a formal patch. Problem is I keep my own version of AOLserver, so I don't have an up-to-date checkout from sourceforge. I'm lazy. Forcing me to interact with a ticket tracker wouldn't improve my community involvement, it would probably make contributions even less likely. What might help me, and maybe others, would be a weekly email summary of unfinished business, dropped balls, or whatever, sort of a running tally with new items on top, and stale items toward the bottom. If weekly is too often, maybe every other week, but I tend to forget about stuff after a week. Not sure if the same person would need to do it every week, maybe a rotating task. tom jackson On Fri, 2009-05-29 at 10:27 -0700, Jade Rubick wrote: > Personally, even though I think many in the community don't like Dossy > acting without community involvement, I'd rather see something done > than nothing, as long as it isn't harming the project. > > Perhaps the problem is that there is no formal structure for > Aolserver, so nobody has the "authority" to act on behalf of the > community. > > What if we had a simple voting application somewhere, and the members > of this mailing list each got a vote? > > J > > Jade Rubick > Director of Development > TRUiST > 120 Wall Street, 4th Floor > New York, NY USA > jrub...@truist.com > +1 503 285 4963 > +1 707 671 1333 fax > > www.truist.com > > > The information contained in this email/document is confidential and > may be legally privileged. Access to this mail/document by anyone > other than the intended recipient(s) is unauthorized. If you are not > an intended recipient, any disclosure, copying, distribution, or any > action taken or omitted to be taken in reliance to it, is prohibited. > > > On Sun, May 24, 2009 at 8:04 AM, Dossy Shiobara <do...@panoptic.com> > wrote: > On 5/21/09 4:32 AM, Sep Ng wrote: > To be frank, the only reason why I keep using the Trac > ticket tracker > is that it's the one I found. Had I known that the > sourceforge ticket > tracker was the active one, I would have used that one > instead. Begs > to question though... why two ticket trackers? > > > We started at SourceForge, using the tracker there. At one > point, I had gotten tired of its clumsy interface and wanted > to try something else. So, I went and imported the tickets > into Trac to let folks see what it might look and feel like. > > As an alternative, I'd be happy to import the data into > Redmine [1], another nice open source project management tool > that has many of the same features as Trac. > > [1] http://www.redmine.org/ > > However, I don't want to do the work if the community would > rather keep using the SourceForge tracker. > > I clearly suck at the whole "consensus-building" thing, and > AOLserver being an open source project means until someone > steps up to volunteer to do that, well, it won't get done. > I'm more than happy and capable to do the tech side of > things, but time and again it's clear that this project needs > a people person to make sure everyone's happy with the > direction things are going in and I'm not that person. > > > -- > Dossy Shiobara | do...@panoptic.com | > http://dossy.org/ > > Panoptic Computer Network | http://panoptic.com/ > "He realized the fastest way to change is to laugh at your > own > folly -- then you can let go and quickly move on." (p. 70) > > > -- > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > <lists...@listserv.aol.com> with the > body of "SIGNOFF AOLSERVER" in the email message. You can > leave the Subject: field of your email blank. > > > > -- > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > <lists...@listserv.aol.com> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: > field of your email blank. > > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
