Minutes from DTP SQL Dev Tools Co-Leads meeting
Wed, Sept 27, 2005

Participants:
	Hung Hsi, Sybase
	Sheila Sholars, IBM
	Gary Xue, Actuate

Agenda/Minutes:
•	Establish regular meetings: frequency, day/time
Every other week on Wednesdays 2-3pm (PT)
Next meeting on Wed. 10/5, 2-3pm (PT)
•	Plan for finalizing our project plan
1.	Establish plan format
Initially, we expect our documents to be simple, so we can use simple text, RTF, html, etc.  PDF ok for read-only docs. 
2.	Establish plan content
a.	Identify SQL Dev Tools subcomponents, focal points and working group members.  
SQL Dev Tools is comprised of several subcomponents.  Although many of these subcomponents have dependencies among themselves, they are often developed and designed by different people.  To avoid having all of us involved in the details of all subcomponents, we have identified a logical list of subcomponents.  Each subcomponent will have a focal point who will be responsible for driving the design and development.  The focal point will interact with the subcomponent’s workgroup (if applicable), who are members also involved in the design and/or implementation.  Information coming from each subcomponent will be reviewed and shared with the overall project to ensure coherency and consistency.  The first action requested of the focal points will be to collaborate with their respective workgroup members to provide details needed as input for overall SQL Dev Tools project plan.

The initial list of subcomponents, focal points and workgroup members are:

Subcomponent	Focal Point	Workgroup Members	
SQL Query Parser	Rupesh Kartha (IBM)		
Routines	Hui Cao (Sybase)	Rick Mandel (IBM)	
SQL Editor	Daniel Huang (Sybase)	Brian Payton (IBM)	
SQL Results View and Scripts History	Idull Yang (Sybase)	Becky Nin (IBM)	
SQL Execution Plan	Idull Yang (Sybase)		
SQL Query Builder	Sheila Sholars (IBM)	Gary Xue (Actuate), Stephen Yu (Sybase)	

b.	Subcomponent focal points to provide input to the overall plan by 10/14:
i.	Features
For each feature, indicate a priority: Critical (Cannot release without), High (must have), Medium (really want), Low (subject to 
This level of prioritizing allows us to know what features we cannot slip out of plan.  It also serves to influence the order in which development is done.
ii.	Tasks
A reasonable breakdown of work items to complete subcomponent implementation.
iii.	Sizings
Specify in terms of Person Days or Person Weeks.  This will have to be a best-guess effort this early in the game.
iv.	Dependencies 
Indicate dependencies not only on components outside of the SQL Dev Tools project, but also dependencies on other subcomponents within this project.
Once this information is obtained from each subcomponent, it will be rolled up into the overall SQL Dev Tools project plan.
3.	Set target for finalizing plan
a.	Target for subcomponent input to overall plan:  Friday, 10/14/05
b.	Target for co-leads to provide overall project plan: Friday, 10/21/05

•	Exemplary Tooling
We discussed the fact that the Routines Framework was being offerered without an exemplary tool.  We agreed that the Routines subcomponent would include the framework as well as exemplary tooling.  If resources do not permit implementation during the 1.0 timeframe, that would be reflected in the plan.  

•	Content for SQL Dev Tools website
More focus on this in the future.