c000000a: ODMdev Construction Zone 2005-2006 Archive

Status	Date	Description
done 2007-07-12	2006-01-21	Siphon completed items to an archive page so this page is not so unwieldy.
done	2006-01-21	Refresh the site to introduce the new logo and front page.
done	2006-01-21	Adjust colors to work well on the front page after the image is set up
done	2006-01-21	Make a version of the master logo for the front page
done	2006-01-21	Bring the NuovoDoc master page here to customize for ODMdev
done	2006-01-21	Create a new master logo in Visio 2003
done	2006-01-20	Scoop the items that aren't needed here to either the construction/ log or one of the devNotes logs.
done 2006-01-20	2005-10-11	Get the creative-commons license set up too. Get the Q D version going quickly. Also, a template case can be done locally (e.g., under D000006, etc.) [dh:2006-01-20 The license is set up and D060101 is the hook about it all.]
done 2006-01-19	2006-01-13	Remember that all materials are now going to be at the ODMdev level as the result of the repaving. This means that the anchor block stops at the ODMdev directory level. There are no shortcuts upward. In effect, ODMA is an anchor site for ODMdev.
done 2006-01-19	2006-01-11	After we have our templates working, we need to see if we can morph nfoWare's construction section to have a similar structure. If we can easily create a new tree and have the current include pages work on nfoWare, we can then move back and forth between like structures. We need to do this with any site having a dev framework.
done 0.25 2006-01-18	2006-01-17	Add devNote structure and begin using it for a note tree about ODMdev and the devKits.
done 0.25 2006-01-18	2006-01-13	I think we need devNotes, just like other note structures. That way, it can be omitted or not, etc., in the propogation of pieces.
done 0.25	2006-01-18	Share to the site image and load for initial, provisional presence
done 0.25 2006-01-18	2006-01-13	This is ODMdev: ActiveODMA Development Framework. Change the nomenclature at this level and propogate to all subordinate levels: construction,
done 0.25 2006-01-18	2005-10-11	Create a canonical tree under /dev, with /dev/template and dev/2005/mm/ for starters. The template should be a variant of the FAQ template using the latest possible source (TROST InfoNote?). [dh:2006-01-17 There is going to be a devNote folder that has this substructure. That makes the depth of levels work out the same as for templates used on other sites.]
done 0.25 2006-01-18	2006-01-17	Only show minimal structure for ODMdev until there is more content to provide.
done 0.25 2006-01-18	2005-10-01	Set up the minimum ODMdev structure for starting out.
done 0.25	2006-01-18	Review the stylesrc attributes of the top-level folders: _private, confirm, core, images, manager, nodist, odmref10,
done 0.25	2006-01-18	Review all of the orcmid links too: front porch, _private, confirm, construction, core, images, manager, nodist, odmref10, odmrun10, samples, tools
done 0.25 2006-01-18	2006-01-17	Repave the additional sections that were already part of ODMA /dev: _private, confirm, core, images, manager, nodist, odmref10, odmrun10, samples, and tools.
done 0.25 2006-01-18	2006-01-17	On construction structure index.htm pages, the anchor-block entry for the current folder should refer to the folder, not the index.htm: front-porch, _private, confirm, construction, core, images, manager, nodist, odmref10, odmrun10, samples, tools. [dh:2006-01-18 No, let's make all of them refer to the folders, not the construction structure, on all classes of pages. On the construction-history block, at the bottoms of pages, default pages should link to construction structure, construction structure, construction material, and document-engineering content can all link to construction zones. Professional-appearance pages will link to their document engineering, and this makes everything pretty navigationally covered.]
done 0.25 2006-01-18	2005-10-11	With the new template, make sure that the timestamps for possible include-sources always have updating set for any changes, not just user edits. [dh:2006-01-17 Also make sure that the timestamp is produced as a single date-time insertion.] Done for front porch, construction, _private, confirm, core, images, manager, nodist, odmref10, odmrun10, samples, tools.
done	2006-01-17	Make an index.htm like the version used for nfoWare, describing the amount of structure that we are going to acknowledge for the starter kit.
done 2006-01-17	2006-01-13	Create a construction zone here on the model of the nfoWare Construction structure beginning: C000000, construction, and index.htm
done 2006-01-17	2005-03-10	When I accessed ODMA.info/dev, I got a cookie-blocking warning from IE 6.0. It seems that SourceForge attempts to plant a (3rd-party) cookie on any machine that views my page. This is done as part of fetching the SourceForge image. There is no supporting privacy statement and in any case, it is bogus, because the visitor to my site will be unaware that SourceForge.net wants to plant a cookie on their machine. So, I can't abide by that. What am I going to do about it? I need to refer to their privacy policy (if there is one) and also look for a way to deal with the situation. Since I intend to log incidents against Blogger and Microsoft for doing the same kind of thing, I guess it is only fair to do it here too. So I have to deal with this as part of TROST and it gets in the way.
done	2006-01-17	Find the cookie and privacy policy from SourceForge and resolve the 2005-03-10 cookie problem. [dh:2006-01-17 As long as we are not hosting a page on the SourceForg site, we don't have to show the image and required link.]
done	2006-01-17	Move the original index.htm description about structure to the ODMdev.htm page and use it as a provisional description until a folio can be used to document-engineer it.
done 2006-01-15	2006-01-11	We are now cut off from the templates at the ODMA level and must get our templates set up so that we can get the pages back to something like the ordinary.
done	2006-01-11	Merge in the construction effort from Blocco and see what we can do with all of this. Do not develop further on Blocco.
done	2006-01-11	The development of ODMdev is pulled out into compagno/ODMdev and mapped to $/ODMdevCompagno which still shares to $/InfoNuovoVServerWeb /odma/dev
done	2005-10-01	Rename the "core/ODMA 2.0" subfolder to "core/ODMA200" for name simplicity and to match the nomenclature used in the development of ODMA downloads.
done	2005-10-01	Delete the nodist/include and keep nodist/MSinclude
done 2005-09-30	2005-03-30	Go to http://msdn.microsoft.com/visualc/using/documentation/default.aspx for more information on the compiler and document what we got (capture it in the Blocco \Blocco directory first. [dh:2005-09-30 There is an account in Q050902c.htm]
done	2005-05-13	Repair the index.htm of the \dev area to describe `nodist/` in place of `/MSreliance`.
done	2005-05-13	Rename the `$/ActiveODMA/nodist/include` to `$/ActiveODMA/nodist/MSinclude`. Get the latest into `C:\crea\ActiveODMA\nodist`, and delete the original nodist subfolders. (The `\MSreliance` material is still there, though.)
done	2005-05-13	Rename the `$/ActiveODMA/nodist/bin` to `$/ActiveODMA/nodist/MSbin`. Get the latest into `C:\crea\ActiveODMA\nodist`, and delete the original nodist subfolders. (The `\MSreliance` material is still there, though.)
done	2005-05-13	Rename the development-machine `$/ActiveODMA/MSreliance` project to `$/ActiveODMA/nodist`and confirm that the version-controlled content switched with it. Get the latest in the new development-project area, `C:\crea\ActiveODMA\nodist\`, with the previous folder still there but no longer version-controlled. (The only sharing is with $/MSSDK content. as this folder's Microsoft content is not intended to be shared into ODMA /dev).
done 2005-05-13	2005-04-22	I do think it may be necessary to create an MSinclude directory or even Win32include directory, or something like that. We should make that change right away too, so it doesn't have to be done later when a switch-throw is more involved. [dh:2005-05-13 I went with MSinclude and MSbin for now. If different other directories are needed, they can be placed in parallel.]
done 2005-05-13	2005-04-22	On the development machine, make the same name changes.
done 2005-05-13	2005-04-22	Repair the site image and after uploading the new material, remove the old material (the only problem might be dangling references into the old section) [dh:2005-05-13 I don't think there are any other than from `dev/` itself.)
done 2005-05-13	2005-04-22	Repair the index.htm of (newly-named) nodist and indicate the approach we take.
done 2005-05-13	2005-04-22	Change the name of the folder to nodist.
done 2005-05-13	2005-04-22	I don't like that I made the `msreliance/` folder specific to Microsoft, when it is really about easily obtained but non-redistributable proprietary materials. If it's not easily obtained, we intend to avoid reliance on it. [dh:2005-05-13 The use of `nodist/` instead accomplishes this.]
done	2005-03-30	Run CL with /? option and capture the brief instructions and list of options to use. It's in the Blocco directory as CL-usage-2005-03-30-1456.txt
done	2005-03-29	Expand the explanation at the /dev level and connect in the first sub-folders once they have indexes.
done 2005-03-29	2005-03-27	First clean up the organization on Blocco, then share into here using VSS. Then add the necessary construction structure: confirm/, confirm/derisk01/, core/. manager/, MSreliance/, odmref10/, odmrun10/, samples/, and tools/. Most of these will need construction zones at the top level at some point.
done	2005-03-28	Delete the batch files and links at the ODMref10 level and share the improved ones that are at the dev level.
done	2005-03-28	Verify that header files shared from the Microsoft Platform SDK 2003-02 Core via VSS to MSreliance folders preserve their MD5 checksums. I did this with WTypes.h.
done	2005-03-28	Add the new MSreliance directory and share the minimum descriptive material, with none of the Microsoft proprietary materials that are recommended to be obtained and replicated into any shadow directory for verifying the development and construction of these materials.
done	2005-03-27	Share the directories to here in VSS and then have them noticed by Recalculate Hyperlinks.
done 2005-03-11	2005-03-10	Switch to the accurate, public /dev name and confirm that this renaming also worked.
done 2005-03-11	2005-03-10	Put changes to construction.htm here back on the same page in /active. [Except version number removed]
done 2005-03-11	2005-03-10	Plant a version number in the construction history of construction.htm, and correct the text.
done 2005-03-11	2005-03-10	Switch to an embargo name and confirm that it such a form is usable on compagno and the InfoNuovo ODMA.info host site. Again, verify for all paths to the folder.
done	2005-03-10	Upload the sequestered section and confirm that it is not accessible on compagno (the local development server) and on InfoNuovo, the current ODMA.info host site. Verify that to be the case for all paths to the folder. [dh:2005-03-10 The section is inaccessible on compagno, but it is accessible on the VServers (Interland) host site. My interpretation is that the URL problem with the 10.3-format name is an IIS problem, can't be counted on as a general trick, and only embargos should be done this way. Sequestering requires something more, such as password protection. Also, on some sites I can sequester a subdirectory, but the naming isn't enough. It takes site administration to solve it.]
resolved 2005-03-11	2005-03-10	Do we really want to refer to construction/C000004.htm and construction/construction.htm from the bottom block on this and similar pages? [dh:Yes on C000004.htm, no on construction/construction.htm.]
done 2005-03-11	2005-03-10	Go back and put nofollow links on the same material in the ODMA /active folder.
done 2005-03-11	2005-03-10	put nofollow links on the pages where needed here: index.htm, C000000, the C000004a, C000004b, C000004c, C000003a, C000003b, C000003c include pages, and construction.htm
done	2005-03-11	Start a construction zone here for supporting the creation of the /dev development tree snapshot folder. [dh: This is a clone of the one created on 03-10 and now brought under the /dev Construction Zone. This consolidates the history of this section as a transformation of a sequestered section to an embargoed section to this public section.]