From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org, ng0 <ng0@n0.is>
Subject: Re: Feedback, ideas, discussion: tracking patches, discussions, bugs.
Date: Sat, 3 Sep 2016 18:44:41 +0200 [thread overview]
Message-ID: <20160903164441.GA1821@thebird.nl> (raw)
In-Reply-To: <878tvafu6g.fsf@gmail.com>
Today was pretty much an E-mail overload on the ML. In itself amazing
:)
Pj.
On Fri, Sep 02, 2016 at 06:54:47PM +0800, Alex Vong wrote:
> ng0 <ng0@n0.is> writes:
>
> > Alex Vong <alexvong1995@gmail.com> writes:
> >
> >> Hi,
> >>
> >>
> >> I think I share the same concern as you do, currently the mailing list
> >> is too crowded and it is difficult to find the relevant bit. Below are
> >> my opinions on it:
> >>
> >>
> >> While it may not be as user-friendly as web-based bug tracker these
> >> days, I think the Debian bug tracking system is still better than our
> >> current approach. In Debian, everything is a package. It is like a
> >> language primitive in the bug tracker system.
> >>
> >>
> >> There is an "intended to package" (ITP) package. When you want to
> >> package something, you simply file a bug against the ITP package. This
> >> has the advantage that, the relevant information stays within the bug
> >> report. So everyone can see the whole process, starting from someone
> >> intending to package, to a fully reviewed package, all in a single bug
> >> report. It is like having "lexical scoping".
> >>
> >>
> >> And the most important argument comes: We already have it now[0]! So,
> >> this could be a working intermediate solution. Currently, we are not
> >> using debbugs to its full potential.
> >>
> >>
> >> My suggestion will be to create a new package called "guix-package", and
> >> all people hoping to introduce a new package to guix should file a bug
> >> report to <bug-guix-package@gnu.org>. If you are new to this type of bug
> >> tracking system, no problem! There is (some) documentation on it[1][2]
> >> and here is my own little example[3].
> >>
> >>
> >> Hope this make sence!
> >>
> >>
> >> Cheers,
> >> Alex
> >>
> >>
> >> [0]: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix
> >> [1]: https://debbugs.gnu.org/Reporting.html
> >> [2]: https://debbugs.gnu.org/server-control.html
> >> [3]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24352
> >
> > Interesting, this is close to the Gentoo system: Everything is a bug.
> > Which means, every update, every bug, every new package, every "our
> > infrastructure server XYZ broke" request, etc.
> >
> > In a recent bug report through debbugs at Guix side I was not able to
> > figure out how to close the bug at all. I think if this isn't covered
> > good enough in upstream docs, we should 1. point it out at our side and
> > then 2. improve upstream documentation as the email sent when you open
> > the bug should state how you close the bug again..
> > I'll report this bug upstream and try to fix it if it's hasn't caught
> > their attention and it still exists - maybe gnu.org version just happens
> > to be outdated.
> >
> Indeed, documentation on the BTS is quite lacking. Looking at the bottom
> of page, the last page is last modified on 31 Dec 2009, which isn't
> update for quite a while. Maybe we can have a wiki page on libreplanet
> like this one[0]. Anyone know how to add a new page on libreplanet wiki?
> (The earlier discussion regarding icecat and tor browser could also have
> its own page.)
>
> To close a bug, sending email to <BUGNUMBER-done@debbugs.gnu.org>
> should work in theory, but I haven't try it yet.
>
> > I think this could really work out.. It would also establish some kind
> > of work flow, where currently we have one, but you are rather free in
> > how it all works out.
> > This would also help to avoid parallel work. Someone wanted to package
> > pybitmessage while I already had pybitmessage packaged, things like
> > that.
> >
> Please Feel free to discuss. Here is only my initial thought (heavily
> borrowed from debian):
> 1. File bug report to <bug-guix-package@debbugs.org> with the title
> being "PACKAGENAME@VERSION".(It can be changed later via bug control.)
> The content of the bug report should mention the license of the
> software.
> 2. Patch reviewing and responding are done by sending email to
> <BUGNUMBER@debbugs.gnu.org>.
> 3. Bug report is closed when patch is pushed (we could even automate
> this one).
>
> Note that this does not account for patches which does not bump the
> version, maybe we should keep the bug report of version N opened and
> only close it when version N+1 is pushed. What do you and the others
> think?
>
> > Appending to my previous email, as John did not provide a link this is
> > the Aegis which was meant: http://aegis.sourceforge.net/
>
> [0]: https://wiki.debian.org/HowtoUseBTS
>
--
next prev parent reply other threads:[~2016-09-03 16:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 10:46 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-13 11:11 ` David Craven
2016-08-13 11:23 ` ng0
2016-08-14 5:41 ` Pjotr Prins
2016-08-14 9:14 ` ng0
2016-08-15 1:39 ` David Craven
2016-08-15 4:55 ` Pjotr Prins
2016-08-15 9:11 ` David Craven
2016-08-16 13:17 ` Ricardo Wurmus
2016-08-16 13:29 ` Pjotr Prins
2016-08-15 11:53 ` Hartmut Goebel
2016-08-15 13:30 ` Danny Milosavljevic
2016-08-15 15:18 ` Alex Vong
2016-08-16 7:20 ` Hartmut Goebel
2016-08-16 14:06 ` Alex Vong
2016-08-18 11:47 ` Hartmut Goebel
2016-09-01 6:32 ` ng0
2016-09-01 11:19 ` ng0
2016-09-02 0:27 ` John Darrington
2016-09-02 0:58 ` ng0
2016-09-02 5:50 ` Alex Vong
2016-09-02 8:21 ` ng0
2016-09-02 10:54 ` Alex Vong
2016-09-03 16:44 ` Pjotr Prins [this message]
2016-09-03 16:55 ` David Craven
2016-09-03 19:19 ` Brendan Tildesley
2016-09-03 19:53 ` David Craven
2016-09-03 20:42 ` Efraim Flashner
2016-09-02 12:39 ` Tracking package submissions with Debbugs Ludovic Courtès
2016-09-02 14:29 ` Ricardo Wurmus
2016-09-03 0:35 ` Alex Vong
2016-09-03 13:47 ` Ludovic Courtès
2016-09-04 2:21 ` Alex Vong
2016-09-03 21:00 ` Efraim Flashner
2016-09-04 2:37 ` Alex Vong
2016-09-04 7:05 ` Andreas Enge
2016-09-04 16:57 ` ng0
2016-09-04 17:00 ` ng0
2016-09-04 17:09 ` David Craven
2016-09-05 12:52 ` Alex Kost
2016-09-05 20:22 ` Ludovic Courtès
2016-09-05 20:39 ` David Craven
2016-09-05 23:12 ` ng0
2016-09-07 20:38 ` Ludovic Courtès
2016-09-05 23:17 ` ng0
2016-09-05 23:54 ` David Craven
2016-09-06 0:01 ` Ben Woodcroft
2016-09-06 7:57 ` ng0
2016-09-06 11:26 ` David Craven
2016-09-06 1:24 ` Alex Vong
-- strict thread matches above, loose matches on Subject: below --
2016-08-16 8:37 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-16 9:01 ` David Craven
2016-08-13 10:18 ng0
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=20160903164441.GA1821@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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).