It's free.

Suddenly: Lightning discussion

Some days ago I tried Twitter. I was signed up for a few minutes, tweeted a few times and then knew microblogging was not for me. I didn’t know exactly why. One day I had a quick conversation with an IRC buddy, and I realised why I didn’t need microblogging, and why it did not work for me.

What is microblogging about?

From what I’ve read, seen and thought, I conceive microblogging is all about sharing and in the best of the situations, benefitting, cooperating and creating something new. Who you follow and who follows you is much about who you respect and think is worth listening to, and vice versa.

While microblogging is also used much to share something that’s happening in your life, I don’t really think you’ll get the most out of it like that – and so doesn’t your followers. Of course, you are free to use microblogging for this as well, but I think other utilities, like Facebook statuses, are better for that.

Jim Campbell has actually written a pretty good article about how to write a good tweet at a conference, but I think those guidelines work with pretty much anything, if you use common sense to adapt them to said situations.

Bring the micro of microblogging to IRC

While IRC is a place of long-term discussion sets, there is no reason why it could not be a place of microdiscussions or lightning discussions, as I humorously nicknamed the concept.

It stroke me that I’ve been doing these kind of short-length discussions with various people for years. I did not know them all before bumping into them in IRC and with some, these lightning discussions were almost the exclusive way for communicating. This was my way to microblog before microblogging existed!

Later on, I realise now, when working in Open Source communities, a big part of the communication is a series of lightning talks between two or more people. While development should be as transparent as possible, it doesn’t need to be as upfront as possible. Logged and web-published IRC channels are as transparent as possible, but they are not overwhelmingly visible. From my point of view, this makes IRC a perfect place for communicating inside the developer community and demonstrates, how the micro of microblogging actually takes place in IRC.

It’s funny though how #xubuntu-devel is still not logged and published correctly to the Ubuntu IRC logs on web.

Does this prove anything?

I really like to avoid overhead on anything, and so do many people. Why would you need yet an another tool to be able to accomplish something that you can accomplish with your current tools? What’s the benefits of microblogging and IRC in relation to what I’ve covered earlier?

Okay okay, real microblogging can present the timeline of discussions better. Microblogging exposes you to a far wider possible audience. Microblogging is made comfortable to do even with your phone (so is IRC, though). Microblogging also reaches people better, considering they know how to subscribe to RSS feeds (because without those, microblogging appears as useful and lively as a real life bulletin board for the follower).

However, microblogging does not scale as well as IRC, when you need or want a broader discussion. Microblogging also does not deliver the same kind of feelings of connection and belonging to something as IRC does. While IRC does not reach a wide audience, it pretty often reaches the desired audience at least in Open Source communities. This is also as often enough, and it does provide a safe feeling that everything you say is not evaluated by the whole world. (Even crazy ideas and painful facts need to be said.)

Summa summarum

While microblogging is a new, powerful way to communicate, it’s not for me. IRC has served me microdiscussions for years, and that’s the way I’ve learned to quickly sort things out and announce things. In addition, the discussions in IRC can easily be extended to as big as I need. If I need something to stick around for a longer time, I can always update my proper blog.

Go have a lightning discussion.

2 Comments »

From my point of view, transparency combined with a feeling of some privacy makes IRC a perfect place for communicating inside the developer community.

New primary email for Open Source stuff

As part of the quest for more efficient and clean computing, my primary Open Source email address is pasi@shimmerproject.org starting from today. Just in case something still ends up there, I will still monitor the old address, as it’s now bound to my general @knome.fi -mailbox.

Thank you for your understanding. Stay tuned, more rants about Thunderbird are going to follow.

Comments Off

My new email is pasi@shimmerproject.org.

No longer the Xubuntu Marketing Lead

I think some of you have seen this coming for some time now, but now it’s official.

As of my email to the Xubuntu Developer mailing list some minutes ago, I’m no longer contributing to Xubuntu as the Xubuntu Marketing Lead. I will continue contributing to Ubuntu and Xubuntu as well through functional teams. This probably also means that I will keep sending some updates to the Ubuntu category of my blog, which is aggregated to Planet Ubuntu.

I hope you’ve had a pleasant journey this far. I have, and I look forward to our future adventures together.

2 Comments »

I’ve had a pleasant journey so far, and I look forward to our future adventures together.

New Ubuntu branding

It’s public! Today Canonical published the new branding for Ubuntu. The brand is based on the idea of “light“, and is reflecting the four key brand values in the Ubuntu project; precision, reliability, collaboration and freedom. To learn and see more of the branding, head to the new brand wiki page.

As the Xubuntu Marketing Lead I was invited to a meeting with the design team and some key members of the community at Canonical offices in London. We got to see the new branding stuff already in Monday, and the new stuff is pretty much exciting. I had a great time there and got to meet nice people from the community, with whom we discussed the new brand and how it could be incorporated into the community efforts, such like Xubuntu or the forums. Thank you Mark, Iain and all of you who were there!

As you can see on the wiki page, we’ve already produced a draft of the new Xubuntu logo as well as a draft for our new website. You can start seeing the new logo on daily images anytime soon, and we’re working hard to get the new Xubuntu website published well before the Lucid release.

Feel free to browse the wiki page and see the new branding yourself. More news on refreshing the Xubuntu branding, artwork and website to come.

2 Comments »

The new Ubuntu branding got published and reflects the four key brand values in the Ubuntu project; precision, reliability, collaboration and freedom.

What is freedom anyway?

Late last year Steve, the co-founder of Shimmer Project, wrote a longish blog entry about freedom. I wholeheartedly recommend that you read the article thorough. Today I’d like to raise up some points from Steve’s blog entry and go even further, pondering what freedom means for me and how I feel it actualizing. Things aren’t going to be easy to say, probably harder to read and even harder, almost heartbreaking, to admit.

A small introduction…

The Ubuntu community is definitely not the worst there is. However, there is lots of room for improvement. I’ve always felt that the Ubuntu community lacks communication. That’s very much what Steve said earlier, but what he said is not the complete truth. Even the Xubuntu team lacks communication and even once we have the contact with each other, probably the majority of us lack communication skills, more or less.

The freedom to speak and to be heard

Xubuntu has come a long way from when I started, and it’s totally because every individual in the team now and then. We all share the same passion – to make Xubuntu better. Developers come and go, but one could expect at least some natural growth for a project that has improved as much as Xubuntu has done. So why is the Xubuntu team as small as I started, or even smaller?

Steve mentioned the lack of information/communication making starting contributing really hard for a newcomer and a possible future contributor. I think Steve agrees with me that this comprises both technical and the more subtle, emotional, human-oriented communication. Getting the technical information out more efficiently would only need a bit more work, but fixing the human-oriented communication is way harder, probably even impossible via online methods only.

Getting the developer-user -communication working is a completely different story. While some of our contributors are seemingly spread amongst the community, there has been debates on how much “official” information they can output for example in their blogs. While I understand that an opinion of a single developer is not the official opinion, who can tell the users what the developer community has been working on and what kind of ideas we have?

The words we don’t have a community Steve promptly said (referring to the fact the Xubuntu developer community hadn’t actually grown at all) actually mean way more than just that. In the end, we’re just individuals who work together, enjoying each other’s company more or less. If our communication doesn’t work or we use our time arguing, where’s the community then? None of us is completely innocent, and I plead my own guilty as well. Sometimes we just don’t have a community at all.

What I’ve learned from my social service studies is that listening is not hearing. The fact that the Xubuntu team has now lost two contributors due to bad communication does tell everything is not alright. To grow our community and get things done in the future as well, we need to communicate better and actually hear each other.

Respecting volunteers

As you all probably know, Xubuntu is not sponsored financially by Canonical. We are an official derivative, using the same repositories as Ubuntu and all the other derivatives. This leads to many technical details and problems in addition to the communication problems inside the project. (The technical details are described in Steve’s blog, if you want to read more about those.)

