Search Results

Generally, the League operates as close to a flat structure as it can be. While it's unlikely that every individual who uses a League node will vote or even want to vote, if they choose to participate in the decision-making process, we encourage them to do so ...

This page will hold the abridged version of our Code of Conduct. The full text will be available tktk.

This page will hold the League's vision statement.

https://broadcast.websiteleague.org/@league Broadcast is a special node of the Website League, intended for official announcements only.

https://consensus.websiteleague.org/ Consensus is our consensus-finding and decision-making system. This is an instance of Loomio, a consensus management application designed for organizations like ours. We use it for taking polls of the Stewards to get a sen...

https://coordination.websiteleague.org/ Coordination is our development, operations, and governance chat. It is an instance of Zulip, a hybrid software that has Discord-style chat, organized into forum-style threads. The tools it provides us help keep convers...

We do have a Discord server; however, we have wound this down for official use, because the work we need to do outgrew Discord's very limited organizational tools. All information and official League chat is on Coordination, which anyone is allowed to join and...

You are currently on Information, our wiki which has been recently reorganized; this is where folks can go to learn about how the League works, how to set up and run a node, and how we govern the organization.

https://planning.websiteleague.org Planning is our kanban board and task tracking system. It is a Vikunja instance. This is where we keep track of what we've done, what we're doing, and what we're going to do.

Muffinlord please stop suggesting we solve all disputes via "the cage"

Posting machine broke? 

If you unfollow/block someone and it doesn't seem to take immediately, restart the service; it's faster than waiting for it to kick in on its own.

Who amongst us hasn't broken notifications between two instances, really?