Add: sprint process to handbook #62
Conversation
community/events/sprints.md
Outdated
|
|
||
| #### THIS LIKELY WON'T WORK Ensure issue and pull request templates are up to date | ||
|
|
||
| A challenge of a successful sprint is that there will be many issues and pull requests to triage after the sprint. To keep track of new issues and pr's, during an event, every pyOpenSci GitHub repository should have a sprint issue and pull request template. Adding this template only needs to be completed once, however |
There was a problem hiding this comment.
I think we should go into scipy with a manual process and just see if automating adding to the board would help. i suspect it won't be that much more beneficial and more infra to maintain. If the pr template worked then it would make sense. but because i don't think the pr template will work (i remember fighting with this for stravalib) then manual labeling might be our best bet here. We could however have an issue template for sprints. that may or may not be useful .
There was a problem hiding this comment.
if we collet github usernames at the sprint start, the remote person would know who is contributing by their username making it even easier to identify sprint related activity.
There was a problem hiding this comment.
@kierisi i see my THIS WONT WORK comment now 😆 it was not visible to me wednesday. but i do remember writing it now.
| and community highlights. | ||
| - **GitHub**: Remind them to continue following and contributing to pyOpenSci | ||
| repositories on GitHub. | ||
| - Discourse? |
There was a problem hiding this comment.
reading my mind! I have a note to talk about Discourse in our upcoming social media quarterly meeting.
There was a problem hiding this comment.
cool. how bout i just comment this out for the time being?
Co-authored-by: Jesse Mostipak <[email protected]>
Co-authored-by: Jesse Mostipak <[email protected]>
|
@lwasser this looks good to me! the only (small, non-blocking) suggestion I have is to link from the TLDR in the sprints section to the expanded sections further in the page. that way if someone reads the TLDR and needs clarification, they can quickly navigate to the spot on the page. |
|
awesome. i can do that @kierisi i'll do that now - push, and merge. and then we can flesh out the other sections later (related to contributor information and our database / gdpr etc!). thank you for the super helpful reviews today. i think it improved the content a lot! |
|
yahoo! all green -- merging! this feels good. and it was a lot of work to document! |
I am not sure that my idea for pr templates will work. i think we will need to go the -- remote person labels things. it gets added to the board once labeled via a workflow. remote person then moves it to the right column. if we do this it could just be easier for the remote person to do all of the labeling and project board adding manually because it would be on the side of the issue or pr and not too much more work to add the project board stuff there. ...