From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker
Date: Thu, 8 Feb 2018 22:01:48 -0500 [thread overview]
Message-ID: <52BC1D4E674E3C4BE804E608A5C0EB63@5ess.inri.net> (raw)
In-Reply-To: 20180208090720.GA87033@wopr
> Bugs shouldn't be prioritized by submitters anyway; they should be
> prioritized by someone else. All bugs are high priority for the person
> reporting the bug. The person fixing the bug should be in charge of
> deciding how quickly that gets done.
I agree.
> So, with Subject coming for free (it's in the email), and state/priority
> just being top-level directories,
This seems good.
> all that's left to annotate is owner
> and subsystem. Just having something that matches /^Subsystem: in any
> file is probably good enough for the latter.
That seems fine. Or, should we just have a file subsystem that is
just a one line (or one word) description of the subsystem. That
would be very easy to create, find, and manipulate.
> The former can just be
> subdirectories inside the toplevel directories.
This is probably fine, too, but do we really even need to assign bugs
to individuals? In our context, what are the benefits vs the
administrative overhead?
sl
next reply other threads:[~2018-02-09 3:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 3:01 sl [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-09 3:31 sl
2018-02-09 5:11 ` Eli Cohen
2018-02-09 3:21 sl
2018-02-09 3:15 sl
2018-02-08 2:55 sl
2018-02-08 1:34 sl
2018-02-08 2:08 ` [9front] " Lyndon Nerenberg
2018-02-08 8:37 ` Julius Schmidt
2018-02-08 9:07 ` Kurt H Maier
2018-02-08 16:54 ` Ethan Grammatikidis
2018-02-08 23:23 ` Steve Simon
2018-02-08 23:56 ` Kurt H Maier
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=52BC1D4E674E3C4BE804E608A5C0EB63@5ess.inri.net \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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.
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 NNTP newsgroup(s).