Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2018-02-20 17:49:20
Size: 6879
Comment: notes dump
Revision 3 as of 2018-02-20 19:14:29
Size: 6915
Comment: PR link for robots.txt, formatting
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Line 4: Line 5:
    Sumana    Nicole    Laura     Dustin    Ernest  . Sumana
. Nicole
. Laura
. Dustin
. Ernest
Line 6: Line 12:
Ernest: * - RIP productivity last two-weeks attending/catching up from PyTN. Was hot to trot Saturday morning when suddenly SPAM Ernest:
Line 8: Line 14:
 * - RIP productivity last two-weeks attending/catching up from PyTN. Was hot to trot Saturday morning when suddenly SPAM
Line 9: Line 16:
Line 12: Line 18:
Dustin * Wrapped up account management & milestone #1 Dustin
Line 14: Line 20:
 * Wrapped up account management & milestone #1
Line 15: Line 22:
Line 17: Line 23:
Line 20: Line 25:
Nicole * finished manage account features (needs user testing) Nicole
Line 22: Line 27:
 * finished manage account features (needs user testing)
Line 23: Line 29:
Line 25: Line 30:
Line 27: Line 31:
Line 29: Line 32:
Line 32: Line 34:
Laura * met with Ernest and helped create codebase description in docs: https://warehouse.readthedocs.io/application/ Laura
Line 34: Line 36:
 * met with Ernest and helped create codebase description in docs: https://warehouse.readthedocs.io/application/
Line 35: Line 38:
Line 38: Line 40:
Sumana: * - bug triage Sumana:
Line 40: Line 42:
 * - Twine RtD fix PR https://github.com/pypa/twine/pull/297

*     - sprint planning (Packaging WG email)

*     - PR testing/review

*     - helped volunteers via IRC/GitHub/email
 * - bug triage
* - Twine RtD fix PR https://github.com/pypa/twine/pull/297
 * - sprint planning (Packaging WG email)
 * - PR testing/review
 * - helped volunteers via IRC/GitHub/email
Line 49: Line 49:
* https://github.com/pypa/warehouse/issues/2285 Rename "/legacy" url to something else * Currently milestone 4 (launch). Need to coordinate with: who? Packaging guide, twine, who else? And should we do this earlier, during the beta, to shake bugs out? * https://github.com/pypa/warehouse/issues/2285 Rename "/legacy" url to something else
Line 51: Line 51:
 * Currently milestone 4 (launch). Need to coordinate with: who? Packaging guide, twine, who else? And should we do this earlier, during the beta, to shake bugs out?
Line 52: Line 53:
Line 54: Line 54:
Line 57: Line 56:
* Possible spamming of package namespace #2859 https://github.com/pypa/warehouse/issues/2859 * user still has concerns * Possible spamming of package namespace #2859 https://github.com/pypa/warehouse/issues/2859
Line 59: Line 58:
 * user still has concerns
Line 60: Line 60:
Line 63: Line 62:
* https://github.com/pypa/warehouse/issues/2533 "499 Client Error: Client Disconnected for url: https://upload.pypi.org/legacy/" * Confusing user experience, unclear where problem originates * https://github.com/pypa/warehouse/issues/2533 "499 Client Error: Client Disconnected for url: https://upload.pypi.org/legacy/"
Line 65: Line 64:
 * Confusing user experience, unclear where problem originates
Line 66: Line 66:
Line 68: Line 67:
Line 70: Line 68:
Line 73: Line 70:
* https://github.com/pypa/warehouse/issues/916 option to turn off indexing in robots.txt across instance (e.g., Test PyPI) * should we offer this at all? or should such an organization use devpi? * https://github.com/pypa/warehouse/issues/916 option to turn off indexing in robots.txt across instance (e.g., Test PyPI)
Line 75: Line 72:
 * should we offer this at all? or should such an organization use devpi?
