guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Feedback, ideas, discussion: tracking patches, discussions, bugs.


From: Alex Vong
Subject: Re: Feedback, ideas, discussion: tracking patches, discussions, bugs.
Date: Fri, 02 Sep 2016 13:50:20 +0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

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 <address@hidden>. 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]