Voting points

Voting points are intended to give you a voice in decisions over priorities in the development of MediaArea tools. Each person with voting points get points that they can assign to a task. After a task has been completed, voting points given towards a task are applied. For example, if a person has 10 points and assigns 2 points to a task, then those points are used only when the task is complete and a person has 8 points remaining. MediaArea will then check which task has the better ratio between points and the cost of a task, and select the next task to work on.

You can see the features list here.

How useful is a single membership (without voting points)?

At the moment, a single membership is a way to show your support and improve MediaArea tools. In the future, contingent on voting, you will get access to more members-only features.

Where does the money go?

MediaArea is an open source organization and works in the open as much as possible. Because of this, we also want to be as transparent as possible with our budget so you can better understand where your money goes. Below is an average estimated annual budget for maintaining and expanding tools we are working on (excluding specific projects):

StaffFR 170 k€/year (3 full-time), US 40 k€/year (partial time)
Hardware/Hosting (including test files backup)15 k€/year
Travel/Meetings10 k€/year
Legal/Administrative10 k€/year
Bank fees5 k€/year

Total250 k€/year

About MediaArea

MediaArea.net SARL (equivalent to LLC) is a French based company founded in 2007 (official source) and selling professional services for 10 years, held at 100% by Jérôme Martinez and with a shareholders’ equity of 125 000 € (public source, and you can order official detailed annual reports from the official source for 6 €).

Severity levels

Critical: production server is blocked and no workaround is immediately available. Substantial portion of critical data is at a significant risk of loss or corruption. Business operations are severely disrupted. Example: a new incoming file makes the server crashing.
Major: operations can continue in a restricted mode, although productivity is adversely affected. A temporary workaround is available. Example: a format feature is expected to be detected but is not, a file is considered not compliant but is actually compliant
Minor: non-critical loss of functionality. Example: text typo