Line 76: Line 74:
 * Task: we should do this when we can.
 * Dustin: ditto, this is something we should do but is not crucial
 * Can be done using headers also -- add as a nice to have issue
 * Resolution: --(Sumana will update as cool-but-not-urgent)-- Ernest has created [[https://github.com/pypa/warehouse/pull/2995|a PR]]
Line 77: Line 79:
 * Task: we should do this when we can. * https://github.com/pypa/warehouse/issues/1000 Email all owners when a new owner/maintainer is added
Line 79: Line 81:
 * Dustin: ditto, this is something we should do but is not crucial

 * Can be done using headers also -- add as a nice to have issue
 * Resolution: Sumana will update as cool-but-not-urgent

* https://github.com/pypa/warehouse/issues/1000 Email all owners when a new owner/maintainer is added * Milestone 4: Launch?
 * Milestone 4: Launch?
Line 87: Line 83:
Line 90: Line 85:
* https://github.com/pypa/warehouse/issues/998 Send confirmation when email address changes * Milestone 4: Launch? * https://github.com/pypa/warehouse/issues/998 Send confirmation when email address changes
Line 92: Line 87:
 * Milestone 4: Launch?
Line 93: Line 89:
Line 96: Line 91:
* https://github.com/pypa/warehouse/issues/997 Email all owners when a new version of a package is uploaded * Cool But Not Urgent? * https://github.com/pypa/warehouse/issues/997 Email all owners when a new version of a package is uploaded
Line 98: Line 93:
 * Cool But Not Urgent?
Line 99: Line 95:
Line 102: Line 97:
* https://github.com/pypa/warehouse/issues/469 Disallow runs of special characters in project names * just for readability, or also for user confusion that might cause security issues? * https://github.com/pypa/warehouse/issues/469 Disallow runs of special characters in project names
Line 104: Line 99:
 * just for readability, or also for user confusion that might cause security issues?
Line 107: Line 103:
* https://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-v12.html * issue to re-publicize the upcoming deadlines? * https://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-v12.html
Line 109: Line 105:
 * issue to re-publicize the upcoming deadlines?
Line 110: Line 107:
Line 112: Line 108:
Line 115: Line 110:
* https://github.com/pypa/warehouse/issues/582 ability to delete legacy docs * who should decide on the policy so we can move forward? * https://github.com/pypa/warehouse/issues/582 ability to delete legacy docs
Line 117: Line 112:
 * who should decide on the policy so we can move forward?
Line 118: Line 114:
Line 120: Line 115:
Line 122: Line 116:
Line 124: Line 117:
Line 129: Line 121:
Line 132: Line 123:
  * Ernest can grant Nicole and Dustin access to that repo
Line 133: Line 125:
  * Ernest can grant Nicole and Dustin access to that repo
Line 136: Line 127:

Warehouse Sync-up Meeting

Monday, Feb 19 2018

Present:

  • Sumana
  • Nicole
  • Laura
  • Dustin
  • Ernest

Current work/announcements/blocked:

Ernest:

  • - RIP productivity last two-weeks attending/catching up from PyTN. Was hot to trot Saturday morning when suddenly SPAM
  • - Kubernetes Object creation is all that remains for full end-to-end deployment via our new infra tooling.
  • - Blocker - [infrastructure deployment issue, requires Donald]

Dustin

  • Wrapped up account management & milestone #1

  • Finished anything I can in Milestone #2
  • not really blocked on anything right now, working on PR review and stuff in Milestone 3
  • Also pushing forward PEP566, which will eventually enable Markdown support in Warehouse

Nicole

  • finished manage account features (needs user testing)
  • issue 1354 - contributor ? package detail page
  • issue 2880 - ?
  • issue 2127 - accessibility issue - working on ui dropdowns - not accessible with keyboard
  • not blocked
  • working on talk proposal for EuroPython

Laura

Sumana:

Bug/PR triage

* https://github.com/pypa/warehouse/issues/2285 Rename "/legacy" url to something else

  • Currently milestone 4 (launch). Need to coordinate with: who? Packaging guide, twine, who else? And should we do this earlier, during the beta, to shake bugs out?
  • Ernest: Problem is client support, we've already changed the URL once... with much confusion/frustration. Making /v0 an alias to /legacy seems fine though (also trivial)

  • Dustin: Personally, I don't think we should do this
  • Sumana: comment with arguments

* Possible spamming of package namespace #2859 https://github.com/pypa/warehouse/issues/2859

  • user still has concerns
  • Ernest: PEP 541 or bust (this is strictly not a MOSS grant scoped issue.)
  • Sumana: update user to wait until PEP 541, give progress update

* https://github.com/pypa/warehouse/issues/2533 "499 Client Error: Client Disconnected for url: https://upload.pypi.org/legacy/"

  • Confusing user experience, unclear where problem originates
  • Ernest: Honestly no idea either. We're going to be moving the upload infra soon... so we'll probably solve and create a whole new host of similar issues. Unclear path forward.
  • Ernest: This _might_ be an issue with Heroku's HTTP routing. Not sure :/
  • Dustin: Seems like some existing issues were due to metadata failing validation? Need example distributions from affected users to be sure
  • Sumana - ask user for more details

* https://github.com/pypa/warehouse/issues/916 option to turn off indexing in robots.txt across instance (e.g., Test PyPI)

  • should we offer this at all? or should such an organization use devpi?
  • Ernest: Not sure what devpi has to do with this. The tl;dr is that the "test" instance of PyPI really has no need to be indexed by search engines.
  • Task: we should do this when we can.
  • Dustin: ditto, this is something we should do but is not crucial
  • Can be done using headers also -- add as a nice to have issue
  • Resolution: Sumana will update as cool-but-not-urgent Ernest has created a PR

* https://github.com/pypa/warehouse/issues/1000 Email all owners when a new owner/maintainer is added

  • Milestone 4: Launch?
  • Ernest: New Feature, falls into security/audit **Post-Launch**
  • Dustin: This is easy to do now. We should also send an email notification to newly added collaborators

* https://github.com/pypa/warehouse/issues/998 Send confirmation when email address changes

  • Milestone 4: Launch?
  • Ernest: New Feature, falls into security/audit **Post-Launch** (BUT GREAT IDEA)
  • Dustin: I punted on this in email management, would be good to do this post-launch

* https://github.com/pypa/warehouse/issues/997 Email all owners when a new version of a package is uploaded

  • Cool But Not Urgent?
  • Ernest: New Feature, falls into security/audit **Post-Launch**
  • Dustin: ditto

* https://github.com/pypa/warehouse/issues/469 Disallow runs of special characters in project names

  • just for readability, or also for user confusion that might cause security issues?
  • Ernest: This would require PEPs to be modified. Not in scope for MOSS grant work.
  • Resolution: Sumana to update noting it's not in scope for MOSS work

* https://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-v12.html

  • issue to re-publicize the upcoming deadlines?
  • Ernest: Mehhhhhhhhhh our request rate for TLSv1.0 and TLSv1.1 is _orders of magnitude_ lower than TLSv1.2
  • Ernest: Outside scope of MOSS grant work, will affect all PSF services hosted behind Fastly. Will take this to Infra-WG+
  • Small number of users use outdated protocols - Ernest will ask PSF to tweet about it

* https://github.com/pypa/warehouse/issues/582 ability to delete legacy docs

  • who should decide on the policy so we can move forward?
  • Eric - wants a separate RTD instance for PyPI, but how do we know where users are coming from, and who can update those docs?
  • blocked on clear path forward on handling documentation, need docs url
  • Who can make authoritative decision - Packaging WG?
  • Ernest will send a message to Eric
  • PyPI not in business of hosting docs -- need division of who does what

Ask Donald to:

Milestone progress

We've hit Milestone 1 and are on to Milestone 2!https://github.com/pypa/warehouse/projects/1 decouple testing/promotional tasks for Milestone 2 from milestone schedule

TODO

  • add a nice to have issue for a "report spam" button
  • Ernest to talk to Infrastructure WG about TLS deadline
  • Ernest to talk to Eric about hosted documentation question (DONE)

PackagingWG/2018-02-20-Warehouse (last edited 2018-02-20 23:56:38 by SumanaHarihareswara)

Unable to view page? See the FrontPage for instructions.