Skip to content

Improving processes for all of http-party, including http-proxy #1383

@indexzero

Description

@indexzero

@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:

  1. How do we cut releases?
  2. How do we prioritize features? (like what I said above – prefer stability over change)
  3. How do you become a maintainer?
  4. What's expected of maintainers?
  5. How do we better maintain – e.g. Issue / PR templates, etc.
  6. How do we do roadmaps?
  7. 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 adopting semantic-release.

... 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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions