Andreas Jaeger wrote:
Let's look how other open source projects basically work (very simplified):
The open source developers work on those areas that they consider critical and are interesting for them to work on. They do look at bug reports, feature requests etc and decide what's in their view is best for the project. Most look forward in a positive way to new developers and embrace them: They help them to get into the project, guide them with their first contribution, review and accept their patches - or explain why the patch is either of bad quality or going in a direction that the project is not going.
I think that's a pretty good summing up.
YaST is an open source project! Discussions and repositories are public, and the YaST team is a friendly crowd that embrace new members that want to contribute to YaST
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? 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. 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. /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org