Communication about shim/SB development is not working well

[Steve Langasek]

On Tue, Apr 20, 2021 at 07:08:40PM +0100, Steve McIntyre wrote:
> I think it's way past time we had a discussion about how we're
> communicating around shim/SB development and maintenance. Most of the
> recent discussion I've seen has been in a closed environment (keybase)
> and I have a strong conviction that it's not working well enough for
> us. *Please* don't take this as me pointing fingers of blame at
> anybody here, I'm just trying to make things better for us.

> Right now, I can see three related issues that are causing real
> problems for many of us. There are probably more!

> 1. Keybase is *awful* for keeping track of discussions

+100

I am on the keybase channels but make no effort to keep up with content
there because the UX is so bad.  I'm only there so that if someone draws my
attention to something that was said there, I have a way to look it up.

> 1. Open mailing list(s) with public archives

>    I've already set up an EFI mailing list [1] and linked to it a few
>    times. Yes, I'm hosting that list. I'm not precious about that,
>    however - if people would rather move it somewhere else, or use a
>    discourse instance, or *something* then that's OK. But IMHO it has
>    to be something with *persistence* and *threading* so that we have
>    a chance of tracking detailed conversation today, and
>    yesterday. And also from three weeks ago when some maintainers were
>    on vacation, or from six months ago to allow new subscribers to
>    learn things. You know what I mean.

>    We can encourage *all* shim maintainers to join up on the list and
>    see what's going on. We should probably have an -announce list for
>    new shim versions, etc. Maybe a -test list for testing reports?
>    Sorry, maybe getting carried away. :-)

>    I'm *not* really thinking about these being list(s) for end-users,
>    but more a place to help us work together better and make sure that
>    SB in Linux is a good experience for those users. We *definitely*
>    should be sharing our problem reports here, for example.

>    [1] https://lists.einval.com/cgi-bin/mailman/listinfo/efi

Thanks, subscribed!

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                   https://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.einval.com/pipermail/efi/attachments/20210420/e3bdddee/attachment.sig>