s/hostea/gna/ last batch
ci/woodpecker/push/woodpecker Pipeline was successful Details

Signed-off-by: Loïc Dachary <loic@dachary.org>
master
Loïc Dachary 2022-09-07 00:50:59 +10:00
parent 52d8914d56
commit 3b8d3862f9
Signed by: dachary
GPG Key ID: 992D23B392F9E4F2
8 changed files with 11 additions and 11 deletions

View File

@ -2,7 +2,7 @@
<img width="80px" alt="Gna! logo" src="./static/gna-logo-rectangle.png" />
<h1>Gna! Website</h1>
[![status-badge](https://woodpecker.gna.org/api/badges/Hostea/website/status.svg)](https://woodpecker.hostea.org/Hostea/website)
[![status-badge](https://woodpecker.gna.org/api/badges/Gna/website/status.svg)](https://woodpecker.gna.org/Gna/website)
[![AGPL License](https://img.shields.io/badge/license-AGPL-blue.svg?style=flat-square)](http://www.gnu.org/licenses/agpl-3.0)
</div>
@ -37,7 +37,7 @@ Build artifacts should be available in `./public/`
This repository uses [Gna!
Woodpecker-CI](https://woodpecker.gna.org/) to build and
[Hostea/Pages](https://gitea.gna.org/Hostea/pages) to deploy on each
[Gna/Pages](https://gitea.gna.org/Gna/pages) to deploy on each
commit.
To setup the CI:

View File

@ -15,4 +15,4 @@ If you are into trouble and need assistance with a Gitea instance not hosted at
---
Do you already have an expertise running Gitea? You are welcome to join the [Gna! collective](https://forum.gna.org/t/57), get in touch [in the forum](https://forum.hostea.org/c/site-feedback/2) or [the chat](https://matrix.to/#/#hostea:matrix.batsense.net).
Do you already have an expertise running Gitea? You are welcome to join the [Gna! collective](https://forum.gna.org/t/57), get in touch [in the forum](https://forum.gna.org/c/site-feedback/2) or [the chat](https://matrix.to/#/#hostea:matrix.batsense.net).

View File

@ -17,7 +17,7 @@ Hosting a Gitea instance on Gna! is now possible (but still experimental). It is
The service is 100% infrastructure as code, published as [Ansible playbooks within Enough](https://lab.enough.community/main/infrastructure/-/tree/9e18ebbf675c8a65d1585d20b4cf6295af6e52ed/playbooks/hosteadashboard). It can be self-hosted on bare metal (with [libvirt](https://libvirt.org/)) or in the cloud (with [OpenStack](https://www.openstack.org/)): follow the [quick start](https://enough-community.readthedocs.io/en/latest/introduction.html#quick-start), configure playbooks for [hostea](https://enough-community.readthedocs.io/en/latest/services/hostea.html) and [the dashboard](https://enough-community.readthedocs.io/en/latest/services/hosteadashboard.html).
The organization supporting Gna! is a [horizontal collective](https://forum.gna.org/c/governance-and-decisions/7) of individuals and organizations. The [revenue sharing model](https://forum.hostea.org/t/decision-revenue-sharing-model/92) is set to dedicate 25% of the income (more than the profits) to help the Free Software projects Hostea depends on such as Gitea, Enough, Django etc.
The organization supporting Gna! is a [horizontal collective](https://forum.gna.org/c/governance-and-decisions/7) of individuals and organizations. The [revenue sharing model](https://forum.gna.org/t/decision-revenue-sharing-model/92) is set to dedicate 25% of the income (more than the profits) to help the Free Software projects Hostea depends on such as Gitea, Enough, Django etc.
### The origin
@ -35,7 +35,7 @@ To keep the madness contained and enjoyable, it was decided to set a deadline to
### A horizontal collective with a revenue sharing model
Another goal of Gna! is to deploy federated forges, even at an experimental stage. Instead of creating a centralized organization to support Hostea, it was decided to create [horizontal collective](https://forum.gna.org/c/governance-and-decisions/7). It feels like a contradiction for a project committed to decentralization to be governed by a centralized organization.
Another goal of Gna! is to deploy federated forges, even at an experimental stage. Instead of creating a centralized organization to support Gna!, it was decided to create [horizontal collective](https://forum.gna.org/c/governance-and-decisions/7). It feels like a contradiction for a project committed to decentralization to be governed by a centralized organization.
The collective is composed of individuals and organizations but, unlike exclusively volunteer based Free Software projects, it is for profit. Customers rent Gitea instances by the month and the income is used to pay for expenses. There is however a difficulty: by nature a horizontal collective cannot be incorporated as it would create a level of hierarchy. The [revenue sharing model](https://forum.gna.org/t/decision-revenue-sharing-model/92) had to be set as an informal agreement between members where one of them receives the income and distributes it to the others, depending on their Gna! related expenses.

View File

@ -8,8 +8,8 @@ description = "Code of Conduct"
* **Be friendly, patient and welcoming.** We strive to be a collective that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion and mental and physical ability.
* **Be considerate.** Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should take those consequences into account when making decisions. Remember that we're a world-wide community and we have a global base of users and of contributors. Even if it's not obvious at the time, our contributions to projects managed by the Gna! collective will impact the work of others.
* **Be respectful.** Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. Its important to remember that a collective where people feel uncomfortable or threatened is not a productive one. Members of the collective should be respectful when dealing with other contributors as well as with people outside of the collective and with users of the projects managed by Gna!.
* **Collaborate openly.** Collaboration is central to projects managed by Gna! and to the larger free software community. This collaboration involves individuals working within teams, cross-project collaboration within Hostea and working with other projects outside of Hostea. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream and downstream projects and others in the free software community to coordinate our technical, advocacy, documentation and other work. Our work must be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress. We do not create private forms of communication that take away transparency or exclude other contributors and collaborators.
* **When we disagree, try to understand why.** Disagreements, both social and technical, happen all the time and Gna! is no exception. It is important that we resolve disagreements and differing views constructively. Remember that were different. The strength of Hostea comes from people with a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesnt mean that theyre wrong.
* **Collaborate openly.** Collaboration is central to projects managed by Gna! and to the larger free software community. This collaboration involves individuals working within teams, cross-project collaboration within Gna! and working with other projects outside of Gna!. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream and downstream projects and others in the free software community to coordinate our technical, advocacy, documentation and other work. Our work must be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress. We do not create private forms of communication that take away transparency or exclude other contributors and collaborators.
* **When we disagree, try to understand why.** Disagreements, both social and technical, happen all the time and Gna! is no exception. It is important that we resolve disagreements and differing views constructively. Remember that were different. The strength of Gna! comes from people with a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesnt mean that theyre wrong.
* **Focus on helping to resolve issues and learning from mistakes.** It is important that we resolve disagreements and differing views constructively and with the help of the collective. When our goals differ dramatically, we encourage the creation of alternative implementations, so that the collective can test new ideas and contribute to the discussion.
* **When we are unsure, we ask for help.** Nobody knows everything, and nobody is expected to be perfect in Gna!. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum.

View File

@ -14,7 +14,7 @@ You can get help from the community on the [Gna! forum](https://forum.gna.org/c/
## How much does it cost?
All Gna! doctors charge a flat hourly rate for consultations held in public (sensitive information is never revealed, even if the consultation is held in public). Private consultations fees depend on the Hostea doctor.
All Gna! doctors charge a flat hourly rate for consultations held in public (sensitive information is never revealed, even if the consultation is held in public). Private consultations fees depend on the Gna! doctor.
## Gna! Doctors
{{ gitea_clinic_doc_reviews() }}

View File

@ -17,7 +17,7 @@ There is no warranty for the service, to the extent permitted by applicable law.
## Limitation of Liability
In no event unless required by applicable law or agreed to in writing will any member of the Gna! community, or any other party who modifies the service as permitted by Hostea, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use the service (including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the service to operate with any other service), even if such member or other party has been advised of the possibility of such damages.
In no event unless required by applicable law or agreed to in writing will any member of the Gna! community, or any other party who modifies the service as permitted by Gna!, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use the service (including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the service to operate with any other service), even if such member or other party has been advised of the possibility of such damages.
## Interpretation of the Warranty and Liability disclaimers

View File

@ -13,7 +13,7 @@ All applications and infrastructure software used in Gna! are published under a
Gna! has no copyright claim over content uploaded by its users.
Gna! hosts, via application software, content in private spaces that are not publicly accessible. Hostea system administrators are committed to not look into those private spaces, even when they have the technical ability to do so, to respect the users privacy.
Gna! hosts, via application software, content in private spaces that are not publicly accessible. Gna! system administrators are committed to not look into those private spaces, even when they have the technical ability to do so, to respect the users privacy.
## Support

View File

@ -44,7 +44,7 @@
<a href="/privacy-policy" title="Privacy Policy">Privacy</a>
<span class="footer__column-divider--mobile-only">|</span>
<a
href="https://gitea.gna.org/Hostea"
href="https://gitea.gna.org/Gna"
rel="noreferrer"
target="_blank"
title="Status"