-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create proposal for PyPI organization #95
Comments
seems like a good idea. I went ahead and requested an |
Once the new org is approved, we should moving all of our libs to the new org: https://pypi.org/search/?q=instructlab Current owners are: |
It has been pointed out that it may be better to create a user owned by the @instructlab/oversight-committee to be the package owner |
I've had some conversations with pypi about this as a "whole," and organizations are still in "progress" and will only be available to the sponsoring organizations any time soon. Unless our project can start sponsoring the PSP and pypi, this should be either completely back burner'd or closed as can't be done. |
So shouldn't we go the user route I've suggested then @jjasghar? Otherwise all these packages will just be owned by a smattering of Red Hat and IBM engineers We can create a user just called |
Yep, that seems like the best path forward. |
Ooooh, a 1password vault :-) |
No, shared accounts are a bad idea. Don't do this. You want to be able to audit account activity and remove access of a person in case they leave the project or their work machine gets compromised. |
What we have now is bad. So what do you propose? |
Use individual, personal accounts in combination with strong 2FA (FIDO). Select a few people (3-4) to be project owners. InstructLab is using trusted publishing for releases anyway. Project admin access is only needed to yank a bad release or to add/remove another maintainer. You could make an argument that people should create a new work account with their work email address and not use their personal PyPI account. I don't think that's necessary. |
We now have two Release Engineers on the team - @courtneypacheco and @ktdreyer - I reckon they would be good people for this |
Oversight Committee member here. 🫡 Christian's last post seems the best approach, let's do that and I approve Ken and Courtney to be added. |
ey ey, ma'am! I have invited
Could you please make sure that you have 2FA enabled? PyPI doesn't show your 2FA status. The following packages also have a sole owner |
Thanks @tiran ! I do have 2FA enabled on my I have accepted all my pending invites for the Instructlab repos. @bjhargrave has invited me to https://pypi.org/manage/project/instructlab-schema . I don't have access to https://pypi.org/project/instructlab-dolomite/ . |
I think you also need to setup testpypi accounts so you can be invited to the packages on testpypi. |
Thanks @bjhargrave . I've done that today. https://test.pypi.org/user/ktdreyer/ is my account. |
Now that we are publishing several PyPI packages we should officially propose creating a PyPI org to own them all: https://pypi.org/manage/organizations/
cc @tiran @russellb curious y'alls thoughts
The text was updated successfully, but these errors were encountered: