DevOS | 36 Members | |
| Seeking help and geeking out together on https://github.com/divnix/devos & https://github.com/divnix/digga | 10 Servers |
| Sender | Message | Time |
|---|---|---|
| 28 Oct 2021 | ||
| If my opinion is worth anything it would be that the quality of discussion is lamentable. | 05:01:09 | |
In reply to David Arnold (blaggacao)It's sad to see that discussion... I'd say the proposal was a fair one, although perhaps instead of a vague RFC like this, something like "disallow anything that is not functionally related to NixOS, nixpkgs, or Nix projects" could maybe work better, considering that is the purpose of nixos.org Matrix if I understand it right. And again, I find it sad that the discussion has gone some bad places... | 07:40:27 | |
| I might be misunderstanding the issue here, but if I may indulge and give my opinion; As far as I've understood, the primary objection to the private chat room is an ideological one; transparancy and openness is more important than a safe space for a minority community. Though I don't think I value the former any less than anyone else, I think transparency and openness are only valuable if everyone that wants to participate can participate. I hope we don't have to discuss the obvious problems of misogyny and queerhate that the tech community faces. I think having a space in which people can talk freely about these kinds of issues and how they relate to the nix community is an important one, and one that is needed to make sure we don't close ourselves off from decent chunks of the population. Transparency and openness start at the human level. I agree that the RFC is too vague, but in a different way:
If I've understood correctly, the "current ambiguous state of affairs" is the existence of one private chatroom as a minority safe space. I might be too far removed from the project, but I don't see how this is a problem, as long as all technical decision making is done in the open and with plenty of room for discussion, which so far has seem to be the case. | 10:37:32 | |
| b12f I think the RFC is quite fundamentally an attempt to (re-)balance transparency with privacy. I ultimately beleive it's a trade -off and balancing act of reason and measure. I think it is without question an important issue, as have some noted, not only at the occasion of (inndeed only one) invite only channel. | 12:53:36 | |
| I totally acknowledge the need for privacy. And I totally acknowledge that it fundamentally conflicts with transparency. | 12:54:59 | |
| I might want to add, that after this discussion & discussion in 98, the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel might be a "safe-house", the open, oublic & transparent discussion is a "war zone". | 13:01:01 | |
| * I might want to add, that after this discussion & discussion in 98, the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel might be a "safe-house", the open, public & transparent discussion is a "war zone". | 13:01:19 | |
| All public discussions should be "safe spaces", in principle. | 13:02:03 | |
| * I might want to add, that after this discussion & discussion in 98, the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel might be a "safe-house", while the open, public & transparent discussion is a "war zone". | 13:02:33 | |
| * I might want to add, that after this discussion & discussion in 98 (surely others), the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel might be a "safe-house", while the open, public & transparent discussion is a "war zone". | 13:03:07 | |
| * I might want to add, that after this discussion & discussion in 98 (surely others, too), the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel might be a "safe-house", while the open, public & transparent discussion is a "war zone". | 13:03:14 | |
| * I might want to add, that after this discussion & discussion in 98 (surely others, too), the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel (or anything else akin to it) might be a "safe-house", while the open, public & transparent discussion is a "war zone". | 13:03:43 | |
| * I might want to add, that after this discussion & discussion in 98 (surely others, too), the very principle of "safe-spaces" seems to have turned into it's opposite. It almost seems as if said channel (or anything else akin to it) might be a "safe-house", while the open, public & transparent discussion between _individuals_ is a "war zone". | 13:04:03 | |
| b12f: thank you for the well reasoned response. If only we could have had more of this in the RFC thread and less assumption, things would have been a lot more productive. With that said, I'd like to dive in a bit if you don't mind:
I get the sentiment here, but this is also partially an issue for me. Why shouldn't we discuss it? Isn't that a requirement for actual understand, organizing and acting? Also, I'm not saying it doesn't exist, and I've seen plenty of examples of it in my own personal life and the wider internet, but I've yet to really see any major examples of this in any of the tech communities I have interacted with.
Fully agree, but I think there is an important distinction to make here. Who is it exactly that made someone feel as though they couldn't participate? I think it matters if it's something external, vs an internal assumption without evidence. Not that I don't understand the latter, as I am totally familiar with feelings of shyness, and irrational fear of new people. I just think, from my own experience at least, that this internal assumption is best addressed at a personal level, and a private chat with friends can surely be helpful with that as well, but what difference does it make if it is official or not? Either way, at some point I'd love for those individuals to just join us in the main chat, they may be surprised to find that myself and others would be more than happy to have them there. Obviously, in the external case, things are different and moderation and understanding from the community and the leadership come in to play.
Absolutely! But in order to avoid that space from becoming an echo chamber which endlessly cycles through the problem without ever arrising at a solution, I personally think that space should eventually become the public rooms. A private chat is great to work up some courage, but at some point, if we really want to address something in the community, then it has to be addressed in the community yes? | 13:05:03 | |
| * b12f: thank you for the well reasoned response. If only we could have had more of this in the RFC thread and less assumption, things would have been a lot more productive. With that said, I'd like to dive in a bit if you don't mind:
I get the sentiment here, but this is also partially an issue for me. Why shouldn't we discuss it? Isn't that a requirement for actual understanding, organizing and acting? Also, I'm not saying it doesn't exist, and I've seen plenty of examples of it in my own personal life and the wider internet, but I've yet to really see any major examples of this in any of the tech communities I have interacted with. And that is a good thing!
Fully agree, but I think there is an important distinction to make here. Who is it exactly that made someone feel as though they couldn't participate? I think it matters if it's something external, vs an internal assumption without evidence. Not that I don't understand the latter, as I am totally familiar with feelings of shyness, and irrational fear of new people. I just think, from my own experience at least, that this internal assumption is best addressed at a personal level, and a private chat with friends can surely be helpful with that as well, but what difference does it make if it is official or not? Either way, at some point I'd love for those individuals to just join us in the main chat, they may be surprised to find that myself and others would be more than happy to have them there. Obviously, in the external case, things are different and moderation and understanding from the community and the leadership come in to play.
Absolutely! But in order to avoid that space from becoming an echo chamber which endlessly cycles through the problem without ever arrising at a solution, I personally think that space should eventually become the public rooms. A private chat is great to work up some courage, but at some point, if we really want to address something in the community, then it has to be addressed in the community yes? | 13:06:10 | |
| I also beleive: a private chat is great to work up some courage. That's btw. +- how DevOS kicked off. 🙂😎 But I also see the solution to more "safe-spaces" and less "war-zone" in an open and honest discussion, not in private rooms of special interest. Solution, that is if we are actually looking for one. I am. | 13:10:28 | |
| That's is a very important point. Cultivating a culture where the default public chat is assumed to be unsafe, equivalent to a culture of bad faith in my mind | 13:14:07 | |
| * That's is a very important point. Cultivating a culture where the default public chat is assumed to be unsafe, is equivalent to a culture of bad faith in my mind | 13:14:23 | |
| * That's is a very important point. Cultivating a culture where the default public chat is assumed to be unsafe is equivalent to a culture of bad faith in my mind | 14:05:49 | |
Though the ideal would be that every chat is a safe-space by default, I think we have to acknowledge that this just is not the case. I personally haven't seen anything bad in the Nix community, but tech in general just can be very hostile[1][2]. In any case, I'd recommend letting the discussion rest for now. If at some point there is a decision made that was somehow discussed in private groups and never brought forward to discuss in public, then that'd be a point of concern in my opinion. Until that, I see no problems at all with private chats. To expand a bit on your thoughts:
I understand this, and to be honest I think the first impulse actually is to do this. I see the concept of safe space perhaps a bit differently; if we allow and support it, it is also us as a community saying "yes, we acknowledge there are issues in IT, yes we do want you here, no we will not stand in the way of anyone who needs to have private conversations about certain topics".
As said, unless this becomes an issue at the technical or project management level, I'd bury the hatchets and let whatever private spacer there are be. [1] Random case in point: https://www.reddit.com/r/programming/comments/mburmc/free_software_advocates_seek_removal_of_richard/gs0z0oh/ | 15:38:43 | |
| also,
For all you know teutat3s and myself might be running endless circles in the echo chamber that is our private chat, but as long as that doesn't affect devos/nix, then who cares :P | 15:44:34 | |
| But in an official room, we have no way of knowing if that echo chamber is affecting the community, and due to the very quick and directed response I've seen in various places, it would seem there may actually be some organization behind the scenes. Of course, I am very free minded and wouldn't even say this is necessarily a bad thing. If people feel strongly about something and wish to share it with their friends and inner circle in order to coordinate a response, then so be it. But that doesn't really seem like an appropriate activity for an official channel, since it is, by definition, an opinionated activity. None the less, I have been seeing this very similar type of response for months, from members who appear to be involved in this room, and I have chosen in each one of those instances to remain essentially neutral. I think there was only one instance where I made a comment, and when it wasn't well received I gave up on it entirely. A part of me was really hoping I could publish this RFC and the community could discuss it's abstract merit, and I had my fingers crossed for that. But seeing this activity over the last several months, I had a feeling someone would accuse me of this. I very much considered whether it was even worth it to post, seeing as there was a very high probability of this happening. I decided to move forward for two reasons. This openness is a very high ideal for me personally. It is something I really care about and it's something I really wish to preserve if at all possible, in the same sense that Nix is trying to preserve "pure" environments, or at least to a similar degree. Second, I don't want to work and operate in a community where I am afraid to speak on what I really feel is important because of potential backlash. I decided therefore to bite the bullet, and if it happened, try to deal with it head on rather than running or avoiding it. I truly wish, if we can't necessarily be friends, to have at least a mutual respect between me and members of the community in question, but the more I see them acting out brazenly against other members without any backlash from moderators, that is becoming harder for me to maintain. Rather than forgoing and giving up, I decided that I should at least attempt to address this directly on an issue that is important enough to me to warrant the trouble. | 16:04:01 | |
| for the record, I will probably link to our comments here if and when the rfc opens up again | 16:09:23 | |
| I think, the violence of this discussion will not remain without consequences, at least for me. I feel it is becoming a duty to call out offenders of a healthy discussion culture directly & precisely. | 18:10:53 | |
| David Arnold (blaggacao): What is the offense? (re: "offenders of a healthy discussion culture") I've been trying to precisely pin down the exact problem. | 18:12:36 | |
| 18:14:21 | |
| * - presumably malicious or at least _very_ careless & forceful reframing (agenda / defence driven) - abandonment of good faith as the default mode of discussion. Not even an effort is perceivable. | 18:15:04 | |
| The latter point is the most critical to me. | 18:15:49 | |
| (in some instances, I'm not wanting to generalize unduly) | 18:16:54 | |
| We're talking about the same problem, but I'm not sure those are useful in practice. Maybe useful is the wrong word. Maybe "solid"? The "good faith" mantra easily becomes as heated and divisive as the original topics. | 18:17:24 | |