Difference between revisions of "RawringTwenties"

From Cibernética Americana
Line 27: Line 27:
 
Source code of C-六, GT2, YAS3, and  all supporting code  for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are required. GT2 and YAS3 are completions for projects from the prior decade which have become presentation vehicles  for bespoke apps/services using various supports but themselves are basically feature static after 4719 with change limited to utilization of new infrastructure.
 
Source code of C-六, GT2, YAS3, and  all supporting code  for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are required. GT2 and YAS3 are completions for projects from the prior decade which have become presentation vehicles  for bespoke apps/services using various supports but themselves are basically feature static after 4719 with change limited to utilization of new infrastructure.
 
</blockquote ></td><td valign=middle width=33% align=left style="font-weight: 600;color: white; background-color: black; margin: 1px;  text-indent: 5px;"><blockquote  
 
</blockquote ></td><td valign=middle width=33% align=left style="font-weight: 600;color: white; background-color: black; margin: 1px;  text-indent: 5px;"><blockquote  
style="position: relative;left: -5px;text-align: justify;">
+
style="position: relative;left: -15px;text-align: justify;">
 
For the value of the interaction, I remain open to joining a group, either deferring my projects for an agreed period, or in joint development agreements. Moving from seriality in the open source commons to fusion with a smaller group has a presumed low but unknown expected value in this period. As a sole trader, I am bound by whatever stipulations various local jurisdictions make for same and will disable access from those where I cannot meet their requirements as they become known.</blockquote>
 
For the value of the interaction, I remain open to joining a group, either deferring my projects for an agreed period, or in joint development agreements. Moving from seriality in the open source commons to fusion with a smaller group has a presumed low but unknown expected value in this period. As a sole trader, I am bound by whatever stipulations various local jurisdictions make for same and will disable access from those where I cannot meet their requirements as they become known.</blockquote>
 
</td>/tr>
 
</td>/tr>

Revision as of 04:13, 11 June 2021


4720-30 Agenda (2020s Era Vulgaris)


  1. MCP/DCP — intelligent OS with mannerisms in homage to mainframes¹
  2. C-六 — php/python Domain CMS
  3. .dom — my TLD
  4. TASKPM tl;dr™ — taskwarrior, MS Project, etc. for DS users
  5. GT2 — (Green Travel Calculator) personal carbon accounting app
  6. YAS3 — yet another S3 client



                      Impressum   

     Domain engineering,   mecha intelligence,   worker capitalism   are  leitmotives.

AutoConsult, doorbell/Ft: legacy labels for intelligent conversational agent and videoconf efforts, respectively.

tl;dr™ and sameboat name app and C-六 based affinity/social networking product lines, respectively.

redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), are designations of support layers.


/tr>

I suppose in the way people talk, MCP/DCP is my passion, the central project and while every 3rd party package I use in its construction is made available here in the form I've found it, I don't intend to release my original sources for the OS product at least in this decade. Everything else is maintained in open source form and can be the basis of various development opportunities. Open source here (as opposed to github) means available at some level of entitlement either simple capitation (AKPERSON) or devops levels.

Source code of C-六, GT2, YAS3, and all supporting code for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are required. GT2 and YAS3 are completions for projects from the prior decade which have become presentation vehicles for bespoke apps/services using various supports but themselves are basically feature static after 4719 with change limited to utilization of new infrastructure.

For the value of the interaction, I remain open to joining a group, either deferring my projects for an agreed period, or in joint development agreements. Moving from seriality in the open source commons to fusion with a smaller group has a presumed low but unknown expected value in this period. As a sole trader, I am bound by whatever stipulations various local jurisdictions make for same and will disable access from those where I cannot meet their requirements as they become known.


¹ Mainly Burroughs, with a nod to VM/CMS.