unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-user@gnu.org
Subject: Re: rfc: next guile 1.8.x release
Date: Wed, 02 Mar 2022 19:11:35 -0500	[thread overview]
Message-ID: <87ilsvao94.fsf@gnuvola.org> (raw)
In-Reply-To: <87pn08bxz4.fsf@web.de> (Arne Babenhauserheide's message of "Tue,  09 Mar 2021 08:14:07 +0100")

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


() "Dr. Arne Babenhauserheide" <arne_bab@web.de>
() Tue, 09 Mar 2021 08:14:07 +0100

   How about taking this at literal value and creating an
   ugg8-repository: Unofficial GNU Guile 1.8? That carries with
   it the connotations of keeping to plain, strong values
   without fundamental changes, and picking up from the 8, so it
   isn’t limited to the minor number behind 1.8.x (with x > 8).

Please see: <https://gitlab.com/restio-al-restio/huge>.  I think
sooner or later the Official Guile maintainers will come around
to see that such a repo (whether on Savannah or Gitlab or ...)
represents a good incubation ground for future hackers, where
the old curmudgeons (i.e., Yours Truly) can mix w/ the new blood
and in the process hone their chops to be official maintainers
in their own right.

If, OTOH, this never happens, well, let that be a lesson for the
idealists and their efforts at pulling down The Wall.  :-D

Since HUGE hopes for re-merge Some Day, i will manage it wearing
my GNU maintainer hat, w/ additional TTN-specific requirements:

- Use TTN-style commit log entries (see, e.g., GNU RCS).
  (However, no need to actually maintain ChangeLog files.)

- "Don't break userland."

- Focus on documentation / bug fixes / implementation quality.

Who knows, maybe Good Things can be forward- and backward- and
sideways-ported to/from HUGE in the years to come.  May all of
Guile-dom benefit from the participation of HUGE hackers!

In order to not corrupt the precious bittily fluids of the HUGE
repo itself (which, as said earlier, is hoped to be a candidate
for re-merge Some Day by more enlightened Guile maintainers),
i'll probably create another repo "HUGE-META" which will have
HUGE as a submodule, where non-GNU-ish stuff can happen.  Like
everything, depends on interest and available energy, i suppose.
(Or maybe someone else can do that.)

Lastly, i get the vibe that Source Hut is all the rage, but my
Day Job doesn't have health insurance, so i'm scrimping by on
the gratis substrates for now.  Let's see how that goes...

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)               ; (2022) Software Libero
   (pcase (context query)               ;       = Dissenso Etico
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


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

  reply	other threads:[~2022-03-03  0:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 21:54 rfc: next guile 1.8.x release Thien-Thi Nguyen
2021-01-11 14:51 ` Mike Gran
2021-01-12 10:55   ` Massimiliano Gubinelli
2021-01-16 22:55     ` Thien-Thi Nguyen
2021-01-16 22:48   ` Thien-Thi Nguyen
2021-01-29 21:35 ` Ludovic Courtès
2021-01-29 23:46   ` Dr. Arne Babenhauserheide
2021-01-30 12:31     ` Ricardo Wurmus
2021-01-30 14:49       ` Dr. Arne Babenhauserheide
2021-01-31 17:35       ` Massimiliano Gubinelli
2021-02-01 21:49         ` Ludovic Courtès
2021-02-07  6:59         ` John Cowan
2021-03-08 20:36 ` Andy Wingo
2021-03-09  7:14   ` Dr. Arne Babenhauserheide
2022-03-03  0:11     ` Thien-Thi Nguyen [this message]
2022-03-14 12:14       ` Thien-Thi Nguyen

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87ilsvao94.fsf@gnuvola.org \
    --to=ttn@gnuvola.org \
    --cc=guile-user@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.
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).