|
| 1 | +--- |
| 2 | +layout: usage |
| 3 | +title: Quarkus at CommonHaus FAQ |
| 4 | +subtitle: Frequently Asked Questions |
| 5 | +permalink: /foundation/faq |
| 6 | +--- |
| 7 | + |
| 8 | +## Why move to a foundation? |
| 9 | + |
| 10 | +Enable us to welcome more contributions from a diverse range of developers and organisations. |
| 11 | + |
| 12 | +## Which Quarkus projects are moving to a foundation? |
| 13 | + |
| 14 | +Initially, all projects under the https://github.com/quarkusio organisation. |
| 15 | +Future consideration would apply to parts or all of Quarkiverse and Quarkus Tools projects. |
| 16 | + |
| 17 | +## What is Commonhaus? |
| 18 | + |
| 19 | +See https://www.commonhaus.org/. |
| 20 | + |
| 21 | +## Why Commonhaus? |
| 22 | + |
| 23 | +The main reason for choosing Commonhaus over another foundation was its governance framework, which emphasises project self-governance. |
| 24 | +See, in particular, its guiding principles. |
| 25 | + |
| 26 | +## Why not [put your favourite foundation here]? |
| 27 | + |
| 28 | +See Commonhaus’ own [FAQ](https://www.commonhaus.org/about/faq.html). |
| 29 | + |
| 30 | +## What does the move consist of exactly? |
| 31 | + |
| 32 | +The move consists of donating intellectual property owned by Red Hat and related to Quarkus projects. |
| 33 | +The donated intellectual property includes in particular: |
| 34 | + |
| 35 | + * the Quarkus trademark; |
| 36 | + * related domain names. |
| 37 | + |
| 38 | +It does not include copyright, since Red Hat does not have exclusive claims to copyright on Quarkus code. |
| 39 | + |
| 40 | +## Is Red Hat reducing funding for Quarkus development? |
| 41 | + |
| 42 | +No. |
| 43 | + |
| 44 | +## How is Red Hat’s involvement in Quarkus changing? |
| 45 | + |
| 46 | +Red Hat’s involvement in Quarkus remains as strong as ever. |
| 47 | + |
| 48 | +The Quarkus team is expecting increased collaboration between Red Hat and other companies, which may require setting time aside to get new contributors on board. |
| 49 | + |
| 50 | +## What is changing in practice for contributors to Quarkus projects? |
| 51 | + |
| 52 | +Commonhaus requires Quarkus to adhere to its [policies](https://www.commonhaus.org/policies/), including in particular its [intellectual property policy]https://www.commonhaus.org/policies/ip-policy/) and [trademark policy](https://www.commonhaus.org/policies/trademark-policy/). |
| 53 | + |
| 54 | +This is great news for you all, as it legally binds the project to remain open-source forever. |
| 55 | + |
| 56 | +Commonhaus also requires having a code of conduct, and provides a recommended one, but each project has flexibility on such details so we could decide to customise it. |
| 57 | + |
| 58 | +Quarkus contributors can opt to become Commonhaus Members; this is not a requirement to participate in the Quarkus project but is a requirement to help define Commonhaus. |
| 59 | + |
| 60 | +The project’s core contributors, internal governance and processes remain the same. |
0 commit comments