bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hurd Mission Statement


From: Arne Babenhauserheide
Subject: Re: Hurd Mission Statement
Date: Wed, 10 Jun 2009 21:52:58 +0200
User-agent: KMail/1.11.4 (Linux/2.6.29-hh2; KDE/4.2.4; x86_64; ; )

Am Mittwoch, 10. Juni 2009 04:02:18 schrieb olafBuddenhagen@gmx.net:
> I just realized though that it could be made a bit shorter still by
> replacing "[...] as much control over their computing environment as
> possible" with "[...] maximal control over their computing environment".
> What do the others think? Is this wording preferable?

I prefer the previous version. "maximal" sounds less clear to me - and I think 
it could more easily be misread to include DRM. 

Also "as much as possible" sounds more like normal speech - more like 
something I could actually say to someone else in a normal 8verbal) 
discussion. 

> (This is indeed where I got the idea: watching the Google tech-talk
> about poisonous people, it's the one thing that really stuck...)

I also enjoyed that one quite much :) 

Maybe a link? 
- http://www.youtube.com/watch?v=ZSFDm3UYkeE

I had one doubt though: KDE furthers personal attachment of developers to 
applications (they coded). I think that this can lead to higher motivation and 
people sticking for a longer time. It has the drawback of pseudo-locking some 
parts, though ("don't you mess with my code! It's my child!"). 

I think it works well for KDE, because KDE contains a backend library and a 
bunch of mostly independent applications. If someone pseudo-locks an 
application, someone else just writes a replacement. 

For a project with stronger interdependencies I assume that the cost of 
attachment is often greater than the benefit, though. 

Best wishes, 
Arne

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -
              http://infinite-hands.draketo.de

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]