kicad-developers team mailing list archive
Mailing list archive
Re: I have a request in to convert sourceforge bug database.
On 4/9/2010 3:41 PM, Dick Hollenbeck wrote:
>> It looks our feature requests will be handled as bugs, but with the
>> "importance" field set to "wishlist".
>> As something "graduates" from wishlist status to a real contemplated
>> solution with implementation strategy, it can be entered then into a
>> "blueprint" by a developer, presumably the one wanting to code it.
> I'm wondering if we'd have less to do if it was harder to enter an
> Enhancement Request?
Less to do. Now that's funny :)
> Most "user" folks will probably continue to simply mention these on the
> user's list, and that would not be a bad thing. Because otherwise they
> have to become a member of "Kicad-Developers" to add to "Bugs". This
> then puts them within reach of the developer's mailing list. After a
> while I fear the nature of the developer's mailing list could drift away
> from actual development discussions, towards that of purely support.
I hope the developers list does not become the user support list. Maybe
a few of the user mailing list folks would be willing to take on the
responsibility of being bug and feature request submitters. They could
act as a gateway between users and developers by being responsible for
preventing duplicate submissions, confirming bugs, and getting user list
input for feature requests. This would save developer time which is a
much more scarce resource.
> So until we get more experience, I would be inclined to not publish the
> "Enhancement Request" storage mechanism in the Bug database. Things
> often get clear with more experience.
I agree but I'm sure it won't be long until someone asks where to submit
a feature request or what happened to the feature request they submitted
on SourceForge. I'm still trying to wrap my head around how I'm going
set up my development branch let alone how to handle feature requests.
I'm sure there will be a few more bumps along the road.