Slackware 10.1 Beta And Pat's Health
phreakuencies writes "The ChangeLog in slackware-current got a distiguished update today on Jan 22: Patrick Volkerding updated us on his health condition stating he is not back in perfect shape but getting more medical tests and results. The initial phrase on the ChangeLog: 'I'm going to call this Slackware 10.1 beta 1, because we're at a state where things are relatively stable.' Read up here"
I think this "event" reflects the way in which most open source projects are lead.
Certainly you won't see in a commercial product news about the health of the developers as items in a ChangeLog.
However, in open source, the freedom to fork is often given as an excuse for allowing one person to be the benevolent dictator of the whole thing. On good merits, it seems, because many argue that if it weren't for that, things would never get done and stuff. But this "dictator" stuff gives the project owner a lot of power and a lot of discretion, and someone said once "power corrupts".
Is it ok to notify the community about how the leader feels and where he's headed from a medical perspective? Yes. But, is the official changelog of the distribution the right place to do it? Would such a thing be done in a commercial product?
This struck me... I use Slack on two *really slow* PCs (233 Mhz) and it makes them perform just fine. And yet I've never paid Pat a dime. I think it's time I started a subscription. What about you?
I sure hope the guy doesn't die soon, Slackware has been the only Linux distribution I ever really liked. Anyway, Pat's ChangeLog gave me an idea, what if most developers kept mental health ChangeLogs? Mhlogs!
Well, that's the idea behind OS - people willingly giving away the product of their mind for others to benefit from. The idea is to expand the common pool of ideas and tools and to do something you enjoy, with the bonus of giving something back to the community.
Compare programmers to artists. You've got your traditional artist (software company) selling his paintings (products) retaining all rights. On the other side you've got the graffiti artists (OS programmers) painting murals on the city walls - everyone is free to enjoy their work. Of course, anyone can sell photos of the work, so it's more along the lines of BSD than Linux, but nobody is obliged to pay to view the original work...
Jw
This guy got finally reasonnable. Instead of trying to take care of by himself, he finally went to a doctor, and, best part : Stayed with the same doctor
Of cours, any doctor usually start thinking of the most plausible and statistically significant cause of disease. Usually patient should come back and only if no improvement has been seen, then only the doctors start considering more unlikely or rarer diseases.
But if the patient is unhappy with the first diagnosis of the first doctor and moves to another doctor, the new will start over again from the very beginning.
It's OK to try change doctors when you're not very sick and when you try to find a nice doctor who you like to have him as the one who you usually refer first to.
BUT when someone health is compromised HE SHOULDN'T keep switching doctors. He should try to stay with one (and eventually have him refer to other colleauges if he need more help).
Because each time a patient siwtch doctors, he loose time because of this start-over-again.
And I'm not speaking about the economical problems : doctor switching reases the health cost a lot because a lot of things (lab exams, etc...) are done twice or thrice.
It's a big problem we have here in Switzerland.
There's some work to avoid this kind of redundancy : One exemple of such project in Geneva (CH) is e-toile (Sorry website in french, you have some english info here).
We hope that by building secured networks, doctors could share some information and avoid repeating the same stuffs all over again.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
In my prior work we were doing customisation work on our companys own product. Most customisation was done my team of 1 Programmer, (1/3)Project Manager and (1/2)Grapician. Sometimes Pm and graphician being the same person. Programmer was generally doing one project at time. Project manager was managing 2 or 3 and graphician was doing mostly one at time, but was resereved only for hald of the time for a project. Typical project lasted 2 months. Getting specification and connectons from client has half the work.
Employees got sick once in a while like people do.
There was allways the trouble to explain customers.
The usual question was. Why have you not replaced him(her). Our project is prime importance.
a) 25 some will most likely be sick 2 days, geting new programmer to understand takes longer.
b) Puting people in middle of half written code that does not do what is needed, usually means large chunks being rewritten, when original author knows what is missing and only adds that.
c) a lot of specification was usually on the air, and doing the code to interface was the minor part.
d) We sure did not have spare developers.
e) Yes, they all are.
I think Debian and Gentoo are the obvious alternatives. Slackware people tend to compile a lot of their own stuff anyway since the default distribution is a bit light on the packages (no OOo for example), and there's a very nice port of emerge to slackware. Debian is quite slack-like but may be too political for many slackers.
I am trolling
I've been using Slackware since it diverged from SLS so many years ago and I'd have to say that you are 100% correct about Debian... nice idea but if I wanted politics, I'd tune in to CSPAN. Their rabid use of GNU/everything has utterly and totally turned me off of the distribution. Gentoo? I don't think so. I think that I'd move to something like Vector Linux which is Slackware based and has a more sensible set of installer defaults (I use my own tagsets though already). The only real reason I'm not using Vector currently is because the ASCII art penguin has to go for starters but more importantly, Slackware is still the 'root' of it and why go with a little offshoot that doesn't change much at the current time?
I have thought of that for one machine of mine (the firewall/proxy), but there is always that one problem: Linux simply supports far more hardware than any BSD variant. Linux hardware support used to be a major issue, now it is almost a given.
/. suggested a couple of years back that Linux would one day be mainstream and 'Uncool', and that people would migrate to BSD. I thought they were joking . . .
Funny, someone here on
Mielipiteet omiani - Opinions personal, facts suspect.
I doubt it. The US spends far more per capita on health care than any other country. Almost 3x as much per person as the UK. See here.
Thanks for that - wish I had Mod points. That's been my contention for some time. All this BS about privatising health care just introduces more companies that want to leach off more profit.
When the (Right wing corporatist) Australian Government gave a $500 rebate for people with health care to encourage the take up of private health cover (admitedly rather well implemented over here but that's not what I'm talking about) the health funds all raised their prices by - wow, $500! What a surprise...
And the oink oink noises from the trough became deafening.
By definition a public owned system will be more "efficient" than private because it is not obliged to take money out of the system for the shareholders - unless you genuinely believe that all of the shareholders will put all of their profits back into your country - duh!!! It may not make a profit because the government may choose to distribute the money in a particular way e.g. running a privatised steel industry at a loss to subsidise the manufacturing sector.
What are you listening to? (http://megamanic.blogetery.com/)