I observe that all the people involved were directors, so this is entirely under our own control and not a good reason to block.
Also in the last board, when these things happened, all the people involved were directors, so that does not grow my trust. If you have spoken out in support of e.g. Paolo, whose messages have been hidden and at least in one occasion manipulated, please share the link - I would be very interested how that discussion turned out, so maybe I will be more optimistic then.
For the moment I’m concerned about Discourse as a tool after what we have seen.
Meanwhile the only way for Trustees to communicate with all Trustees is via tdf-members@…
We do have many channels, including a private tdf-internal mailing list, a public board-discuss forum, Telegram, Matrix and many others. There’s a wide variety of choice for trustees to engage in conversation! Even more so, each quarter, every three months, we announce the tdf-internal list to each and every member again.
which is rigorously controlled to the extent that even I as deputy chair have to ask for posts to be moderated through by staff. So I am unclear why censorship by directors is a problem to stop us opening up to allow Trustees to perform the role the Statutes envisage, but not a problem elsewhere.
I am not sure if that now helps the discussion. Staff supports, amongst other things, with moderation of lists. As we have seen, they do so even during nighttimes, holidays and with usually a very quick reaction time. As one example, the moderation of your mail on the list took only few minutes yesterday evening, even if it was way past 8pm already.
Any announce-only list, like e.g. the announce@tdf list, is moderated for everyone, to prevent accidential posting of messages. This, by the way, was something required by every board ever since, and it makes a lot of sense.
It creates quite mixed feelings to read “rigorously controlled” and “censorship” in this context.
I would have continued now to explain that also the function of the list and how to get moderator rights has been explained during the onboarding, but as this discussion is taking a very unpleasant turn, I’d rather not.