💾 Archived View for gemi.dev › gemini-mailing-list › 000319.gmi captured on 2024-03-21 at 17:22:35. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-12-28)
-=-=-=-=-=-=-
Putting the spec in a git repo would make it easy to see what changed between versions of the specification. This of course would be complementary to the current spec on Gemini/web/gopher which would show the latest spec (and could be generated from git?). Thoughts? Sot
On Mon, Aug 10, 2020 at 10:32:34AM +0000, Sotiris Papatheodorou wrote: Hi! > Putting the spec in a git repo would make it easy to see what changed > between versions of the specification. This of course would be > complementary to the current spec on Gemini/web/gopher which would show > the latest spec (and could be generated from git?). Thoughts? I like this idea! Bye! C.
Specifications are not designed to change often; they thus should be well-versioned, well-defined as to anything breaking, and all versions should coexist in the same location. Version control is for sites of rapid and subtle change with many authors. It isn?t necessary in my opinion, but it?s fine anyway. Matilde > On Aug 10, 2020, at 11:23 AM, cage <cage-dev at twistfold.it> wrote: > > On Mon, Aug 10, 2020 at 10:32:34AM +0000, Sotiris Papatheodorou wrote: > > Hi! > >> Putting the spec in a git repo would make it easy to see what changed >> between versions of the specification. This of course would be >> complementary to the current spec on Gemini/web/gopher which would show >> the latest spec (and could be generated from git?). Thoughts? > > I like this idea! > > Bye! > C.
The spec (and FAQ, best practices, etc) do actually live in a git repo, I have just been lazy so far about making it publically cloneable, although people do keep asking. I'm not opposed, just haven't gotten around to it yet. I will try to do so this week, though. Cheers, Solderpunk
On Mon, Aug 10, 2020 at 10:10:49PM +0200, Solderpunk wrote: > The spec (and FAQ, best practices, etc) do actually live in a git repo, > I have just been lazy so far about making it publically cloneable, > although people do keep asking. I'm not opposed, just haven't gotten > around to it yet. I will try to do so this week, though. Great! Thank you! :) C.
On Tue Aug 11, 2020 at 9:00 PM CEST, cage wrote: > On Mon, Aug 10, 2020 at 10:10:49PM +0200, Solderpunk wrote: > > The spec (and FAQ, best practices, etc) do actually live in a git repo, > > I have just been lazy so far about making it publically cloneable, > > although people do keep asking. I'm not opposed, just haven't gotten > > around to it yet. I will try to do so this week, though. > > Great! Thank you! :) > > C. This is finally possible! Sorry for the long wait, to everybody who has been asking for this. You should be able to: git clone git://gemini.circumlunar.space/gemini-site and end up with a repo which contains the entire gemini://gemini.circumlunar.space site, except for the CAPCOM instance (which is powered by a cronjob) and, of course, the user directories. So, you'll find the current specification under docs/specification.gmi in your cloned repo. If you wind the history back far enough in time, it will jump from containing the entire site to containing just the essential documents and, at the very first commit, only the (then very rough!) specification. I hope people enjoy this glimpse into the history of the protocol! Cheers, Solderpunk
On Sun, Aug 16, 2020 at 08:32:50PM +0200, Solderpunk wrote: [...] > I hope people enjoy this glimpse into the history of the protocol! Thank you Solderpunk! Browsing the changes happened to specifications is not only useful but also fascinating someway! Bye! C.
---