unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Giovanni Biscuolo <g@xelera.eu>
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 14:18:51 +0100	[thread overview]
Message-ID: <20221123131851.shpa6sm3w7igkixe@thebird.nl> (raw)
In-Reply-To: <87cz9eufoj.fsf@xelera.eu>

On Wed, Nov 23, 2022 at 11:29:48AM +0100, Giovanni Biscuolo wrote:
> Homepage is https://tissue.systemreboot.net/
> 
> Wow!  Very interesting project, it deserves more visibility! (why did I
> miss its existance?!? :-O )

Ah well. We have just been using it and building it up over the last
year :). We wanted to get away from github issue trackers and that was
rather successful. All you need is a git repo and a guix package.

We also have ci and cd based on our own system containers in Guix.

=> https://ci.genenetwork.org/

It would be good to write a Guix blog about all this.

> Please Arun is there a devel mailing list dedicated to tissue so we can
> discuss details of the project?

Sounds like an idea. Though in the spirit of tissue we might as well
set up a repo.

> I'm not a Guile developer but I would like to help with testing and (the
> lack of) documentation, if I can.
> 
> I'd also like to understand and possibly discuss the overall
> architecture design of tissue, in particular compared to git-issue
> internals [1]

I did not know of that project, but it looks similar in concept. With
gemini support you get some other interesting features. And then Arun
has added powerful search. Also, when you see Jonathan's E-mail, we
are not done building on this.

> Last but not least: what about to have tissue packaged [2] in Guix? :-D

It is about time - and a package and system definition exists in a
channel.

Pj.


  parent reply	other threads:[~2022-11-23 13:19 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
2022-11-23 16:53                   ` indieterminacy
2022-11-23 13:18               ` Pjotr Prins [this message]
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=20221123131851.shpa6sm3w7igkixe@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=arunisaac@systemreboot.net \
    --cc=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    /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).