Difference between revisions of "C-Liu"

From Cibernética Americana
Line 13: Line 13:
 
"DCMS" is used in the widest sense to refer not just to the php/python core (C六) but to content management in domain space generally outside of the </html>[[MCP|<span style="color: lime;">DCP</span>]]<html> providing manifold services to </html>[[AKPERSON|<span style="color: lime;">AKPERSONS</span>]]<html>. <a style="color: lime;" title="pronounced 'DCMS bra'" href=https://eg.meansofproduction.biz/eg/index.php/Redvant>DCMS&lt;</a> and <a style="color: lime;" title="pronounced 'DCMS ket'" href=https://sameboat.live/DCMS/>DCMS&gt;</a> name front and back end elements relative to the Drupal 7 codebase, respectively.  C六 php will remain d7 based&sup3;.
 
"DCMS" is used in the widest sense to refer not just to the php/python core (C六) but to content management in domain space generally outside of the </html>[[MCP|<span style="color: lime;">DCP</span>]]<html> providing manifold services to </html>[[AKPERSON|<span style="color: lime;">AKPERSONS</span>]]<html>. <a style="color: lime;" title="pronounced 'DCMS bra'" href=https://eg.meansofproduction.biz/eg/index.php/Redvant>DCMS&lt;</a> and <a style="color: lime;" title="pronounced 'DCMS ket'" href=https://sameboat.live/DCMS/>DCMS&gt;</a> name front and back end elements relative to the Drupal 7 codebase, respectively.  C六 php will remain d7 based&sup3;.
 
<br><br>
 
<br><br>
In Novemeber, 2022 D7 will reach EOL and drupal.org will cease to support it. Drupal has a vendors program for extended support which is inappropriate for me as C六 isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. Instructions on how to set my servers for the drupal update function will be posted here before the EOL allowing the module update mechanism  to continue for the from that point diverged lines. As far as the C六 line is concerned, security issues are covered by domain space security. At this point, most core and contrib modules are unaltered, but all will formally diverge when their live status contrasts with d.o.  D7 module maintainers  will be able to use the D7 project mechanism here whether or not the module is used in C六. <br><br>
 
 
<a href=https://sameboat.network><span style="color: lime;">Sameboat commons</span></a> is the stable </html><ref><font size=1>Version of function in live may be different from what makes it to commons.</font></ref><html> branch from my <a href=https://sameboat.live>live sandbox</a> and the first stop before downstream deployments. The <a style="color: lime;" href=https://sameboat.live/sb-app>common app platform</a> supports C六 and my product lines as a base. The sandbox will be privately routed with the same .live suffix after its IANA registration is dropped in November, 2022 requiring use of the domain space nameservers.<br>
 
<a href=https://sameboat.network><span style="color: lime;">Sameboat commons</span></a> is the stable </html><ref><font size=1>Version of function in live may be different from what makes it to commons.</font></ref><html> branch from my <a href=https://sameboat.live>live sandbox</a> and the first stop before downstream deployments. The <a style="color: lime;" href=https://sameboat.live/sb-app>common app platform</a> supports C六 and my product lines as a base. The sandbox will be privately routed with the same .live suffix after its IANA registration is dropped in November, 2022 requiring use of the domain space nameservers.<br>
</blockquote>
+
Also in Novemeber, 2022 D7 will reach EOL and drupal.org will cease to support it. Drupal has a vendors program for extended support which is inappropriate for me as C六 isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. Instructions on how to set my servers for the drupal update function will be posted here before the EOL allowing the module update mechanism  to continue for the from that point diverged lines. As far as the C六 line is concerned, security issues are covered by domain space security. At this point, most core and contrib modules are unaltered, but all will formally diverge when their live status contrasts with d.o.  D7 module maintainers  will be able to use the D7 project mechanism here whether or not the module is used in C六. <br><br></blockquote>
 
<blockquote style="width: 80%;">
 
<blockquote style="width: 80%;">
 
Key Events
 
Key Events

Revision as of 18:57, 4 May 2022


                       
  C六


Biz case #65, the php and python codesets at the core of the Domains CMS.
Defining use cases are the sameboat network and the AKSAMBAR products.


 
"DCMS" is used in the widest sense to refer not just to the php/python core (C六) but to content management in domain space generally outside of the DCP providing manifold services to AKPERSONS. DCMS< and DCMS> name front and back end elements relative to the Drupal 7 codebase, respectively. C六 php will remain d7 based³.

Sameboat commons is the stable [1] branch from my live sandbox and the first stop before downstream deployments. The common app platform supports C六 and my product lines as a base. The sandbox will be privately routed with the same .live suffix after its IANA registration is dropped in November, 2022 requiring use of the domain space nameservers.
Also in Novemeber, 2022 D7 will reach EOL and drupal.org will cease to support it. Drupal has a vendors program for extended support which is inappropriate for me as C六 isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. Instructions on how to set my servers for the drupal update function will be posted here before the EOL allowing the module update mechanism to continue for the from that point diverged lines. As far as the C六 line is concerned, security issues are covered by domain space security. At this point, most core and contrib modules are unaltered, but all will formally diverge when their live status contrasts with d.o. D7 module maintainers will be able to use the D7 project mechanism here whether or not the module is used in C六.

Key Events

c. 4719 — Portable Groups. Fork live and commons prod, rebuilding the latter².

c. 4716 — Pursuant to SA-CORE-2018-004, C六 drupal was rebuilt from scratch.

c. 4714 — First selection of sameboat name based on concept of affinity group support.

c. 4705 — First selection of Drupal as php CMS of choice and the C六 name after C5.




  ²C-六 exceeds drupal tolerances ( best practice), engineering/curation to make it so and make it work is part of the ops concept. Live now has 464 and commons 279 non core.   ³D9/10 branch for devops use, other php packages generally track latest release for the operational stack.

C5 (whence "C-6") C六书 d.o
  1. Version of function in live may be different from what makes it to commons.