On 03/24/2014 06:50 PM, Stephen John Smoogen wrote:



On 24 March 2014 12:18, Lennart Poettering <mzerqung@0pointer.de> wrote:

 
It's a pity though that nobody in Fedora is actively working on getting
rid of legacy cruft. I really wished we had some people who oversee
deprecating things more proactively, figure out how to deprecate things,
write stub code to provide smooth transitions, write release notes and
so on. Being at the bleeding edge of things also means deciding that
some things really should go, from time to time... Besides deprecating
old cruft like libwrap, this would also mean removing all the old crap
from comps "standard" that we still install by default (894110)...


Old cruft is in the OS because for some set of people it is useful, and it is very hard to design around stuff people think should be there because it was there before. The only way to get around that is to build something completely new with a different 'brand' which does not have expectations from people already there. I think you would have a better chance starting from a ground zero and putting new wine in a new winesack versus trying to put it in an old one and then wondering why it keeps bursting.


It has been tried and tested and the people that suggested that ( me in particular in relation with the serverWG ) got burned on the stakes, accused wanting to "fork" Fedora for suggesting just that as in cleaning and implementing the output from that work in a separated repository's under a new brand until we were confident enough to with that effort and drop replace Fedora as we know it with that effort.

The fact is there is a lot of legacy cruff we should be removing as well as doing other necessary cleanups to make Fedora agile again for the upcoming changes in the IT industry landscape.

But certain people seem to rather want to drown Fedora in bureaucracy and vague future proposals and working groups instead of doing what needs to be done.

JBG