#off-topic

1 messages · Page 8 of 1

onyx sphinx
#

There's a proposal to move pip-tools to pypa which would pull it's maintainers with it

vast wren
#

huh

#

I'm confused how this affects the pypa org

onyx sphinx
#

There's a new python GitHub namespace policy here https://discuss.python.org/t/new-python-organization-repository-policy/17376

Discussions on Python.org
New `python` organization repository policy

Hello, When asked about adding the typing_extensions repository to the Python organization (#126), the Steering Council discussed a general policy for the organization, as the current one seems outdated. We decided on the guidelines below. Note that existing repositories can stay under python. However, we will ask that: PSF infrastructure b...

#

If pip is determined to be a non-General-use tool there's a process to bring it under the python namespace

silk jungle
#

hmm, does this mean mypy will eventually be moved to the psf?

#

I can't see them accepting the CLA requirement

onyx sphinx
#

No mypy is banned by name

vast wren
#

They're not requiring any specific thing to be moved under the python/ namespace

#

just saying what kind of things are allowed to live under it

onyx sphinx
#

If that's landed there's now a path to plonk the jazzband maintainers into the python maintainers group

silk jungle
#

I really doubt that would ever happen.

onyx sphinx
#

Oh yeah someone will probably stop it

vast wren
#

I think they're just trying to restrict the proliferation of nonsense repos under python/, not trying to steal packages from other orgs

onyx sphinx
#

No I'm not suggesting they're trying to steal packages 🤣

vast wren
#

I have a migraine so I may be confused what you're suggesting too 🙂 I don't think that pip et al have any real desire to be under the python/ org

silk jungle
#

Also, it's not 100% clear whether these policies apply to the psf/ repositories too? I'm pretty sure it's "no, it does not" but hmm

#

I also don’t think we want the PSF pulled into any legal issues based on the code being hosted under our org due to the lack of CLA, which isn’t a huge burden IMO.
sounds like any PSF managed organisations should (not will mind you) require the CLA

onyx sphinx
#

There's a process started to land pip-tools into the pypa namespace, and the pypa namespace policies drag maintainers in with adoption

#

pip-tools currently has 1.3k maintainers

junior narwhal
#

process started to land pip-tools into the pypa namespace

link?

onyx sphinx
vast wren
#

I'm just speaking for myself, but I suspect that we would not drag all 1.3k maintainers of jazzband into the pypa

nocturne swallow
#

To be fair maintainers who join pypa don't get org rights, only admin over their project

#

So technically only maintainers that would follow pip tools to pypa would became pypa voters

vast wren
#

I was more just thinking of the logistics of going from 82 to 1382

#

seems rough

onyx sphinx
#

If pip vendors pip-tools, and implements pip sync and pip constrain --generate-hashes, this could all just go away...

junior narwhal
#

doesn't the work Stéphane has been doing kinda make pip-tools obsolete?

shadow zealot
#

We’re not all the way there yet but yes the direction is to (sort of) make pip-freeze and pip-sync functionalities part of pip

humble phoenix
humble phoenix
#

The pip installation report has other use cases, though. For instance the pip-audit project showed interest in the feature.

dreamy hatch
ebon nymph
dreamy hatch
onyx sphinx