Add: page on github issues in our organization #67
Conversation
community/github/issues.md
Outdated
|
|
||
| - **Clear Title:** A concise and descriptive title summarizing the issue or feature request helps us scan through issues and understand what each issue is about. Below are some example titles that are specific | ||
|
|
||
| * `Bug: broken link in link-to-page-here / name of page / document etc` |
There was a problem hiding this comment.
LOVE that there are examples!
community/github/issues.md
Outdated
|
|
||
| ### If you have permissions, label the issue | ||
|
|
||
| While outside contributors will not have permission to label issues, pyOpenSci core team members and volunteers will. Be sure to add appropriate labels to |
There was a problem hiding this comment.
it would be helpful to have a quick list here on what our labels are and what they're used for
There was a problem hiding this comment.
we have an open help-wanted ticket on the labels. the labels are different in each repo.
https://github.com/orgs/pyOpenSci/projects/3?pane=issue&itemId=62313858
so while this is a good idea it's a lot more complicated than a quick list! we will need to complete the task abbove which involved deciding what labels we want to curate and syncing them across repos! jon did a bunch of work on this at our scipy sprint. you can open a new issue about this here that will be a future issue when we get that workflow setup if you wish.
Co-authored-by: Jesse Mostipak <[email protected]>
|
Ok merging this!! and we have some todo's related to other open issues such as labels! |
This pr adds a page on how we prefer to add and manage issues in our organization.
i'm torn about whether to add information around assigning people to issues as that seems to be more sprint related (see #62 )
However now that i'm thinking about it it may not be in either page. we can open an issue once we decide where that information should live