C-Liu

(12 intermediate revisions by the same user not shown)

Line 17:

<center style="position:relative;top:-5px;">C-Liu (C6*): part of DCMS, reuses final [[PHPCMS|D7]]<html></center> "DCMS" is domain content management in the large

outside of </html>[[MCP|DCP]] not just C六. C六 runs in a php 7 [[MCPCELL|MCP cell]], I support only for that context but it is mostly unaltered

D7 modules. To be clear, generally in DCMS. e.g. 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 <html><a style="color: lime;" href=https://github.com/haskell-beam/beam>beam</a> and <a style="color: lime;" href=https://github.com/pa-ba/compdata>compdata</a></html> based unification of the relational schema of the constiuent backend CMSes.<ref> As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).</ref></td>

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 <html><a style="color: lime;" href=https://github.com/haskell-beam/beam>beam</a> and <a style="color: lime;" href=https://github.com/pa-ba/compdata>compdata</a></html> based unification of the relational schema of the constiuent backend CMSes.<ref> As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).</ref></td>

<td width=3%></td><td> <center style="position:relative;top:-19px;"><html><a style="color: lime;"

title="pronounced 'DCMS bra'" href=/eg/index.php/Redvant><DCMS</a> and <a style="color: lime;" title="pronounced 'DCMS ket'"

href=https://sameboat.network/DCMS/>DCMS></a> name front and back end elements relative to this PHP codeset, respectively ³.</center>

C六 became a fork of D7 as of 7.99 </html><ref>selective changes thru 101 ~~were~~ applied ~~by November 2025~~.</ref> which ~~contains~~ changes I ~~don't~~ want in core, ~~so it's Dec 2023 not~~ Jan 2025 ~~for C六~~. 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.

~~I occasionally use C六~~ to ~~refer~~ to ~~php in DCMS generally, D7, or current mediawiki~~ and ~~wordpress in~~ a ~~way that should be clear in context or~~ by ~~a disambiguating qualifier~~.

C六 became a fork of D7 as of 7.99 </html><ref>selective changes thru 101 have been applied.</ref> which contained changes I didn want in core, then d.o after many false starts did in fact decommit in Jan 2025.<ref> 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.</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 by normal users and most developers.

As far as the C六 D7 line is concerned, [[:en:security by design|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)~~. <~~ref~~><~~font size=1~~>~~Registration plus~~ a ~~provided waiver will entitle~~, ~~message me for it~~.<~~/font></ref><span~~>

As far as the C六 D7 line is concerned, [[:en:security by design|security]] and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with core and contrib modules diverged as indicated above and the project/update modules are modified to use sameboat commons. D7 module authors can get forgejo access with social networked, i.e. free entitlement C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress, other pkgs/oddments.

Line 39:

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-07 — Modules rebuilt as projects and redirected to 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.

@@ Line 17: / Line 17: @@
 <center style="position:relative;top:-5px;">C-Liu (C6*):  part of DCMS, reuses final  [[PHPCMS|<span style="color: lime;">D7</span>]]<html></center> "DCMS"  is domain content management in the large
 outside of  </html>[[MCP|<span style="color: lime;">DCP</span>]] not just C六.  C六 runs in a php 7 [[MCPCELL|MCP cell]], I support only for that context but it is mostly unaltered
-D7 modules. <br><span style="position:relative;top:8px;">To be clear, generally in DCMS. e.g. 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 <html><a style="color: lime;" href=https://github.com/haskell-beam/beam>beam</a> and <a style="color: lime;" href=https://github.com/pa-ba/compdata>compdata</a></html> based unification of the relational schema of the constiuent  backend CMSes.<ref><span style="font-size:10px;"> As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).</span></ref></span></td>
+D7 modules. <br><span style="position:relative;top:8px;">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 <html><a style="color: lime;" href=https://github.com/haskell-beam/beam>beam</a> and <a style="color: lime;" href=https://github.com/pa-ba/compdata>compdata</a></html> based unification of the relational schema of the constiuent  backend CMSes.<ref><span style="font-size:10px;"> As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).</span></ref></span></td>
 <td width=3%></td><td> <center style="position:relative;top:-19px;"><html><a style="color: lime;"
 title="pronounced 'DCMS bra'" href=/eg/index.php/Redvant>&lt;DCMS</a> and <a style="color: lime;" title="pronounced 'DCMS ket'"
 href=https://sameboat.network/DCMS/>DCMS&gt;</a> name front and back end elements relative to this PHP codeset, respectively &sup3;.</center>
-<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 were applied by November 2025.</font></ref> which contains changes I don't want in core, so it's Dec 2023 not Jan 2025 for C六. 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. <br>
-I occasionally use C六 to refer to php in DCMS generally, D7, or current mediawiki and wordpress in a way that should be clear in context or by a disambiguating qualifier.<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 by normal users and most developers.<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>
+<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 diverged as indicated above and the project/update modules are modified to use sameboat commons.  D7 module authors can get forgejo access with social networked, i.e. free entitlement<span><br><br>C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress, other pkgs/oddments.<br>
 </span>
 <html></td></tr>
@@ Line 39: / Line 39: @@
 <span style="font-size:8px;">domains common era after ceremonial</span><br>
 <blockquote>
-<p>075-05 &mdash; Selected modules rebuilt as projects and update mechanism modified to use either d.o or sameboat commons.</p>
+<p>075-07 &mdash; Modules rebuilt as projects and redirected to sameboat commons.</p>
 <p>075-04 &mdash; django-cms adopted as sister CMS.</p>
 <p>075-01 &mdash; D7 disappears from new d.o guided flow  but still available with others going back to D5.</p>

C-Liu: Difference between revisions

Navigation menu

Page actions

Page actions

Personal tools

About

Search

forewords

novel

Tools