What’s our shared technical vision? What’s our strategy?
In a way it’s not as urgent as setting up a proper governance model, but
OTOH, it’s a key motivating factor for the geeks and activists in us.
Lack of technical leadership means that nothing happened in terms of
defining a direction since the GNU Manifesto. Maybe we cannot yet
positively define a new vision, but maybe we can have a shared view on
where GNU fits in the whole free software movement.
For example, I recently read this article:
It’s part of a longstanding push towards non-copyleft software and away
from the GNU toolchain, but it also raises technical questions relevant
to GNU packages: on writing memory-safe programs (relevant to GCC and
notably its Rust frontend, to Guile), on assembling OSes/distros
(toolchain, Guix), on bootstrapping (Mes), on increasing OS
fault-tolerance and security (Hurd), etc.
Perhaps we can’t define yet a shared vision for GNU Assembly packages,
but we could, in this example, work out a shared response. Plus, that
would be good use of our brand new gnu.tools blog.