[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Debbugs handling of packages
From: |
Ludovic Courtès |
Subject: |
Debbugs handling of packages |
Date: |
Wed, 08 Feb 2017 14:46:35 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello Guix!
Ricardo Wurmus <address@hidden> 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
> address@hidden *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’.
- Guix package incubator (later a channel), Pjotr Prins, 2017/02/06
- Re: Guix package incubator (later a channel), Ricardo Wurmus, 2017/02/07
- Re: Guix package incubator (later a channel), ng0, 2017/02/07
- Re: Guix package incubator (later a channel), Pjotr Prins, 2017/02/08
- Debbugs handling of packages,
Ludovic Courtès <=
- Debbugs handling of Guix patches, Ludovic Courtès, 2017/02/09
- Re: Debbugs handling of Guix patches, Glenn Morris, 2017/02/09
- Re: Debbugs handling of Guix patches, Ludovic Courtès, 2017/02/10
- Re: Debbugs handling of Guix patches, Glenn Morris, 2017/02/10
- Re: Debbugs handling of Guix patches, Ludovic Courtès, 2017/02/10
- Re: Debbugs handling of Guix patches, Christopher Allan Webber, 2017/02/10
- New guix-patches mailing list not showing up on Mailman, Ludovic Courtès, 2017/02/11