Virtualenv creation, management and use is a common problem for users in Toolforge.
Creating good documentation about it seems like a step in reducing problems.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Lea_Lacroix_WMDE | T187319 Documentation sprint @Hackathon 2018 | |||
Declined | None | T101659 Run a documentation sprint for Cloud VPS and Toolforge | |||
Duplicate | None | T187659 Document virtualenv creation in Toolforge |
Event Timeline
The most comprehensive current documentation is probably https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#Using_virtualenv_with_webservice_shell, but that only covers the bare starting instructions for a venv.
I've wondered about making programming language specific collections before. This is how Heroku organizes their getting started docs and in a lot of ways I think that might be easier for newcomers to understand. Maybe @srodlund has some thoughts about how we should be thinking about making this type of specialized detail more discoverable?
@srodlund: Hi! This task has been assigned to you a while ago. Could you maybe share an update? Do you still plan to work on this task?
If this task has been resolved in the meantime: Please update the task status (via Add Action... → Change Status in the dropdown menu).
If this task is not resolved and only if you do not plan to work on this task anymore: Please consider removing yourself as assignee (via Add Action... → Assign / Claim in the dropdown menu): That would allow others to work on this (in theory), as others won't think that someone is already working on this. Thanks!