One of my recent CWG (KDE Community Working Group) emails said, in part:
...the confrontation seems to have clarified some issues...
Of course! That is what confrontation is about. It isn't necessarily a power struggle, although it's usually seen that way. Confrontation, argument, fights are all about issues. Of course sometimes the issue is power, and access to resources, but more often the issue is about how to get to a shared goal or value. Confrontation is best and most productive when it clarifies: How can we best collaborate?
Arguments aren't bad! They bring issues out in the open. And if people learn to 'fight fair' - focus on resolving issues, not people, not positions, then stuff gets done. Even if you aren't directly involved in an argument, sometimes your part is to remind the 'opponents' of that, and support them as they 'get to yes.' If there is anger involved, it's good to be able to blow off steam without injecting that heat into the argument itself. Often a friendly ear is invaluable there.
I think confrontation is scary to people because most of us are taught as children NOT to confront, but to obey authority. This is understandable from the parents' point of view, but over the long term, people need to learn confrontation, negotiation, and fighting fair. As a parent I tried to teach my kids how to fight fair --even with me. Because mama is not always right.
I've only been in the community for a few years, so I can't compare 'the old days' to now. The KDE, Kubuntu and Ubuntu communities are spread all over the world, with people from a lot of different cultures; it would be amazing if we had no misunderstandings, spats, fights, disagreements. It is my hope that we all learn to do this better, and remember to be respectful during the struggle.
The Codes of Conduct are our support here. A CoC is often seen as a club, or a codification of law, which I think is wrong. Re-read your CoC, and I think you'll find that it is a description of the community we want, and the way we want to work. I hope to see fewer mentions of "CoC violation" and more examples of living up to our shared ideals. Read 'em again:
KDE Code of Conduct: http://www.kde.org/code-of-conduct/
Ubuntu Code of Conduct: http://www.ubuntu.com/about/about-ubuntu/conduct
Linuxchix boils it down the best, I think. Two rules: Be polite, and be helpful.
Showing posts with label Code of Conduct. Show all posts
Showing posts with label Code of Conduct. Show all posts
Thursday, August 29, 2013
Friday, May 24, 2013
Catalyst Leadership
I read a list post thread tonight that saddened me. I won't say what community it is part of, or point out the participants, because it is far too common in many of our community meeting places, whether they be lists, IRC or forums. Stereotypes are used rather than names here.
Newperson speaks up, I think for the first time, wondering when a new project result will be put to use, and offering a possible sample.
Longtime Devel speaks up, using rather angry questions about how the old symbol came to be displaced.
Another Oldtimer speaks up defending the symbol, accusing Longtime Devel of being out of touch.
And on. And on. The listowners don't redirect the discussion, and when questions are asked, they are answered angrily.
Newperson probably has departed by this point.
This seems like a small occurrence, but it is bad for every single participant, and each bystander has the power to change the conversation at each point.
This blog is a call for each of us to think about our power to influence the community spaces we inhabit, to exercise leadership, to become a catalyst for dialog, to open up trust. When I was first asked to become an IRC channel operator, I was asked to read the Freenode Philosopy: Catalysts. Whether or not you use IRC, I recommend reading this page to change your thinking about how you interact with others in your free software project. In fact, these ways of thinking about personal interaction would transform business, education and politics if put into wide use.
We know that bullying in schools can be brought to a stop by bystanders who show the courage to immediately speak up on behalf of the victim, and walk away from the confrontation. While I don't want to label those who use abusive language as bullies, we can transform tense situations in similar ways by speaking up in a positive, calm manner, as outlined in the Catalyst page.
Labeling people as trolls doesn't defuse the situation, or create an atmosphere of trust and dialog.
Please folks, if you are in an IRC channel, on a list, or help out on a forum: read the Catalyst page, and remind yourself often to be the change you want to see in the world. You don't need to be an op, a listowner, or a moderator, to be a leader; bloom where you are! Our Codes of Conduct aren't bludgeons to be used against evildoers; rather they are guides to our everyday interaction with one another.
Newperson speaks up, I think for the first time, wondering when a new project result will be put to use, and offering a possible sample.
Longtime Devel speaks up, using rather angry questions about how the old symbol came to be displaced.
Another Oldtimer speaks up defending the symbol, accusing Longtime Devel of being out of touch.
And on. And on. The listowners don't redirect the discussion, and when questions are asked, they are answered angrily.
Newperson probably has departed by this point.
This seems like a small occurrence, but it is bad for every single participant, and each bystander has the power to change the conversation at each point.
This blog is a call for each of us to think about our power to influence the community spaces we inhabit, to exercise leadership, to become a catalyst for dialog, to open up trust. When I was first asked to become an IRC channel operator, I was asked to read the Freenode Philosopy: Catalysts. Whether or not you use IRC, I recommend reading this page to change your thinking about how you interact with others in your free software project. In fact, these ways of thinking about personal interaction would transform business, education and politics if put into wide use.
We know that bullying in schools can be brought to a stop by bystanders who show the courage to immediately speak up on behalf of the victim, and walk away from the confrontation. While I don't want to label those who use abusive language as bullies, we can transform tense situations in similar ways by speaking up in a positive, calm manner, as outlined in the Catalyst page.
Labeling people as trolls doesn't defuse the situation, or create an atmosphere of trust and dialog.
Please folks, if you are in an IRC channel, on a list, or help out on a forum: read the Catalyst page, and remind yourself often to be the change you want to see in the world. You don't need to be an op, a listowner, or a moderator, to be a leader; bloom where you are! Our Codes of Conduct aren't bludgeons to be used against evildoers; rather they are guides to our everyday interaction with one another.
Labels:
Code of Conduct,
communication,
community,
dialog,
FLOSS,
FOSS,
Freenode,
KDE,
Kubuntu,
leadership,
Linuxchix,
respect,
Ubuntu
Friday, March 22, 2013
Intentional community
This blog is generally seen in the planets for Ubuntu, KDE, and Linuxchix. These are all FOSS intentional communities, by which I mean that the founders and members form a community to in which they can create. I found Linuxchix first (thanks, Megan!), and I loved how welcomed I was, although I was still at the time using Windows. How many linux channels welcome an mIRC user? The longer I hung out there, the more I learned, and the more I was impressed by all the different work the community members were doing out in the greater FOSS world. I also loved that it was women and men working together to make FOSS a better place for women.
When I ended up using Kubuntu (after trying Mandrake and then Gentoo, and GNOME/Ubuntu), some of the Ubuntu Women members welcomed me onto Freenode. When I found that that freenode was where the Amarok team hung out as well, I added the server to my Konversation server list. Members of both of those teams made me welcome, taught me some of the Freenode quirks, and I learned a bit more about how Linux is made. Lots of teams, loads of projects, each with their own culture and ways of working. Because Ubuntu and KDE both have a Code of Conduct, I felt somewhat safe, although I had heard lots of horror stories about linux channels on freenode and elsewhere. After experiencing some quite frightening attacks in the Linuxchix channels, I learned how resilient a community can be, and how creative security can be -- even fun.
So, codes of conduct. In the wake of the recent controversy following PyCon, one of my friends said that they imply that all men are assholes. This surprised me. Linuxchix has two rules: Be polite. Be helpful. All people are expected to follow them; I see the rules as intentional community. We want polite and helpful resources, so those are the rules for everyone. The Ubuntu CoC has grown a bit through the years, but is still phrased positively: http://www.ubuntu.com/project/about-ubuntu/conduct. I prefer the old shorter one, but both are focused on creating a helpful, respectful community.
I like the KDE CoC a lot. Once I found it, I felt much better about becoming involved. It reminded me very much of the simple Linuxchix rules.
So I ask each of my readers, what do you want? Is your behavior creating what you want? This is not aimed at men, by the way. All of us create our culture together, intentionally or not. I hope we will more consciously make our community the most pleasant, welcoming and creative in all of FOSS.
[Note on PyCon: The entire controversy has left me feeling sick. Congratulations are in order to the conference staff and leadership, who conducted themselves well. Yet they now have this mess connected to their fine conference, rather than good memories. There are no winners here, from what I can see. Since I didn't attend, and am not part of that community, no comments on PyCon itself or the controversy will be published here.]
When I ended up using Kubuntu (after trying Mandrake and then Gentoo, and GNOME/Ubuntu), some of the Ubuntu Women members welcomed me onto Freenode. When I found that that freenode was where the Amarok team hung out as well, I added the server to my Konversation server list. Members of both of those teams made me welcome, taught me some of the Freenode quirks, and I learned a bit more about how Linux is made. Lots of teams, loads of projects, each with their own culture and ways of working. Because Ubuntu and KDE both have a Code of Conduct, I felt somewhat safe, although I had heard lots of horror stories about linux channels on freenode and elsewhere. After experiencing some quite frightening attacks in the Linuxchix channels, I learned how resilient a community can be, and how creative security can be -- even fun.
So, codes of conduct. In the wake of the recent controversy following PyCon, one of my friends said that they imply that all men are assholes. This surprised me. Linuxchix has two rules: Be polite. Be helpful. All people are expected to follow them; I see the rules as intentional community. We want polite and helpful resources, so those are the rules for everyone. The Ubuntu CoC has grown a bit through the years, but is still phrased positively: http://www.ubuntu.com/project/about-ubuntu/conduct. I prefer the old shorter one, but both are focused on creating a helpful, respectful community.
I like the KDE CoC a lot. Once I found it, I felt much better about becoming involved. It reminded me very much of the simple Linuxchix rules.
This Code of Conduct presents a summary of the shared values and “common sense” thinking in our community. The basic social ingredients that hold our project together include:In my opinion, there is nothing in any of these codes or rules that blames men, or is negative. They paint a picture of a place where we want to work, and hang out with friends afterwards. I'm an older woman as the name of this blog implies, and I don't want to pretend to be a guy to collaborate without hassle. I want to be myself, and be welcomed for the skills and passion I bring. I also want more women and other minorities to feel welcome. A boy's club is not welcoming, and linux has that reputation. Too often well deserved.
- Be considerate
- Be respectful
- Be collaborative
- Be pragmatic
- Support others in the community
- Get support from others in the community -- quoted from http://www.kde.org/code-of-conduct/
So I ask each of my readers, what do you want? Is your behavior creating what you want? This is not aimed at men, by the way. All of us create our culture together, intentionally or not. I hope we will more consciously make our community the most pleasant, welcoming and creative in all of FOSS.
[Note on PyCon: The entire controversy has left me feeling sick. Congratulations are in order to the conference staff and leadership, who conducted themselves well. Yet they now have this mess connected to their fine conference, rather than good memories. There are no winners here, from what I can see. Since I didn't attend, and am not part of that community, no comments on PyCon itself or the controversy will be published here.]
Labels:
Code of Conduct,
community,
diversity,
FOSS,
Freenode,
geek culture,
IRC,
KDE,
Kubuntu,
linux,
Linuxchix,
Ubuntu,
Ubuntu-Women
Thursday, November 10, 2011
Thinking Together for Success
Tonight I heard an excellent interview on Fresh Air called How Birth Control And Abortion Became Politicized. Don't worry, I'm not going to write about politics, history, or medical procedures! I was struck by how positions on this subject have changed over the years. And yet many Americans now line up on one side or the other, and little dialogue is taking place between the two sides. As a consequence, my country is making little progress in resolving this issue. We have a shocking number of unwanted pregnancies here, with little discussion about improving the situation.
I just finished an interesting book about religion and politics by Francis Shaeffer (Sex, Mom and God), where he makes an eloquent lament about the same issue, and he's been on all sides of it, including creating the Religious Right in the US with his father and some others. When people stop listening to one another, they stop thinking together, which is the process we need to solve the really tough problems.
I'm reading again the excellent Dialogue: The Art of Thinking Together. The author illustrates many tough problems which have been successfully solved in dialogue, and some cases where dialogue broke down, and why. Unfortunately, the most often used attempts we are making to solve problems and make decisions aren't as effective as they could be. I see this in Western culture, and in Free and Open Source Software. I see a lot of conversations which turn into an airing of long-held positions, arguments, and debates, instead of creativity, fresh thinking, and problem solving.
There is another way, and I thank those in Linux who are fostering team-building, sprints, and larger in-person meetings such as Canonical's UDS, the KDE e.V.'s sprints, Akademy, Desktop Summits, and the GNOME Foundation's Guadecs and Desktop Summits. So much great dialogue can happen in those gatherings! There are other excellent groups sponsoring other opportunities for people to dialogue, but these are the ones I've experienced. I'd like to see us carry out dialogue on our mailing lists, blogs, forums and on IRC as well as our face-to-face meetings.
To the extent that people can begin to listen to one another as much as talk about their own knowledge and ideas, we'll begin to think together more and more, and craft more amazing solutions to our common problems. Until we learn how to do this better, we'll be a minority movement. We have to offer not just better software than the closed, unfree stuff, but also an attractive community, where we model mutual respect and helpful partnership.
This week I've read some really discouraging blog comments, IRC discussions, and mail list threads. We can do better! And we must do better, if we want to be ultimately successful. This isn't about enforcing codes of conduct, but about listening, and engaging in thinking, together. As Mahatma Gandhi said, Be the change you want to see in the world.
I just finished an interesting book about religion and politics by Francis Shaeffer (Sex, Mom and God), where he makes an eloquent lament about the same issue, and he's been on all sides of it, including creating the Religious Right in the US with his father and some others. When people stop listening to one another, they stop thinking together, which is the process we need to solve the really tough problems.
I'm reading again the excellent Dialogue: The Art of Thinking Together. The author illustrates many tough problems which have been successfully solved in dialogue, and some cases where dialogue broke down, and why. Unfortunately, the most often used attempts we are making to solve problems and make decisions aren't as effective as they could be. I see this in Western culture, and in Free and Open Source Software. I see a lot of conversations which turn into an airing of long-held positions, arguments, and debates, instead of creativity, fresh thinking, and problem solving.
There is another way, and I thank those in Linux who are fostering team-building, sprints, and larger in-person meetings such as Canonical's UDS, the KDE e.V.'s sprints, Akademy, Desktop Summits, and the GNOME Foundation's Guadecs and Desktop Summits. So much great dialogue can happen in those gatherings! There are other excellent groups sponsoring other opportunities for people to dialogue, but these are the ones I've experienced. I'd like to see us carry out dialogue on our mailing lists, blogs, forums and on IRC as well as our face-to-face meetings.
To the extent that people can begin to listen to one another as much as talk about their own knowledge and ideas, we'll begin to think together more and more, and craft more amazing solutions to our common problems. Until we learn how to do this better, we'll be a minority movement. We have to offer not just better software than the closed, unfree stuff, but also an attractive community, where we model mutual respect and helpful partnership.
This week I've read some really discouraging blog comments, IRC discussions, and mail list threads. We can do better! And we must do better, if we want to be ultimately successful. This isn't about enforcing codes of conduct, but about listening, and engaging in thinking, together. As Mahatma Gandhi said, Be the change you want to see in the world.
Labels:
Canonical,
Code of Conduct,
CWG,
Desktop Summit,
KDE,
kde e.v.,
Kubuntu,
Ubuntu,
UDS
Saturday, November 6, 2010
Listening to Our Better Angels
I've been most distressed tonight, to hear of my friend Noirin being assaulted at an ApacheCon party, here: http://blog.nerdchic.net/archives/418/. Worse, there are people calling her out for naming the attacker! Seriously, people? (I hear the comments are even worse over at Hacker News. I refuse to get even more disturbed and upset, so I'm not going to be reading them.)
In two separate discussions about this, with people who know and love Noirin, women said that the story makes them reluctant to attend cons and other FLOSS events, since assaults seem to be common. Yes, if you haven't been keeping up with the news, this happens OFTEN.
This doesn't make me fearful, it makes me ANGRY. Of course I'm angry at the perpetrators, but I'm also angry at those who protect them, and those who say 'we want more women to participate,' while not setting the standards of NO ASSAULT, and enforcing those standards. That seems like a very low expectation, don't you think? No ASSAULT!?
I can't help but contrast this assault with my experiences at last week's UDS in Orlando Florida. Ubuntu has a Code of Conduct, and not only enforces it, but has an even higher standard for community leaders. And there is discussion about having the Leadership CoC be formally signed also. I applaud this initiative, and hope that more communities create enforceable standards, and that conventions and other large gatherings will do likewise. There is no reason for any person to fear for their safety at these gatherings! I felt completely safe in Orlando, and I credit the high standards for that feeling of safety. Of course my favorite Kubuntu is covered by the same codes of conduct.
I call on the LinuxFest Northwest to set up and announce No Assault or Harrassment standards, and enforce them. I guarantee that a reputation as a safe space *will* result in more women attending. See the Con Anti-Harassment Project for specifics.
However, I think we need to go beyond a negative, and move toward positive expectations. I love the LinuxChix famous two rules: 1. Be polite, and 2. Be helpful. Indeed! And many projects have a standards. Among them, KDE Community Code of Conduct, GNOME Code Of Conduct, Gentoo Linux's Code of Conduct, the Mandriva Linux Code of Conduct, to name those I could easily find.
In addition, Freenode has an inspiring description of the "catalyst" role and how important it is to the continued use and usefulness of Freenode IRC: http://freenode.net/catalysts.shtml. And today, Jono Bacon, the Ubuntu Community Leader for Canonical, has posted The OpenRespect Declaration: http://openrespect.org/. I think we all owe it to one another as free humans, to respect one another.
PS: In case another reminded is needed: http://www.lovelight.me/2009/11/how-to-prevent-rape.html. Thanks for posting this link just when I needed it, Hypatia.
PPS: Also see The Open Source Women Back Each Other Up Project
In two separate discussions about this, with people who know and love Noirin, women said that the story makes them reluctant to attend cons and other FLOSS events, since assaults seem to be common. Yes, if you haven't been keeping up with the news, this happens OFTEN.
This doesn't make me fearful, it makes me ANGRY. Of course I'm angry at the perpetrators, but I'm also angry at those who protect them, and those who say 'we want more women to participate,' while not setting the standards of NO ASSAULT, and enforcing those standards. That seems like a very low expectation, don't you think? No ASSAULT!?
I can't help but contrast this assault with my experiences at last week's UDS in Orlando Florida. Ubuntu has a Code of Conduct, and not only enforces it, but has an even higher standard for community leaders. And there is discussion about having the Leadership CoC be formally signed also. I applaud this initiative, and hope that more communities create enforceable standards, and that conventions and other large gatherings will do likewise. There is no reason for any person to fear for their safety at these gatherings! I felt completely safe in Orlando, and I credit the high standards for that feeling of safety. Of course my favorite Kubuntu is covered by the same codes of conduct.
I call on the LinuxFest Northwest to set up and announce No Assault or Harrassment standards, and enforce them. I guarantee that a reputation as a safe space *will* result in more women attending. See the Con Anti-Harassment Project for specifics.
However, I think we need to go beyond a negative, and move toward positive expectations. I love the LinuxChix famous two rules: 1. Be polite, and 2. Be helpful. Indeed! And many projects have a standards. Among them, KDE Community Code of Conduct, GNOME Code Of Conduct, Gentoo Linux's Code of Conduct, the Mandriva Linux Code of Conduct, to name those I could easily find.
In addition, Freenode has an inspiring description of the "catalyst" role and how important it is to the continued use and usefulness of Freenode IRC: http://freenode.net/catalysts.shtml. And today, Jono Bacon, the Ubuntu Community Leader for Canonical, has posted The OpenRespect Declaration: http://openrespect.org/. I think we all owe it to one another as free humans, to respect one another.
PS: In case another reminded is needed: http://www.lovelight.me/2009/11/how-to-prevent-rape.html. Thanks for posting this link just when I needed it, Hypatia.
PPS: Also see The Open Source Women Back Each Other Up Project
Labels:
Assault,
Code of Conduct,
FLOSS,
Freenode,
Gentoo,
Gnome,
harrassment,
KDE,
Kubuntu,
LFNW,
Mandriva,
OpenRespect,
rape-prevention,
standards,
Ubuntu,
UDS-N
Subscribe to:
Posts (Atom)