More stability for the existing contributors can be provided by securing a permanent WuppSpace, which would be financed by the Core Team members themselves and donations and/or loans from friends and family (estimations on how much money can be generated this way and clear statements on which amount to spend at max. is deemed acceptable by yuniteers would be needed!).

More speed towards the first release can be generated by minimalizing the specifications to initially only develop a foodsaving tool, which manages store pick-ups for international communities. The elaborate hierarchical structure of the German foodsharing.de page would not be replicated. This lean tool could then be tested by existing foodsharing communities, who as of now don't have access to any specialized software to help them organize their endeavors and therefore would probably be glad to be part of the testing group - even knowing that there will be bugs and downtimes.

As soon as the international foodsaving tool is ready and data is generated, we'd have something to show and to expand and would be able to effectively integrate new developers. Those do not necessarily need to be paid! The first step would be to promote the existing software directly to developers and hope to find some willing to work without pay because of enthusiasm for the idea. To use money to regularly pay them would not be considered before having thoroughly explored the possibilities to acquire a development team through the connection established via our vision and mission and the stability given by a permanent WuppSpace! (Exact timeframes and the definition of terms like 'thoroughly explore' - of course - need further clarification, which would be given if this general approach was to be supported by the group.)

Due to a modular structure the development of a lean foodsaving tool would not contradict the bigger vision of yunity: It is supposed to be build in a way that allows for further features to be added and larger amounts of data to be processed without the whole software having to be rebuild when the demand arises.

Advantages

more releasing and testing ensures software quality and the relevance of the approach
having something to play with attracts new developers
having smaller short-term goals motivates the existent developers
builds on the existing programming work already done
speeds up the internationalization of foodsharing by giving existing communities a functional foodsaving tool to use
generates data on how fast users flow in and how they use the tool
only clarifies the approach for a relatively short period of time (~6 months)

Disadvantages

before having the lean foodsaving tool new devs would probably not be integrated
the needs of the German foodsharing community are ignored for now
does not address the health insurance issue
only clarifies the approach for a relatively short period of time (~6 months)

Browser not supported