Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

A day in the life of the CentOS team

Posted Mar 25, 2006 18:34 UTC (Sat) by lutchann (subscriber, #8872)
Parent article: A day in the life of the CentOS team

This kind of thing has happened before.

People get really paranoid when their computers fail in mysterious ways...

(Log in to post comments)

A day in the life of the CentOS team: the thttpd experience

Posted Mar 26, 2006 21:22 UTC (Sun) by nicku (subscriber, #777) [Link]

At least the CentOS team persisted till the "agrieved" people understood what was happening.

The repo man seems to be still in the dark.

It may just be that you are supposed to be a tiny bit more clever to be a city manager than a repo man.

Ahh, the need for disclaimers.

Posted Mar 27, 2006 15:54 UTC (Mon) by kirkengaard (subscriber, #15022) [Link]

"I am not responsible for the actions of the people using my software. I have no implicit relationship to my users except as the developer of software they freely choose to use. The mere fact that my users choose to advertise their use of my software should not be taken as evidence of any more relationship than that already expressed, and is in no way a personal statement which can, or should, be traced to me. The users of my software speak for themselves.

Should you have issues to discuss with any of the users of my software, you will need to contact them personally to address these issues. Contacting the developer over issues with a third party is futile."

Ahh, the need for disclaimers.

Posted Mar 27, 2006 16:23 UTC (Mon) by kirkengaard (subscriber, #15022) [Link]

hmm. Not strictly true.

"My responsibility for the actions of the users of my software only extends as far as it does for the manufacturer of any other tool. As hand-tool manufacturers are not responsible for the quality of, or expressions contained within, the projects built using their products, no more am I responsible for the content or structure of the projects made using my software, except in as much as the design constraints of my software limit the shape of projects made with said software."