Repository navigation
docs(openspec): propose add-open-party-joining - #26
Merged
Merged
Conversation
TheMeinerLP
force-pushed
the
docs/propose-add-open-party-joining
branch
from
October 30, 2026 19:27
3778d25 to
168e714
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Players want to join a friend's party without a chat exchange and an invite. Streamers want their viewers to walk in
without being invited one by one. This proposal describes both, and the rules that keep the leader in charge.
A player who wants in types
/party request <player>. The leader of that party sees a prompt with[Approve]and[Reject], and has a minute to answer. If nobody answers, the request lapses and the player can try again after ashort wait. A leader who trusts the room can open the party with
/party public on, and then anyone who knows theleader's name types
/party join <player>and is in. An open party holds up to 20 members; a private one keeps its8. A player who was kicked stays out until the leader invites them again. Nothing lists public parties: you have to
know the name.
The change ships as
feat(party). Once it is merged, the code follows in its own pull request.Out of scope: listing or announcing open parties, passwords, bans that outlive a party, and redirecting chat.
Types of changes
Checklist
Further comments
This PR only adds the OpenSpec proposal under
openspec/changes/add-open-party-joining/; it changes no code. Theproposal and the decisions in
design.md(permission checked on the proxy only, an open party closes on a change ofleader, an invite lifts a kick ban) are open for review here before the code pull request is opened.
Opening a party needs
quelea.party.public; closing does not, so a leader who lost the permission can still close.Known gap for the rollout: a join request reaches the leader only through the event stream, so the leader's proxy needs
the new plugin before players start requesting. This is written into
design.mdunder mixed-version compatibility.Validation:
openspec validate add-open-party-joining --strictexits 0. The only remaining message is an info line that the base spec is not archived yet.