Per Jessen - 20:51 16.06.15 wrote:
YasT also appears to be in the hands of SUSE.
How so?
Robert, I responded with a couple of examples where the community is clearly not "in complete ownership of their "baby"". That's all. I totally appreciate that e.g. yast and xen are open to contributors, but that's a far cry from complete community ownership. If you can point us to non-SUSE contributors to YaST, I agree that YasT is not entirely in the hands of SUSE. I did in fact once offer to maintain the LILO section of the bootloader module, but then LILO was deprecated, well .... the same thing happened for JFS fileystem support in the partitioner. There was never any call for help, btw.
Well, unless people complaining that there is no non-SUSE guy sending patches to YaST start actually sending some patches, there is a little somebody else can do. And no call for help? No invitation to participate? Closed? Really? https://news.opensuse.org/2015/02/25/openness-brings-fresh-air-to-yast/ http://kobliha-suse.blogspot.cz/2013/08/yast-modules-summer-sale.html http://lists.opensuse.org/opensuse-factory/2013-08/msg00239.html http://kobliha-suse.blogspot.cz/2013/09/yastteamfreenode.html -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org