Comments (11)
See my comments on the equivalent issue you raise over on the pip tracker. Basically, I'm -1 on doing this until we understand the implications on project governance better. And I think it should be a PyPA-wide decision, not a per-project one.
from virtualenv.
I don't own pypa so can't really make that transition.
from virtualenv.
I think @pradyunsg might have access. Or @di. Though, for this to happen, they have to have access to both the virtualenv project (as an Owner) on PyPI and to the org + have a Manager+ access in the org.
You'll need to invite that individual to the virtualenv project, I suppose.
Oh.. Maybe @pfmoore is in the org? That would probably be enough.
from virtualenv.
What would being in the pypa org on PyPI mean? Would it alter who can do releases or manage the project? If so, I'm not sure that's necessarily something we'd want. I don't even know who has rights on the pypa org :-(
Edit: Actually I don't seem to be in the pypa org, so if this project was moved, would that mean I lose my rights on the project? I'm not very active, but removing maintainers seems like a bad idea for bus factor reasons if nothing else...
from virtualenv.
The individuals can still be added with Owner or Maintainer privileges. It'll show up under the org and the org will be linked from the project page.
Additionally, there would be a possibility to have teams added with the corresponding privileges. The team members aren't listed on the public project page but could publish if there's enough privileges configured. The individually added people are listed.
The trusted publishing setup isn't affected as it's connected to the projects and not the users.
As for the org owners, they are not public but I'd assume @di since he's just move pip-audit there. He'll know more since I don't have visibility into the org.
from virtualenv.
not a per-project one.
I'd argue that our current governance model does not allow authority over such per project topics. So must remain project specific.
from virtualenv.
I'd argue that our current governance model does not allow authority over such per project topics. So must remain project specific.
Sorry, I wasn't clear. Whether to be part of the pypa org is a per-project decision, certainly. But whether and how to manage the pypa org is a PyPA decision, and as far as I can tell, projects can't reasonably join the pypa org until that's sorted out (if for no other reason than we have no process at the moment for deciding who will be owners/members of the PyPA org on PyPI, and hence be able to manage projects in that org - something I assume individual projects will care about).
from virtualenv.
See pypa/pip#12250 (comment) -- let's hold off on this.
from virtualenv.
@gaborbernat Dustin posted some implications FAQ in the ML here: https://mail.python.org/archives/list/[email protected]/thread/E6MWIHEK3M232UILXGQFYPHGJHF7VYW7/.
from virtualenv.
I did reach out to him to go ahead, but he didn't get back since then.
from virtualenv.
So apparently it's already been transferred. Closing.
from virtualenv.
Related Issues (20)
- Add PKG_CONFIG_PATH to variables set by venv activate HOT 1
- Extra Closing Parenthesis in the Code
- deactivate command not available in shell scripts or sub-shells (activate script does not export "deactivate") HOT 1
- `try-first-with` behaves differently for `--python` full paths and version specs HOT 3
- post-create hooks for discoverers/discovery HOT 1
- not work properly with pywin32 HOT 2
- Update for platformdirs v4 HOT 14
- pytest fails in five units HOT 14
- tests/unit/create/test_creator.py::test_create_no_seed --creator venv fails on Python 3.13 HOT 7
- cpython3_win_embed test failures with Python 3.13 HOT 6
- mkvirtualenv fails with: ModuleNotFoundError: No module named 'platformdirs' HOT 3
- venv base-executable path does not resolve symlinks using realpath() HOT 2
- Values in `pyvenv.cfg` do not reflect the real paths on case insensitive file systems HOT 5
- Virtualenv should support workon command by default. HOT 3
- https://bootstrap.pypa.io/virtualenv/3.11/virtualenv.pyz returns "Error 503 No healthy backends" HOT 3
- (Bitcoin wallet )15RFhHGkrB8F3TTtt4KgsyB5Mn3UQrGQnz
- Questions about Copilot + Open Source Software Hierarchy HOT 1
- Virtualenv fails to create environment on Windows HOT 3
- Discovery with a generic spec fails to find specific python
- Latest release no longer respects PATH on Windows HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from virtualenv.