Excellent explaination of our workflow. We might use this text as a introduction on Bugzilla site?
Greetz Christopher ________________________________________ Von: thron7 [[email protected]] Gesendet: Mittwoch, 25. Juli 2012 16:34 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] the contrib site On 07/25/2012 03:28 PM, panyasan wrote: > thron7-2 wrote >> On 07/25/2012 02:28 PM, panyasan wrote: >>> Great! I this a long-term project or a feature that will be implemented >>> soon? >> As nobody has created even a bug for it yet, nothing can be scheduled, >> so I wouldn't expect anything soon. >> >> > I can file a bug for this, if this is what you want ;-) But I am afraid that > alone won't make it happen, as long as you're not free to put developer time > behind it. So my question really was if that is a feature that has some sort > of priority. I would vote for it. People seem to misjudge the role of bugs in our project (although it is apparent enough if you've followed the project for a while): 1. Our workflow is driven by bugs/issues. Nothing really happens without a bug. We can discuss and analyse a lot on the mailing list. But without a bug you will hardly see any form of implementation, be that framework classes, documentation or project infrastructure. 2. Having a bug is by no means a guarantee that something will happen. It is a *necessary* but not a *sufficent* condition for it. But without a bug ... see 1. 3. Once a bug exists, you can greatly enhance its chances of being implemente by providing compelling use cases, background information, or even code. You can even vote for it. Others can do the same. Without a bug, nothing like this is possible. 4. Bugs might get scheduled (meaning they are assigned to a future release/"target milestone"). Only scheduled bugs get done (with few exceptions). Without a bug, an issue will never get scheduled ... see 1. 5. Users open bugs, not core developers. This is important. The core team opens bugs every now and again, but this is only second-best. Only a bug opened by a user *documents* a need from the community. Core developer-created bugs are sort of second-class citizens, as they always carry the connotation of something arbitrary, something you might or might not do, something with possibly questionable backing from the community. So you usually won't see us open bugs for you. 6. The core team playes the reactive part here. Bugs are scheduled, analyzed, prioritized, delayed, assigned or rejected. If there isn't a bug, nothing of this happens. So the question goes back to you, whether the new contrib system is something that *you* want :-). T. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
