惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
DataBreaches.Net
F
Fortinet All Blogs
D
Docker
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
WordPress大学
WordPress大学
罗磊的独立博客
Y
Y Combinator Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
J
Java Code Geeks
T
The Blog of Author Tim Ferriss
U
Unit 42
N
Netflix TechBlog - Medium
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
V2EX
云风的 BLOG
云风的 BLOG
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
Hugging Face - Blog
Hugging Face - Blog
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
酷 壳 – CoolShell
酷 壳 – CoolShell
P
Proofpoint News Feed
G
Google Developers Blog
H
Help Net Security

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
Expulsions and the community bylaws [LWN.net]
einpoklum · 2026-05-08 · via LWN.net comments

Expulsions and the community bylaws

Posted May 8, 2026 10:01 UTC (Fri) by einpoklum (guest, #183672)
Parent article: Digging into drama at The Document Foundation

A few more points to bear in mind:

  • The "Community Bylaws" under which so many of my colleagues and friends have been expelled have never gone into force. TDF statutes require that community bylaws be accepted by a vote of the trustees to go into force; no such vote was taken. I suspect our current (unelected) leadership was worried they would not win such a vote, so they just put our statutes aside and proceeded to presume to do whatever the hell they want.
  • Our statutes require a procedure vis-a-vis the Board of Trustees in order to expel a member. Unfortunately, the foundation has a statutes loophole which can been misused for affecting expulsions with no formal charges, no hearing, no presentation of evidence, etc. This mechanism is an annual membership renewal. The renewal was supposed to ensure that the trustees are active contributors, not just people who were active sometime in the past and are now just holding on to their status. But - technically, as a trustee you need an annual formal approval to continue your status; and a dis-approval does not have to establish or prove that you are inactive in the community. Also, even if you've been active for years and years - you still have to undergo this every year. That means that in order to "politically assassinate" someone, or to purge an undesired group, one doesn't even need to convince a momentary majority of trustees, but it is enough to influence a few members of the "Membership Committee". And since being on that committee is not a "sexy" position, and it has a tradition of doing very little and having no accountability to the board of trustees - this manipulation is quite possible.
  • ... To this we should add that a candidate MC member who had the potential to offer some resistance, and who won a seat in the last elections, was expelled before being seated: Our Board of Directors decided to disqualify this candidate _retroactively_, after the elections had already been held. Obviously, this was severe elections tampering (whether the disqualification was justified or not). This member was then purged from the TDF Board of Trustees entirely, through the very mechanism I mentioned before, of membership non-renewal.
It must be said that the expulsion of Collabora employees from the TDF has caused extreme damage to LibreOffice already, and if it is allowed to remain in effect, i.e. if fences are not mended, that damange will become permanent and compound further. It is literally the majority of vetern developers involved with the project that are now turned away from involved with it in favor of another product and a separate codebase. It is a collosal failure of our leadership, which are either saying nothing or in some cases making petty (and invalid) excuses for splitting our community in half.
(Context: I am a LibreOffice contributor focused on Right-to-Left support QA and UI/UX, and a trustee since 2022. I am not associated with Collabora, Allotropia or any other commercial entity whose business involved office software)