3 ms·

This is the 3rd person to resign in 10 days (Colin Watson, Russ Allbery and now Ian Jackson).

by CJefferson 12y ago

RexRollman 12y ago
and Joey Hess.
- onestone 12y ago
  And Tollef Fog Heen (partial resignation), but he and Joey were not Technical Committee members.
- cgh 12y ago
  According to his blog, he didn't resign because of systemd. In fact, he seems to quite like it: https://joeyh.name/blog/entry/a_programmable_alarm_clock_using_systemd/ https://joeyh.name/blog/entry/a_programmable_alarm_clock_usi...
danohuiginn 12y ago
That's 3 of the 8-member Technical Committee, which is the group that's ultimately responsible for all technical decisions in Debian.
- _delirium 12y ago
  That's a bit of an overstatement; it's responsible for very few technical decisions in Debian, and doesn't normally have even a theoretical ultimate-decision-maker role of regularly reviewing or steering them. Their only role is technical dispute-resolution, and they are supposed to wade into even that as minimally as possible. Most technical decisions are made by a mixture of individual package maintainers, the Debian Project Leader and release-management team, and informal consensus-building. To the extent there's an "ultimate" technical decision-maker, I would say for the majority of issues, the release team working with the project leader functions in that role.
- morsch 12y ago
  What does that really mean? Debian is a community project, not a hierarchical organisation with a managerial chain of command. The Technical Committee seems much more like an advisory board and the forum for and arbiter of the tiny number of contentious issues. They're not involved in, informed of or responsible for the vast majority of technical decisions.
qznc 12y ago
So systemd is a plot by RedHat to kill Debian and make RedHat/CentOS/Fedora the number one Linux distro? :)
- dijit 12y ago
  it would kill redhat too then. systemd was created by well intentioned people, solving a real issue but being a bit too aggressive and attempting to rewrite everything.
  - makomk 12y ago
    systemd is designed to work with Red Hat's way of doing things. For example, they've never supported upgrading to new distro releases from within the running system - you're supposed to either boot from the install CD or reboot into a special pre-boot environment - whereas that's the normal way of upgrading Debian. So systemd is designed under the assumption that major upgrades will only happen through that special preboot environment.
- sigzero 12y ago
  hand waving sure.
plus 12y ago
I would like to point out that of the 5 people being talked about here (Colin Watson, Russ Allbery, Ian Jackson, Joey Hess, and Fog Heen), only one of them has actually resigned from Debian as a whole in any real sense (Joey Hess). Colin Watson is still on the TC for the time being, Colin, Russ, and Ian are all still acting in their other roles as DDs, maintainers, what have you, and Fog Heen has only indicated that he no longer is the maintainer of systemd. Four of these five people have expressed an intention to continue being involved in Debian, just not necessarily in all of the same roles they have been.

This is the 3rd person to resign in 10 days (Colin Watson, Russ Allbery and now Ian Jackson).

RexRollman 12y ago

and Joey Hess.

onestone 12y ago
And Tollef Fog Heen (partial resignation), but he and Joey were not Technical Committee members.
cgh 12y ago
According to his blog, he didn't resign because of systemd. In fact, he seems to quite like it: https://joeyh.name/blog/entry/a_programmable_alarm_clock_using_systemd/ https://joeyh.name/blog/entry/a_programmable_alarm_clock_usi...

danohuiginn 12y ago

That's 3 of the 8-member Technical Committee, which is the group that's ultimately responsible for all technical decisions in Debian.

_delirium 12y ago
That's a bit of an overstatement; it's responsible for very few technical decisions in Debian, and doesn't normally have even a theoretical ultimate-decision-maker role of regularly reviewing or steering them. Their only role is technical dispute-resolution, and they are supposed to wade into even that as minimally as possible. Most technical decisions are made by a mixture of individual package maintainers, the Debian Project Leader and release-management team, and informal consensus-building. To the extent there's an "ultimate" technical decision-maker, I would say for the majority of issues, the release team working with the project leader functions in that role.
morsch 12y ago
What does that really mean? Debian is a community project, not a hierarchical organisation with a managerial chain of command. The Technical Committee seems much more like an advisory board and the forum for and arbiter of the tiny number of contentious issues. They're not involved in, informed of or responsible for the vast majority of technical decisions.

qznc 12y ago

So systemd is a plot by RedHat to kill Debian and make RedHat/CentOS/Fedora the number one Linux distro? :)

dijit 12y ago
it would kill redhat too then. systemd was created by well intentioned people, solving a real issue but being a bit too aggressive and attempting to rewrite everything.
- makomk 12y ago
  systemd is designed to work with Red Hat's way of doing things. For example, they've never supported upgrading to new distro releases from within the running system - you're supposed to either boot from the install CD or reboot into a special pre-boot environment - whereas that's the normal way of upgrading Debian. So systemd is designed under the assumption that major upgrades will only happen through that special preboot environment.
sigzero 12y ago
hand waving sure.

plus 12y ago

I would like to point out that of the 5 people being talked about here (Colin Watson, Russ Allbery, Ian Jackson, Joey Hess, and Fog Heen), only one of them has actually resigned from Debian as a whole in any real sense (Joey Hess). Colin Watson is still on the TC for the time being, Colin, Russ, and Ian are all still acting in their other roles as DDs, maintainers, what have you, and Fog Heen has only indicated that he no longer is the maintainer of systemd. Four of these five people have expressed an intention to continue being involved in Debian, just not necessarily in all of the same roles they have been.