However, can't we use bugzilla also to track (serious) feature requests? There are a couple of other "enhancement" requests in there, should we also close them and add them to the wiki page?
We created http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatureRequests Monday in the frenzy of the Hackathon, but IMHO (and in retrospect) having them in Bugzilla makes more sense.
The Wiki page can then explain how we handle them and include a bugzilla link to the list of currently open feature requests.
We have to be clear on how we separate them from bugs though, I think feature requests should all have priority=Enhancment, is that ok? And what about [PATCH]es?
I'm sorry, but I hate bugzilla enough, we should try to reduce its use rather than increase it. it's usability is terrible, it's a punch in the face everytime you try to do something.
But as long as it is in use we should it use as much as possible. Dividing issues on many resource locations does not help.
the wiki is much friendlier and feature requests are not something that requires lots of structure (rather the opposite).
It's only the thing of having similar thing on different locations.
also, i don't want to do conversations over bugzilla, it's painful and removes the ability to estimate people relationships (think agora)
Hmm, stupid answer, but is it better to communicate over the wiki? I don't think so.
Does anybody know the status of the move to Scarab? Is it project dependent? Does Scarab improve the usability/issue category handling?
Joerg
-- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de
