(Note that the resolution was approved, clarification, more info.)
(removed draft status and intro, framework adopted by board on 2020-07-30 https://wiki.osmfoundation.org/wiki/Board/Minutes/2020-07#Adopting_the_hiring_framework)
|(One intermediate revision by the same user not shown)|
== Scope of paid work ==
Our priority is to keep OpenStreetMap’s core systems running smoothly. We‘re prepared to make use of paid work towards this end.
== Implementation ==
We prefer implementations of paid work which keep our administrative overhead low and give us access to talent from our international community. Our focus will be on:
* contracting with firms
When contracting with firms, we will still apply the considerations described below to the individuals who would end up doing the work.
== Relationship with volunteers ==
OSM has given rise to a vibrant decentralized ecosystem. We want workers paid by the OSMF to collaborate seamlessly with volunteers and commercial actors. Workers will cooperate remotely, and through the same platforms that volunteer contributors to that team or project also have access to.
Before deciding on paying additional people, the OSMF board will consider whether volunteers are available to fill the role, whether the activity falls within the scope of the OSMF’s mission, and whether the Foundation ought to offer (or continue offering) a particular service. The intention to enlist additional paid work, along with a job description and the board’s reasoning, will be publicly shared and discussed with the community. The board will assess community support by informal consultation before proceeding.
Workers will occasionally produce high-level reports on what they have achieved and spent their time on. To encourage transparency, these reports must be visible to the OSM community, not just to the OSMF board of directors. Workers cannot be expected to accommodate each community member, but we expect them to keep an ear on the OSMF’s community channels in general. They should not limit their communications to fellow team members and OSMF institutions.
If a contract ends, including because a worker becomes unavailable, it should not be replaced as a matter of routine. We will be mindful of the risk of organizational bloat.