![](https://seccdn.libravatar.org/avatar/e6dc8afd12f42302ae7b5ea72e4dd686.jpg?s=120&d=mm&r=g)
Hi Matěji,
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.
The conclusion of these two points is that every package in Factory carries with itself some (small) cost, and there is no point in trying to push all of PyPI into Factory.
Therefore I suggest these limitations on putting new packages into Factory:
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).
I am against such a measure, as this is very much subjective and will
result in one of the following:
a) the devel project maintainer wants to encourage collaboration, so
nothing really changes for them, except that they now have to read
business reasons as well (and the submitter has to come up with
one).
b) the devel project maintainer does not want to have an overloaded
project, so they either would reject such a package anyway, or they
make the submitter the maintainer. Also in this case, I fail to see
how a business reason helps.
Imho the best solution would be: if you submit a package, then you have
to maintain it. If you fail to do so, then it gets dropped. Don't add
any additional (arbitrary) conditions. We already have wildly different
and mostly unwritten rules for submissions to devel projects, we don't
need more of that, rather less.
Just my 2ct,
Dan
--
Dan Čermák