7
Debian project leader elections 2023
source link: https://lwn.net/Articles/926209/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Debian project leader elections 2023
The 2023 election for the Debian project leader looks to be a relatively
unexciting affair: incumbent leader Jonathan Carter is running unopposed
for a fourth term. His platform lays
out his hopes and plans for that term.
(Log in to post comments)
From: | Kurt Roeckx - Debian Project Secretary <secretary-AT-debian.org> | |
To: | debian-devel-announce-AT-lists.debian.org, debian-vote-AT-lists.debian.org | |
Subject: | Debian Project Leader Elections 2022: Candidates | |
Date: | Wed, 15 Mar 2023 00:46:36 +0100 | |
Message-ID: | <[email protected]> | |
Archive-link: | Article |
We're now into the campaigning period. We have 1 candidate this year: - Jonathan Carter The platform is available at: https://www.debian.org/vote/2023/platforms/ Kurt Roeckx Debian Project Secretary
(Log in to post comments)
Debian project leader elections 2023
Posted Mar 15, 2023 18:16 UTC (Wed) by nickodell (subscriber, #125165) [Link]
>But I think we can, and should do more. I would like us to collectively identify the top problems in Debian that give users a hard time, find potential solutions for them, and if it seems plausible, make it a release goal. I'll list two examples from my own personal suffering below, and they're examples, so this DPL vote isn't a vote to override a maintainer in any way, but I'm listing them to give you an idea of what I'm talking about.
>
>On desktop systems, automatically run fsck when a filesystem encounters a problem. On a very regular basis, a contact sends me an email or Signal message containing a photo of their laptop/desktop/server with a busybox prompt with a message above saying something like "filesystem check failed for /dev/sda2". And then I get to be the hero who tells them "Type 'fsck -y /dev/sda2', then reboot!". I can understand that on some servers, some might want to be conservative and intervene manually, but on a desktop system the answer to the user is almost always going to be to run the filesystem check, so why not just do it automatically? The incident can still be reported to the user in other ways after the filesystem is fixed.
>
>On desktop systems, automatically run fsck when a filesystem encounters a problem. On a very regular basis, a contact sends me an email or Signal message containing a photo of their laptop/desktop/server with a busybox prompt with a message above saying something like "filesystem check failed for /dev/sda2". And then I get to be the hero who tells them "Type 'fsck -y /dev/sda2', then reboot!". I can understand that on some servers, some might want to be conservative and intervene manually, but on a desktop system the answer to the user is almost always going to be to run the filesystem check, so why not just do it automatically? The incident can still be reported to the user in other ways after the filesystem is fixed.
I'm glad to see this in jcc's platform. He may not be able to directly do these kinds of things, but being an internal advocate for it is still valuable.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK