C000000: ODMA /active/ODMref1.0 Diary

Status	Date	Description

	2005-09-10	The pattern about how header versus library dependencies are resolved needs to be handled and explained somewhere.
	2005-09-10	We need a place where the linker options and the practice of not using the debugging builds is established. The use of the MT versions must also be motivated.
	2005-09-10	On uses of the compiler on ODMdev, we need to be concerned about library choices. We will normally use the basic CLIB with
	2005-09-10	I was thinking about the portability of a copt that allows a console window as well as a command-line operation. This becomes even more interesting if the program is opened as a GUI application. I am not so sure this is a great idea! But it is an interesting one.
	2005-09-10	The tools section on nfoWare, and the dev section there can be set up exactly the same way as the tools here in terms of non-ActiveODMA application. That can be an example referenced from tools here, and some of the supporting information here could be duplicated there.
	2005-09-10	It appears that the ODMref/10 tools section needs its own construction section. Also, some of the tools are related to TROSTing and could well-be described there, or at least the pattern of their use could be described there. For example, the use of screen capture and browser capture, the use of browser capture as a way of preservice cited material, etc. Also, the overall citation business (though better when there is nfoWare to rely on), etc. Also, WinZip is a tool on TROSTing and that pattern can be handled there too.
	2005-07-05	Version this page and siphon off completed items into an archive-backup page to make it easier to find open items.
	2005-04-11	The status report should be updated to refer to TROSTing locations for some of the mentions that it makes.
	2005-04-11	There are references in material here to TROSTing /pilot, and it should be TROSTing /projects/pilot.
	2005-04-11	index.htm refers to TROSTing and TROSTing /pilot. Those sections require useful scaffolding and directories by the time we announce ODMref 1.0 and even more by the time we go through the ODMref engagement.
	2005-04-11	index.htm and other pages here refer to `/dev` and `/dev/confirm`. Make sure there is a meaningfully descriptive directory there before we announce ODMref 1.0.
	2005-04-07	Create a default.asp entry facade on this section as part of ODMref engagement.
in progress	2005-04-07	Create a status folder here and give it a minimal construction structure. It deserves its own construction zone. Provide that prior to ODMref Engagement but after the updating for work-breakdown and tracking are complete.
	2005-03-05	There is a bug that apparently happens in how FrontPage caches material from the server, especially if a file has been moved into a new place. The links to include pages are updated just fine, but they don't work. I am wondering if closing FrontPage and starting again cures it. [dh:2005-03-06-00:12 that seems to take care of it. Just close FrontPage and re-open it, then the page finds its included parts properly.]
	2005-03-05	I must also move the earlier papers to the site and also include that material in a project-management or PM section here. I think it should be named project or management or planning, and hold project items. I'm conflicted. I need to do risk management based on the material that I already have. This will be a problem.
	2005-03-05	Bring the project for ODMref1.0 (P041201) here. [dh:2005-03-07 There is apparently no such Project that needs moving. It is not in the catalog. There should be one, though, with a new number.]
done	2005-04-11	Add rel="nofollow" to the construction-structure links here, and also make sure we are using hardhat-thumb for the image: index.htm, construction.htm, C000000.
done 2005-04-11	2005-04-07	Add an index of what's here to the current index.htm as a provisional guide until an entry facade is constructed.
done 2005-04-11	2005-03-07	There are items here that can be part of the identification of tools task. This can be an ODMref 1.0 and TROST activity. There can be two versions. One on the TROST aspects and one on the ODMref1 1.0 aspects. It can also be at higher levels, but we need to deal with tools and dependencies for ODMref 1.0 specifically, as well as for TROST. [dh:2005-04-11 We are approaching it that way. The tools section doesn't explain this yet, though. It was close, and I have now reflected this angle too.]
done 2005-04-11	2005-03-05	Correct the current construction zone to refer to ODMref1.0 and not ODMAref1.0, in addition to any other conformance required: C000000, construction.htm, index.htm
done	2005-04-10	Clean up the index page of the engage/ subfolder (noticed when customizing for TROST Pilot).
done 2005-04-05	2005-03-05	Create a simple folder for /mitigate. Move P050301 into it.
done 2005-04-05	2005-03-05	There is planning for the risk mitigation and then there is the risk mitigation. The second is a kind of execution. So the mitigation section can have a plan as part of it, consisting of the initiation, plan, and closure along with the execution. This is an useful structure. I will use it and see if simply following a formula is good enough.
done 2005-04-05	2005-03-05	It looks like I must focus on the risk mitigation experiment. This is a bit like com.orcmid/.../pn/ALPHA and I notice there is a fair amount of material under ALPHA that it would do well to place in subordinate structure too. In any case, the risk mitigation experiment is enough to move down to its own level. [dh:2005-04-11 There is a separate section in the project structure, and also in the /dev structure, under the confirm cases.]
done 2005-04-11	2005-03-05	Add no-follow links in the construction zone here: C000000, construction.htm, index.htm, default.htm (why not default.asp?).
done 2005-04-09	2005-03-05	Clean up the materials here so this project is not too cluttered. I may need subfolders. Also, any one subproject can have substantial material. It looks like it would be wise to slip them into subfolders per subproject. More decisions. I can also see how the development tasks might create some kind of subtree under an ActiveODMA root, with more above it. So there could be a code tree. [dh:2005-04-07 The ODMA /dev tree is being developed to carry the currently available code as it is developed, along with documentation on how to shadow that development, create and test derivative works, etc. I am also buildiing substructure her based on the identification of project folios with the work-breakdown structure of the current plan update.]
done 2005-03-29	2005-03-07	Create and populate the development tree as active/dev here. [dh:2005-03-07 Or I can put it higher in the tree and have it at the ODMA level. There is refresh activity here, and that can work as well.] [dh:2005-04-06 The top level is exactly what we are doing, and ODMA /dev is there.].
done 2005-03-29	2005-03-07	I need a name for the root. On Blocco it is c:\crea, something I use for projects a lot. I don't want to use projects, the favorite Microsoft term, because it might be confused with the plan and manage aspects. I think it is the dev tree on ODMA.info/active but I am not all that sure of things. I will look on SourceForge later. I can also think about needing docs and similar subtrees. [dh:2005-03-07 There is no problem on CVS which can match the c:\crea\ActiveODMA subtree. There needs to be a separate tree on http://ODMA.info/active/dev that also corresponds to that CVS and the Blocco-local development-project tree.][dh:2005-04-06 That will be the ODMA /dev tree that is now here and is partially shared with the VSS image of the development tree on my local machines. This can work with CVS as well although it is not clear which image we will use (and we get to figure that out later).
done	2005-03-07	Create P050302 for Mitigation Experiment #1. This is to create a DLL that is registered and callable. It will have its own Job Jar.
done	2005-03-07	Create ODMref1.0/plan folder with minimal construction structure.
done	2005-03-07	Create a directory tree for ActiveODMA development work. There are resources that are relied on for ODMref10 (such as the latest header files) that are not part of the same tree. It looks something like core The ODM interfaces and the related files. manager The Connection Manager in its various incarnations - the ODMA and ODMA32 DLLs and their installation procedures, etc. samples The sample software and their implementations, information about their use, etc. ODMref10 The ODMA 1.0 reference implementation and whatever else is needed for that. ODMrun10 The ODMA 1.0 test harness for processing and confirming operation of implementations. tools The utilities and other elements required to configure, build, and use the materials. There may be different toolcraft requirements for different components and their implementations. This is enough for right now.
done	2004-12-01	Create this minimal Construction Zone scaffolding for /active/ODMref1.0.