PyCon Sprint Guide #201
PyCon Sprint Guide #201
Conversation
Provide several easy issues for first time contributors Provide ideas for other long term contributions Somewhat related to python#7
| #. #python-dev on `freenode <http://webchat.freenode.net/>`_. | ||
|
|
||
|
|
||
| Dev Guide Issues |
There was a problem hiding this comment.
We could have a shared Google Docs/ Spreadsheet / Label these issues with pyconsprint2017 (etc), instead of listing them in a PR. And we could mention that link here.
Because we will likely encounter more issues that will get added and we may not need a new PR to add an issue.
There was a problem hiding this comment.
I wasn't sure myself where to list these issues, I realize the devguide may not be the best place.
But at least it becomes community-maintained.
Whereas if it's a google docs, someone has to take ownership of it.
My thinking is people should not add tickets randomly just because they think it's an easy ticket.
We should still vet each ticket to make sure that it is a legitimate issue that needs fixing/improvement. When it is listed in the devguide, it's a sign that it's been approved by a core developer.
There was a problem hiding this comment.
In the past, we have had a shared document (similar to paste bin). That was the reason for my comment. And yes, usually a core dev takes an ownership to keep the doc updated. At the same other others can edit too. (If ownership is a problem, I can volunteer to be an owner of shared doc).
I am not -1, just sharing a point that it will be a cumbersome to keep list alive.
There was a problem hiding this comment.
What if we enabled the wiki on this repo, and added this list as a page there?
There was a problem hiding this comment.
That's a fantastic idea. I am +1 on that.
There was a problem hiding this comment.
Sounds good.
I don't have access to add the wiki :)
There was a problem hiding this comment.
@zware yep, add a wiki page instead of this PR, because a sprint code session can change from a pycon to an other one.
|
Let's rework this PR to provide basic guidance for a sprint organizer at a meetup or another event by removing the PyCon 2017 content to the wiki/etherpad as suggested. @Mariatta I likely have some sprint guides from other communities (SciPy etc) if you want to take a look. |
|
There is also https://github.com/python/devinabox which is meant to act as a guide for people hosting a sprint for CPython. |
|
Is there any limited to used to sprint guide in PyCon (or outside PyCon)? If I want to make a sprint in PyCon Taiwan, could it use this as a guide? |
|
@mlouielu If you'd like to use this PR as a template for your own sprint, please go ahead :) I agree that the sprint guide is better suited elsewhere (eg wiki?) but I likely won't have time to continue work on this until next few weeks... |
|
Just saw @brettcannon 's comment about devinabox. Should this 'guide' be moved there then, instead of a wiki? |
|
Seems like a reasonable plan to move most of the "How to run a sprint" and any future templates to support running a sprint to devinabox (or new sprints repo). The devguide can guide users, organizers, and contributors to the sprint resources. |
|
@mlouielu Since I'll be at PyCon Taiwan, I would be happy to participate in a CPython sprint. |
|
Alright I'll close this and open an issue in devinabox :) Thanks all |
|
Just a note regarding the wiki: due to persistent spam problems, getting edit access to the wiki is a bit of a pain, and there's also no easy way to institute a collaborative review process for proposed changes. So for most things, the GitHub+ReadTheDocs combination is going to provide a superior experience - you still get online editing support, anyone with a GitHub account can submit a PR, and the level of review required can vary based on the sensitivity of the content (e.g. devinabox could likely operate on the basis of "Accepted PR -> Merge privileges if you want them") |
Provide several easy issues for first time contributors
Provide ideas for other long term contributions
Somewhat related to #7