[alf-dev] ALF Proof of Concept Face-to-Face meeting minutes

["Kevin Parker" <KParker@xxxxxxxxxx>]

Dear ALF'ers,

Here are the minutes of the meeting held at the Serena HQ building in San Mateo, CA on Thursday 16th February 2006.

Attendees:  Bjorn Freeman-Benson, Tracy Ragan, David Stevenson, Boris Kapitanski, Mirinda Lowe, Kevin Parker, Ali Kheirolomoom, Kelly Shaw, Bob Brady, John Streiff, Manny Panis, Tim Buss, Cliff Utstein, Steve Taylor, Brian Carroll, Ward Cunningham, Leslie Boveri, Daniel Gross, Christopher Rollo, Michael Fiala, Richard Sherand, Hampus Weinger, Petra Gratzer, Doug Fiero, Patrick Flanigan

Meeting started at 09:00

Introductions and welcome

ALF Presence at EclipseCon
o	Purpose Build the Ecosystem
o	Purpose Recruit Contributors	
	
Encourage vendors to want to ALF-enable their products
Encourage Consumers to talk to their vendors & encourage them to ALF enable the tolls they have purchased
Drive excitement around the project and attract interest from potential contributors

ALF Demo at EclipseCon:
o	Keep it simple & short
o	3 audiences – consumers, analysts/press, technical
o	Make it clear that "it’s real today"

Be flexible – demo a small part & see where the audience wants the discussion to go next
Discuss the Goal, the Use Case, & show the Demo
Show both the vendor software path & an open source path (possibly identical use cases)

Possible Additions to Add by EclipseCon
o	Open Source tools:
.	Bugzilla – No current web services, can send emails
.	CVS – No current web services, has triggers that can be used
.	ACTION: Steve Taylor create a Web Service that can run any command line utility
.	ACTION: Tim Buss download the tools and integrate with ALF
.	ACTION: Kelly Shaw create use case to add these in and call meeting to review w/team
o	Corona project – likely they will not be part of the demo, but we do want to discuss the use case of the integration with their project
o	Fault Handling & Compensating – either demo or use case:
.	Possibly add a compensating service for Build Management
.	ACTION: Discuss in ALF Planning meeting Friday 2/24 to develop plan
o	Branching Options – choose which services to use:
.	TT could have this ability
.	Segue Test Case – add in JUnit, show details, etc.
.	ACTION: Discuss in ALF Planning meeting Friday 2/24 to develop plan
o	Print out Use Case & show that:
.	Possibly add to the white paper being created
.	ACTION: Kevin Parker/Tracy Ragan add to White Paper; work with Shaw & Tim Buss to get use case picture
o	Have Vendor Stubs available via CVS as a download w/the working ALF system
.	ACTION: ALF Planning team continue to plan & develop this

Additional Demo Ideas:
o	Show the Event Manager/BPEL Engine Functionality more to demonstrate what ALF really does
o	Show what it takes with & without ALF to achieve these results – manually, through coding, etc.
o	Show how you can plug in an alternate tool or service flow easily or add another step via the BPEL Engine; have an alternate or additional pre-ready Service Flow available to plug-in
o	Include statements about what the tools did & didn’t do to make this work
.	ACTION: Tim Buss/Kevin Parker include the 4 items above in the demo
.	Post the demo in advance of EclipseCon to get feedback from the Eclipse Community
.	ACTION: Kevin to post this version & updated versions

Additional EclipseCon Items:
o	Sign up for Demos and Posters as these are not yet finalized
.	Posters will be at the Wed night reception; need a Big Title, Pretty Picture, & an Enthusiastic Person
.	2 Demos possible that Bjorn will give ALF – possibilities 
.	ACTION: Sign up for these to Bjorn by 2/20

Validation Phase Next Steps:
o	Provide open & transparent information to the community
.	All data, presentations, etc. on the website for all
.	Do we have a community of users, developers, plug-in users, etc.  Is it open & will accept anyone?  Good that there are already multiple partners. 
.	Look at the developer email list – can you see decisions being made?
.	Does most of the Eclipse community agree there is transparency?
.	Good examples are the C Development Group & Web Tools Projects
.	Team should strive to email more via the ALF_dev list and not individual emails for decisions, etc.

Meeting closed at 15:15






**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.