all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: Leo Famulari <leo@famulari.name>,
	 Christopher Baines <mail@cbaines.net>,  Andy Tai <atai@atai.org>,
	 guix-devel@gnu.org
Subject: Re: core-update scope
Date: Sun, 15 Dec 2024 12:50:03 +0900	[thread overview]
Message-ID: <87frmpzjtg.fsf@gmail.com> (raw)
In-Reply-To: <Zt2nFXw8lacA36iT@jurong> (Andreas Enge's message of "Sun, 8 Sep 2024 15:31:01 +0200")

Hello,

Andreas Enge <andreas@enge.fr> writes:

> Hello Leo,
>
> Am Sat, Sep 07, 2024 at 01:47:03PM -0400 schrieb Leo Famulari:
>> I agree, we don't have to have a team for this. I'm not sure anyone else
>> cares about the "media" packages as a whole. But if there is interest,
>> that's good too.
>
> as an outsider, I would just like to chime in that I liked your idea of
> creating a "media software" team, Leo. It is definitely an area that is
> important for many users and in need of qualified input. Notice that a
> "team" need not have more than one member :)
>
> But as I am not qualified in the matter, I will not push for it,
> it is of course up to you to create a new team or not.

I'd also welcome a media-team, to ease the flow of keepings things like
gstreamer and ffmpeg regularly updated.  Its team and the desktop
(gnome, kde) teams would need to keep in sync to avoid duplicated
efforts though, as updating GNOME often means updating the gstreamer
stack.

-- 
Thanks,
Maxim


      reply	other threads:[~2024-12-15  3:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 21:32 core-update scope Andy Tai
2024-09-02 17:37 ` Leo Famulari
2024-09-04  9:01 ` Christopher Baines
2024-09-07 17:47   ` Leo Famulari
2024-09-08 13:31     ` Andreas Enge
2024-12-15  3:50       ` Maxim Cournoyer [this message]

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

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

  git send-email \
    --in-reply-to=87frmpzjtg.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=andreas@enge.fr \
    --cc=atai@atai.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=mail@cbaines.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.