Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Laid down the framework for "ARGON devops": ARGON code lives in CARBON stuff published by entities, so I laid out a framework for a "document entity" that publishes something with distributed workflow, ticketing, change control, etc. |
---|---|
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
44239360342516c32b9db0af848821c4 |
User & Date: | alaric 2017-03-16 18:19:22 |
Context
2017-06-02
| ||
21:57 | Expounded on Iodine Object Push, and wondered about special support for it within MERCURY. check-in: 6ad45702f4 user: alaric tags: trunk | |
2017-03-16
| ||
18:19 | Laid down the framework for "ARGON devops": ARGON code lives in CARBON stuff published by entities, so I laid out a framework for a "document entity" that publishes something with distributed workflow, ticketing, change control, etc. check-in: 4423936034 user: alaric tags: trunk | |
2015-07-08
| ||
08:51 | "Phiosphy" type (thanks to Oskar Schirmer for spotting it!) check-in: 536f2beab9 user: alaric tags: trunk | |
Changes
Changes to intro/iodine.wiki.
︙ | ︙ | |||
42 43 44 45 46 47 48 | Link to entity. Edit list of linked entities and their local metadata. Provides CARBON directory links in the public CARBON data. <h1><tt>/argon/iodine/container</tt>: Storage Container</h1> | | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 | Link to entity. Edit list of linked entities and their local metadata. Provides CARBON directory links in the public CARBON data. <h1><tt>/argon/iodine/container</tt>: Storage Container</h1> Offers the user the ability to create an entity, given a template. Provides CARBON directory links to contained entities. <h1><tt>/argon/iodine/document</tt>: Editable document</h1> This interface is for editing document entities, whose primary function is to publish some static data, for example CHROME source code or general CARBON reference data. The document entity doesn't directly publish the data in its CARBON metadata, but provides personas whose CARBON metadata is each a version of what is published. The document entity itself provides links to the latest release and other useful information. In essence, a document entity provides a version control system suitable for maintaining a published artefact: * Commits/Versions/Diffs * Branches and merges * Pull requests * Code review process for pull requests * Tagging a release (only "release" versions are listed on the "front page") * Ticket tracking, and linking tickets to commits * The ability to clone a document entity, and then to push pull requests back to the origin * Managing the "project metadata" also exposed from the document entity; this covers the functions of project home page and project wiki for internal documentation that shouldn't be versioned along with the source (THAT stuff can actually live in with the source). This itself is a "document" in its own right, so is modelled as a chain of versions inside the document entity itself - but with a separate root commit, similar to how github pages work. The project metadata doesn't have releases and code reviews, though. Each actual version (release or not) gets a persona that exposes that data via CARBON, plus a small metadata statement marking it as a version of something, with a link to the document entity itself and to all parent/child versions, and metadata declaring it as a release or not. A special persona reflects the "latest version" of each branch, by issuing a redirection to the actual persona for that version, too. <h1><tt>/argon/iodine/entity</tt>: Entity Administration</h1> Edit ACLs, delete entity, directly edit TUNGSTEN state. This one might deserve some special-casing somewhere in LITHIUM/WOLFRAM/TUNGSTEN in order to allow designated cluster super-users to let people back into entities they've locked themselves out of... <h1><tt>/argon/iodine/physical</tt>: Physical object</h1> Location information, and images (from pictures to 3D models) of its physical manifestation. |