Per Jessen <per@computer.org> writes:
[...] I chose my wording badly - there's no doubt in my mind that openSUSE is an open source project. I just have some doubts are about how open the management is - YaST is a key element of openSUSE, but in my view, it's not really an open source community driven project as are e.g. apache and others. YaST is driven by Novell/SUSE, and decisions to drop or include features appear to be less open and not very community driven?
Some of this decision making could be improved, I agree - but have a look at past discussions, it
I don't want to flog a dead horse, and I'm also perfectly happy with the compromise we found, but the deprecation of JFS and now more recently LILO were clearly Novell decisions, not community decisions.
Let me ask differently: What do you consider a community decision? If one person complains loudly and the rest is silent? Should we vote for everything - and who should?
I think perhaps the case of JFS was a good start - it's still part of YaST, yet clearly marked as unsupported. Why not do the same with e.g. LILO ? That way you leave the door open for someone to step in and take over the support. And maybe even submit a patch or two.
As Stano said: The yast-bootloader is a beast that needs to be simplified to reduce the complexity of it - and that's why we rip out lilo support. If there are some people that would like to stand up and take over the lilo support in yast-booloader and friends, then say it and discuss it with Stano! Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126