While the Ubuntu project has a specific governance that the Xubuntu project also has to obey, nobody is saying how we should organize our inner governance. We definitely need a project leader that is well aware of the project overview, but I don’t think we need a project leader who can use a veto-vote everywhere.

With all respect to Cody, our former project leader, I regretfully have to say I’ve experienced a bit too much micromanagement for quite a long time. Weighting this and some recent discussions, I’m left with the feeling I’m not heard and especially that my skills are not valued. Comments like “you can be replaced” and “we don’t have to use your work anyway” are totally true, but tell a lot about the communication and relationships between community members, especially as long as there is no-one else in the sight replacing anybody and as long as the community like what you do anyway. Once you hear these comments from your own leader, who originally appointed you to take care of some area of the project, you will lose part of your motivation. That motivation is really hard to build up again.

Our vision…?

I was really excited to be building a new kind of Xubuntu community, based on council rather than a single project leader with complete dictatorship. Our meeting about the new governance went actually pretty well and we made some nice progress; the main direction seemed to be that experts (people who are given the responsibility for a specific area in a project, for example marketing, artwork, documentation, or packaging) and leaders on their subjects should have somewhat more weight in their words than other developers, since they most probably know their subject better than someone else in the team, including the project leader.

The sad truth is that after this meeting we’ve kind of reversed back to the old way of working. Right now I don’t even know if there is a possibility to get the council-type approach at least partially as our new governancy structure. Are people too afraid to do something wrong, to fail, to admit they were wrong? Is it better to go the “safe way” and continue struggling with the ever-decreasing amount of developers, with the Xubuntu project eventually diminishing for the lack of developers – or passion? What do we have to lose here?

Taking the next step

What do we need to do now to be able to step to the next level and bring more sustainability for the Xubuntu developer community and in consequence of it, the whole project?

Get the rest of the Ubuntu community communicate with us.

Again, this is mostly what Steve already described in his blog. As long as Xubuntu is part of the larger Ubuntu family, sometimes referred as hugebuntu, we need to get the latest news from the rest of that community. Many things affect us directly or indirectly and we could save the diminishing amount of developer hours if we knew most of the changes and plans the broader Ubuntu community did beforehand.

Too bad I don’t know where to start. As long as there are even a few people who are almost hostile about any cooperative efforts between the derivatives, not even talking about all the different core teams, our possibilities to work on the subject are very limited. I already tried to rant about communication in the Jaunty developer summit, but the outcome was pretty bad. I’ve heard a few efforts with similar ambitions have greatly failed before.

All this just leaves me thinking there is a big problem inside the Ubuntu community – lack of communication. I don’t know what would be the best solution for this, but the first step to get rid of problems is to acknowledge them. To be fair though, there is also people who get the community working better, but sadly enough their scope can’t cover all of the project.

Communicate more with users.

While I’ve already had some good feedback on listening what our users want and being available for them, it can’t be a one-man show. The developer community as a whole needs to reach out for our users. Our users are giving us valuable information on what could be better on Xubuntu and what already is awesome. Communicating with our users is the only way to build up a decent user community.

We also need to keep our work as transparent as possible, giving the users as much information on what we do and what is going on. This also means we shouldn’t do all we can to hide the negative vibes our community is having. Listening to our users first gives us the possibility to get them listening to us – whatever we want to say.

Communicate more with each other.

Any developer community needs communication. We’ve made progress on this already, but we have to start thinking what is the correct kind of communication. We are working on the project together and we should encourage and cheer each other as much as possible. We need to respect the fact that we are all volunteers and we all are pretty good in what we do for Xubuntu.

Good communication means people can throw suggestions around and give constructive criticism without anybody feeling they are not valued. We should trust our developers work according to the responsibility they got when they were appointed as team leaders and became part of the Xubuntu team.

Now that all this is said, it’s time to start taking actions. Let’s continue the discussions about new governance, start communicating more efficiently and attract new developers. If we can do that, it’s very likely that the Xubuntu community will be more powerful than ever.

Comments Off

Freedom in Open Source should not only be free software but also freedom to speak and act in the community.