Showing posts with label UDS. Show all posts
Showing posts with label UDS. Show all posts

Thursday, May 15, 2014

Today's catch-up meeting with the Ubuntu Community Council

The Kubuntu team has been thinking about what to bring up to the CC for a few weeks, and at our Mumble meeting, discussed it there as well. Rohan Garg, Scott Kitterman, and Philip Muscovac (Shadeslayer, ScottK, and Yofel) attended with me (thank goodness!).

We put all our discussion items on a wiki page: https://wiki.kubuntu.org/Kubuntu/CCmeeting. Since the moin moin wiki is unreliable, here is our list:

Summing up -- PAST

Since last year, the threats of legal action against Mint and other derivative distributions have upset our community. We were disappointed in the reaction of the CC -- it seemed to us that the CC was just doing as Canonical directed, rather than work with Mint to bring them into the community.

We continue to feel apprehension over Wayland/Mir situation, which has brought the Ubuntu brand into controversy, and has caused a lot of bad feelings from our upstream. We hope for peace and technical excellence.

We are missing our face-to-face UDS meetings with the rest of the Ubuntu community. Last year and again this year we've arranged a Kubuntu meeting at the KDE yearly meeting, Akademy. Last year we met in Bilbao, this year it will be held in Brno, in the Czech Republic. However, we really miss being able to touch base with the rest of the Ubuntu community.

PRESENT
We have our own webserver now, at Kubuntu.co.uk. Kubuntu.org will be moved there soon.

We're now using the KDE wikis to develop our user docs, and some community wiki pages. Moin moin is just not reliable. We've gained some more translations this way for the documentation. We ran out of people who were experts in Docbook, which is why we started using the MM wiki.  http://userbase.kde.org/Kubuntu is for writing; when docs are done they are moved to the website.

We are wondering about the state of donations. On the donations page, a report is promised, but we've not seen one, and none are linked to. http://community.ubuntu.com/help-information/funding/

FUTURE

Discussing how to handle KDE's new Frameworks, Plasma Next, and new Qt. In 14.10 we'll be rather conservative, and offer the newest stuff being released this summer in a PPA. We may be able to spin an ISO of this software; we are still pondering our best path forward.


It was encouraging to hear from Mark Shuttleworth during the meeting, as well as Jono on the funding report. I'm not sure any issues were resolved, but it did feel like the air was cleared.

Full text of the meeting is here: http://irclogs.ubuntu.com/2014/05/15/%23ubuntu-meeting.html#t17:39. Thanks to tsimpson for the link. :-)

Saturday, May 18, 2013

The water we swim in

Healthy relationships. I've been thinking about them not in my personal life, but in terms of teams in free software. When I first began contributing, it was within a team creating an application (Amarok), so rather small. Then I became active in Ubuntu-Women, which is larger, but still not huge. Then Kubuntu, then the larger Ubuntu community, and now KDE, which is truly enormous.

In all of these projects, communication and trust are paramount. Dialog which fosters creativity and progress is only possible when people enlarge their trust in one another. Along the way to the highest trust levels, many barriers will come down, as people allow them. Sometimes these barriers are invisible, until someone points them out.

I thought I'd seen a cartoon illustrating this story, but a web search tells me it's a story by David Foster Wallace:
Two young fish meet an older fish, who asks them “How’s the water?” The younger fish look at each other and say, “What the hell is water?”
I was reminded of this story recently while observing the various reactions to the removal of the Community link on Ubuntu.com, the portal to the Ubuntu project. The link is coming back, so I'm not complaining. However, what I've noticed is that most of the people discussing the issue seem to be talking past the folks they are hoping to connect with. The emotions expressed range from puzzlement, to shock and outrage, with little understanding on the other "side" on the perceptions causing these reactions.

