unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: iyzsong@envs.net,  Hilton Chain <hako@ultrarare.space>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: (Lx)Qt team in Guix
Date: Thu, 07 Mar 2024 20:46:12 -0500	[thread overview]
Message-ID: <87h6hhh4wr.fsf@gmail.com> (raw)
In-Reply-To: <ZemQ-ChBfTaP7AP7@jurong> (Andreas Enge's message of "Thu, 7 Mar 2024 11:03:36 +0100")

Hi Andreas,

+guix-devel

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> I am reaching out since I am receiving in cc patches for Qt, and realise
> that I do not feel quite confident about them; I added myself because I
> feel able to work on C code, but I think you are much more involved and
> competent for Qt than I and also sufficiently numerous, so I could safely
> remove myself.
>
> But when trying to do so, I realised that the situation is a bit convoluted:
> In addition to a qt team, there is an lxqt team, and I was actually part
> only of the latter; but the two overlap in claiming responsibility for
> gnu/packages/qt.scm. Moreover Maxim is part of qt, and 宋文武 and I are
> part of lxqt.

I think the reason qt.scm is part of the lxqt team is historical; lxqt-team
predates qt-team.  We should probably just remove qt.scm from
lxqt-team's scope.  What do you think?

> So I would suggest to sort this out somehow; maybe merge lxqt into qt?

I'd keep both team separated; I'm interested in maintaining qt upgrades
but not much lxqt.

-- 
Thanks,
Maxim


       reply	other threads:[~2024-03-08  1:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ZemQ-ChBfTaP7AP7@jurong>
2024-03-08  1:46 ` Maxim Cournoyer [this message]
2024-03-08 11:05   ` (Lx)Qt team in Guix Andreas Enge
2024-03-09 14:45     ` Hilton Chain
2024-03-08 12:08   ` 宋文武
2024-03-09 18:02     ` Maxim Cournoyer

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=87h6hhh4wr.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=hako@ultrarare.space \
    --cc=iyzsong@envs.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).