Appeal/recourse mechanism #11
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
spoons.technology/plots#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mistakes will be made.
How do we make sure the response to someone feeeling wronged is fair and consistent?
We should keep in mind that:
Appeal/recorse mechanismto Appeal/recourse mechanismAgain, not my forté, but important. I think my thoughts boil down to:
I think the "case law" thing makes a lot of sense - basically a decision log, probably in git?
Not sure how desirable the log being public is - there's a fair chance that it would contain things that would be (at best) unpleasant for some people.
Perhaps we should create public policies, based on decisions that were made as a result of problems? Then the policy can be discussed, rather than the specific case?
On the "appeal process" specifically, perhaps "you can ask for someone else to look over the case" would work initially?