Hi Andreas,
Hi Gaetan,
just reading up on the mailing list, thanks for your initial question.
I'd like to add a few comments, as your comments may have been a bit
misleading. ;-)
thron7 <[EMAIL PROTECTED]> wrote:
[...]
You see, there's a lot of activity which is not just SVN commits and
"developing" means more than coding ... :)
I know, I'm a developer myself. It's just the current *apparent*
slowdown reminded me of the last time you did an external project and
didn't speak about it until I asked. So I decided to ask again. Seems
like I was wrong. Sorry for the noise.
Of course there is a drop in SVN activity since the 0.8 release. We have
recently focused on other parts of the project that are equally as
important (and made more sense during vacation time). Thomas has gone
into details already about the different tasks, so let me just name a
few: wiki documentation (both manual and project pages), bugzilla
reorganization and updating, project plan updates, 3 new team members,
and so on ...
I think that it is an *excellent* sign that the core dev team is
focusing on other things after a massive release like 0.8. Getting the
code out the door is only part of the whole, and things like
(vacations!) documentation are more than just 'nice-to-haves'.
I thought the weekly status updates would cover much of the project and
provide close, detailed and up-to-date info? :-( In those blog posts we
repeatedly talked about all core developers leaving for summer vacation
after the qooxdoo 0.8 release. Tomorrow is the first day (!) since
August that all core developers are back from vacation.
I've been checking in each week on your status updates -- very much
appreciated, and gives a really nice high-level overview of what's up.
Anyway, I think qooxdoo is one of the most transparent and "open"
JavaScript frameworks (weekly status updates, roadmap planning, public
bug and enhancement tracking, public SVN, qooxdoo-contrib, etc.).
Everybody is also welcome to send any project related questions and
suggestions to me directly, I'd be glad to answer, :-)
My only other JS framework proj experience is with YUI, and I can say
that qooxdoo absolutely rocks in the above compared to YUI (nothing
against the devs of YUI, as they do a great job and are *very*
talented). The qx community is much smaller and more tight-knit, which
means a lot more interesting things happening versus a LOT less noise (I
am close to giving up on the YUI mailing list, as it only seems to
contain people who want someone else to do their work for them, before
they even read the YUI docs).
qooxdoo has a much cleaner and focussed feel to it. No, its not perfect,
but seems to be headed that way :-)
I find these type of discussions really fantastic. Great insights and
connections to the project. Personally can't wait for qx 1.0!
Cheers,
-Chris
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
