Re: Gemini Digest, Vol 26, Issue 3

I'm not sure if it's entirely what you're looking for but have you checked 
out sloum's stagit fork:

https://git.rawtext.club/sloum/stagit-gemini

Doesn't look like it's actively maintained but I'm guessing it's 
considered complete.  I think there are some other options out there but I 
can't recall them off the top of my head.

On 9/2/21 1:25 AM, gemini-request@lists.orbitalfox.eu wrote:
> Send Gemini mailing list submissions to
> 	gemini@lists.orbitalfox.eu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.orbitalfox.eu/listinfo/gemini
> or, via email, send a message with subject or body 'help' to
> 	gemini-request@lists.orbitalfox.eu
> 
> You can reach the person managing the list at
> 	gemini-owner@lists.orbitalfox.eu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gemini digest..."
> 
> 
> Today's Topics:
> 
>     1. Git Forges (Jonathan McHugh)
>     2. Re: Git Forges (Rohan Kumar)
>     3. Re: [off topic] For the people still using old 16bit vintage
>        PCS - ngIRCd - IRC Server (Benjamin Cronin)
>     4. Re: [off topic] For the people still using old 16bit vintage
>        PCS - ngIRCd - IRC Server (cas@strotmann.de)
>     5. Re: [off topic] For the people still using old 16bit vintage
>        PCS - ngIRCd - IRC Server (defdefred)
>     6. Re: [off topic] For the people still using old 16bit vintage
>        PCS - ngIRCd - IRC Server (steeph)
>     7. Re: [off topic] For the people still using old 16bit vintage
>        PCS - ngIRCd - IRC Server (Philip Linde)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 01 Sep 2021 16:25:02 +0000
> From: "Jonathan McHugh" <indieterminacy@libre.brussels>
> To: "Gemini Mailing List" <gemini@lists.orbitalfox.eu>
> Subject: Git Forges
> Message-ID: <7f224c1236848667644f1c807a4b17b3@libre.brussels>
> Content-Type: text/plain; charset="utf-8"
> 
> Hello all,
> 
> I have been deliberating regarding which git forge tool most compliments 
Gemini's protocol.
> 
> Naturally, web frontends such as Cgit are a product of legacy thinking - 
to serve git in a HTTP environment.
> 
> I do agree with Anna "CyberTailor", that Cgit outputting Gemini would be 'poggers'
> => https://lists.zx2c4.com/pipermail/cgit/2021-April/004633.html
> 
> Alas, I equally am not so well positioned to adapt the HTTP coding in C
> => https://git.zx2c4.com/cgit/tree/html.c
> => https://git.zx2c4.com/cgit/tree/html.h
> 
> However, I have been looking into Gitolite further:
> => https://gitolite.com/gitolite Homepage
> => https://guix.gnu.org/manual/en/html_node/Version-Control-Services.html
 Guix OS' service configuration settings
> 
> # Gemini Advantages with regards to Gitolite
> * One could eschew READMEs and delve straight into writing GemText in repos
> * Post pushing of repos could initiate Gemini parsing or syslinking functionality
> * Output can be pushed into server content (according to parameters and ACL)
> * Gemini content can provide the interface to users repos and how to 
make the most of clustered and decentralised forges.
> 
> # Classical Advantages
> * Lean approach to managing repos via SSH(d) and more (CGit)
> * Long pedigree
> * Used at scale by Operating Systems
> * Extensible
> * Perl?
> 
> # Points of Concern
> * A site with heavy commits could test the appropriateness of 'slow internet' Gemini
> * This could obviously be mitigated with more granular servers, as well 
as federating (eventual
> consistency?)
> 
> # Points of Inquiry
> * Has anybody had success providing Gemini centric repos? - while I see 
lots of self hosters within the Gemini comm
> unity, Im not sure Ive seen people go without HTTP services
> * Do people have a positive impression of Gitolite?
> * Or are there better approaches to Git forges with respect to Gemini?
> 
> Its also worth referencing Alan's recent comments regarding his hopes of 
Archlinux stype Wikis for serving Gemini interests
> => gemini://gemi.dev/gemini-mailing-list/messages/007060.gmi Re: More Awesome Gemini
> 
> As well as Solderpunk's thoughts regarding the growth of the community 
at the start of 2021
> => gemini://gemi.dev/gemini-mailing-list/messages/004642.gmi [announce] Gemini in 2021
> 
> Any thoughts?
> 
> ====================
> Jonathan McHugh
> indieterminacy@libre.brussels
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 1 Sep 2021 10:10:37 -0700
> From: Rohan Kumar <seirdy@seirdy.one>
> To: Jonathan McHugh <indieterminacy@libre.brussels>
> Cc: Gemini Mailing List <gemini@lists.orbitalfox.eu>
> Subject: Re: Git Forges
> Message-ID: <20210901171037.x5m56mu7vmmm2n6d@rkumarlappie>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> On Wed, Sep 01, 2021 at 04:25:02PM +0000, Jonathan McHugh wrote:
>> I have been deliberating regarding which git forge tool most
>> compliments Gemini's protocol.
>> Naturally, web frontends such as Cgit are a product of legacy thinking 
- to serve git in a HTTP environment.
>> I do agree with Anna "CyberTailor", that Cgit outputting Gemini would be 'poggers'
>> => https://lists.zx2c4.com/pipermail/cgit/2021-April/004633.html
> Indeed, anybody who could pull this off would be a certified PogChamp?.
> 
> That being said, I'm not certain that this should be of high priority. I
> think a good Gemini landing page for a project is probably better. A
> Gemini export of `git log` might be worthwhile, but the rest can still
> be better seen with a git clone.
> 
> Expecting users to do a `git clone` for very large repos is unrealistic,
> of course. However, Gemini is not optimized for very large files with
> many thousands of lines. This isn't quite the "DocuWeb" niche that
> Gemini occupies.
> 
> Gemini is an *alternative* to the WWW, not a *replacement*. Bringing
> complete git frontends to Gemini doesn't seem as good as simply making
> good landing pages for projects. Sample content in such a landing page
> may include:
> 
> - the README
> - Repositories with names, links, sizes, and last-commit dates, and
> 	clone addresses.
> - Links to the issue trackers and discussion platforms (e.g. lists,
> 	chatrooms)
> - License summary (could be in README)
> - maybe a link to a paginated Gemini export of `git log`.
> 
> In other words, not a *complete* Git experience, but just what's
> appropriate for Gemini.
>