On Wednesday 07 October 2009 13:54:20 Daniel Molkentin wrote: > Hi, > > I see rising frustration about the lack of subjectively pressing > features. This is understandable. However, let us try to find a positive > approach to solve the issues. > > Let me start out by explaining our view: In spite of "being Nokia" (more > precisely: being part of it), a seemingly huge company, our team does > not have infinite resources to spend on this project. While we gladly > pick up feedback in an unbeaurocratic way if possible, there is a limit > to what we can do in this respect, since we have to commit to our roadmap. > > This does, however, not mean that your features must remain > unimplemented. You can always contribute, as numerous people have > already done. And if you feel like you have any obstacles in your way > while developing on Qt Creator, like a lack of class documentation > (which probably is one of the most pressing problems right now for > external contributions) or understanding general design principles, > please talk about it. > > If you have a joint interest in a particular feature with other people > on this list, please try and develop it together. Gitorious has awesome > team functionality: > > http://blog.gitorious.org/2009/05/09/weve-made-a-few-changes/ > > Enabling contributions from _everyone_ is one of the foremost reasons > why Creator is Open Source instead of just closed-source Freeware: > Giving you the power to get involved, no matter what our internal agenda > looks like. So please make use of it. We will happily assist with any > serious effort into either improving documentation or getting started > with implementing your desired functionality into Qt Creator. If you > have any questions, please follow up on this mail.
Hi Daniel, Let me take this mail as a good starting point on how to contribute. You said that everyone can contribute, and it's true: * create an account on gitorious * clone qt-creator * do your change in your own clone, and then push on gitorious * do a merge request and after? I personally did this, and my merge request is still waiting after 22 days, without any answer (not to say that now I need to update the code, because of conflicts). I can understand that you don't have time, that my feature is only interesting for me, that my code is crap, I would be ok with an answer like: "We don't add new feature untill 1.3 is released" or "this won't work", "this is buggy as hell", but no answer _at all_ is really discouraging. Another example: I found a bug in the code, asked on the mailing list, Daniel Teske sent a patch to test, I tested it... and that's all. As far as I know, the patch is not applied and the bug is still here... discouraging. All the enthusiasm I had when I started coding on Qt Creator vanished, and I prefer to spend my spare time on something else, Qt Creator isn't fun for me anymore. Or maybe I'll work on external plugin and won't waste my time trying to do merge request (sometimes difficult, everything is not available for plugin developer). I know you all have a todo list longer that what you can handle in a life- time, it's the same for me, I just ask for more communication (and saying "we don't have time, wait until 1.3' is not really time consuming). Also, it would be nice to have a view of your roadmap, even if things can change it would help us and avoid duplicating the work (/me needs scripts, is it planed or can I start to work on it?). Nicolas -- Nicolas Arnaud-Cormos | [email protected] | Software Engineer Klarälvdalens Datakonsult AB, a KDAB Group company Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
