Organization &

Code of Honor

Community

We want a productive, happy and agile community that can welcome new ideas in a complex field, improve every process every year, and foster collaboration between groups with very different needs, interests and skills.

We gain strength from diversity of ideas, and actively seek participation from those who enhance it. This code of honor exists to ensure that groups collaborate to mutual advantage and enjoyment. We will challenge each other in good faith so that we may grow and perform at our best.

The Code of Honor governs our general conduct with Vircadia. We expect it to be honored by everyone who represents the project officially or informally, claims affiliation with the project, or participates directly.

Axiom of Reason

To execute a code of honor that is fair to all involved parties, the measure for compliance and violation cannot be subjective but rather objective. More than that, it must be reasonable and hold to truths in the world.

Disagreements, social and technical, are normal, but we do not allow them to persist and fester leaving others uncertain of the agreed direction.

We expect participants in the project to resolve disagreements constructively. When they cannot, we escalate the matter to structures with designated leaders to arbitrate and provide clarity and direction.

To achieve the unthinkable, we must be exceptional. To be exceptional, we must be able to grow as individuals, and together. We must be able to trust in one another for the journey.
Failure is an option that we must not take.

Duty of Respect

Disagreement is no excuse for poor manners. We work together to resolve conflict, assume good intentions and do our best to act in an understanding fashion. A community where people feel uncomfortable or threatened is not a productive one.

Being generally civil and respectful is paramount to helping keep cool heads and to allow for opportunities of recourse and understanding. Make a reasonable and conscious effort to foster this sort of environment. Be kind, be fair, be grounded, be reasonable.

Freedom to Act & Interact

Outside the sphere of the community, we lead our own lives. Given that said activities are not a direct & immediate threat to the effort or a direct counter to the core principles of an open and free metaverse (decentralized, no censorship), then these affairs must be considered private and non-actionable.

For personal matters that may harm or affect the project, you may not claim to be representing the project, rather you must make clear that these are your own opinions.

Taking care to ensure that the project’s future paths are accounted for should be a priority, you are expected to take this into consideration whenever possible when taking any action.

We Are an Open Meritocracy

We invite anybody, from any company, to participate in any aspect of the project. Our community is open, and any responsibility can be carried by any contributor who demonstrates the required capacity and competence.

Contribution may never be rejected on the basis of the person submitting it. All contributions should be evaluated by the merit of their content.

Project Representation

While the goal is a FLOSS, decentralized, and uncensorable metaverse, the Vircadia project still follows some centralized conventions for its organization and representation.

For example, representing the Vircadia project publicly (e.g. social media, etc.) or as an agent/representative requires permission from the Founder & Project Lead (FPL).

If you are no longer affiliated with the project as a contributor or collaborator, you may not represent yourself as being a part of the Vircadia project.

This applies to using any branding marks, trademarks, logos, and similar.

These are the standards of honor and respect that we must hold ourselves to.

Responsibility of Leadership

We all lead by example, in debate and in action. We encourage new participants to feel empowered to lead, to take action, and to experiment when they feel innovation could improve the project. Leadership can be exercised by anyone simply by taking action, there is no need to wait for recognition when the opportunity to lead presents itself.

Delegation

The Founder & Project Lead delegates specific responsibilities and the corresponding authority to the Core Maintainers (CM). They then delegate to a series of teams and individuals.

We are a meritocracy; we delegate decision making, governance and leadership from senior bodies to the most able and engaged candidates.

Measured Delegation

Nominations to teams and councils are at the discretion of the Core Maintainers, however the Core Maintainers will seek the input of the community before confirming appointments.

Leadership is not an award, right, or title; it is a privilege, a responsibility and a mandate. A leader will only retain their authority as long as they retain the support of those who delegated that authority to them.

Teamwork

A leader’s foremost goal is the success of the team.

“A virtuoso is judged by their actions; a leader is judged by the actions of their team.” A leader knows when to act and when to step back. They know when to delegate work, and when to take it upon themselves.

Unity & Collaboration

What we produce is a complex whole made of many parts, it is the sum of many dreams. Collaboration between teams that each have their own goal and vision is essential; for the whole to be more than the sum of its parts, each part must make an effort to understand the whole.

Collaboration reduces redundancy and improves the quality of our work. Internally and externally, we celebrate good collaboration. Wherever possible, we work closely with upstream projects and others in the free software community to coordinate our efforts. We prefer to work transparently and involve interested parties as early as possible.

Discussion & Decisiveness

We gather opinions, data and commitments from concerned parties before taking a decision. We expect leaders to help teams come to a decision in a reasonable time, to seek guidance or be willing to take the decision themselves when consensus is lacking, and to take responsibility for implementation.

No Poor Decisions

The poorest decision of all is no decision: clarity of direction has value in itself. Sometimes all the data are not available, or consensus is elusive. A decision must still be made. There is no guarantee of a perfect decision every time – we prefer to err, learn, and err less in future than to postpone action indefinitely.

Reasoned & Principled

We recognise that the project works better when we trust the teams closest to a problem to make the decision for the project. If we learn of a decision that we disagree with, we can engage the relevant team to find common ground, and failing that, we have a governance structure that can review the decision based on the facts of the situation. Ultimately, if a decision has been taken by the people responsible for it, and is supported by the project governance, being backed by principle and reason, it will stand. None of us expects to agree with every decision, and we value highly the willingness to stand by the project and help it deliver even on the occasions when we ourselves may prefer a different route.

Organization

This is not a democracy, it’s a meritocracy. We try to operate more on consensus than on votes, seeking agreement from the people who will have to do the work.

All members of the community are expected to adhere to the Code of Honor, acting diligently and with respect to themselves and their peers.

We are all collaborators.

Founder & Project Lead

The Founder & Project Lead (FPL) has the responsibility to unify the project towards the shared goal of metaverse. To this end, they will continue to maintain guidelines and general direction for forward motion on this path with the collaborative community as a whole.

This person delegates specific authority and responsibility on the project to the Core Maintainers. The FPL will make the final decision on disputed cases, however this is usually not necessary. Normally, the FPL will break grid-locks when a quorum (⅔ of CMs) cannot reach an agreement.

Secondary to being the FPL, this person has the role and responsibility of a CM as well.

Core Maintainers

A Core Maintainer is appointed by the Project Lead in consultation with the other CMs.

A Core Maintainer does not have to be a developer. Core Maintainers are tasked with the responsibility of guiding and contributing to the project in all aspects, delegating and deferring as needed. The CMs represent the project and therefore act accordingly.

A Core Maintainer is expected to adhere to the Code of Honor. If significant problems arise with a CM then the FPL in conjunction with the other CMs will decide on an appropriate course of action to take, and if necessary, dismissal may be warranted. All procedures and guidelines are not directly codified as it is the general belief that merit and honor should be upheld at all times. Actions by Core Maintainers should be taken with this consideration at the forefront.

A Core Maintainer’s responsibilities are greater than that of a typical collaborator. Their support and dedication is expected and relied upon.

Collaborators & Community

The collaborators and community contribute code, feedback, and in general their presence to the project.

Their contributions are essential to the growth and life of the metaverse as it springs into existence slowly but surely.

The community is given a strong foundation to stand on by Vircadia’s various collaborators. We work together to ensure that the community can help shape the future that we all dream of.

”  When we dream alone it is only a dream, but when many dream together it is the beginning of a new reality. “

Friedensreich Hundertwasser

 

Adapted from the Ubuntu Code of Conduct 2.0