So how is the water? To me, the drama played out completely predictably, because any time you have one company selling a product, and volunteers working in that same project, you will have class issues, and class is like the water fish swim in. People are often not aware of it, and thus have difficulty dealing with their emotions around it, because they have been taught to ignore it, or even that it doesn't exist. So when the designers removed the link, it was felt as a slap to the face of community members, while the designers see it as just a step to a clean, functional design. The conversation about this change at the recent vUDS clearly betrays this lack of understanding of the other on all sides. http://summit.ubuntu.com/uds-1305/meeting/21740/community-1305-ubuntu-website-planning/

There is no such thing as a culture without class. There are always power imbalances, and privileges. However, that doesn't mean that class is the death of the Ubuntu project, or that volunteers and companies can't happily co-exist. They can, but the fact of class must be acknowledged, and those with privilege and power must realize what they have, and use them on behalf of the project.

A healthy culture has hierarchy, but not one based on domination. In fact, in FOSS that is part of what we are attempting to dislodge, right? We want our hierarchies to be constructed for function, not to rule over us. For instance, those who demonstrate their skill in packaging or coding are given the right to upload to the repositories. And those who grant them that right are those who already have built their reputations by using their skill and trustworthiness in that domain.

Recently there has been a breakdown -- or an apparent breakdown -- in that hierarchy of function in Ubuntu. And I think that both those inside Canonical and those outside, perceive that the other is the one causing that break. So, some repair is needed.

All of our differences can be overcome as we build (or re-build) trust. However, all sides of the issue will need to think about, process emotion about, and finally discuss openly what has gone on. The replacement of the Community link alone will not mend this breach, nor will brief virtual UDS sessions. In fact, I think the lack of in-person face-to-face interaction is allowing this divide to grow.

Folks, we don't want resentment and suspicion to grow, so we are all going to need to work on this if the Ubuntu project is going to continue to thrive as a free software enterprise. In my opinion, thinking about and discussing class issues are fundamental to that effort.

This blog appears on the Linuxchix, KDE and Ubuntu planets, and these issues of class appear in all teams. Health and progress are the goal, and honest dialog is the means. I propose we look one another in the eye and start a conversation. These are difficult dialogs, but our health is at stake.

Thursday, March 7, 2013

Thoughts and worries about the proposed new Ubuntu processes

Today began in a virtual UDS session (Google Hangout) with the Xubuntu team. The video can be seen here: http://summit.ubuntu.com/uds-1303/meeting/21666/community-xubuntu-contingencies/ . Xubuntu devels stopped by #kubuntu-devel and asked us to bring our list of concerns to share. The list we developed:

  • The new system will do away with releases for each upstream KDE release, which is a prominent feature of Kubuntu. One idea is to do releases of LTS+PPA with latest KDE but that's against policy and needs technical changes to make happen. Or will there be a way to create ISOs from PPAs?

  • Mir is a worry since KWin will clash with it (a compositing manager inside a compositing manager). How good will continued Wayland and X support be?

  • Where to put Beta releases of software? Testing is a huge part of quality. So while a PPA seems the obvious suggestion, but they'll get less testing there. Now we use a beta ppa only for backports. Consistent quality would require staging major changes somewhere else.

  • How will library transitions be handled outside of cadence?

  • Launchpad breakdowns. We are trying to automate more of our building tasks, but often the scripts must be run repeatedly because of Launchpad timeouts.

  • Weakness of unit & hardware testing. This is crucial for a successful rolling release.   

  • Security updates - who gets them? When, and how often? (LTS will get them as usual, but for rolling it seems the monthly snapshots don’t get any? you need to use rolling)

  • We will be more dependent than ever on syncing with Debian for rolling. We already import, and release, Debian packages with RC bugs. Colin Watson suggested checking Ubuntu-Critical bugs anyway. Scott Kitterman replied that this would recreate painful Debian transition. Beta/buggy software is often uploaded into Debian Unstable, and proposed changes mean even less prevents bad software  from getting into Ubuntu -release.

  • We need a policy for when to move packages from PPA to rolling.

  • PPAs for non-Canonical contributors have low armhf/powerpc ability.           
          * KDE doesn't compile in qemu (bug 1077116) [Philip Muskovac]
          * Fixing these might be an acceptable cost of rolling release according to Steve Langasek.

I wish I could say we got answers to all of our questions. On the other hand, it was good to have those advocating for a rolling release listen to our concerns. The discussion continues on the Ubuntu-devel list and in the IRC channels. Of course the Kubuntu developers will continue to voice our concerns, and listen as the proposals change over time. As Rick Spencer said, he made a proposal to Ubuntu developers, not a announcement from Canonical. As we heard in the session today, no proposal has been formally submitted to the Technical Board. It seems possible that 13.04 will be released as planned, with the beginning of new processes put off until more of the necessary supports are put in place.

I want to thank everyone involved who continue to work so hard to provide an excellent user experience, even when we disagree about how best to do that. And especially the Kubuntu and KDE communities. You rock!

PS: This mini-UDS was a good place to share our concerns, and perhaps do some planning. But it in no way compares to a real UDS, with actual face-time, and the essential "hallway track."

Wednesday, March 6, 2013

Adventures in the CLI: fixing sound using apt logs

Plunging back into community involvement this week meant installing mumble, a free messaging system. The virtual UDS (Ubuntu Developer Summit) Canonical is hosting at short notice this week (today and tomorrow, actually) is being conducted on Google Hangouts. While these can be cool, they limit participation to ten, and to those who have GooglePlus logins. So the Kubuntu devels wanted to try mumble instead for our meeting(s).

I usually use apt-get to upgrade and install packages, just because it is faster and easier. Alt-F12 to get nifty drop-down bash session, up-arrow to get to commonly used commands, and viola, done! However, this time apt-get installed most of GNOME along with mumble, such as evolution, plus gnucash and other stuff! Once all this was installed, I had no sound of any sort; from speakers, in flash, through earphones. Sadness.

I began working through the sound troubleshooting guide, but none of it worked, and didn't seem to apply anyway. When I asked in #kubuntu-devel about the mumble install, Scott Kitterman asked the right questions, and told me that his list of dependencies was small, as was the list of recommended packages, and how to find the complete list:

$ cd /var/log/apt/
$ ls 
$ cat history.log

This gets you a wonderfully detailed list of all packages dealt with by apt. I started by removing the obviously un-needed packages, including mumble itself. The list was so huge that I didn't get far, however, ScottK had suggested removing slpd and roaraudio. After reading the man page for apt, I got a bit more clever about getting more stuff in one fell swoop:

sudo apt-get purge gnome-mahjong*

for instance, gets the libs and -dbg packages too. Once I went back and purged roar* -- I got the offending libs, and had sound again!

By coincidence (I think) I had a problem in flash in Firefox at the same time. So Youtube videos were silent and about 100 times too fast. Once sound came back, I noticed that I had sound in Youtube in Chromium, and everything was the correct speed as well. Flash still seems broken in FF, but that now seems unrelated.

By the way, when I re-installed mumble using Muon, everything worked well. Although I haven't tested it yet, I expect it to work as advertised. 

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.

Saturday, August 6, 2011

Contributions of Non-Technical People

First, congratulations to Bambi, Romain Perier for his new Kubuntu Developer status. He's one of our wonderful packagers who create the new KDE packages we need to run the latest Kubuntu. Bambi does some development, and this is important. And we need non-technical contributions too!

In fact, if you run and love Kubuntu, we want and need your creativity, your testing, your bug reports, your corrections on the wiki, your help on artwork, documentation, promotion (like this blog!), your helpful voice in IRC, identica, twitter, Google+ -- the sky is the limit! Community work is as important as the code, because people create the love, create the community, create the software.

As a non-technical person, I wanted to give back to Free and Open Source software, which I've been using for about 10 years. My process was to think beyond Linuxchix, which had been my homebase for those 10 years. I thought about my favorite application, which is Amarok. I looked around in the documentation, to see how I could help out. I noticed that the user documentation was outdated and not well-maintained. So after reading the mail list for a few months, I got my courage up, and asked about helping on the list. I was immediately greeted, and asked to join the IRC channel to talk about my ideas. Once I connected to Freenode and set up my identity there, I was made most welcome in #amarok, which made me feel wonderful, and more confident that I could contribute. It ended up that I headed up the Documentation team, and have been writing and editing the newsletter as well as the Userbase documentation. Through this process, I worked with the KDE WWW team, and learned more about how both Kubuntu and KDE work. Basically, I became part of the community team, even before joining the Community Working Group.

In Kubuntu, I haven't done as much as I would like, but I plan to get more active in the documentation team; editing if nothing else. The Kubuntu Council granted me membership, which is also Ubuntu Membership, based on my work with the LoCo, my help in #kubuntu, and work with the Ubuntu-Women. And Canonical sponsored a trip to Orlando, Florida to Ubuntu Developer Summit (UDS) last year.

I'm writing this blog post from Desktop Summit in Berlin; my lodging and travel sponsored by the KDE e.V. In June, they sent me to Randa, Switzerland for a sprint. Some of the wonderful rewards for contributing. If I can do it, you can do it!

Friday, April 22, 2011

Weeeeeeeeeeeeeeeeeeee!!!!!!!!!!!!!!!!! Kubuntu Natty is on the way!











Wow, it seems like just a few months ago we did the planning for this release, at UDS-N. Now beta time is almost done, and Natty Narwhal will emerge fully-formed. It really has been an amazing ride, and I'd like to thank the Kubuntu team for all their wonderful work.

Also, without the encouragement of first the Linuxchix, and then Ubuntu-Women, I never would have been part of it. A minor part, but I did my best to help out where I could.

In this next cycle, Oneiric Ocelot, I'll be less involved with UDS-O, since I'm attending remotely. However, I *really want* to work on the Kubuntu documentation this cycle, and I resolve to do so.

Thursday, October 28, 2010

Surviving, Thriving at Ubuntu Developer Summits

First: to survive, one must attend, in person or remotely. Attending in person involves either asking for sponsorship from Canonical, or paying your own way. Attendence is free, so local folks can register and walk in. Without the encouragement of my fellow Ubuntu-Women team members, requesting sponsorship is not something I would have considered. However, the application process was painless, and I was sponsored! My flight, food and lodging are all included, which is amazing.

Since I have a wonderful friend who lives close to Orlando, Florida where this UDS is being held, I flew in Friday, and spent two wonderful days on the Wekiva River, paddling and boating up and down the river. Besides hours spent catching up on our lives (years spent separated by an entire continent!), we ate simply and slept when we were tired. So I arrived Sunday night rested and ready to work.

Second: Promptness is appreciated. Rooms are shared with a room-mate, so set your alarm early enough to allow time for both of you to shower, dress, eat, and arrive for the first events at nine in the morning. This involves going to bed the night before, rather than spending it at the hotel bar!

Third: Set up what you will need to participate fully in your sessions before they begin. If attending in person, a netbook with good battery life is best, with Quassel-with-a-core installed, along with your favorite browser(s), Gobby (*UGH!*), and time to review the documents associated with the sessions you'll be attending. This involves first reading the blueprints of the issues you find important, subscribing to them, and registering your attendence as essential if this is so. The scheduling software (Summit) attempts to allow every essential person to attend all their sessions by shifting the timing of the sessions. I haven't found a way to go back and change subscribing to subscribing and must attend if there is a way. There are a couple I had to miss because I didn't check the essential box. Once you find out the name of the rooms, join all the room channels in Quassel so you don't have to do this later. I chose Quassel on my netbook because it is lighter in weight than my favorite Konversation, but I didn't have time to set up a core account. I wish I had done, so I had all UDS sessions in IRC.

If you are attending remotely, you'll need to connect to the streams through Amarok or your favorite music/streaming app. Fire up IRC, join all the room-named channels, and you're ready. You might want earphones since some of the voices are far from the microphones. Don't be afraid to "speak up" in IRC, and ask people to repeat things, or to speak more clearly/loudly. If gobby is being used in your session, be prepared to help take notes, fix spelling errors, clarify points, etc. This is a collaboration. Etherpad may be used as an alternate, if the session leader chooses.

Fourth: Eat enough - there are good meals provided, with plenty of fresh fruit and vegetables. I tried to sit down most of the time with people I did not know, and fix that. :-) Drink enough -- not at the bar, silly! Drink enough water to keep you healthy. Coffee is provided, along with tea, pop, snacks, etc. Sleep enough -- this is the hard part. You will be meeting all the people you've been working with all year, many for the first time. The temptation to spend all your time socializing will be strong! Don't exhaust yourself. Have fun -- yes, the work is fun, but there are opportunities to party, to visit local cool sites (here, Disneyland, of course! And Universal Studios, Sea World, etc.). Choose wisely, take lots of pictures, and you'll have a time you'll never forget!

Fifth: Take time to blog, tweet, dent about what you are doing. There are countless people who want to know, or need to know. Be eyes and ears for them.

PS: If I sound preachy, it's my future self I'm preaching to. :-)
PPS: Pictures in a bit.

Thursday, October 21, 2010

UDS and You, Wherever You Are

I was fortunate to get sponsorship to the Ubuntu Developer Summit in Orlando, Florida, but most of the participants did not! Many if not most folks will be in IRC and listening to the streams, and we on-site participants will be in IRC also, and be responding real-time to those of you who are remote.

Laura Czajkowski has written a great guide to doing this, http://www.lczajkowski.com/2010/10/19/how-to-remote-participate-at-uds-n-and-get-the-most-of-the-sessions/ and I hope you will try it out. Look at the sessions, and pick a couple of them, and BE THERE!

Apachelogger has updated his Icecast script so you can listen right from Amarok. Use the script search to find it, and then select your sessions from the Internet session.

I look forward to "seeing" you there -- especially you Kubuntu folks!

Saturday, October 16, 2010

Blogger sadness > New Blog

I'll keep up my Linux Grandma blog here for now, but Blogger has started adding an insidious ad across the blog content, obscuring it from the reader. That must be really annoying, and I don't want to subject people to that. Serendipity is the blog software that KDE uses, and so far, it seems great. I might install it on my own server for the other blogs I have, and move the content from Blogger. What a pity; Blogger used to be great.

Maverick Meerkat Kubuntu, released 10/10/10, was quite an adventure in installation, due to PEBKAC (problem exists between keyboard and chair), but with the help of my son, and friend maco, and my blogged experience of the last install, I have quite a beautiful install going.

All apps installed well, most importantly Amarok and Konversation. Once I regained my old /home partition, I have my music again, unfortunately without covers and lyrics. However, the new cover-fetching is excellent, and I hope to have that all rebuilt in the next couple of months. Until then I'll be playing "Random" a lot!

While mentioning Amarok, I have to say that it's Roktober, so give! I did, and it feels great. Also, it's great to have it built from git again. All the latest!

The biggest surprise with Mav was installing Skype again, to test my built-in video camera and mic. Previously, the camera worked, but never the mic. I thought maybe it was mis-installed. However, once I unmuted it in pavucontrol (Pulseaudio controller), it worked perfectly!

I've been recently given Kubuntu membership, and am headed for UDS next weekend, to plan for Natty, the next release. Please give me any feedback you'd like me to take to Florida about the future of Kubuntu.

I'll be blogging, at least about KDE, Kubuntu, and Amarok here: http://amarok.kde.org/blog/categories/31-valoriez.

Such a pity about Blogger. ::sigh::