P050404a: ODMref1.0 Project Engagement

A running diary and job jar of work items and notes on ODMref 1.0 Project Engagement

Status	Date	Description






	2005-07-05	Verify the activeodma-discuss instructions and also place information on the ActiveODMA list about what is happening, treatment of Spam, etc. It looks like maintenance of the discussion list should be a mini-Project here.
	2005-07-05	Scrub the FAQtips catalog and clean up the summary of FAQ as part of engagement.
	2005-07-05	Complete contact.htm (Q050701) as part of engagement. Add Contact as a link on the front-porch home page.
	2005-05-14	On many of these, it might be useful to indicate initiation from a tracking Gantt and also show the completion condition in terms of tracking Gantt. This could be a generic deal part of templates too. Add intiation and completion sections.
	2005-05-14	This activity is very stale. The entire folio needs to be reviewed and some action taken.
	2005-05-14	Add inputs, outputs, and conditions of satisfaction
done	2005-05-14	Review the folio cover page for any aberrations too.
done 2005-05-14	2005-05-13	Correct the bottom row of this column to be left-justified rather than centered.
	2005-04-07	Review the ODMref 1.0 Construction Zone and complete all activities there as part of opening up this section for ODMref 1.0 Engagement.
	2005-04-06	The engagement must make it clear that the ODMref 1.0 activity that is part of the first base is embedded in the TROST Pilot Project and that dictates schedule.
	2005-04-06	Put the engagement information, or the announcement, on the site file repository too.
	2005-04-06	Tie the CVS tree to either my developer image or my ODMA image, but tie it in one way or the other. The developer image seems like the most likely case. The binaries and files can go to the file side of the SourceForge project.
	2005-04-06	Tie the ODMref10 and /dev tree together in a way that leads people from the one to the other.
done	2005-04-06	Create this page with the Lab Notebook style