all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Debbugs handling of packages
Date: Wed, 08 Feb 2017 14:46:35 +0100	[thread overview]
Message-ID: <87r338pzgk.fsf_-_@gnu.org> (raw)
In-Reply-To: <87shnplrjh.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 07 Feb 2017 20:38:58 +0100")

Hello Guix!

Ricardo Wurmus <rekado@elephly.net> skribis:

> I see two possible outcomes of establishing an additional “incubator”
> repository: it might fragment our review community as some people will
> try to upstream incubator patches and others handle mailing list
> patches; another outcome is that the incubator never gets accepted by
> reviewers and mentors because it is more work, leading to growing
> parallel infrastructure and second-class code.  Neither of these
> outcomes is desirable in my opinion.

Yeah, I share the same concerns.  The example of external repos that you
gave seems to confirm this.

But like Pjotr said, if people want to have their own package set
somewhere else, that’s also fine.  We’ll just work hard to make sure
there’s no real incentive to do that.  :-)

> Our workflow involving the mailing list is far from perfect.  We had
> further discussions over post-FOSDEM dinner and drinks and there seemed
> to be consensus among the people present (including long time
> contributors, reviewers, and successful mentors) that it would be a
> great improvement to keep track of package contributions in a separate
> Debbugs instance (e.g. one “bug” per package submission).  It gives us a
> way to track the state of things more easily, it accomodates people who
> prefer to use a web browser, it permits us to continue to use email, and
> it doesn’t force yet another account onto submitters.
>
> Admittedly, the web interface that Debbugs comes with is kinda bland and
> hard to use, so a second step would be to develop a better UI frontend
> to Debbugs that would be closer to what people expect from an issue
> tracker.
>
> This was discussed before at
> <https://lists.gnu.org/archive/html/guix-devel/2016-09/msg00140.html>
> and we could request a separate Debbugs instance for
> “guix-packages@gnu.org” *right now* if we wanted to.
>
> What do other people think about this?

I think we should just go ahead and setup that Debbugs instance like I
said I’d do back in September.  It can only be an improvement over what
we have now anyway.

Objections?

Thanks,
Ludo’.

  parent reply	other threads:[~2017-02-08 13:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 19:09 Guix package incubator (later a channel) Pjotr Prins
2017-02-06 21:44 ` ng0
2017-02-07  5:42   ` Pjotr Prins
2017-02-07 18:59     ` Christopher Allan Webber
2017-02-07 20:37       ` ng0
2017-02-07 19:38 ` Ricardo Wurmus
2017-02-07 20:59   ` ng0
2017-02-08  6:58   ` Pjotr Prins
2017-02-08 13:46   ` Ludovic Courtès [this message]
2017-02-08 14:29     ` Debbugs handling of packages Ricardo Wurmus
2017-02-08 19:15       ` Andreas Enge
2017-02-12 11:05         ` ng0
2017-02-09 23:12       ` Debbugs handling of Guix patches Ludovic Courtès
2017-02-10  0:40         ` Glenn Morris
2017-02-10 12:41           ` Ludovic Courtès
2017-02-10 17:41             ` Glenn Morris
2017-02-10 22:46               ` Ludovic Courtès
2017-02-11  1:43                 ` Christopher Allan Webber
2017-02-11 14:37                   ` New guix-patches mailing list not showing up on Mailman Ludovic Courtès
2017-02-11 22:11                     ` [Savannah-hackers-public] " Assaf Gordon
2017-02-11 22:51                     ` Karl Berry
2017-02-12 13:54                       ` Ludovic Courtès
2017-02-12  1:51                 ` Debbugs handling of Guix patches Glenn Morris
2017-02-12 14:01                   ` Ludovic Courtès
2017-02-26  8:42                     ` Pjotr Prins
2017-02-12 14:11           ` New guix-patches mailing list hooked to Debbugs! 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

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

  git send-email \
    --in-reply-to=87r338pzgk.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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.