Okay, I've been working on this for a while but need to get an initial version posted so we can iterate on it. If anyone (particularly existing collaborators, but really open to anyone who happens to stop by) can give some feedback on this it'd be greatly appreciated.
Notes:
Fixes #68 (for now) and fixes #139
Does not resolve (yet) #117-- I don't have great answers about how to run Mastodon locally, to be honest, because I find it difficult and haven't done it very much
I'm erring on the side of putting as much as possible in the actual .md/repo for now since discussing stuff via PR is easier for getting feedback. If things crystallize here I may at some point in the future extract some portion of this into the wiki and then link to it from the CONTRIBUTING.md, but for now you get a giant info dump in one file.
Thanks to @andypiper for suggesting the Contributors' Covenant in #139; they also volunteered to be an alternate point of contact for CoC violations in that discussion and I'll add an email address (or whatever preferred contact method) once they share that!
also contains a fix to the LICENSE file that included some Glitch-provided mentions of other libraries and dependencies, many of which we aren't even using any more; I don't know what obligation we have to include that info in our LICENSE file but even if that is a requirement there's no point in including the wrong info
My eyes started glazing over today while trying to document the development process with as few assumptions about someone's knowledge of things like npm, eslint, etc. as possible, so please let me know if something seems wrong there or if I got distracted by my dogs and left off the end of a sentence or something.
I was having a discussion with some other folks at Glitch last week about ways we can make it easy for people to pull in changes to their Glitch project from the Git repo after they've remixed it; I'm excited about some stuff that might come out of that but it might make sense in a followup to write/link to some information about setting up this repo as an upstream remote in your install and pulling in new changes as we release them 🤔
Okay, I've been working on this for a while but need to get an initial version posted so we can iterate on it. If anyone (particularly existing collaborators, but really open to anyone who happens to stop by) can give some feedback on this it'd be greatly appreciated.
Notes: