search

mochajs / admin

Project admin, governance, etc.
Apache License 2.0
1 stars 2 forks source link

create expense policy #5

Open boneskull opened 5 years ago

boneskull commented 5 years ago

So, we have some money. But mostly we're not using it. Let's figure out how to do that.

Here's Gulp's expense policy, for example: https://github.com/gulpjs/gulp/blob/master/EXPENSE_POLICY.md

Gulp's seems OK, but I think it can be improved upon for us. Is anyone interested in creating bug bounties?

The main thing I like is this: To be paid for work, the maintainer must create a proposal first. To accept a proposal, we'll need to define what a "quorum" looks like, because we can't expect every maintainer to weigh in on every proposal.

cc @mochajs/core

juergba commented 5 years ago

We could support some of our dependencies / services we use for free like Travis or Appveyor. This could be done by signing a fee-based service plan or by sponsoring an amount. More than a few of our dependencies are maintained weakly (eg Appveyor, Yargs), maybe we could help that way.

Sometimes I wonder who pays the bill at the end of the chain, when everything is free on the internet like music, films, education, software ...

craigtaub commented 5 years ago

Agree with @juergba.

Bug bounties, supporting dependencies and significant changes (perhaps min 3 core members per proposal?) all sound good uses IMO. We could trial a bug bounty and see how it goes.

Also "significant changes" could include "critical fixes" e.g a major release includes broken feature and somebody loses out on personal plans to fix it. Be good to outline what would need to be defined pre code change and what post.

outsideris commented 5 years ago

Supporting dependencies is a great idea.