11–20 of 88 posts
> BUS FACTOR OF ZERO Bus factor is usually defined as the minimum number of team members that have to be hit by a bus to put the project in jeopardy. The Wikipedia article linked from the site defines it the same way. So a bus factor of zero would mean that the project is in jeopardy even if all the maintainers are alive.
Wow, I'm really digging that minimal css design! Really tasteful and keeps the site usable while smartly using tags for the main content area.
A very clever approach, mirroring the way FreeBSD, OpenBSD have traditionally managed their core competencies.
I am a lifelong Debian fan but it has always troubled me that I can’t check out a copy of the OS’s metadata — that which is packaged in all of the DSC files or `debian/` directories — in one place.
A monorepo containing all of your business logic is a successful tactic to getting things done. There are some great pieces of behind-the-scenes Debian infra to support this — with SVN, and later git, and internal projects like Alioth — but the first class citizen of the project is still a deb-src apt entry. Inherently a one way HTTP link from the vendor to me with only a published Changelog to track changes. A solid and stable technology for a venerable project, but git-log / git-blame it ain’t.
(Of course, the success of giant open source projects and especially Debian is often because there is no central coordination. The technical and other committees were social constructs to try to keep everyone on track. Do they still function well?)
> BUS FACTOR OF ZERO Bus factor is usually defined as the minimum number of team members that have to be hit by a bus to put the project in jeopardy. The Wikipedia article linked from the site defines it the same way. So a bus factor of zero would mean that the project is in jeopardy even if all the maintainers are alive.
> There is a rare alternative definition for the bus factor, namely: the number of people who are indispensable for the project.[2] In other words, it is the minimum number of people who are a single point of failure. If using this definition, then a high bus factor is considered a bad thing (since the loss of any person included destroys the project), and zero is considered the ideal bus factor.
Earlier quoted context omitted.
"less is more" doesn't imply trivial/easy, instead it implies that tradeoffs were carefully considered and made.
"Simplicity" does imple trivial or easy though, at least to an extent.
If I told someone I’d found a simple distro, I wouldn’t expect them to prep to compile their own kernel
> BUS FACTOR OF ZERO Bus factor is usually defined as the minimum number of team members that have to be hit by a bus to put the project in jeopardy. The Wikipedia article linked from the site defines it the same way. So a bus factor of zero would mean that the project is in jeopardy even if all the maintainers are alive.
That same Wikipedia page also states: > There is a rare alternative definition for the bus factor, namely: the number of people who are indispensable for the project.[2] In other words, it is the minimum number of people who are a single point of failure. If using this definition, then a high bus factor is considered a bad thing (since the loss of any person included destroys the project), and zero is considered the…
Earlier quoted context omitted.
That same Wikipedia page also states: > There is a rare alternative definition for the bus factor, namely: the number of people who are indispensable for the project.[2] In other words, it is the minimum number of people who are a single point of failure. If using this definition, then a high bus factor is considered a bad thing (since the loss of any person included destroys the project), and zero is considered the…
That's true, and in fact I'd prefer it if that was the mainstream definition. Given that it isn't, there may be better replacements for the headline, along the lines of "maintainable by one person".
Earlier quoted context omitted.
That same Wikipedia page also states: > There is a rare alternative definition for the bus factor, namely: the number of people who are indispensable for the project.[2] In other words, it is the minimum number of people who are a single point of failure. If using this definition, then a high bus factor is considered a bad thing (since the loss of any person included destroys the project), and zero is considered the…
That's true, and in fact I'd prefer it if that was the mainstream definition. Given that it isn't, there may be better replacements for the headline, along the lines of "maintainable by one person".
> BUS FACTOR OF ZERO Bus factor is usually defined as the minimum number of team members that have to be hit by a bus to put the project in jeopardy. The Wikipedia article linked from the site defines it the same way. So a bus factor of zero would mean that the project is in jeopardy even if all the maintainers are alive.
So, PHP, then.
I wish they didn’t just take the well established name of a principle and re use it in their distro-name. As much as I appreciate this initiative I think they should consider the importance of naming and branding. An original product should have an original name.