Skip to content

come up with a good message to set context for contributions #2

@travi

Description

@travi
  • make it very clear that we have very little bandwidth and no budget for maintenance and that one of our primary goals is to keep effort to a minimum so that we don't drop important responsibilities
  • our first priority is making sure we have meetings organized each month
  • maintaining other stuff is secondary to that primary goal
  • maintenance effort will usually be given to tasks that reduce the effort of the first goal over other tasks
  • we welcome help from the community, but are careful to protect ourselves from contributions that will complicate maintenance efforts once the contributor has moved on
  • it is a good idea to give us a heads up about a contribution early so we can make sure we're on the same page and would accept the contribution. having a conversation with the maintainers by opening an issue before putting effort into a PR, etc is a great way to help the process go smoothly

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions