Open
Description
@http-party/create-servers @http-party/http-proxy @http-party/http-server @http-party/portfinder Creating this issue here because there isn't an "org wide issue" concept in Github.
The http-party
organization was created this year so we could focus on process & governance for for these popular HTTP-related projects once with enough folks to get a decent consensus.
Processes like:
- How do we cut releases?
- How do we prioritize features? (like what I said above – prefer stability over change)
- How do you become a maintainer?
- What's expected of maintainers?
- How do we better maintain – e.g. Issue / PR templates, etc.
- How do we do roadmaps?
- How do we do CHANGELOGs?
- n.b. @jsmylnycky did a great job with his recent PR to get this project up to date with any sort of
CHANGELOG.md
. That said going forward we may need something slightly cleaner – or go full hog on that like actually adoptingsemantic-release
.
- n.b. @jsmylnycky did a great job with his recent PR to get this project up to date with any sort of
... so ... how do y'all want to handle this? One great recent change to Github is the .github
repository functionality. Feels like we can leverage that for PR / Issue templates at least.
Metadata
Metadata
Assignees
Labels
No labels