Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #20

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #20

wants to merge 1 commit into from

Conversation

shaunagm
Copy link
Collaborator

@shaunagm shaunagm commented Nov 18, 2024

Added some info about how to add/triage issues

Addresses #18

Added some info about how to add/triage issues
@shaunagm
Copy link
Collaborator Author

@KasiaHinkson @sharinetmc let me know if this looks good to you or if I should add more info

@shaunagm
Copy link
Collaborator Author

shaunagm commented Nov 18, 2024

Oh maybe there should be guidance re: how to claim issues, otherwise people might feel shy

@KasiaHinkson
Copy link

Yeah I think it's a good start! A section on how to claim issues is a good idea. I've got multiple people asking me how they can contribute to Parsons when they don't work in progressive teach, and I think well developed and scopes issues will be a great resource, but they'll need to know what process to follow to claim it as a thing they're working on.

We might also want to develop guidelines on how to follow through with claimed issues? Like, "here's how to claim an issue! Once it's claimed, Shauna or another Parsons representative will try to check in regularly, see if you need any help, be available to support, make sure you're still working on the issue, etc."

@shaunagm
Copy link
Collaborator Author

re: following through, for some of the issues there might be some basic guidelines (like "10 steps to run a Parsons Party" or "5 steps to write a blog post" etc.) but in general, maybe letting folks know about community meetings? if we ping folks on all claimed issues as part of the community meetings that's roughly a monthly check in.

also maybe a brief "unclaim an issue" to normalize that it's totally okay to say "whoops got busy, let me give this task back"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants