I think that badges make more sense; paying a content bounty is an interesting idea, but it could also yield super low quality work, not to mention an enormous amount of work to review and test user submissions ----- Original Message ----- From: Stefan Arentz <[email protected]> To: Matthew R. MacPherson <[email protected]> Cc: [email protected], apps <[email protected]>, [email protected], [email protected] Sent: Mon, 24 Feb 2014 09:16:50 -0800 (PST) Subject: Re: Strong recommendations to help developers make better apps
Those mortar templates are great. Btw we do have a successful bounty program in place for security related issues. We pay a lot of money each year to people who contribute to that program. So I don't think it is that crazy or not in the spirit of Mozilla to also do something similar for documentation contributors. And the submissions would not be completely random of course. They would have to be on topic to be useful. We can have a list of things we would like to see written. And coordinate so that people don't work on duplicate things. This is also what Digital Ocean does. You first submit a proposal. (Which is really 'i want to write XYZ. Ok?') S. ----- Original Message ----- > This is a project we're working on with mortar templates, but I don't random > mini bounties are in the spirit of Mozilla. _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
