Validation Review Meeting
We had a superb meeting yesterday with many of the ALF contributors and committer and even some of our consumers.
The highlight of the meeting was a full on demo of the Proof of Concept code which was delivered by Tim Buss. After the demo there was a lot of feedback on how the demo can be improved and Tim and Ali have agreed to go back and incorporate that feedback. We are putting up the early version of the demo so that you can give your feedback. We also got approval from each of the partner companies to be able to show there products through the demo.
One very interesting idea that we will try to implement before EclipseCon is the orchestration of some Open Source tools into the demo like Bugzilla and CVS.
The rest of the meeting was very effective too. We looked at the plans for the deliverables needed to complete the project for version 1.0 which is expected to be in October. Ali Kheirolomoom led a discussion goals and objectives that need to be completed including the special needs for Security and Single Sign On which are going to be critical components in the final design.
We also too a deep look into the Vocabulary Groups and Steve Taylor made an excellent presentation on how these groups should be organized. Brian Carroll laid out the detailed deliverables that the Vocabulary Groups will need to produce for the project's success. As the debate embedded and flowed it became apparent that the best approach to teasing out the vocabularies, and the way that would avoid most conflict, would be to use Use Cases as the driving force that validates the vocabularies.
At the end of the meeting we had a roundtable discussion with Bjorn Freeman-Benson and Ward Cunningham from the Eclipse Foundation and they gave us some very good advice about how to improve our communications and transparency on the project.
We had a good discussion about EclipseCon and agreed that we would try to secure 3 Demo Slots and a Poster session at the conference to give the broadest opportunity to show the efficacy of the ALF solution which in turn should build the ecosystem and attract further contributors to the project.
All the presentations and documents have been posted on the ALF site and so has the Flash Demo.
Kevin

2 Comments:
The feedback link on the ALF site goes to: alf-dev@eclipse.org
You have to join the email list to send emails to it, which I have no desire to do.
So I will just post my feedback here:
==============================================================
I found the demo very confusing.
Here are the questions I wrote down as I watched the demo:
"What is going on here?"
"What are we trying to do?"
"What the heck is team track?"
"What is demensions?"
"What is running where?"
"Where is ALF involved?"
"What is Dimensions?"
"What is Catalyst?"
"Why is there a 'Active BPEL engine'?, I thought ALF had a BPEL engine?"
"What is Silk Central?"
"What just happened?"
I think it would be better to start the talk about ALF (this is an ALF demo right?), what ALF does in general and then specifically what ALF is going to do in this demo.
Talk about the problems ALF is trying to solve, show how difficult it would be to do these processes without ALF. Maybe get some 'wow' factor going on.
Howabout a nice diagram showing the interactions that ALF is going to help manage.
Then once you have talked about ALF then talk about all the tools it is going to be working which so I know what the heck everything is.
You are absolutely right and thanks for the input.
We have fixed that in version 0.2. Please have look at that and give us more feedback.
Post a Comment
<< Home