diff --git a/content/about.md b/content/about.md index aca8e2f..5cdecdf 100644 --- a/content/about.md +++ b/content/about.md @@ -4,7 +4,7 @@ date: "2021-01-05T20:00:00+09:00" draft: false --- -# About Dragon Linux +# About Dragon Linux [WIP] Dragon Linux is a project and community with the goal of porting Linux to Apple Silicon Macs, starting with the 2020 M1 Mac Mini, MacBook Air, and MacBook Pro. diff --git a/content/community.md b/content/community.md index 748a768..8b785cd 100644 --- a/content/community.md +++ b/content/community.md @@ -10,9 +10,9 @@ If you're interested in the project, you're welcome to drop by! Check out [ways Please remember that all community members are expected to abide by our [Code of Conduct](/code-of-conduct). -## IRC +## Discord -Most development and project discussion takes place on IRC. We have several channels on the OFTC IRC network: +Most development and project discussion takes place on Discord. We have several channels on the OFTC IRC network: * #asahi [[logs](https://oftc.irclog.whitequark.org/asahi)] - General project discussion * #asahi-dev [[logs](https://oftc.irclog.whitequark.org/asahi-dev)] - Development discussion diff --git a/content/governance.md b/content/governance.md deleted file mode 100644 index 0380675..0000000 --- a/content/governance.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Governance -date: "2025-08-01T00:00:00+00:00" -draft: false ---- - -# Governance - -Dragon Linux is led by our community of open source developers. If you want to work on something, work on it! We welcome contributors from different backgrounds. By and large, we make change by “doing”. Dragon Linux is about the code, and the code comes from anyone who wants to write it. Development uses a “lazy consensus” model: the work happens when people do it. Other developers can veto to force a discussion, but developers don’t need to chase people for trivial issues. - -To support that code, we need infrastructure and funding, to run servers and support developers. While development happens with a “lazy consensus” model, these logistical issues are governed by our project board. - -There are seven board members, aside from temporary vacancies. The current members are: - -* [Matthew Pitsicalis](https://home.venith.net) (administrator). - -The board is responsible for project governance, infrastructure, and money. It also acts as the ultimate arbiter in case of conflict, including code-of-conduct enforcement. The board meets monthly by video call to do business in meetings. Our meeting minutes are public. - -The board appoints specific members to the following roles by majority vote: - -* Treasurers have access to our [Open Collective](https://opencollective.com/asahilinux) and implements the financial decisions the board makes by vote. They do not themselves decide how to spend money. -* The secretary schedules meetings, drives meetings, and maintains meeting minutes. -* Administrators have access to project infrastructure, including our servers. Like developers, they operate by “lazy consensus”. - -The board votes on how money should be spent. If the money’s recipient is a board member, that member is ineligible for the vote. For example, if a developer needs a new Asahi development machine, the rest of the board would approve that expense. The treasurer then handles the transaction. Finally, the board audits transactions after the fact, aided by Open Collective’s transparent documentation of transactions. - -Board members may be added (when there are vacancies) or removed by vote. These bylaws may be amended by vote. A vote passes with the approval of four members. - -It is sometimes necessary to vote between meetings, occurring in our [public Discord room](https://discord.go.venith.net). diff --git a/layouts/index.html b/layouts/index.html index 545909e..f5fe868 100644 --- a/layouts/index.html +++ b/layouts/index.html @@ -40,7 +40,7 @@
- Dragon Linux Discussion + Dragon Linux Discussion
@@ -55,21 +55,6 @@ -
-
-
-
- -
-
-

We also have more resources for support available below.

-
-
- -
-