DCMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
Explicit Design Goals | Explicit Design Goals | ||
*A role in the Large Systems Revival relative to MCP analogous to these original Burroughs subsystems: DMSII, possibly CANDE and NDLII/NAU. | |||
*Reuse of unmodified existing CMS, specifically these: Drupal, WordPress, mediawiki, ecore, and mezzanine. | *Reuse of unmodified existing CMS, specifically these: Drupal, WordPress, mediawiki, ecore, and mezzanine. | ||
*Mature apps are developed as literate artifacts in the WFL book metaphor. | *Mature apps are developed as literate artifacts in the WFL book metaphor. | ||
* | *DCP (the Burroughs Data Comm Processor not the later same acronymed thing here) using the distributed-process family of haskell modules on MCP nodes. | ||
*Apps start life in discrete subject CMSes (e.g. sameboats, | *Apps start life in discrete subject CMSes (e.g. sameboats, tl:dr[n], <span class="plainlinks">[https://pm-lets.principalsonly.org poo domain]</span>), the admin server in django/mezzanine), migrate into the larger context as the driving case of development of our enterprise. | ||
Explicit Non Goals | Explicit Non Goals | ||
