unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Steve George <steve@futurile.net>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	 Guix Devel <guix-devel@gnu.org>, <maxim.cournoyer@gmail.com>
Subject: Re: Status of ‘core-updates’
Date: Fri, 12 Apr 2024 22:21:01 +0200	[thread overview]
Message-ID: <877ch249jm.fsf@gnu.org> (raw)
In-Reply-To: <vocmum4xgvs4lefeqf3s24ar4w77bk5fuxum7dnoxqpk5ywbmq@el6mhnwz35y4> (Steve George's message of "Thu, 11 Apr 2024 11:18:12 +0100")

Hi Steve,

Steve George <steve@futurile.net> skribis:

> On 10 Apr, Ludovic Courtès wrote:

[...]

>> To be clear (but I guess it’s crystal clear to anyone who’s been around
>> long enough :-)), what we need most is someone to keep track of changes,
>> coordinate efforts, decide what goes in the branch and what’s postponed
>> or moved to a separate branch, and send periodic (weekly) status updates
>> over the course of a couple of months.  This can (and probably should)
>> be done without doing any actual hacking on the branch.
> (...)
>
> This sounds like something I can do:
>
> - track changes (in branch)
> - co-ordinate blocking issues (in bug system)
> - co-ordinate with people doing the actual work :-P
> - send (periodic) weekly emails
> - encourage shipping by minimising scope creep ;-)

Awesome, thanks for volunteering!

> Sounds like there's already agreement to revert the 'pkgconf' change and push a new branch without them which becomes 'core-updates'. Josselin on IRC I had the impression you were working on that?

I’m not sure what the situation is (I see Maxim just pushed changes on
top of current ‘core-updates’, so maybe it’s OK?).

Josselin, Maxim: could you explain what problems there are around
pkgconf and what you would recommend?

Thanks,
Ludo’.


  reply	other threads:[~2024-04-12 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 11:21 Status of ‘core-updates’ Ludovic Courtès
2024-03-30 10:55 ` Josselin Poiret
2024-04-10 14:39   ` Ludovic Courtès
2024-04-11 10:18     ` Steve George
2024-04-12 20:21       ` Ludovic Courtès [this message]
2024-04-17 17:47         ` Maxim Cournoyer
2024-04-17 22:52           ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-04-19 14:13           ` Ludovic Courtès
2024-04-19 15:22             ` Maxim Cournoyer
2024-04-22 16:20           ` Efraim Flashner
2024-04-20 11:14 ` Christopher Baines
2024-04-20 21:15   ` Maxim Cournoyer
2024-05-02  7:53   ` bug#70456: Request for merging "core-updates" branch Ludovic Courtès

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=877ch249jm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=steve@futurile.net \
    /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).