Bureaucrats, Interface administrators, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), Administrators, Widget editors
23,007
edits
RawringTwenties: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
By 73 cog and machine arch conceptual design was settled. Then, a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines.<br> <span style="font-size:12px;position:relative;left:5px;top:5px;color:lightsalmon;"> The Sistine Chapel took 5 years, static content & Don Knuth started [[:en:TAOCP|<font color=lime>TAOCP</font>]] in 1962.</span></p> All AKPersons have access to C-六/DCMS and FOSS projects not on github at S class entitlement. Development of a bespoke app, or developer use of the KEE<ref>Our Knowledge Engineering Environment</ref>, requires devops entitlement. GT2 originating in the early teens will, with the rest of the tl:dr line have completions early in this period as drivers for DCP/MCP with change limited to maintenance after product baselines achieved.<ref>Sources of C-六 and the tl;dr products are available per entitlement.</ref><ref>Mechanism vs. content: DCP will remain binary dist, while it's knowledge bases will be in standard file formats. Even documentation will be deferred past the first cohort of knowledge engineers other than myself. Everything else (including MCP) is maintained here in source form and can be the basis of various development opportunities.</ref></blockquote ></td><td width=1%></td></tr></table> | By 73 cog and machine arch conceptual design was settled. Then, a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines.<br> <span style="font-size:12px;position:relative;left:5px;top:5px;color:lightsalmon;"> The Sistine Chapel took 5 years, static content & Don Knuth started [[:en:TAOCP|<font color=lime>TAOCP</font>]] in 1962.</span></p> All AKPersons have access to C-六/DCMS and FOSS projects not on github at S class entitlement. Development of a bespoke app, or developer use of the KEE<ref>Our Knowledge Engineering Environment</ref>, requires devops entitlement. GT2 originating in the early teens will, with the rest of the tl:dr line have completions early in this period as drivers for DCP/MCP with change limited to maintenance after product baselines achieved.<ref>Sources of C-六 and the tl;dr products are available per entitlement.</ref><ref>Mechanism vs. content: DCP will remain binary dist, while it's knowledge bases will be in standard file formats. Even documentation will be deferred past the first cohort of knowledge engineers other than myself. Everything else (including MCP) is maintained here in source form and can be the basis of various development opportunities.</ref></blockquote ></td><td width=1%></td></tr></table> | ||
<span style="position:relative;left:7px;text-align:center;" class=plainlinks>[https://meansofproduction.biz/rawr <span style="color: lime;">Impressum</span>]</span> | <span style="position:relative;left:7px;text-align:center;" class=plainlinks>[https://meansofproduction.biz/rawr <span style="color: lime;">Impressum</span>]</span> | ||
<br><span style="position:relative;left: | <br><span style="position:relative;left:20px;font-size: 8px;">In chrono order of completion; Besides DCP, all are in maintenance after mature baseline ...</span><br><span style="font-family: Papyrus;font-size: 14px;color: cyan;">[[:zh:wiki/%E4%BF%AE%E8%BA%AB|<span style="font-size: 14px;color: white;">修身 — </span>]] Zero-th precedence. Failing it moots projects, if it succeeds failure in them tolerable / temporary.</span><br><br> | ||
<ol style="width:60%;position:relative;left:-7px;list-style-type: cjk-ideographic;"> | <ol style="width:60%;position:relative;left:-7px;list-style-type: cjk-ideographic;"> | ||
<li><html><a onclick="return checkRouting();" href=https://sameboat.dom title="only works if you're routing my alt root">.dom</a></html> — Domain Space (DS) <ref>The .dom TLD in operation for most of the prior decade, support for it deepening in this one. The name has been routing since c. 2014, encompasses everything else.</ref></li> | <li><html><a onclick="return checkRouting();" href=https://sameboat.dom title="only works if you're routing my alt root">.dom</a></html> — Domain Space (DS) <ref>The .dom TLD in operation for most of the prior decade, support for it deepening in this one. The name has been routing since c. 2014, encompasses everything else.</ref></li> | ||
