orcmid.github.io
Construction Zone |
|
Status |
Date |
Description |
|
transposed 2023-09-02 done 2013-11-25 |
2007-11-11 |
|
|
2024-11-09 | SECURITY.md There should be a TOC on this one, since it is rather lengthy and clues regarding the progression of content would be handy. | ||
2024-11-09 | SECURITY.md Add illustration of all the severity parameters for the least-vulnerability case. | ||
2024-10-31 | Provide a link to creation of ASCII-armored encrypted text messages. This will likely be in nfoTools unless I can find something public elsewhere and also to reference from nfoTools. | ||
in progress | 2024-09-28 | Link to Security Policy from front-porch home pages, where those exists. orcmid.github.io, miser, DocInterp, Adv10, docEng, myCleanC, rayLab, nfoTools, wingnut. [dh: Include the README.md, along with its improved description of the sandbox. [dh:2024-11-02 This should also be in hybrid footers.] | |
in progress | 2024-09-25 | On privately reporting, add https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability and explain that the form is designed for use by security researchers. Indicate that others can contribute by providing only mandatory information, which will exclude ecosystem for all orcmid on GitHub projects at this point. So fix the template and also add the guidance: orcmid.github.io, miser, DocInterp, Adv10, docEng, myCleanC, rayLab, nfoTools, wingnut. [dh: r124c41 successfully created a minimal report. This is not so bad.] [dh:2024-09-26 CVE seems to be Common Vulnerability Enumeration, which is a way of giving vulnerabilities unique numbers in a CVE cataloguing. There is also a Common Vulnerability Scoring System (CVSS) in use and that is reported in CVE entries and, typically, in published vulnerability reports. These are all for coordinated use by cybersecurity professionals and security researchers.] | |
in progress | 2024-09-24 | Propogate "Exclusion of Forked/Cloned Projects" as needed for orcmid.github.io, miser, DocInterp, Adv10, docEng, myCleanC, rayLab, nfoTools, wingnut. [dh: I wonder if this might be stated separately, although I am unclear where else this might be stated. Perhaps some general place.][dh:I am talking about security policies here, and the acceptance of vulnerability reports.][2024-11-09 Use the Miser one for subsequent versions.] | |
2024-09-22 | When nfoTools has a folio on PGP security, It needs to be linked from the SECURITY.md policy statements for Orcmid on GitHub. | ||
2024-09-18 | I need to figure out what to do with ODMA and DMA materials, as well as the ODMAdev and ODMJNI materials. These are also worthy of hybridForms or pure HTML preservation. | ||
2024-09-18 | Prepare for retirement of nfoCentrale.com. I must ensure scooping of essentials from nfoWorks, nfoTools, and anywhere else. | ||
in progress | 2024-09-18 | Security Policies: Update all of these so that the SECURITY.md points to the correct security tab in each case: orcmid.github.io, miser, DocInterp, Adv10, docEng, myCleanC, rayLab, nfoTools, wingnut. [dh:2024-11-01We are redoing all of these following the major changes in the sandbox version that will lead to revision of all other existing policy statements. | |
2024-09-18 | I also wonder how hybridForms works at this level (and I think not, or not so much. At the moment, the only direct topics are bib/ and orcmid/ (and maybe construction/. I suppose it works at this level just as well. I wonder what form index.md is in. [dh: Ohhh, it is already in hybrid format. OK, an option. And look at 2023-12-04 in progress.] | ||
2023-12-12 | It may be appropriate to have the nfoWorks handling of namespaces here. This also means bringing over the "professional appearance" format. Not a bad idea. | ||
2023-12-12 | I notice that there are more "container" tools needed for nfoTools, such as Zip, and base64, RIFF, and others. This is appropriate for nfoTools. | ||
2023-12-10 | orcmid.github.io.txt: Consider tombstoning with or without salvaging the TODOs. The synopsis is rather handy. It could go somewhere perhaps. | ||
2023-12-10 | index.htm: Make the merged subordinates explicit | ||
2023-12-04 | I am running into a practice issue around knowing places where there are active TODOs. In the site-server model, it is always handy to check in a Diary & Job Jar page with a flag to leave the page checked-out, so it will have a red flag in a file list. I have a trick that might work to have flags set after a git check-in, but it involves reloading and saving a page that has a time entry in the location block on the far right of a title block. This will only work on web pages and not hybrid pages that don't have such web components. All of these considerations need to be echoed to docEng. So this item isn't complete until I have done that. | ||
in progress | 2023-12-04 | hybrid document-engineering. I am having difficulty reminding myself that when I want to record something in a Diary & Job Jar about hybrid pages, I must have the page open in VS Code but the construction aspects and logging require me to open FrontPage as well. I don't have a good way out of this. However, hybrid pages (*.md ones) will be opened in VS Code (the default for *.md on my Windows setup). I think I must get in the habit of opening FrontPage first when doing document engineering. For working on code, maybe not so much, since that is not in GitHub repository areas handled as GitHub Pages. I need to check to see if this is a source of problems where I have to force-quit FrontPage. Another wrinkle is I need to have the file folder open to see what TortoiseGit shows me as "checked-out" because FrontPage is unaware of git. [NOTE: ClustrMap's only work on links from orcmid.github.io and its subfolders. hybridForm markdown in other places, such as SECURITY.md on Miser, cannot work and the ClustrMap should be removed from those Security Policy statements.] | |
in progress | 2023-12-01 | Review subordinate projects for hybrid front porches: bib, docEng, miser, nfoTools, orcmid, construction [dh:2024-11-06 I think there is confusion between local-to the orcmid.github.io repository and those blended from GitHub Pages of other orcmid on GitHub projects. | |
2013-12-14 | Review the entire front porch after the repaving top levels are complete. | ||
in progress perpetually |
2007-05-04 | Make a web review and catalog broken places. | |
done | 2024-11-09 | SECURITY.md: Update for the Miser Project makes clear the need to distinguish the Sandbox policy statement as an walk-through exemplary for reporting vulnerabilities with respect to other projects/repositories. Do a clean-up to emphasize that. | |
done 2024-11-06 |
2024-11-03 | SECURITY.md: Emphasize Security Statement versus Security Policy. Maybe adjust title and text to help cement the distinction. | |
done 2024-11-06 |
2024-11-04 | I am unclear how published advisories become visible via the security tab. I might have to include a link. I am uncertain that it will work. It looks like <https://github.com/orcmid/orcmid.github.io/security/advisories> will do the trick, although I am unclear what is seen by others than the owner. There's a nice account and I am uncertain how visible that is to anyone. I'm not intending to document how to handle vulnerability reports by repository owners. I do need a way to know what is going on with regard to drafts, Triage, and what can be known to observers of any kind if I provide the link. This will take some experiments. [2024-11-05 It looks like there is some confusions about GitHub security and security of software hosted on GitHub repositories. It is difficult to navigate that because I have to see how that looks to a reporter (not a manager), and also to others concerned about advisories that have occured. I may have to create a separate catalog for advisories, by project, and also deal with the dependabot business. My only experience with dependabot is for npm-based projects. [2024-11-06 I got through this and managed to see what contributors and what non-contributors see.] | |
done 2024-11-06 |
2024-11-03 | Create a PRACTICE report that demonstrates what announcements look like. [2024-11-03 I don't think this will work. Published advisories go into a global database and they are unlikely to accept completed PRACTICE ones. So I have to close them, I suspect.] I need to reflect that in the sandbox mechanism. | |
done | 2024-11-03 | SECURITY.md: Show a submit button. | |
done | 2024-11-03 |
SECURITY.md: Show a Security Tab. Show the
selection of the applicable statement. [dh: It doesn't work like that.
The statement comes up directly, with the submission button. I
don't know what happens if there *are* published security advisories.
I need to work that out.][dh:The security tab as selected appears in the policy statement preentation. All good. |
|
done 2024-11-03 |
2024-11-02 | Expand the PGP message instructions concerning what to put in the message and what not to put in the plaintext and message subject. | |
done 2024-11-02 |
2024-10-31 | Use hybridForm pages for SECURITY.md, starting with orcmid.github.io. See if that works when digging into the GitHub resources and viewing the Security Policy via a project . [dh:2024-11-03 This works directol and in the Security tab view of the Policy Statement. | |
done | 2024-09-30 | Align README.md and account for how it is published for orcmid.github.io. Bring index.htm into conformance. Refine the Sandbox explanation. | |
done | 2024-09-29 | Add README.md and rethink the sandbox idea concerning Secuity Policy for orcmid.github.io. [dh:2024-09-29: The README.md does not interfere with index.md so there can be both.] | |
done 2023-12-05 |
2023-12-04 | index.md: There needs to be more linking to resources such as GitHub, git, VSCode, Markdown, and even FrontPage. | |
done | 2023-12-04 | index.md: Fix the blemishes in the first two tap-dance paragraphs. | |
done | 2023-12-04 | index.md: Add "(Hard Hat Required)" to the construction link, making it unnecessary to call it out in the text. | |
done | 2023-12-04 | index.md: I have started using https://orcmid.github.io/ in places where I am asked for a URL. I am reviewing and touching up because of that. I'm also checking on the practice, noted today, on operating "FrontPage first." I also don't want to emphasize the anchor business so much, although I am proud about it. | |
done | 2023-12-03 | index.md 0.1.2 smoothing of the synopsis | |
done | 2023-12-01 | index.md touch-ups | |
won't fix 2023-12-01 |
2017-07-22 | Besides the 2004-05-30 concerns for HTML 4.01-transitional identification, there are now breaking HTML 5 changes that newer browsers (such as Edge and Chrome) are making. I need to figure out a responsive solution. This is going to be a pain in the tuckus. | |
done | 2023-12-01 | index.md: Make hybrid page | |
done 2023-11-26 |
2023-11-25 | index.html: Add bib to Orcmid's Table of Content | |
done | 2023-11-25 | propogate repurposing completion through bib/ and anywhere else where a tree is complete | |
in progress 2023-09-02 |
2017-07-22 | Ditch movable type. I need a different static-page blogging arrangement, with handling of images here and also with use of Discus for comments, so they are not actually on the static site. This creates an archive issue and I'll have to deal with that another way. Bill Anderson gave me some pointers. [2023-09-02 This still applies and we're not dealing with the blogs just yet, getting web sites materials of my continuing interest preserved first.][2023-11-16 The abandonment of Movable Type is also achieved by transpositions to here, <https://orcmid.github.io>, and to GitHub Orcmid projects/repositories ] | |
done 2023-11-25 |
2013-12-14 | When all of the "propogate repaving" work items are closed, the top level Construction Structure/Zone repaving notices and work items can be replaced with completion notices. | |
done 2023-11-25 |
2006-10-29 | In moving to Apache, there is a lot of breakage around case sensitivity. There are also some bad links (See #55.69). There is a lot to work out here. | |
done 2023-11-25 |
2004-05-30 | Bring Construction Structure of existing sections up to nfoCentrale HTML 4.01 style: _private, astraendo, construction, images, notes, ob, ofrugal, omiser, projects, readings, sketch, front porch [dh:2013-10-04 double-check on construction and also the repaving for modern Construction Structure.] [dh:2023-11-16 Now here at https://orcmid.github.io/miser, the top-level structure is being changed. The material that is here now has upgraded Construction Structure and that will be continued as more material is refactored to here.]] | |
done 2023-11-25 |
2023-11-19 | orcmid/index.htm Fix to be correct Construction Structure. There should be a Construction Zone as well. | |
done 2023-11-16 |
2017-06-25 | Convert to Apache License. That means we need a LICENSE and a NOTICE at the root of this content. | |
won't fix 2023-11-16 |
2006-07-11 | Add version number to this page. | |
done 2023-11-04 |
2006-07-11 | Change construction office to use nested template and construction-note format. Rename to Construction Material | |
done | 2023-10-23 | Visit all FrontPage-managed pages and ensure UTF-8 encoding on all of them. | |
done | 2023-09-02 | Scrub these work items to reflect the current transposed situation. | |
done | 2023-09-02 | Scrub those work items from miser-theory.info that are inapplicable here. | |
inapplicable 2023-09-02 |
2017-07-22 | Change notations.htm to a document-engineering professional appearance page. This should probably not be the primary location, but only maintained to preserve existing links that others may have made, however unlikely. | |
inapplicable 2023-09-02 |
2017-07-22 | Replace binsearch.py with a tombstone and keep a version of the file somewhere else. | |
inapplicable 2023-09-02 |
2017-07-22 | Replace binsearch.cpp by a tombstone and keep a version of the file somewhere else. | |
inapplicable 2023-09-02 |
2013-10-15 | Propagate repaving to sketch/ with construction zone? [dh:2013-12-06 The Construction Zone will be eliminated. Sketch will become a professional-appearance structure with its document engineering in n020600 in the Notes section. There will be a hierarchy of default.htm pages that unfold the sketch.] | |
inapplicable 2023-09-02 |
2013-10-15 | Propagate repaving to projects/ | |
inapplicable 2023-09-02 |
2013-10-15 | Propagate repaving to omiser/ with construction zone? | |
inapplicable 2023-09-02 |
2013-10-15 | Propagate repaving to ofrugal/ | |
inapplicable 2023-09-02 |
2013-10-15 | Propagate repaving to ob/ | |
inapplicable 2023-09-02 |
2013-10-15 | Propagate repaving to astraendo/ with construction zone | |
inapplicable 2023-09-02 |
2013-10-15 | In construction, review the default standby pages in c000010 for folio and document-engineering structure. Double-check their construction-structure links and dependencies. | |
inapplicable 2023-09-02 |
2013-10-15 | notations.htm move to document-engineering folio | |
inapplicable 2023-09-02 |
2013-10-15 | synopsis.htm move to document-engineering folio [updating n011101 to that purpose] | |
inapplicable 2023-09-02 |
2013-10-15 | notations.htm construction-structure and style cleanup | |
inapplicable 2023-09-02 |
2013-10-15 | synopsis.htm construction-structure and style cleanup | |
inapplicable 2023-09-02 |
2013-10-15 | mt-static/ Create private construction structure for this add-on domain subfolder | |
inapplicable 2023-09-02 |
2013-10-15 | cgi-bin/ Create private construction structure for this add-on domain subfolder | |
inapplicable 2023-09-02 |
2013-10-04 | The /ob folder is where Ot should be handled. It currently has the synopsis (not the sketch). There needs to be folio structure throughout this site. The question is whether or not /ob is like a narrative folder and the details are in notes or whether /ob has a folio substructure. The same question applies to /omiser and /ofrugal, which could be documentation. The question becomes one of document engineering and whether the /projects folder should be replaced by a /dev folder or not. I think I might retire the /projects folder. Well, maybe not. I could have used a separate projects folder on OdmDev. The sketch is in n020600 and that is a challenge. I am leaning toward the use of notes, dev, and projects. The sketch folder is perhaps the overview that I want, but it needs to be structured better. Document engineering needs to be set up across the entire site, and that comes with construction structure first. So repaving counts. If I have enough construction pages, I can capture work items. [dh:2013-03-17 The notes folder will be where content, including document engineering is produced, and the ob/ folder will have the professional-appearance structure. It could have a construction zone, though, although a notes/ folio might be the best way to handle that.] | |
inapplicable 2023-09-02 |
2007-11-09 | Implement the first repaving based on the folio. Cover Construction structure, Notes, and Astraendo. Catch other folders as we move through the construction-structure propagation. [dh:2013-10-13 Maybe do projects folder early in this as well.][dh:2013-10-15 the first propagation is construction/.] | |
inapplicable 2023-09-02 |
2007-05-04 | Turn the Synopsis into a folio and work through the progressions. I can capture the issue of defining the items to be demonstrated more extensively as work items for the folio. | |
inapplicable 2023-09-02 |
2007-04-29 | Incorporate Creative Commons material here. | |
inapplicable 2023-09-02 |
2007-04-29 | Add construction structure to the notes/ subfolder so that I can continue to reorganize my material on programs vs. algorithms and what algorithms are. | |
inapplicable 2023-09-02 |
2006-06-06 | Repave the notes section too. Figure out what to do with the Readings and Projects sections too. [2014-05-03 The Readings section is handled.] | |
inapplicable 2023-09-02 |
2004-08-27 | During a slamdown at the root or at a blog default page, the index may show through while swapping is happening. Make the index.htm pages appropriate for being leaked onto. | |
inapplicable 2023-09-02 |
2004-06-04 | Clean up the table-of-content style and formatting on the default entry | |
inapplicable 2023-09-02 |
2004-06-04 | Conform the additional root material to the nfoCentrale.net structure, including <p>-form title blocks. | |
inapplicable 2023-09-02 |
2004-05-30 | Document link to anchor-site construction and also the use of /miser mirror-relative shortcuts. | |
inapplicable 2023-09-02 |
2004-05-30 | Remove link to the anchor-site construction section from the index.htm page | |
inapplicable 2023-09-02 |
2004-05-30 | Repopulate and clean up the compagno root after disrupting it with the miser renaming | |
inapplicable 2023-09-02 |
2003-12-09 | Have all sections of the sketch be bookmarked and grounded. These should be in the archive copies (that is, the note versions). The top level of the sketch may actually be an include-page use of a note body, though I have to worry about top and bottom bars. Something to think about in terms of having the sketch work like a W3C versioned specification. This applies to other specifications too. Think about it. Start using cross-references everywhere. | |
inapplicable 2023-09-02 |
2003-12-09 | Move all of the sketch material to the sketch section. Create a job jar there and continue its construction work. | |
done 2017-09-23 |
2013-10-15 | Propagate repaving to construction/ with construction zone | |
done 2017-07-08 |
2007-05-04 | Make a paned default.htm and front porch on the model of NuovoDoc. | |
done 2017-07-08 |
2014-04-21 | Make the new front page, once under document engineering, on the model of the NuovoDoc or ODMA Development Framework pages. De-emphasize the repaving and make a simpler default page. | |
done 2017-07-07 |
2013-10-15 | default.htm move to document-engineering folio | |
done 2017-07-07 |
2013-10-15 | default.htm construction-structure and style clean-up | |
done 2017-07-06 |
2014-03-28 | Correct the templates so that the ClustrMap is not brought in as part of the bottom control block but is included on a customized basis. [dh:2014-03-28 It would also work to have two versions of the footer. I also need to deal with the Creative Commons Attribution International 4.0 migration. The ClustrMap should be available only for Default and maybe Construction Material pages. It is also done differently with professional-appearance document engineering.][dh:2017-06-22 I am going to change this to Apache License v2. But the ClustrMap change should go through now. We don't need visit counts on construction materials.] | |
done | 2017-06-25 | make n170601 on the model of nfoWorks.org note n080201. | |
done | 2017-06-25 | Create notes/2017/06/ construction structure | |
done 2014-05-03 |
2013-10-15 | Propagate repaving to readings/ and decide about construction structure, whether to keep local material [dh:2104-05-03 The pages are repaved to current styles and formats, with possible staged transposition of the bibliographies to Orcmid's Lair to be done later.] | |
done 2014-04-27 |
2013-12-14 | Create a dev/ and Construction Zone for development work. This does not replace projects/, which is more about the project-management level of work, if used at all. | |
done 2014-04-27 |
2013-10-15 | Add dev/ with construction zone for managing development and deployment of Miser Project artifacts. | |
done | 2014-04-19 | Add keybase.txt to index.htm local content | |
done 2014-04-18 |
2014-04-15 | Add keybase.txt and site proof after updating the site. | |
done 2014-04-18 |
2013-11-03 | Get enough top-level repaving going to update the mirror and the site. There is too much unpublished material accumulating on Quadro. | |
done 2014-04-18 |
2013-10-15 | Accomplish a minimum necessary for updating the site and continuing. | |
done 2014-04-17 |
2004-01-06 | Create notes structure in the notes section (after HTML 4.01 style established here), and systematically bring the notes into conformance. | |
done 2014-03-17 |
2013-10-17 | Delete _private/construction.htm from the mirror and the hosted-site. | |
done 2014-03-17 |
2013-12-14 | _private/index.htm Correct "any comment there might be" to "any content there might be" | |
to c000006 2013-12-14 |
2006-07-11 | Add ClustrMap to Miser and to Numbering Peano [dh:2007-11-09 Figure out when this was done with addition of c000006. dh:2013-10-13 There still needs to be propogation throughout the site. dh:2013-12-14 The propogation is managed from c000006.] | |
done 2013-12-06 |
2013-10-04 | Review the Construction Materials and see what in c071101 an c071102 is working here. Do the Front Porch and then work through Construction Material in preparation for complete repaving. [dh:2013-10-13 c071101 is the Repaving Project, c071102 is the Creative Commons license, and c000006 is the ClustrMap. | |
done 2013-12-05 |
2013-10-15 | Propogate repaving to notes/ with construction zone | |
done | 2013-10-23 | Add notes/ and /astraendo to front porch Construction Zone hierarchy | |
done | 2013-10-23 | Add notes/ and /astraendo to front porch Construction Structure | |
done 2013-10-23 |
2013-10-15 | Propogate repaving to images/ | |
done | 2013-10-17 | In the Construction Structure bottom message block, fix the link to Construction Structure to go to the top. | |
done 2013-10-17 |
2013-10-15 | Propogate repaving to _private/ | |
done 2013-10-15 |
2007-04-30 | Correct title-block styles and text sizes for this construction zone material: c000000, default, construction, index.htm, default.htm | |
done 2013-10-15 |
2006-07-11 | Introduce latest styles and include pages. [dh:2010-10-15 Front Porch only] | |
done 2013-10-15 |
2007-05-04 | Implement construction-structure links for the front porch pages: default.htm, c000000.htm, construction.htm | |
done 2013-10-15 |
2013-10-04 | construction.htm: This is an ODMdev clone. It is not fully customized. It needs to be revamped as well to be part of the construction structure. It can be marked for repaving first, if necessary. | |
done 2013-10-13 |
2006-07-11 | Use the Construction Structure Style for this front porch and put propagation into construction project. [dh:2007-04-27 This involves using the Construction Structure model being slowly propagated on other sites. ODMdev is currently the best model. dh:2013-10-04 This is now hung off of c071101 and it can proceed here.] | |
done 2013-10-13 |
2007-05-04 | Make index.htm into a construction structure page on the model of http://ODMA.info/dev/index.htm | |
done 2010-04-30 |
2007-11-09 | Create a ClustrMap insertion folio (template c000006) | |
done 2007-11-11 |
2007-11-09 | Create a repaving folio | |
done 2007-11-11 |
2007-11-09 | Set up for repaving Miser-theory.info. Create template sections 00 and 10 and set up catalog and annualized material. [dh:2007-11-11 This is handled in the Construction Material section] | |
done 2007-11-11 |
2007-05-04 | Create a hardhat-thumb.gif version and use it as the direct image in construction blocks on the front porch. Create its replication elsewhere. | |
done 2007-07-11 |
2006-10-29 | Add warning notice about repaving, broken links, etc. Link to the treatment on clueless or orcmid.com [dh:2013-10-13-13:53 The repaving project mus include attention to broken links as the result of migration to A2 Hosting.] | |
done | 2007-05-04 | Review and correct links from the default.htm page. | |
done | 2007-05-04 | Fix default.htm to link to Construction Structure. | |
done | 2007-05-04 | The incorrect title block was added to default.htm. Correct the anchor link and make into "Provisional Entrance." | |
done | 2007-05-02 | Add the ClustrMap to the left sidebar of Numbering Peano. | |
done | 2007-05-02 | Change the caption on the ClustrMap on c000005c. | |
done | 2007-04-30 | Add the ClustrMap to the you-are-here strip for ordinary pages. | |
done | 2004-06-04 | Connect to astraendo/ | |
done | 2004-06-04 | Clean up the default page for updated entrance style | |
done | 2004-06-04 | Adjust the index for presence of a Construction Zone, if necessary | |
done | 2004-06-04 | Convert the construction.htm page here to a Construction Zone introduction. | |
done | 2004-06-04 | Add Construction Zone Diary & Job Jar (this page). |
You are navigating |
created 2004-06-04-16:11 -0800 (pst) by orcmid |