P050501: Develop Project Folio Boostrap

Status	Date	Description








	2005-08-15	Notebook #46.89: Put an outline around the project summary grid. Review to make sure the specimen entries in the grid match the current latest model (P050601 here or a later one on ODMA).
	2005-06-30	Some of the changes collected for i000006 0.10 may apply here as well (catch when customizing on ODMA, and off P050601 here).
	2005-06-28	In P000006a 0.10, remove the red rule and gratuitous paragraph in front of the table.
	2005-06-22	In P000006c 0.10, the First Steps #6 has a duplicate "when" around the parenthesized phrase. There's also a typo on the page that the spelling checker highlights.
	2005-06-22	The development link in the p000006c.htm 0.10 under the specimen 0.00 history is incorrect. It needs to be to P050501d, not P050501c.
	2005-05-25	With P000006c.htm of 0.10, some of the different adaptation scenarios need to be spelled out, especially the customization of P000006b.htm that will be pretty mysterious without some diagrams and an external description. It should not all be done in P000006c.
	2005-05-25	The 0.13 revision history in P050501d.txt has a misplaced "," and could be tightened a bit. This is not urgent~~, but don't let it infect the corrections to P000006c.txt manifest template version 0.09~~. [dh:2005-05-26 The P000006c.txt is adjusted just fine.]
	2005-05-25	For 0.20, there might need to be better explanation of how the versions of P050501x.txt are kept in sync with the VSS version numbers. This can't go on indefinitely but it is a nice connection to the privately-retained source-control versions. This fits into a pattern of how the scaffolding project quality provisions blend beneath this higher level accountable-progression activity. (Also, when push-pull-click-click is done, these versions start at different numbers if we want to keep in synchronization with VSS. This only works for a little while, but we can do it long enough to demonstrate how obsessive we can be.)
	2005-05-25	When this is done, P050501c.zip and P050501d.zip can be further decorated and made more useful, but the captured parts are regarded as indelible. It may be desirable to capture their respective .htm pages (in .mht form) too. At some point later, P050501e can be started along with the creation of an 0.20 in a warm-up pen.
in progress	2005-05-25	Push-pull, click-click fits into the working ahead case here, and also ties in with software configuration management as infrastructure/plumbing/scaffolding that the trustworthy practices sit astride. The recovery that I just did of the project plan document, which was messed up on 2005-05-24, but I reverted to 2005-05-23's and rolled forward again, is a great example of that pattern. Catch this as a pattern or two.
	2005-05-24	There are additional items and notes to capture by reviewing my notebook pages #45.79-.82
	2005-05-23	We need a note about adjusting the Construction Zone links to the nearest zone in the P000006 template, too. (do for 0.20) [dh:2005-05-25 This is done for most 0.10 pages, but it is good to review again.]
	2005-05-21	Add that we want to capture a series of snapshots as a record of how this particular bootstrap progressed. It is something to rely on for future illustrations. We would not normally capture so many snapshots.
	2005-05-21	In the business about rewriting the anchor-block links, we could use a step by step example showing what the links are like and how they need not change. Annotated screen shots would be nice. Also, it should say what the end-state must be, no matter what was in the template already.
	2005-05-21	Review page P000006 and identify all of the places where links to further explanation and expanded illustration are needed.
	2005-05-21	This folio should specify the performance patterns that are honored in the design and use of the template, either by reference or as a specific aspect of this project unit.
	2005-05-21	In the bottom-right construction-history block, the comment about source-control software needs to be linked to something more informative. [dh:2005-05-25 do in 0.20 after instructions for applying the template(s) exist.]
	2005-05-21	In the anchor block, point out somewhere that the date-time stamp is created automatically and does not require any manual adjustment so long as FrontPage is being used. Otherwise, the HTML should be edited to provide the correct date-time in a way that leaves the FrontPage "bot" commentary intact. [do in 0.20 after instructions for applying the template(s) exist.]
	2005-05-21	Rewriting and generating web pages via semi-automatic procedures and scripts is something that we will wait for from nfoWare. We can mention that, though.
	2005-05-21	Document why we do it all "manually" first and have manual procedures as a fall-back (and bootstrapping into a new site) needs to be made clear somewhere.
	2005-05-21	Need to say something about shortcutting the meticulous construction process and about making a local template that is oriented to a particular section of project folios ~~needs to be mentioned~~ somewhere. [dh:2005-05-25 likewise, in developing an expanded folio, it is often convenient to clone pages that are already customized to that folio. This is a push-pull click-click pattern opportunity also.]
	2005-05-21	The assumed location of the nearest construction zone needs to be clarified too. [dh:2005-05-25 For example, this folio has a construction zone closer above (in /projects/pilot/ than is the case for the template.]
	2005-05-21	The business about the same folio depth needs to be explained and also the assumptions about the include pages as they are handled in the construction section. (The ones we are using aren't fully-customized yet. We just converted what we needed. There is more to do there. A note is needed about that in the construction section.)
	2005-05-21	The template dependence on Microsoft FrontPage should be linked to a configuration element with information about the actual installation used, etc. The current version identification is useful for now.
	2005-05-21	In the first template section, item (2), a link to template instructions is required.
done	2005-08-15	Use the new technique of shifting all completed items to the bottom, in reverse chronological sequence.
done 2005-06-30	2005-06-23	Move notes and findings on use of P000006 back here for further revisions there. We need to look at whether this makes a new version or not, whether they are safe as editorial changes (maybe not, because of archiving), or whether we just save them up for the next "release," including feedback from the i000006 0.10 experience, manifest tweaks, etc. These also impact customization of P000006 under ODMA.
done 2005-06-30	2005-06-28	Remove the red rule and unnecessary paragraph above the table on this page.
done	2005-06-02	Update P050501d.htm to reflect the inflation of P050501d.zip with new material for sealing up with 0.10.
done	2005-06-02	After this job jar is captured in P050501d.zip, roll the completed items on this page into an archive sub-page so this page is easier to work with.
done 2005-05-26	2005-05-25	When this is done, P000006 is ready to be used in a traceable way in making other project folios and also in making other templates by cloning or at least donating material to other pages (e.g., back to i000006). [dh:2005-06-02 This can start anytime after P000006 and P050501 are stable enough at the 0.10 level to allows cloning~~, as it will be described in P050502~~.]
done 2005-06-02	2005-05-25	Add related job-jar and P050501 materials to P050501d.zip too. This is at least this page, in .mht form, as it is when this last act is carried out.
delegated 2005-06-02	2005-05-23	Roll the changes made to the P000006c.txt back to i000006c.txt too, via the Project Folio for that task. [dh:2005-05-25 do after 0.10 is stabilized.][dh:2005-06-02 This is now continued under P050601.]
done 2005-06-02	2005-05-21	Capture an 0.10 archive that illustrates the new P000006, P000006a, and the P050501 [dh:2005-05-25 ?] and P050501a that were arrived at for 0.10. (The P050501 project details aren't customized yet, though.)
done	2005-05-21	Customize this page for use as the job jar of the P050501 bootstrapping ASAP, so that it is usable in capturing notes about the steps taken in documenting the first trial-use of the template.