C-Liu: Difference between revisions
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
<span style="position:relative;top:-10px;">C六 became a fork of D7 as of 7.99 </html><ref><font size=1>selective changes thru 101 have been applied.</font></ref> which contained changes I didn want in core, then d.o after many false starts did in fact decommit in Jan 2025.<ref><font size=1> Since the actual decommit at d.o, all modules in our charge have their sources pointing to our server. However existing d7 modules on d.o can still be installed with an URL in C六. The C六 update mechanism will not convert them and they will show as unsupported as all modules do in a regular d7 site since the decommit.</font></ref> The direction for DCMS is as indicated to the left, the d7 codeset is used as is as a bolus of function to be replaced at a later date and it is best taken as a black box.<br> | <span style="position:relative;top:-10px;">C六 became a fork of D7 as of 7.99 </html><ref><font size=1>selective changes thru 101 have been applied.</font></ref> which contained changes I didn want in core, then d.o after many false starts did in fact decommit in Jan 2025.<ref><font size=1> Since the actual decommit at d.o, all modules in our charge have their sources pointing to our server. However existing d7 modules on d.o can still be installed with an URL in C六. The C六 update mechanism will not convert them and they will show as unsupported as all modules do in a regular d7 site since the decommit.</font></ref> The direction for DCMS is as indicated to the left, the d7 codeset is used as is as a bolus of function to be replaced at a later date and it is best taken as a black box.<br> | ||
<span style="position:relative;top:8px;">As far as the C六 D7 line is concerned, [[:en:security by design|<span style="color: lime;">security</span>]] and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with core and contrib modules formally diverged as of 7.98 and the project update mechanism redirected to commons. D7 module authors get free forgejo access (via requested waivers). <ref><font size=1>Registration plus a provided waiver will entitle, message me for it.</font></ref><span><br>C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress or other pkgs in a way that should be clear in context or by a disambiguating qualifier.<br> | <span style="position:relative;top:8px;">As far as the C六 D7 line is concerned, [[:en:security by design|<span style="color: lime;">security</span>]] and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with core and contrib modules formally diverged as of 7.98 and the project update mechanism redirected to commons. D7 module authors get free forgejo access (via requested waivers). <ref><font size=1>Registration plus a provided waiver will entitle, message me for it.</font></ref><span><br><br>C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress or other pkgs in a way that should be clear in context or by a disambiguating qualifier.<br> | ||
</span> | </span> | ||
<html></td></tr> | <html></td></tr> | ||
Revision as of 10:59, 18 July 2025
℠
C六
A PHP network DCMS façade
C六 was derived from Drupal 7 for use in MCP contexts.
Outside sameboat, the curated modules are mostly unaltered and others will generally work if they did in final D7.
C-Liu (C6*): part of DCMS, reuses final D7 "DCMS" is domain content management in the large outside of DCP not just C六. C六 runs in a php 7 MCP cell, I support only for that context but it is mostly unaltered D7 modules.
To be clear, generally in DCMS, i.e. in mediawiki, WordPress, php is at the supported level, e.g. 8 or whatever the php code requires. DCMS aims to realize CMS generalization via beam and compdata based unification of the relational schema of the constiuent backend CMSes.[1]<DCMS and DCMS> name front and back end elements relative to this PHP codeset, respectively ³. C六 became a fork of D7 as of 7.99 [2] which contained changes I didn want in core, then d.o after many false starts did in fact decommit in Jan 2025.[3] The direction for DCMS is as indicated to the left, the d7 codeset is used as is as a bolus of function to be replaced at a later date and it is best taken as a black box.
As far as the C六 D7 line is concerned, security and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with core and contrib modules formally diverged as of 7.98 and the project update mechanism redirected to commons. D7 module authors get free forgejo access (via requested waivers). [4]
C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress or other pkgs in a way that should be clear in context or by a disambiguating qualifier.
Roadmap: C六 relegated to SB network, Redvant headed django-cms becomes the default concrete CMS.
The common app platform supports C六 and my product lines on Android and iOS.
A Timeline
domains common era after ceremonial
075-05 — Selected modules rebuilt as projects and update mechanism modified to use either d.o or sameboat commons.
075-04 — django-cms adopted as sister CMS.
075-01 — D7 disappears from new d.o guided flow but still available with others going back to D5.
074-12 — Merge selected final (7.103) changes.
073-12 — Drupal 7.99 drops, diverge from d.o.
c. 4721 — IANA .live replaced by .network.
c. 4719 — PG Concept. 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.
This page has a music track, mouseover for title.
| *C5 (whence "C-6") | C六书 | d.o |
³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 101 and commons has 77 packages.
D10/11 branch for devops use, other php packages generally track latest release for the operational stack.
- ↑ As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).
- ↑ selective changes thru 101 have been applied.
- ↑ Since the actual decommit at d.o, all modules in our charge have their sources pointing to our server. However existing d7 modules on d.o can still be installed with an URL in C六. The C六 update mechanism will not convert them and they will show as unsupported as all modules do in a regular d7 site since the decommit.
- ↑ Registration plus a provided waiver will entitle, message me for it.
