Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve security policy / security page content #1323

Closed
nlhkabu opened this issue Jul 1, 2016 · 4 comments
Closed

Improve security policy / security page content #1323

nlhkabu opened this issue Jul 1, 2016 · 4 comments
Labels
documentation needs discussion a product management/policy issue maintainers and users should discuss
Milestone
Post Legacy Shutd...

Comments

@nlhkabu
Copy link
Contributor

nlhkabu commented Jul 1, 2016

For launch we are going to use the content currently in the Warehouse docs, but in the long term, it would be good to improve the policy to something that does not rely on Donald and Richard answering emails.

Once a new policy is decided on, the security page will need to be updated accordingly.
@nlhkabu nlhkabu added documentation requires triaging maintainers need to do initial inspection of issue labels Jul 1, 2016
@ghost

This comment has been minimized.

Sign in to view
@brainwane brainwane added this to the 5: Shut Down Legacy PyPI milestone Feb 11, 2018
@brainwane brainwane added Post launch - medium priority needs discussion a product management/policy issue maintainers and users should discuss and removed requires triaging maintainers need to do initial inspection of issue labels Mar 6, 2018
@brainwane brainwane modified the milestones: 5: Shut Down Legacy PyPI, 6. Post Legacy Shutdown Mar 6, 2018
@brainwane
Copy link
Contributor

In today's Warehouse core developers' meeting we decided to pare down our near-future milestones on our development roadmap so they really only contain the absolutely essential bugfixes and features we need to launch, replace legacy PyPI, and shut down the old site. So I'm moving this issue into a milestone further in the future; sorry for the wait.

brainwane added a commit to brainwane/warehouse that referenced this issue Mar 8, 2018
@brainwane
Add security and feed information to docs
4a7338a 
Ref. pypi#1323
brainwane added a commit to brainwane/warehouse that referenced this issue Mar 8, 2018
@brainwane
Add API link to user help
a266dda 
Ref: pypi#1323.
@brainwane brainwane mentioned this issue Mar 8, 2018
Merged
di pushed a commit that referenced this issue Mar 8, 2018
@brainwane @di
Add journal usage guidance, remove download methods in API docs (#3173)
9848325 
* Add security and feed information to docs

Ref. #1323

* Update XML-RPC API docs fields, usage info

After testing, update fields and briefly describe responses.

* Update API docs since PyPI no longer offers download stats

* Add API link to user help

Ref: #2413.
Mariatta pushed a commit to Mariatta/warehouse that referenced this issue Mar 9, 2018
@brainwane @Mariatta
Add journal usage guidance, remove download methods in API docs (pypi…
547ef1a 
…#3173)

* Add security and feed information to docs

Ref. pypi#1323

* Update XML-RPC API docs fields, usage info

After testing, update fields and briefly describe responses.

* Update API docs since PyPI no longer offers download stats

* Add API link to user help

Ref: pypi#2413.
@di
Copy link
Member

di commented May 15, 2018

@brainwane The security page (https://pypi.org/security/) now suggest that folks email [email protected], I think this issue might be resolved. Do you think anything else could be added here?

(cc @99)

@brainwane
Copy link
Contributor

Sounds good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation needs discussion a product management/policy issue maintainers and users should discuss
Projects
None yet
Milestone
Post Legacy Shutdown priorities
Development

No branches or pull requests
3 participants
@di @brainwane @nlhkabu