Hi Wayne,
Thank you for summarizing action items. As for _javascript_ and Python the situation is following:
Python: there are no engineers working on Python component for more than year, and as a result it's featureless and unsupported. DLTK Core team just trying to keep it consistent to work with DLTK Core Frameworks changes, but do not evolve further.
_javascript_: there is only one committer working on _javascript_ component, it is more feature-reach and stable, however we lack of adopters and users of the component, so I can't say it's mature enough to be included into Galileo or graduate.
Opposite, and for example DLTK TCL actively used by hundreds of engineers at Cisco, we're close in touch with them and according to feedback from Cisco and other companies we feel that TCL is mature enough to become graduate eclipse citizen. Ruby is good as well and used by Embarcadero as a foundation for their products.
So there is a huge gap in terms of maturity and support among DLTK components, so we think contributing Python and/or _javascript_ to Galileo would not be a good step - decreasing overall simultaneous release quality and almost useless for Galileo users. Also it looks to be impossible to evolve all the components seamlessly - each component may have different development cycle, committer base, etc, and DLTK split into different projects probably the only one solution, which would resolve the problem.
Python is the biggest concern: our company do not have resources to work on it, and I'm not sure there are people around (in the ecosystem) who would be interested to take over the project... So Python termination could be another option (definitively sad one).
As for Move Review, thank you for comment and for +1 :), I'll add "the reason for move" slide shortly and send you for comments.
Thank you very much again, and
Kind Regards,
Andrey
----- Original Message -----
From: "Wayne Beaton" <wayne@xxxxxxxxxxx>
To: dltk-dev@xxxxxxxxxxx
Sent: Wednesday, June 10, 2009 11:32:37 PM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] DLTK Release/Graduation Review follow up
Hi. I'm following up on the discussion we had on the call today.
I'd like to better understand why _javascript_ and Python support are not
included in the release. Is it that they're just not ready for release
yet? Have you updated the project plan to capture this?
At the end of the review documentation, you discuss a future move to
Tools Top-level Project. This will require a move review sometime after
the Galileo release. A move review requires very little documentation: a
short document with a single paragraph describing why you want to move
should do it.
While the development process doesn't explicitly require it, you should
get a +1 from the two PMCs. I'll start you off... +1 from the Technology
PMC.
Wayne
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev
