Thursday, July 23, 2015

I'm loving Akademy!

And it hasn't even started. Scarlett and I flew to A Coruña arriving Tuesday, and spent yesterday seeing the town. Today is all about preparing for the e.V. AGM and the Akademy talks and BoFs following. 

Wish you were here!

Wednesday, May 27, 2015

Challenges and opportunities

Challenges are a normal part of life; and seeing opportunities is a skill all of us can get better at. This past week, though, has been something new.

The Ubuntu community and philosophy has been home to me. The Ubuntu Code of Conduct is not just about individual conduct, but how we make a community. In fact, the first sentence is Ubuntu is about showing humanity to one another: the word itself captures the spirit of being human.[1] This is my kind of place, where we not only have high ideals, but live those out in our practice. And so it has been for many years.

So it was a complete shock to get a secret email from the Community Council to me as a Kubuntu Council member announcing that Jonathan Riddell had been asked to step down from Kubuntu leadership. We (the KC) recently met with the CC, and there was no discussion of any issues they had with Jon. They never wrote to us asking for feedback or discussion.

Jonathan's questions to the CC about a legal issue and that of funds donated to the flavors were not personal, but done on behalf of the Ubuntu community, and on behalf of us, the Kubuntu Council and the Kubuntu community as a whole. We are still concerned about both these issues, but that pales in comparison to the serious breach in governance we've experienced this past week.

The Code of Conduct states: We expect participants in the project to resolve disagreements constructively. When they cannot, we escalate the matter to structures with designated leaders to arbitrate and provide clarity and direction.

The CC did not follow this basic procedure. The Community Council is full of great people; a couple of them are personal friends. The CC was established after the Kubuntu Council, and while the KC consists of members nominated and elected by the Kubuntu Members, the CC candidates are selected by Mark Shuttleworth, and then elected by the Ubuntu Members. [2]All Kubuntu Members are also Ubuntu Members. I first stated that the CC is unelected, which is incorrect.[3] I regret the error.

The fact remains that the CC did not follow the Code of Conduct in their procedure.

We have had a number of emails back and forth during the week.[4] What has stood out to me is the contrast between their approach, and our own. They have focussed on their feelings (feelings about working with Jon), whereas we continue to point out facts and ask them to follow the Code of Conduct. Naturally, we all experienced emotions about the situation, but emotion is not a basis for decision-making.

Of course, the members of the CC may perceive the situation entirely differently.

I wish I knew how this conflict will work out long-term. The Council supports Jonathan, and continues to ask for resolution to the issues he has raised with the CC on the community list. We have done so formally yesterday.

Jon is the person who brought KDE to Ubuntu, and Ubuntu to KDE, and has always functioned as a bridge between the two projects and the two communities. He will continue to do this as long as he is able, and we rely on his faithfulness for the success of Kubuntu. He is the magnet who draws new developers to us, and his loss would spell the end of Kubuntu-the-project.

The CC did not follow the basic procedure and raise bring the issue they had with Jon to us, the Kubuntu Council. We await their return to this principle as we work to find a way forward. We are determined to find a way to make this work.


Thursday, January 15, 2015

Last chance to celebrate KDE 2014 fundraiser

Today is your last chance to get a KDE-branded exclusive postcards! Donate at the KDE End of Year 2014 Fundraising.

They are beautiful!

Sunday, January 11, 2015

Drawing in new contributors and growing the community

It's a really exciting time to be active in both KDE and Kubuntu. So many new initiatives, projects, new collaborations. And yet.

Comment often heard over the past couple of years: we've lost $person / we're missing people to maintain/lead/do $project. This is understandable, and to be expected in a large, mature organization such as KDE; a dynamic project loses people as well as gains new contributors.

In contrast, almost daily in #kde and #kde-devel IRC channels we have new people trying to find some way to get involved with KDE. In an effort
to bring the solution and the problem together, at Akademy we
brainstormed and came up with the Mission forum.

