Skip to content
This repository was archived by the owner on Aug 28, 2025. It is now read-only.
This repository was archived by the owner on Aug 28, 2025. It is now read-only.

Try to determine (multiple?) fair remuneration methods for contribution #5

@jayaddison

Description

@jayaddison

Is your feature request related to a problem? Please describe.
RecipeRadar would like to exist for a long time and build gradually, without time pressure on any participants, and with fair and worthwhile rewards for contributions. Some people seem to enjoy writing software and providing it (and their time) to the community for free. Other people, equally fairly, determine that their time has a value that they'd like to maximize relative to a currency.

OpenCulinary C.I.C. (the company entity that exists to develop and support RecipeRadar) is backed by 65536 (2^16) shares, currently all held by the sole director (me). I'm not sure whether I want any of those really, long-term - I just want the project to be successful, where success metrics include improving education, meal nutrition and enjoyment of food at economically effective prices.

RecipeRadar should always be optional and should be completely free (and libre), modifiable and adaptable. It may generate revenue, although it doesn't yet, and it must not violate user privacy in order to do so.

Under these conditions, what is a good model to incentivize participation and contribution to RecipeRadar? Is it possible to measure contribution value, or does attempting that measurement only create friction? Are there similarities with salary and compensation transparency?

Describe the solution you'd like
Uncertain, but it should make almost all contributors feel like they have a good deal, and that they're happy to be involved. Moreso, they should feel like they can change the terms of their contribution and participation should their lifestyle, circumstances and opinions change over time.

Describe alternatives you've considered
(still under consideration) OpenCollective seems popular in this kind of direction. At the same time, it'd be worth trying to avoid non-optimal situations like mochajs/mocha#4467

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions