Skud is currently certified at Master level.

Name: Skud
Member since: 2000-02-22 14:36:24
Last Login: 2011-08-05 22:03:27

FOAF RDF Share This

Homepage: http://infotrope.net

Notes:

Yow, how long is it since I've used this thing? That bio was seriously out of date. See my website for latest.

Projects

Articles Posted by Skud

Recent blog entries by Skud

Syndication: RSS 2.0

Meanwhile, in an alternate universe…

So this happened.

I like to think that in another, better, universe, it went like this:

When we launched Google+ over three years ago, we had a lot of restrictions on what name you could use on your profile. This helped create a community made up of people who matched our expectations about what a “real” person was, but excluded many other real people, with real identities and real names that we didn’t understand.

We apologise unreservedly to those people, who through our actions were marginalised, denied access to services, and whose identities we treated as lesser. We especially apologise to those who were already marginalised, discriminated against, or unsafe, such as queer youth or victims of domestic violence, whose already difficult situations were worsened through our actions. We also apologise specifically to those whose accounts were banned, not only for refusing them access to our services, but for the poor treatment they received from our staff when they sought support.

Everyone is entitled to their own identity, to use the name that they are given or choose to use, without being told that their name is unacceptable. Everyone is entitled to safety online. Everyone is entitled to be themselves, without fear, and without having to contort themselves to meet arbitrary standards.

As of today, all name restrictions on Google+ have been lifted, and you may use your own name, whatever it is, or a chosen nickname or pseudonym to identify yourself on our service. We believe that this is the only just and right thing to do, and that it can only strengthen our community.

As a company, and as individuals within Google, we have done a lot of hard thinking and had a lot of difficult discussions. We realise that we are still learning, and while we appreciate feedback and suggestions in this regard, we have also undertaken to educate ourselves. We are partnering with LGBTQ groups, sexual abuse survivor groups, immigrant groups, and others to provide workshops to our staff to help them better understand the needs of all our users.

We also wish to let you know that we have ensured that no copies of identification documents (such as drivers’ licenses and passports), which were required of users whose names we did not approve, have been kept on our servers. The deletion of these materials has been done in accordance with the highest standards.

If you have any questions about these changes, you may contact our support/PR team at the following address (you do not require a Google account to do so). If you are unhappy, further support can be found through our Google User Ombuds, who advocates on behalf of our users and can assist in resolving any problems.

I’m glad they made the policy change. But I sure would have liked to see some recognition of the harm done, and a clearer demonstration that they don’t think that “real people” and “people who were excluded” are non-intersecting sets.

Syndicated 2014-07-16 00:40:45 from Infotropism

Three realisations about community

Through May/June I was travelling in the US, to a number of feminist and tech events including WisCon, AdaCamp and Open Source Bridge.

I gave talks, ran unconference sessions, and sat on panels at each event, as well as talking to lots of smart people doing good stuff. In between, I hung out with remote colleagues and met new ones in spaces like San Francisco’s feminist hackerspace Double Union.

Along the way, I made three realisations, all of which are related to community in some way.

1. Community is my career, now

Especially at AdaCamp and OSB, I found myself looking at the schedule and considering which talks and sessions were right for me.

I find I’m no longer interested in most of the tech talks — if I want to learn about a specific technology, I can usually do so more effectively online when I need it. I used to go to those sessions out of a sense of duty, but now I’m out of the tech industry and working for myself, I don’t have to fake it any more. I still go to some tech talks, but usually to see what cool stuff other people are working on, not because it’s particularly relevant to my work.

Then there were the community sessions, ones covering topics like how to create a welcoming environment for newbies to your open source project, moderation strategies for online forums, and distributed agile development. All interesting and worthwhile topics, but ones I’ve been dealing with for years.

Back in 2009, I attended SXSW (and hated it, but that’s another story) and went to a session for first-timers, where someone gave the advice: “Never attend a session whose subject you already know about.” You’ll sit in the audience either bored, or frustrated. Without wanting to denigrate the excellent community sessions at the conferences I went to, I do have to say that a lot of them fell into this category for me. I attended to support my friends who were speaking, and I certainly picked up a few interesting tips, but if my goal was to learn new things then I’m not really sure these sessions were worth my time.

My realisation, over lunch on the first day of OSB (and thanks to Sara Smollett for helping me figure this out), is that I’m a mid-career community organiser. This is why open tech/culture events aren’t working for me — the tech content is no longer particularly useful to me, and the community content tends toward the 101 level.

So, how can I advance my skills and experience as a community organiser? Community management events in the tech field aren’t going to do it. I need to look wider, at fields with more established community theory and practice: social work, activism, politics, organisational behaviour, social psychology, just to name a few. So this is what I’m doing now: trying to learn and level up my community skills by reading and studying in these areas. Next year, I hope I’ll find a way to get to conferences that cover those areas in depth.

2. Community organiser, not community manager

The second realisation I had is around terminology.

Management is a business term. Organizing is a political one. I’m more interested in community organizing — helping people come together to achieve social change — than in managing people for business purposes.

I came to this realisation through my efforts to study things from outside the online/tech community management field. I’m re-reading Jane Jacobs’ “The Death and Life of Great American Cities”, which talks about what makes effective neighbourhoods. Jacobs was instrumental in organising her neighbourhood community to resist having a freeway put through it in the 1950s. Reading about her on Wikipedia I found that she appreciated the work of Saul Alinksky, considered to be the founder of modern community organizing.

That’s when it clicked for me. Community organising is a practice with a long and successful history of working for social and political change, and community organisers aren’t afraid to upset those in power to make a better world.

So, from now on I am using the term “community organiser” rather than “community manager” about my own work. Reframing it this way has given me a new perspective and momentum. I have a lot to learn, but at least I’m clear on what direction I’m heading in.

3. I’m still not an open source person

Back in 2011 I wrote Why I’m not an open source person any more, and reading back over it, it still holds true… mostly.

At AdaCamp someone requested an “introduction to open source” session in the 101 timeslots, and I since I wasn’t interested in most of the of the other 101 sessions and knew the subject well, I stepped up to run it. I talked about licensing, culture, and software development practices. I hope it was useful to the people who attended, but I felt unsatisfied by it. It’s not what I wanted to be doing.

The next day, someone asked me if I would help them promote their open source outreach program in Australia. I said, regretfully, that I wasn’t up for that. Open source isn’t my thing any more, and I don’t have the enthusiasm to do a good job of it. She pushed me, and I pushed back, and I came away really frustrated — partly that I hadn’t been listened to, but also partly because I had had trouble expressing my own boundaries and needs, because I didn’t really understand them myself.

Well, reframing my community work as political has helped me figure that out. For me, open source is a tool for social change. Specifically, I’m interested in social justice and sustainability, and I use open source toward those ends.

If someone asks me to do something simply “because it’s open source” (or open data, or open access, or whatever other kind of open stuff), I’m not going to be into that. I’ll need a lot of convincing that open source is a worthwhile end goal in its own right.

If someone asks me to do something open-source related that’s for another social or political goal that I support (say, government transparency, or individual privacy) then I’ll wish them well and help spread the word, but it’s not where my focus is.

I use open source and other open-licensed stuff as a tool for social change, especially in the areas of social justice and sustainability. But it’s just one part of my toolkit. I’m not an open source person any more. I’m a community organiser who uses open source.

Syndicated 2014-07-11 00:08:40 from Infotropism

My talks from Open Source Bridge

I finally got around to uploading the second set of slides from my talks at Open Source Bridge, so here they are.

First up, Knitting for Programmers teaches you how to knit something more interesting than a rectangle, using geometry and common design patterns.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!