Skip to content

Commit 8a024ea

Browse files
Add public minutes for the Nov and Dec 2025 MGMs
Co-authored-by: Aaron Jones <amdj@libera.chat>
1 parent e51afeb commit 8a024ea

File tree

2 files changed

+82
-0
lines changed

2 files changed

+82
-0
lines changed
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Monthly General Meeting, November 2025
3+
author: She
4+
excerpt: >
5+
Approval of a new organisation member, discussion about election process,
6+
bylaws change for removing organisation members who do not vote during two
7+
consecutive elections, discussion about ban automation tools
8+
---
9+
10+
## Propositions and Motions
11+
12+
### Confirmation of new members
13+
14+
This meeting voted to confirm the membership of the newest member of staff.
15+
16+
### Election stuff
17+
18+
This agenda item was added to provide an opportunity to voice any ideas or
19+
concerns regarding the election platform, timelines, or any bylaws changes
20+
regarding the election process or board makeup before candidate
21+
announcements kick off.
22+
23+
The elections are typically held in March. An asynchronous election is run
24+
on [CIVS](https://civs1.civs.us/) whose results are then confirmed during
25+
the general meeting (due to bylaws requirements). No ideas or concerns
26+
were raised regarding this process at this time.
27+
28+
### Proposed bylaws change for idle removals
29+
30+
A [change to bylaws][bylaws] was proposed for this meeting that would codify
31+
that an asynchronous election must take place, as well as require organisation
32+
members to vote in one at least every other year to maintain
33+
membership. Casting a blank ballot would be permitted. Notably, the exact
34+
process for performing the asynchronous election would not be codified,
35+
so as not to tie us to any particular platform.
36+
37+
It was noted that, as-written, someone could be elected to a position but
38+
be removed from the organisation for failing to vote in the election.
39+
The meeting agreed that this is unlikely to occur and that, if necessary,
40+
the board can call an EGM to immediately re-invite the member.
41+
Concerns were also raised that other forms of contributions to the network or
42+
the organisation running it should also count for the purposes of retaining
43+
membership in the organisation. However, in absence of specific suggestions,
44+
the meeting agreed that the proposal could be adopted as-is and amended later.
45+
46+
There has been support for some mechanism for removing very-inactive
47+
organisation members without having to specifically vote to do so during a
48+
general meeting, and voting in an asynchronous election that occurs
49+
once a year and is open for thirty days is a low bar of effort to clear.
50+
Ultimately, the meeting voted to adopt this proposal,
51+
and will be enacted for the next asynchronous vote.
52+
Therefore, the earliest someone can be removed from the organisation
53+
due to this policy is after the AGM in 2027.
54+
55+
[bylaws]: https://github.com/Libera-Chat/libera-chat.github.io/commit/7bfe67bd94091008d01f67c4ee24b4aaef3cdcfe
56+
57+
## Other questions
58+
59+
### Should we forbid the use of network ban automation that staff cannot disable?
60+
61+
Earlier in the month, a ban evasion detection tool running from a staffer's
62+
connection began to produce false positives with no way of disabling the tool
63+
without forcibly disconnecting the staffer. Bots run by staff usually run
64+
under a dedicated user account on an internal toolbox server, but in this case
65+
the tool in question was written as a script for a graphical IRC client and
66+
would require a significant rewrite in order to run independently.
67+
68+
This meeting agreed that it would be beneficial to have an internal rule
69+
that ban automation needs to have a documented process for any member of staff
70+
to disable it if necessary. The meeting also emphasised that long-running
71+
autonomous software really should on our infrastructure. The meeting also
72+
agreed that a few other internal policies and guidelines that
73+
had been agreed upon but never formalised should be written down alongside
74+
this latest internal policy item.
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
title: Monthly General Meeting, December 2025
3+
author: She
4+
excerpt: Empty agenda. Happy holidays!
5+
---
6+
7+
This meeting occurred, but no items were added to the agenda prior to
8+
invitations being sent out, nor were there any late additions to the agenda.

0 commit comments

Comments
 (0)