P050402a: TROST Engagement - Diary & Job Jar

Status	Date	Description







done	2005-06-20	Make an announcement on TROST-discuss that we have sufficient structure for the bootstrap to be completed in the next month. Give a forward statement of how it will go.
done	2005-06-20	Shrink to 1.00 that is good enough for now and through the bootstrap. The other aspects can be brought up during further spirals.
done	2005-06-20	This mini-project is way over-scoped. All of those things can't be accomplished in a simple initial engagement. Boil it down and create something else on futures.
removed 2005-06-20	~~2005-04-30~~	Add P050402b here and use it for the web site checklist for having the site clean enough to open up for engagement. This is more direct than what might be carried on in an "Establish TROSTing and Pilot Project" folio, if we even need it.
done	2005-04-30	Split the TROST engagement between web site and SourceForge. The SourceForge development can lag behind the web site establishment. However, as templates are being developed, a SourceForge pattern for review, etc., needs to be in place. [dh:2005-04-30 We have that in P050405. We need one for the web site. Part of the checklist work can be here, but some must continue elsewhere.][dh:2005-05-04 We're not going to rush to have a separate folio for the web site, this one will do.]
removed 2005-06-20	2005-04-21	Create a job-jar or checklist of the items that must be cleaned up and/or reviewed under ~~each of the "Establish TROSTing and Pilot Project" and~~ "Establish SourceForge Project" folios.
removed 2005-06-20	2005-04-19	Create a separate "Establish TROSTing and Pilot Project" folio for all of that engagement involving TROSTing.org, with checklists that apply there. [dh:2005-04-21 Include MD5 and establishment of the practice, along with review of info/ for it.]
done	2005-04-20	Create a separate "Establish SourceForge Project" folio for all of that engagement and checklists that apply to it specifically.
	2005-04-19	The creation of these cross-linked folios and document controls/information is a pattern of accountability exhibited in TROST itself. This is an aspect of design with regard to the life-cycle framework.
	2005-04-19	I need to create a tools-you-need to follow along kind of thing. Some of the ones that are involved are simple. I think this is the topic of an InfoNote We should put it there, but its creation is an activity of engagement. [dh:2005-04-19 This starts with browsing, what the browsing requirements are, and what kinds of pages are present. There are static HTML and text files available. To download materials, it is usually necessary to have Zip or an equivalent. The contents of each Zip file and identification of what is needed to make use of the contents is provided separate from the Zip file so that it can be reviewed without having to download the material first. There are other patterns about knowing what is the latest and being able to provide comments and feedback. Ah. So I need SourceForge. So we need to deal with privacy, contact, and intellectual property concerns.]
	2005-04-11	This is a mini-rolling wave. The envisioning will be important.
moved	2005-04-11	Obtain the SourceForge administration information for walking through and identifying the configuration details that we want. [dh:2005-04-13 Make a separate engagement folio just for that.]
done 2005-06-20	2005-04-11	Create the desired state for the initial engagement [dh:2005-06-20 A greatly-simplified case is introduced for the initial bootstrap spiral.
done	2005-04-11	Create this page with the Lab Notebook style