-1 Am 20.11.20 um 08:17 schrieb Matěj Cepl:
Hello,
At the time of writing we have 538 packages in d:l:python which are out of date and require updating.
There are only two reasons why any Python package should be packaged for OpenSUSE: either it is dependency of another package in OpenSUSE, or we want to maintain it. Otherwise, if an user wants an unmaintained package, every user has pip available and they can install a package from PyPI directly.
They can do it in any case. Whether there is an outdated package in openSUSE or not. But the more you push people to PyPI (or Anaconda for d:l:python:numeric), those users will have unmaintainable ecosystems with all sorts of clutter - https://xkcd.com/1987/ . This is why I have always preferred to have an up to date, zypper managed, python sitelib. And it is the reason why I am a big proponent of the upcoming coinstallable python3 flavors.
1. Every new package submitted to d:l:p (or any other official OpenSUSE project) SHALL include in its submit request message “business reasons” for including the package into OpenSUSE (either because it is dependency of some other package, or some other reason, why it is needed).
Other than creating additional workload for both submitter and reviewers , I see no point. There is always a reason to submit a package: Someone want's to use it on their system and is so kind to share their work with the community.
2. Everybody who wants to submit new package to OpenSUSE, MUST submit two updates of packages already in Factory from the list delivered to this list every week.
I thought openSUSE was about encouraging volunteer work.
3. Packages which fail to build for sufficiently long time SHALL be removed from Factory and d:l:python (or moved to d:l:p:misc).
At least for Factory, this policy is already in place, isn't it? If I remember correctly, one of my first packages submitted ever (python-photutils) got removed from Factory a few weeks later, because it started to fail and I did not set up my e-mail notifications correctly. Ben