[wtp-pmc] Re: [atf-dev] Open Mettings and getting the Source Code
I would of responded to you sooner,
but have been on vacation.
I will work on improving the communication
to the open source community. The ATF team is starting to look at where
we should be heading in the future. The team has gotten to the point where
we need to assess what we have done in ATF and what functionality should
be in ATF for a product. As we go forward we will be announcing our thoughts
to the community to get feedback and layout our plans. There are a number
of things that the ATF has done that we don't think should be in a product.
The team has announce two of this items to the ATF Dev forum (Dropping
of the Personality and Zimbra support) to get community feedback. We are
probably one or two months away from laying out our plans.
I will update the Web site with our
latest plans for our next milestone and announce the plans to the ATF Dev
forum I will also work on your specific bullets below. I will
also continue to work WTP PMC on the best course of actions to improve
communication to the open source community.
IBM Emerging Technologies
512-838-8824 T.L. 678-8824
ATF Developers, Webtools PMC,
|Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent by: atf-dev-bounces@xxxxxxxxxxx
08/03/2007 11:30 AM
Please respond to
AJAX Toolkit Framework discussion <atf-dev@xxxxxxxxxxx>
"'Bjorn Freeman-Benson'" <bjorn.freeman-benson@xxxxxxxxxxx>
|Re: [atf-dev] Open Mettings and getting
the Source Code|
I was disappointed to read this statement (below) in the atf-dev mailing
list. A project is not open and transparent unless it is open and transparent
all the time. My experience is that people (and groups of people;
even me) always revert to base behavior under stress. In other words, if
you can't stay open and transparent during a "heads down" cycle,
then you aren't really committed to being open and transparent.
Related to that, I browsed around your mailing list archives, newsgroup
archives, and project website:
The project is just not being
very open and transparent. The WTP PMC needs to crack down on the ATF project
and either get them to be an open and transparent and Eclipse-like project
or to reboot the project with a different team that will be. This could
be a really cool project for Eclipse and the Eclipse community. But not
as a closed-shop project with an open source repository. It's not good
for Eclipse and it's not good for Webtools and it's not good for the ATF
- Your 2.1 downloads do not have the word "incubation"
in them. Your project is no longer "incubation-conforming".
- You are not using the standard Eclipse version numbering
as 0.2.1 is not (in Eclipse naming) a milestone of 0.2. It should be something
more like 0.2.1M4.
- I couldn't find a project plan. I found this
roadmap but it's out of date. Plus it has no
- Are you all doing Eclipse-standard six week milestones
aiming for a 1.0 release? You should be, but I don't see any documentation
of it anywhere.
- I see
that code is being written, but I don't see much/any discussion of design,
architecture, use cases, unit tests, or development in the dev
- I looked at the ATF
wiki. All but one of the pages haven't been
touched for more than nine months.
On Behalf Of Robert Goodman
Sent: Wednesday, July 25, 2007 10:13 PM
To: AJAX Toolkit Framework discussion
Subject: Re: [atf-dev] Open Mettings and getting the Source Code
We do generally have an open meeting. At this time the team is heads down
trying to get something out the door real soon and before I go on vacation.
We are just having impromptu meetings until we get over the hump. I will
send you a note, once we get the meetings started again. We are obviously
interested in people who would like to contribute to the project.
We are interested in the ATF Project and we would like to know
the the project has Open Mettings. How we can participate from this
atf-dev mailing list