|
| 1 | +--- |
| 2 | +title: Monthly General Meeting, January 2026 |
| 3 | +author: She |
| 4 | +excerpt: > |
| 5 | + Accepting direct donations, election platform choice, |
| 6 | + deferring privacy policy update to next meeting, removing VACATION |
| 7 | +--- |
| 8 | + |
| 9 | +## Propositions and Motions |
| 10 | + |
| 11 | +### Do we want to turn on direct Stripe-based donations? |
| 12 | + |
| 13 | +This meeting discussed whether Libera Chat should be able to accept direct |
| 14 | +donations through Stripe in addition to Liberapay. This has the advantage |
| 15 | +of giving us more reliable income data, better support for one-time |
| 16 | +donations, and a more streamlined path to donation for new donors. |
| 17 | +This would require a minor privacy policy update |
| 18 | +in order to allow us to retain donor information as required by Swedish law, |
| 19 | +which would be retained by Stripe on our behalf. |
| 20 | + |
| 21 | +This proposition passed unanimously. |
| 22 | + |
| 23 | +### Election platform decision |
| 24 | + |
| 25 | +As participation in asynchronous elections is now required for continued |
| 26 | +membership in the Libera Chat organisation, this meeting was tasked with |
| 27 | +resolving how best to resolve an issue with the election system Libera Chat |
| 28 | +had used in previous years. The platform does not support disclosure of who |
| 29 | +voted in a particular election without also disclosing the exact votes cast, |
| 30 | +which was agreed to be undesirable. The meeting discussed either making a |
| 31 | +separate "roll-call" poll with ballot disclosure, or exploring an alternative |
| 32 | +voting platform that does not support ranked-choice ballots. |
| 33 | + |
| 34 | +The meeting ultimately agreed that adding a roll-call poll to the previous |
| 35 | +platform was the best way forward. |
| 36 | + |
| 37 | +### Privacy policy amendment |
| 38 | + |
| 39 | +This meeting proposed amending the privacy policy in order to contain explicit |
| 40 | +wording regarding what data may be retained by our channel management bot |
| 41 | +`litharge` in order to limit it scope. |
| 42 | + |
| 43 | +The meeting decided that the proposed amendment was premature |
| 44 | +as it doesn't cover data that may be retained by future channel management |
| 45 | +bots and that it should be revisited next meeting. |
| 46 | + |
| 47 | +## Other questions |
| 48 | + |
| 49 | +### Should we remove the NickServ vacation module? |
| 50 | + |
| 51 | +This meeting discussed removing the `NickServ` `VACATION` command |
| 52 | +which has had relatively little legitimate use. `VACATION` triples nick |
| 53 | +expiration times during the next logout. The meeting also considered |
| 54 | +whether the expiration of primary nicks should be extended due to this command |
| 55 | +being removed. |
| 56 | + |
| 57 | +The meeting agreed that `VACATION` should be removed, and that users who |
| 58 | +plan to be away from the network for more than a third of a year may contact |
| 59 | +staff to arrange an extended expiry time if necessary. |
| 60 | +The meeting agreed NOT to extend expiration times across the board, but did |
| 61 | +agree that unexpired accounts which have `VACATION` set should still keep |
| 62 | +the benefits of `VACATION` until their next login. |
0 commit comments