mirror of
https://gitlab.computer.surgery/matrix/grapevine.git
synced 2025-12-17 15:51:23 +01:00
rearrange introduction
I think it's most important for people to read the "Chat with us", "Can I use it?" and "Expectations management" sections, though I'm not sure what the best ordering is. This is probably fine.
This commit is contained in:
parent
5c4d7bbe37
commit
8537c0e8ac
1 changed files with 24 additions and 26 deletions
|
|
@ -21,6 +21,30 @@ If you'd like to engage in or observe any of those things, please join!
|
||||||
|
|
||||||
[room]: https://matrix.to/#/#grapevine:computer.surgery
|
[room]: https://matrix.to/#/#grapevine:computer.surgery
|
||||||
|
|
||||||
|
## Can I use it?
|
||||||
|
|
||||||
|
Theoretically yes, but it's not ready for general use yet, because:
|
||||||
|
|
||||||
|
* [There aren't any releases][releases-issue].
|
||||||
|
* [There isn't very much user-facing documentation][docs-issue].
|
||||||
|
* There have been several additions and breaking changes to the configuration
|
||||||
|
file format that haven't been documented in detail. This means you'll need to
|
||||||
|
read the source code to figure out what all the options are and what they do.
|
||||||
|
|
||||||
|
If these issues don't scare you away, go for it! (And if you use NixOS, [here's
|
||||||
|
an example][nixos-example].)
|
||||||
|
|
||||||
|
[docs-issue]: https://gitlab.computer.surgery/matrix/grapevine/-/issues/21
|
||||||
|
[releases-issue]: https://gitlab.computer.surgery/matrix/grapevine/-/issues/18
|
||||||
|
[nixos-example]: https://gitlab.computer.surgery/charles/servy-fleet/-/blob/main/config/grapevine/default.nix
|
||||||
|
|
||||||
|
## Expectations management
|
||||||
|
|
||||||
|
This project is run and maintained entirely by volunteers who are doing their
|
||||||
|
best. Additionally, due to our goals, the development of new features may be
|
||||||
|
slower than alternatives. We find this to be an acceptable tradeoff considering
|
||||||
|
the importance of the reliability of a project like this.
|
||||||
|
|
||||||
## Goals
|
## Goals
|
||||||
|
|
||||||
Our goal is to provide a robust and reliable Matrix homeserver implementation.
|
Our goal is to provide a robust and reliable Matrix homeserver implementation.
|
||||||
|
|
@ -81,32 +105,6 @@ We require at least 1 approving code review from a maintainer[^2] before changes
|
||||||
can be merged. This number may increase in the future as the list of maintainers
|
can be merged. This number may increase in the future as the list of maintainers
|
||||||
grows.
|
grows.
|
||||||
|
|
||||||
## Expectations management
|
|
||||||
|
|
||||||
This project is run and maintained entirely by volunteers who are doing their
|
|
||||||
best. Additionally, due to our goals, the development of new features may be
|
|
||||||
slower than alternatives. We find this to be an acceptable tradeoff considering
|
|
||||||
the importance of the reliability of a project like this.
|
|
||||||
|
|
||||||
## Can I use it?
|
|
||||||
|
|
||||||
Theoretically yes, but it's not ready for general use yet, because:
|
|
||||||
|
|
||||||
* [There aren't any releases][releases-issue].
|
|
||||||
* [There isn't very much user-facing documentation][docs-issue].
|
|
||||||
* There have been several additions and breaking changes to the configuration
|
|
||||||
file format that haven't been documented in detail. This means you'll need to
|
|
||||||
read the source code to figure out what all the options are and what they do.
|
|
||||||
|
|
||||||
If these issues don't scare you away, go for it! (And if you use NixOS, [here's
|
|
||||||
an example][nixos-example].)
|
|
||||||
|
|
||||||
[docs-issue]: https://gitlab.computer.surgery/matrix/grapevine/-/issues/21
|
|
||||||
[releases-issue]: https://gitlab.computer.surgery/matrix/grapevine/-/issues/18
|
|
||||||
[nixos-example]: https://gitlab.computer.surgery/charles/servy-fleet/-/blob/main/config/grapevine/default.nix
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
[^1]: A "maintainer" is someone who has the ability to close issues opened by
|
[^1]: A "maintainer" is someone who has the ability to close issues opened by
|
||||||
someone else and merge changes.
|
someone else and merge changes.
|
||||||
[^2]: A maintainer approving their own change doesn't count.
|
[^2]: A maintainer approving their own change doesn't count.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue