[ Topics split and merged by JasonJAyalaP]
Another thing (Patrick talked about this) that puts a big question mark onto my head: What actually constitutes a “team member”? I.e. what differentiates a “team member” from a “community member”? I might be wrong here (please explain) but I consider this distinction somewhat harmful for community thinking and especially building. That is, Whonix - to my understanding - is a FLOSS community project, there are no contracts involved or something. For example, fortasse - to my knowledge - administers the servers and pays for them. Obviously this constitutes being a “team member” rather than a “community member”. I myself don’t even know (sorry for being naive) what Jason actually is to Whonix. I mean, so far, I like his tone and language in the forums, i.e. I consider him a friendly person, but that’s about it (what I know currently). Still, he’s considered a “team member”.
You may wonder why I come up with this … Actually, looking into the (hopefully thriving) future of Whonix, we’ll get to a point where a (more formal) decision making process needs to be established, a governance if you will. We may have an (elected) board, a council (whatever entity) that oversees important decisions, acts as a guidance for the community, etc, etc. Also thinking about the role of a imaginable 501c3, e.V. here. I’m wondering how to move forward if we have a “team member” VS “community member” differentiation; from a community management perspective. At least, it has its implications if we move forward with this. Especially if the differentiation and its reasons are unclear, intransparent (to me at least; so far) - so to speak.
Looking forward to your input here!