Am Freitag, 20. November 2020, 08:17:08 CET schrieb Matěj Cepl: Hi Matej,
At the time of writing we have 538 packages in d:l:python which are out of date and require updating.
sometimes having them out of date is a feature (when the newer version breaks everything else). But that should be a minority.
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.
"We want to maintain it" is a very vague term.. is that more than the "the initial submitter wants to maintain it"? if so, what is it?
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).
Whats a "business reason" for a community project?
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.
Huh? Why? I get the idea, you want people to help contributing also in other areas, but imho thats why we had all the splitting of dlp into subprojects (with the corresponding pain for people that just want to use a set of working and updated packages on older distros)
include me, I have still rights for some Fedora packages) cannot just use `pip install --user copr-cli`?
Thats the same reason for every of those python-packages, right? lets assume I want to have certbot. I can totally install that from pip, so why is it packaged in openSUSE? I'm not against defining a policy for inclusion, but we need to chew a bit more on the rules for that. Personally, I can live without the set of python packages, as well as I can live with packaging more. I can also live with outdated packages that I don't care about, as long as they still build and don't cause my packages to fail building. There are just a few packages that are incredibly painful to maintain, as they are breaking frequently when its dependencies are updated. maybe we should try to do something about them first (e.g. Twisted is one that came accross). Greetings, Dirk