Manjaro 2.0 Manifesto

[Aragorn]

@philm

Any transfers of company assets or infrastructure require close consultation with the company and yet to be established new legal entity, in order to ensure that the interests of both parties are safeguarded as amicably and smoothly as possible.

Agreed.

@philm

Any actions that could damage the business must be ruled out.

It is most definitely not our intent to harm the business. What would be the purpose of that?

@philm

To ensure the smooth operation of the company, assets relevant to the company will remain within the company.

It does not have to be that way. In the document, we have explicitly specified that the Manjaro GmbH may continue using the infrastructure of the Manjaro e.V. until the Manjaro GmbH has managed to migrate its own infrastructure requirements away from the e.V.'s infrastructure.

We see no problem with that.

@philm

Finally, I would like to note that any actions or comments that could damage the business or reputation of myself or the company should be refrained from in order to ensure a mutually agreeable process and avoid legal actions.

Our intentions have always been noble and honorable. As @dennis1248 said…

@dennis1248

To make it extra clear, the goal is NOT to remove anyone from the project, we only hope to see a change is leadership and to again turn Manjaro in to a proper healthy community project. The project is dying, radical change is needed to save it.

We even hope to continue working with yourself as an individual, and we do sincerely appreciate and respect your technical contributions to the Project, but at the same time, it is abundantly clear to everyone that the way things are being run right now is only going to lead to a downfall, for both Manjaro as a GNU/Linux distribution and the Manjaro GmbH.

In fact, we believe that the proposed change in the organizational structure is going to benefit us all.

Always remember, @philm, that the whole can be greater than the sum of its parts. Right now it’s the other way around, due to the bottleneck imposed by the current organizational structure.

That all said, I believe @romangg’s post below deserves a sincere reply.

@romangg

Thank you Philip for your participation in this discussion and your general agreement in that a Manjaro association should be founded.

You say that any “transfers of company assets or infrastructure require close consultation with the company”. But the above document already provides a precise list of assets, that are supposed to be moved into the association:

@Aragorn

• The Manjaro Linux, Manjaro-Kernels and Manjaro-ARM GitHub organizations.
• The self-hosted Manjaro GitLab.
• Any relevant Git repositories.
• The manjaro.org domain.
• The Manjaro forum.
• Relevant Manjaro cloud organizations at for example Hetzner.
• The Manjaro CDN.
• Community finances and donations, such as OpenCollective.
  […]

From my perspective I don’t see an issue with these assets being moved into the association, do you?