[yast-devel] Some YaST Packages Will Be Out of Maintenance Soon
Hi, We'd like to stop maintaining some of the old YaST packages in both openSUSE and SLE in the near future because there are more important tasks we should focus on. This means that the current YaST Team will not take care of them anymore: add features, fix bugs, submit to Factory, etc. We have a few options what we could do depending on the fact whether the openSUSE community wants to keep them: - Remove from GitHub completely (not a good option) - Delete all files from master branch and add README that would state that $this package is free for taking over - Move to openSUSE project and add some README without removing files from the master branch, and also removing from openSUSE - Offer these YaST modules to community at opensuse-factory In all cases, we should replace the current MAINTAINER with some generic (opensuse-factory?) mailing-list. Packages in question (examples) - yast2-phone-services - yast2-modem - yast2-x11 - yast2-mouse - yast2-irda - yast2-fingerprint-reader Let's discuss the possibilities and then let's decide which one is the best. Thanks Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Wed, 07 Aug 2013 14:47:49 +0200 Lukas Ocilka <lukas.ocilka@suse.com> napsáno:
- Delete all files from master branch and add README that would state that $this package is free for taking over
This is what we are currently doing for dropped packages.
- Offer these YaST modules to community at opensuse-factory
In general, yes, we can offer maintenance of some packages to community. but sometimes the drop needs to be final. Looking at those modules:
- yast2-x11
As discussed elsewhere, the package is needed (might be renamed, of course)
- yast2-irda - yast2-fingerprint-reader
In the drop requests, main reason was that: - IrDA is obsolete technology, there's no need to support that (and so no need to look for new maintainers) - there are fingerprint reader solutions for desktop environments, so again, no need for YaST module. Besides, mentioned problems of this module are based on lack of hardware support in the underlying library, so giving maintainership of yast module would not solve anything without solving such (upstream) problems. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.8.2013 14:47, Lukas Ocilka napsal(a):
Packages in question (examples)
[...]
- yast2-mouse
yast2-mouse is used in AutoYast and in yast2-dirinstall, so we need to adapt these packages before dropping it... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.8.2013 14:47, Lukas Ocilka napsal(a):
- Move to openSUSE project and add some README without removing files from the master branch, and also removing from openSUSE
I assume that by this you mean moving in Git from https://github.com/yast/yast-whatever to https://github.com/openSUSE/yast-whatever If so, then I think it would be very confusing to have YaST repositories on two different places. Users and random contributors don't care if the module is maintained by core YaST team or someone else and will expect everything under one project.
Let's discuss the possibilities and then let's decide which one is the best.
My not-that-much-informed opinion is that we should ask the following question for each considered module: Does the module still make sense and we only don't have manpower to maintain it, or is it completely obsolete? If it is completely obsolete, let's drop it (the README way seems reasonable). It it makes some sense, let's try to find an active maintainer (by posting into relevant mailing lists). If one appears, (s)he'll maintain the module, if not, let's drop it. By active maintainer I mean someone who will at least respond to bugs, read yast-devel and react to pull requests in timely fashion (important especially for mass changes). Someone able and willing to make module-local decisions. Preferably, he will also actively improve the module. Doesn't matter if he is from SUSE or not. Note that by above definition a generic maintainer (some mailing list) can't really be "active". -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 7.8.2013 14:47, Lukas Ocilka napsal(a):
- Move to openSUSE project and add some README without removing files from the master branch, and also removing from openSUSE
I assume that by this you mean moving in Git from https://github.com/yast/yast-whatever to https://github.com/openSUSE/yast-whatever If so, then I think it would be very confusing to have YaST repositories on two different places. Users and random contributors don't care if the module is maintained by core YaST team or someone else and will expect everything under one project.
Let's discuss the possibilities and then let's decide which one is the best.
My not-that-much-informed opinion is that we should ask the following question for each considered module: Does the module still make sense and we only don't have manpower to maintain it, or is it completely obsolete? If it is completely obsolete, let's drop it (the README way seems reasonable). It it makes some sense, let's try to find an active maintainer (by posting into relevant mailing lists). If one appears, (s)he'll maintain the module, if not, let's drop it. By active maintainer I mean someone who will at least respond to bugs, read yast-devel and react to pull requests in timely fashion (important especially for mass changes). Someone able and willing to make module-local decisions. Preferably, he will also actively improve the module. Doesn't matter if he is from SUSE or not. Note that by above definition a generic maintainer (some mailing list) can't really be "active". -- David Majda SUSE Studio developer http://susestudio.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (4)
-
David Majda -
Jiří Suchomel -
Ladislav Slezak -
Lukas Ocilka