Aggregrotto is a reengineering of Spacemacs' core using literate programming

[bryce-carson]

@syl20bnr
@JAremko
@smile13241324
@bcc32
@fnussbaum
@sunlin7

I have created a literate (aggressively so) programming fork of Spacemacs core
functionality which I am calling Aggregrotto. It's called Aggregrotto because
it is an aesthetic, artificial cave within Spacemacs' (otherwise natural)
mountain of code. I'm taking an aggressive approach to literate programming:
everything that can be done from within a single Org file is being done from
within that file. The name is unimportant, however.

As a repository of code, Aggregrotto is lean (only a few files) and does not
seek to reproduce everything Spacemacs proper does: CI, tests/, and layers/
are not a part of Aggregrotto. Those things are already taken care of within
Spacemacs' repository and I don't want to replace Spacemacs nor reimplement
everything it does. At the moment it offers only a new approach to
(re-)engineering the core of Spacemacs, and any other parts of the project which
are impacted by changes to the core.

In terms of a fork it is not taking Spacemacs in a different direction. For now
it only produces Spacemacs' core files and an increasingly useful literate
program when exported as HTML.

Tangling Aggregrotto produces core/, and other changes, which can be applied to
Spacemacs as a large patch; Aggregrotto cannot be merged directly. Originally
the changes coming out of Aggregrotto could've been merged directly, but I
wanted to ensure that the core files themselves were not edited, so I deleted
them. That change spurred many others, and I've ended the pruning process with
just LICENSE, README.org, and org/*.o rg.

While it is a fork, it isn't taking Spacemacs in a massively different
direction, except that core/ is the product of tangling the literate program (as
are other files and directory trees). The objective is to provide a
better-documented core/ of Spacemacs, and also provide an opportunity to explore
the upper limits of Org mode's literate programming facilities.

---

Everyone tagged was either in the COMMUNITY.org list as a current maintainer/contributor, or has push access.

[bryce-carson]

Within the literate program, where it reads as follows, the changes will be rolled back to make it produce Spacemacs again. The updates to the copyright were unnecessary, mostly, but the use of Noweb chunks is a still a very good idea for that.

;; Copyright (c) 2012-<<copyright year>> <<copyright holders>>
;;
;; Author: <<bryce>>
;; URL: <<aggregrotto url>>

<<sylvain>> and <<ghurl>> were used prior to <<bryce>> and <<aggregretto url>>.

[bryce-carson]

It makes it very easy to increment the copyright year throughout the entire project, and to ensure that all files have consistent and correct information.