[coreboot] [RFC] What to do with the issue/bug tracker and bugs?

[Julius Werner]

Is there an easy way to sign up for notifications on new issues in certain
categories? I'm happy to sign up and be responsive for areas that I'm
familiar with, but I don't really have time to just keep up with the whole
thing.

Also, If we wanted to allow something like that we'd likely need much finer
categories. Right now there's only "board support"... we'd probably need a
separate category for every architecture, SoC and board so that people
could really sign up for their specific areas of expertise.

An easier alternative might be to add some more names to the MAINTAINERS
file and then tell people to find and CC the right people from there
whenever they file a bug.

On Wed, Apr 26, 2017 at 12:12 AM, Paul Menzel via coreboot <
coreboot at coreboot.org> wrote:

> Dear coreboot folks,
>
>
> In the past an issue/bug tracker was requested, and Lynxis set it up
> [1] and maintains it.
>
> Currently, there are 109 issue, where 78 of them are open.
>
> In the last coreboot community meeting, it was discussed, if that needs
> to and could be improved, and it was decided to start a discussion on
> the mailing list.
>
> The main question to the developers is, if a issue/bug tracker is still
> wanted, and, if yes, what prevents you from using it more? Unawareness?
> Bad usability?
>
> One issue already pointed out is, that the issue/bug tracker should be
> better integrated with Gerrit [2].
>
> The next question is, how open bugs could be fixed? One proposal is,
> that the “subsystem” maintainers should be responsible for that, at
> least that the report is looked at and responded to.
>
>
> Thanks,
>
> Paul
>
>
> [1] https://ticket.coreboot.org/issues/
> [2] http://review.coreboot.org/
> --
> coreboot mailing list: coreboot at coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20170426/4dcf0e86/attachment.html>