What that forum needs is postings! When a developer is thinking
about giving up maintainership, please write a Maintainer Wanted
post. When you are fixing bugs, and see a valuable bit of code which needs
porting, please write that up and put it on the forum.

Naturally we always need ideas for possible Google Summer of Code projects, and the forum is a good place to post and develop those ideas. Eventually they will be moved to our GSoC docs, but they can be discussed and refined on the forum.

New skills needed, documentation, internationalization, translation, artwork, promo, and web work tasks are also suitable. If you have written a "help wanted" blog or mail list email in the past, dig it out and post it on the forum. Be sure to clearly outline for people how to undertake your tasks.

In fact, once Google Code-in is over, how about putting some of those tasks which remain into the forum? Those teams who didn't have time to mentor during the contest can still write up small tasks and put them into the forum as well. Once you get into the habit of creating postings, you'll be prepared and want to participate in GCi next year!

I know developers often don't like forums, but guess who does like them?
Beginners and people who are using search engines. We need these
people to join our community and start helping out. That will happen
when we ask in a public place, which is the forum.

One more time:

Students, Google Summer of Code is coming, but not quite yet....

We've been seeing more and more questions about GSoC and how to get involved.

GSoC 2015 will be happening, but it is not yet time for orgs to even apply, much less be accepted. So we have no ideas page as yet for GSoC 2015.

That said, the best way to have your GSoC proposal accepted is to join
a team NOW and work with them on triaging and fixing bugs, and working
on old and new projects. As you work with your team members and the
codebase, you will be learn how to create a proposal which fits the needs
of the project, and also find willing and able mentors willing to guide you. Remember, mentoring is hard work. Probable mentors want to choose students they can trust to complete their proposal successfully.

The time to prepare for GSoC is now -- but it is not the time for
creating proposals yet. The important part of GSoC is embedding
yourself into your chosen project.Your energy can transform a project
from one lacking a spark into one brimming with enthusiasm. Go for it!

How to join a team:
  • Find the best list(s) and subscribe, and scan the archives.
  • Join the relevant IRC channels and hang out there All The Time.
  • Search the forum for areas/posts where you can help out.
  • Start searching for bugs which you can test, and fix.
  • Learn how to propose your code changes to Reviewboard.
Other ways to prepare yourself:
  • Read the KDE Developers manual and prepare your development environment.
  • Read the GSoC Student Manual.
  • As you work your way through the documentation, please fix errors you find, or update it. Remember, documentation is part of the code we provide to both other developers and users.

Monday, December 29, 2014

The Innovators by Walter Isaacson

I just want to mention The Innovators by Walter Isaacson. I loved that "How a group of hackers, geniuses, and geeks created the digital revolution" began with Babbage and Lady Lovelace.

We're familiar with many of the people and projects Isaacson discusses, but there were many people of whom I knew nothing. Vannevar Bush, for instance, and his prophetic essay, As We May Think in July 1945.

What I appreciated most was the focus on collaboration. Time after time "lone geniuses" labored alone, and saw their work die with them. The work that lasts is done by teams of people who both inspire and perhaps annoy one another, but manage to bring their skills and  best selves to the group effort.

A good read.

PS: A day later, I'd like to add that we need better STEAM education from preschool through college, for boys and girls. Science Technology Engineering Arts Mathematics for all.

Wednesday, December 24, 2014

Solstice greetings, happy Christmas, looking ahead to the new year

Time to sum up 2014 and look ahead to 2015.

I'll start with the bad in my personal life: I heard this week that my dear younger cousin has cancer in his lungs, brain, bones and lymph. This is very hard to accept. He is only 57. My dad continues on his slow downward slide, but I think Brian will go first. I don't see how it is possible to beat cancer that is basically everywhere. My long-time Alsachat friend Maria has gotten word that she too has cancer, and they hold out some hope. She has cancer in one ovary and is on chemotherapy.

The good: my husband has worked his last day at Boeing after over 30 years there, and is retiring officially at the end of the year. His plans for hiking the Pacific Crest Trail are falling into place; he has most if not all his equipment, and has tested it, and the clothing he'll wear, and food he'll eat. He is hiking over 20 miles many days, and I think if the weather holds out for him he'll make his goal of walking from Mexico to Canada from April to September. to follow his progress.

Bob's schedule will complicate mine this year. I'm unsure whether travel to Europe will be possible, although my son Thomas has offered to live here when I leave, feed my cat, make sure the bills are paid, Bob's blog updates are published, and food boxes sent. I hope this all works out.

Also this past year we made some progress in remodeling our house; our new bathrooms are awesome! Bob gave me a 23&me kit for Christmas in 2013, and I got results this year. It's been quite fun to find distant "genetic" cousins, and also do some research and database cleanup. Gramps is great!

In mid-summer, Bob and one of his hiking buddies wanted to do a hike from half-way up Lake Chelan to Stehekin at the north end of the lake via the Lake Trail. I took the ferry north with them, and waved goodbye when they hopped off the boat at the trailhead. At Stehekin, I bussed up to the Ranch, where I had the most lovely peaceful stay. Bob and Patty eventually got to Stehekin and joined me at the Ranch for a day, before we left on the fast boat down-lake to Chelan, and then the drive home. Patty and I plan to meet Bob at the Ranch this year, near the end of his hike. Should be fun!

Now for the KDE and Kubuntu side of my life, which was really rich this past year. As KDElibs were split into the KDE Frameworks, I was asked to edit another book for KDE, about the Frameworks. Since I'm no coder, we assembled a team to work at the Randa Meetings. See some of my blogs about this or for more. In short: we have a good start to our book and hope to publish early in 2015. Also in KDE this year, Plasma 5 has debuted, and the Visual Design Group (VDG) has attained world domination. That team is the bubbles in the champagne of the KDE community for sure.

At the end of April I staffed a booth at Linuxfest Northwest for Ubuntu and Debian. Unfortunately, I was mostly alone except for *lots* of visitors who wanted DVDs or USB drives of the latest ISOs. Sooooo busy! This year, I think we'll have a KDE booth. I don't think I'll have time for burning ISOs unless we share with Ubuntu and there are others to staff the booth too.

This year I've already committed to traveling to Spokane for a new Linux fest there in May. Should be fun!

Early in August 2014 I flew to Geneva and met up with a friend I only knew online before now. I also got the chance to meet up with Christian, and another friend I only knew from Kubuntu IRC. Then the best train ride in the world to Randa, where we got together with all the Frameworks team to get our book well underway. Because of some connectivity problems, we ended up with the best process ever: our book chapters live in each of the Frameworks git repositories. We have a process to assemble all the chapters simply, so people can get PDFs or ePubs. Stop by #kde-books on freenode if you'd like to help out.

Early September, it was time to meet Scarlett, another person who was a friend only online until then, and fly to Vienna together. There we met Stefan, who walked around his beloved Vienna showing us his favorite places. What a great lead-up to Akademy in Brno! A very nice part of this trip was that it was sponsored by the Ubuntu Donors since we were headed to the annual Kubuntu meet there at Akademy. Such support feels great. I'll write a separate blogpost about Akademy, the plans and work we did there, and how much progress has been made.

This fall, some cool things happened. Locally, we got a KDE Meetup going. That helped a lot when the LISA/USENIX conference happened in Seattle, because quite a few of us could plan to be there to staff the KDE booth. One of our guys sat in front and used Krita to draw stuff most of both days. That drew a lot of interest from many of the attendees. Finally, I was a lot more active in our KDE mentoring programs this year, first Google Summer of Code, then Season of KDE this fall, and now Google Code-in through the next few weeks. I do love working with my fellow admins, the mentors, and especially the students. It is really cool to see how we can all work together.

Altogether, 2014 was an amazing year, absolutely full of wonderful experiences and learning. While some terrible times lay ahead in 2015, many exciting opportunities await as well. Hopefully the mourning is balanced by the work, the friendships, the research, writing, cleaning, simplifying .... too many more verbs to list.