unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: indieterminacy <indieterminacy@libre.brussels>
Cc: Pjotr Prins <pjotr.public12@thebird.nl>,
	Arun Isaac <arunisaac@systemreboot.net>,
	guix-devel@gnu.org
Subject: Re: issue tracking in git
Date: Wed, 23 Nov 2022 15:19:01 +0100	[thread overview]
Message-ID: <877czlvjmy.fsf@xelera.eu> (raw)
In-Reply-To: <fd3bd40d9ec102cc3079457e039a77e3@libre.brussels>

[-- Attachment #1: Type: text/plain, Size: 3238 bytes --]

Hello Jonathan,

nice to read you!

I saw your «L'Union Qiuy Fait La Force» presentation at Ten Years of
Guix [1] and I have to admit I still have to "digest" it, because I
still do not understand the overall architecture (see below).

indieterminacy <indieterminacy@libre.brussels> writes:

[...]

> FWIW, Ive been working on Gemini and issue trackers in parrallel to 
> Genenetwork.
>
> Arun did such a great job with a minimalist setup that I thought it more 
> proper to create a bigger ladder (given the reach of all the domains 
> which Tissue provides(.
>
> I have two main strands:
>
> Firstly, I have been combining Gemtext's terse syntax with that of the 
> Emacs-Hyperbole format, Koutliner, as well as the 
> "recursive-modelling-language" I have been developing Qiuy.
>
> https://git.sr.ht/~indieterminacy/1q20hqh_oqo_parsing_qiuynonical/
>
> As a consequence, it has grown into something different and more 
> complex. I need to trim this, especially as the results of some sprints 
> but once I refactor it it shall be a lot more solid.
>
> Secondly, I have been returning to Gemtext from the perspective of Git 
> diffs, with the idea to generate RDF perspectives one each revision per 
> file and then use RDF calls to resolve more complex queries.

RDF representations of diffs (commits?) so we can combine this knowledge
with others (represented in RDF) AFAIU is great: (open) linked data for
knowledge management

IMHO RDF is still a little bit underestimated :-D

> https://git.sr.ht/~indieterminacy/1q20twt_oq_parsing-commits_txr
>
> I shall be folding the logic of the first tool into the second 
> (carefully). I need a bit more time to do this to be fully satisfied.

what about gNife?

https://git.sr.ht/~indieterminacy/5q50jq_oq_configuring_emacs
--8<---------------cut here---------------start------------->8---

gNife, an Emacs environment for high throughput issue-tracking and
knowledge-management - utilising GemText, Koutliner and Qiuy

--8<---------------cut here---------------end--------------->8---

is it still relevant or do you plan to substitute it with the tools
listed above?

> There are some other tools floating around my forge (concerning hash 
> trees for different interpreters and rdf from the perspective of project 
> management), its mainly in TXR, Gawk and eLisp (though I will be doing 
> more with respect to Guile for these areas over time).

Looking at the Icebreaker project descriptions:

1. https://nlnet.nl/project/Icebreaker/

2. https://portal.mozz.us/gemini/icebreaker.space

I can undertand the design principles of the tools you are developing
and I'm really impressed with the completeness of this approach with
knowledge management, unfortunately I miss the overall architecture and
some important detalils that allows me to completely understand how to
use (or try to contribute to, one day) this tools: do you plan to add
some more documentation soon?

Happy hacking! Gio'

>
> Kind regards,
>
>
> -- 
> Jonathan McHugh
> indieterminacy@libre.brussels


[1] https://10years.guix.gnu.org/video/l-union-qiuy-fait-la-force/

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2022-11-23 14:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  6:29 issue tracking in git Adriano Peluso
2021-08-13 13:18 ` Ricardo Wurmus
2021-08-13 16:19   ` Giovanni Biscuolo
2021-08-14  8:30     ` Adriano Peluso
2021-08-15 10:39     ` Pjotr Prins
2021-08-15 15:28       ` Giovanni Biscuolo
2022-11-22 17:57         ` Giovanni Biscuolo
2022-11-23  4:35           ` Pjotr Prins
2022-11-23 10:29             ` Giovanni Biscuolo
2022-11-23 10:59               ` indieterminacy
2022-11-23 14:19                 ` Giovanni Biscuolo [this message]
2022-11-23 16:53                   ` indieterminacy
2022-11-23 13:18               ` Pjotr Prins
2022-11-23 14:58                 ` Giovanni Biscuolo
2022-11-25 13:45                 ` zimoun
2022-11-25 22:03                   ` Arun Isaac
2022-11-26  9:51                     ` zimoun
2022-11-24 22:01               ` Arun Isaac
2021-08-14  8:29   ` Adriano Peluso
2021-08-13 14:39 ` raingloom
2021-08-16  4:39   ` Adriano Peluso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877czlvjmy.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=indieterminacy@libre.brussels \
    --cc=pjotr.public12@thebird.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).