In case you missed it, Qt is now being developed with the help of an open gitorious system. This was a long time in the planning and a lot of work to get out the door (including funding some development of gitorious), so hats off to the people at Qt Software for that.
What this means is that we can now both contribute easily to Qt itself as well as track development of Qt as it happens. Right now it's only syncing twice daily to the Qt Software internal git repository, but as I understand it this window will shrink down to realtime as the system proves itself to be working well.
Seeing the number of clones that have already popped up and the sorts of things people are working on in them (ranging from bug fixes to performance improvements to new features) it should be pretty interesting to watch this evolve.
I remember being at a Trolltech Dev Days a few years back when someone in the audience asked Matthias Ettrich, who was on stage taking questions after his keynote presentation, why some feature was missing in Linguist ... and the next question was someone asking something similar about Designer. It struck me that these are exactly the kinds of small features that the people in that audience could have contributed themselves quite easily had they the opportunity to do so. Now they do. :)
Now I wonder how much longer until KDE's sources are hosted in a git repository... :)
Subscribe to:
Post Comments (Atom)
8 comments:
Does this mean qt-copy will finally go away?
"Now I wonder how much longer until KDE's sources are hosted in a git repository... :) "
Is this proposal on the table at all?
@Robert: that's one of the goals, yes.
@Jason: yes, it is.
I don't think a KDE move to git should be proposed now, there will be to many opposition from people that resist change.
I suggest creating more awareness first, like some blog posts from time to time about the advantages of git, were does it kick ass.
Then it will be a piece of cake to convince everyone :)
@sergio: it was proposed quite a while ago and there is general agreement that it's the right path. it's not a matter of generating consensus at this point, but generating the resolve and man power to execute on it.
@aseigo: AFAIK the porting of the infrastructure (scripty etc.) is what makes the transition so slow.
For the record: I don't think that git is a good DVCS because its user interface is inconsistent, full of bad naming and ill documented.
Your last sentence was exactly what I was thinking as well.
Looking at it, now it is easier to provide your ideas/patches to the Qt devs in comparison to what it is in KDE. In fact only from a technology point of view.
Simply because git is so useful and asking for a merge and when doing the merge is so easy.
Post a Comment