From 922144f3ff09205deedb1ff4efbfa19ffadff53f Mon Sep 17 00:00:00 2001 From: PrincipalSpears Date: Tue, 15 Jun 2021 23:48:27 +0000 Subject: [PATCH] Currently in draft. --- Ettiqute.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 Ettiqute.md diff --git a/Ettiqute.md b/Ettiqute.md new file mode 100644 index 0000000..b4c5b5f --- /dev/null +++ b/Ettiqute.md @@ -0,0 +1,6 @@ +Things are quite simple ettiqute wise: +* Keep conversations tangentally related to an issue or PR. If you notice there is a new problem, don't comment it on another issue, create a new issue. +* Check for duplicate issues or PRs before making a new one, if you have more information about an issue or PR, simply comment it on an open issue/PR. If your issue is grander in scope, but includes an old issue, make said issue anyway (i.e if theres a broken sprite, but you found multiple broken sprites including that first broken sprite, then make a new issue with the greater number of issues enumerated). +* Alert others when you are working on something. If know one knows your working, they may pick up the job and then you'll end up with redundant code. Best to be effective and save time, communicate. +* Avoid pushing to master unless said push is absoltely nessecary. A merge between an update/patch branch and the master to make it the new stable, or the update is to something like documentation or licensing are fine though. This is to keep master always stable and of our last release. +* Over all, just be responsive and cordual whenever possible. Don't shy away from speaking because you're unsure. Don't be afraid to be corrected, don't be afraid to give corrections, don't be afraid to critique. Simple as, just be a rational person. \ No newline at end of file