Following up on the discussion opened up by Colin Watson on ubuntu-devel and further discussions at vUDS, we’ve created a public mailing list to continue exploring and coordinating all the work around the new packaging format and changes needed to the surrounding systems.
You can sign up joining this Launchpad team: https://launchpad.net/~ubuntu-appstore-developers
Since we didn’t want to block on having everything cleaned up, some documents thrown in the mailing list may not be publicly visible. Apologies in advance while we slowly move them over to be accessible by everyone. We’ve decided to take a pragmatic approach here instead of blocking until everything was perfect so the discussions could all happen in public.
So, I've been around the Ubuntu community for a while. I installed 4.10 (Warty Warthog) as soon as it came out, I was fighting to keep my Debian installation usable at the time. I instantly fell in love and dove into the community, I wanted to do whatever I could to make the project succeed. It was exactly what I was looking for. At the time, Canonical was also shipping CDs to anyone who wanted them, which gave the project a much more professional feel to it.
And, the focus Mark set for the project turned out to be the right one, it very quickly converted thousands of open source enthusiasts to it and a solid, technically capable community started to be built around it. Soon enough, with the focus laser-sharp on making Ubuntu as usable as possible, non-technical folks started to show up, people who were Windows users but were tired of it and looking for something better. These people gave our project an awesome foundation for support (once they figured out how to make certain things work, they'd immediately help the next person who came along with this problem). Translations grew, since it was a great way for a non-technical person to help. documentation grew, advocacy grew, communication, marketing, you name it, it was growing.
As things moved forward, there were some tough decisions to be made. I remember when Compiz came around, it was very immature and almost guaranteed it would break your system, just have a quick read through the Slashdot comments! You could very easily replace the word "compiz" for "unity" when it was first introduced and you'd have most of the same comments that went on when that first happened.
But, it was the right choice. The hard and unpopular choice. We, the community at large, mostly wanted a stable system. Mark, Canonical, were pushing to mature the technology so be able to build awesome things on top of it. It was the same story for Pulseaudio, the same for binary drivers, we've been here before, over and over.Change is very hard, and a lot of it feels wasteful. Nobody wants to waste their free time, you want to make it count.
As for where we stand today, I first want to be clear that my initial reaction to the flood of changes being proposed upset me as well. A lot. I laid low for a while so I could clear my head and understand what was going on before reacting. When the Rolling Releases proposal came out, I read the email on ubuntu-devel (which, btw, is where I read about it, there was no internal Canonical "announcement") and I was frustrated with how it was being presented. It felt like Canonical imposing whatever they wanted, bulldozing over the community. How could Rick do something like that? He's a smart and well-intentioned person, this isn't the smart thing to do. I started writing up an angry email to the Community Council, and as I did, I stopped to re-read the original email to rant with specific references. When I did, I couldn't believe my eyes. The email was clearly stated as a proposal, open to discussion with quite of bit of work done beforehand, ending the email with:
"Such a change needs to be discussed in the Ubuntu community. Therefore, I asked my team to put together a strawman proposal for how such moving to a monthly cadence with rolling release might work."
Go ahead, read it yourself. As a long-time member, my gut feeling is that in the past this would of been presented to the Technical Board first to be discussed, and then a wider conversation would be had. But the reverse makes more sense to me actually, have a wider conversation first, then bring it to the Technical Board.
So, now I deleted my email and started all over again. I explained how I was feeling rather than rant about things that apparently didn't happen as I imagined them, and just admitted that I no longer knew where we were as a project and needed to talk it out a bit.
So we did. We talked, vented, ranted, looked at the positive side of things, the negative, remembered the past, imagined the future.
The way I see things now is that the project has changed. But this was the path all along, it should of been more obvious. First we won the Linux distro user base, gained support, a community, a clearer focus on what less technical people wanted and it felt great. People were moving to Ubuntu left and right, first on the desktop, then the server migrations came along with it. But that was not the goal. The goal was (and I quote from bug #1) "Our work is driven by a belief that software should be free and accessible to all.". The "all" part of that is the key. That's why we made the desktop slow and buggy for a while to introduce compiz, even though it didn't really fill any need for technical users. Same with Unity, same with Pulseaudio, same with the Ubuntu font, same with shipping free CDs to anywhere in the world.
So as we progressed in our goal, technical users felt a bit more and more distant from what was changing, because they were no longer the primary user. It makes the "scratch your own itch" part of free software a bit harder. In exchange, I started to meet taxi drivers who were Ubuntu users, musicians, graphic designers, writers. I'd see Ubuntu out in the while in the strangest places.
And now, the world has changed. It no longer seems like the way to make computing available as free software to everyone can be accomplished with just a great desktop. Mobile phones and tablets is where most of people's time seems to be shifting to. It's a multi-device world and it's here to stay. If we want to fix bug #1, we now need to change tactics and tackle the full story. There seems to be a window of opportunity for us as a project right now, I don't think we'll get many more of these. It feels like a now-or-never kind of moment, and I can't imagine having invested most of my energy in the last 8 years fading away into a niche market. That's not what I set out to help do.
It's going to be a bumpy ride for a while, we need to move fast, and speed is not one of the easiest things to do when you need to find consensus across many different people, timezones, interests, goals, agendas and languages. I don't see what other choice we have than to rise up to the challenge and find a way to make it work.
Speaking purely from a personal point of view, I think Canonical will need to push harder for changes in processes, tools, libraries and focuses. I also happen to think Canonical has done poorly at presenting and driving these changes. Not due to a lack of trying to do the right thing, it's just really hard to do. Stress, pressure, deadlines, partners, confidentiality agreements, private negotiations, business deals to ship Ubuntu on millions of devices, it all sets you up to rush and get things done as quickly as possible. That's how the market works. But when you're not immersed in all of that, from the outside, it just looks slightly evil and a bit like bullying.
I think Canonical can and will do better, it has to, I feel the survival of the company partially depends on it.
One thing to remember though, is that free software is very much like evolution, survival of the fittest. This means trying out many different things, and the best ones overall survive and thrive. Competition is essential. The fact that Canonical is putting out there more free software projects is the best thing that can happen to the movement, no matter how many times you yell out that you know for a fact that if that same effort was spent on an existing project it would all be better. If that were true, there would be one Linux distro, period.
As long as it's free software, and Canonical is shoveling code into it, that's what counts at the end of the day. Working, maintained code. Don't forget that. If Canonical is wrong about, let's say, that investing in Mir is a better bet than investing in Wayland, ultimately, it's Canonical's money. If it's done in a way that developers are drawn to help, it'll be cheaper and happen faster. It's a win-win. The fact that they are betting on free software no matter what is what counts.
So I think it's time. In many ways this feels like the last big battle. We fought and won a lot to get here, it's now time to win or loose the war.
There seems to be quite a bit of buzz around Yahoo! effectively laying off remote workers (making them choose to start going to an office or resign), and I've read different perspectives on the subject, for and against remote working.
Having worked at Canonical for over 4 years, and in open source projects for quite a bit longer than that, my knee-jerk reaction is that the folks crying out that remote working just isn't as productive as working in an office is pretty short-sighted.
Canonical has hundreds of employees working remotely, far more than working in an office, and it seems like we're generally a very productive company. We take on huge competitors who have ten times the amount of people working on any given project, and we put up a pretty good fight. So I can tell you remote working is full of awesome for both the company (productivity, get to choose from a huge pool of talent) and the employee (no commute, less distractions).
I also think that the fact that open source projects are taking over the world at an incredible pace is a pretty huge testament to just how great remote working can be. This is even an extreme case where people aren't even available on a regular schedule with much tighter and clearer shared goals.
All that said, there are several ways things can go wrong with remote working.
Thoughtlessly mixing remote and co-located teams. All-remote and all co-located tends to work out easier. Mixing these things without having a clear plan on how communication is going to work is most likely going to end up badly. The co-located team will tend to talk to each other in the hallways and not bring the people who are remote into the loop, mostly because of the extra cost of communication there. If making decisions in person is accepted, and there are no guidelines in place to document and open up the discussion to the full audience, then it's going to fail. Regardless of remote-or-not, documenting these things is good practice, it provides traceability and there's less room for people to go away with different interpretations.
Hiring remote workers that are not generally self-directed. I can't stress this point enough. Remote working isn't for everybody, you have to make sure the people who are working remotely are generally happy making decisions on their own on a daily basis, can push through problems without a lot of hand-holding and are good at flagging problems when they see one. These types of people are great to have on site as well, but in a remote situation this is a non-negotiable skill.
Unclear goals as a team or company. If what people are suppose to be doing isn't crystal clear to everybody involved remote working is going to be very messy. Strongly self-directed people are going to push forward with what they think is the right thing to do (based off of incomplete information), and people less strongly independent are going to be reading a lot of RSS feeds.
I also think there are some common sense arguments against remote working that are actually an argument in favor of it.
Slackers will slack harder when at home. So, if you're at home, who's going to know if you spent your morning watching TV or thinking about a really hard problem? When you're at the office, it's much easier to check up on what you're doing with your time. I think that if you have an employee that you need to check up on what he's doing with his time, you have a problem. The answer is not going to be to put him in an office and get him to learn how to alt-tab very quickly to an IDE when you walk by. You should be working with them to make sure their performance is adequate. If it's not, and you can't seem to find a way around it, fire him. Keeping him around and force-feeding work is a huge waste of time and money. Slackers are going to slack harder at home, use that to your advantage to get rid of people who aren't up to task or don't care anymore quicker.
Communication is more expensive. It is. It also forces people to learn how to communicate better, more concisely, and in a way that's generally documented. While you can easily have calls, in the end you need to email a list or some form of communication that reaches everybody. So there's a short-term cost for a long-term benefit. You may need that short-term benefit right now, in which case you bring people together for a week or two, spend some of that money you've saved on infrastructure, and push things forward.
So, in general I think having remote workers forces a company to have clearer, well-communicated goals, better documentation on decisions, hiring driven and self-directed people makes you think long and hard about your processes and opens up to hiring from a much larger pool of people (all over the world!). I think those are great things to have pressuring you consistently, and will make you a better company for it.
Like everything else, if you have remote workers and pretend they are the same as co-located it's going to fail.
12.10 is out, how awesome is that? Go ahead and get it if you haven't yet. I've upgraded all my computers months ago and they've been stable and receiving polish and new features almost every day since, how awesome is that? It has tons of new features that put closed-source competitors to shame, how incredibly awesome is that!? It looks nicer, it works faster on my slower machines and a lot of the small bugs in 12.04 have magically gone away, awe-some.
Then, as if things couldn't seem better in a project nearing it's 10th year of attempting to take over the world in a lot of very literal ways, Mark spontaneously decides to take on more financial risk by further opening up the current skunkworks projects Canonical works on and what happens? A lot of crap gets thrown his way. How insane is that?
I can understand competitors taking the opportunity of spinning this as a bad thing, highlighting the fact that there are such projects at all, and how X or Y project is 100% open and pure (although, maybe not as successful). Then there's the usual Ubuntu trolls, folks who are bitter about Ubuntu being successful in the format that it adopted, blending commercial and community development in a unique way that requires a constant balancing act. They were betting on Ubuntu failing and they hate that it hasn't, they hate that for a huge number of people "Linux" actually means "Ubuntu". They also hate that there are millions of people who don't even know (or care) what Linux is, and happily use Ubuntu. That's fine, this is how life works, let them be bitter.
But I cannot understand strong, long-time Ubuntu members and contributors bashing Mark, Canonical or Ubuntu. It feels very disconnected from reality.
I can understand Unity sucked, everybody hated it and it made everything slow. It doesn't any more. In fact, it's crazy fast, crazy stable and it sets us apart from everybody else by a very long stretch. In some areas we leap-frogged a worthy competitor like Apple, and in many cases even forgot about Windows, our bug #1. This happened with many things, compiz, pulseaudio, empathy, you name it. Those sucked too, but ultimately rocked. For us, and for the rest of the open source ecosystem.
And yes, now you can purchase things from the Dash. It'll offer up items even though you maybe weren't looking to buy something, just opening your email. But it helps the project, it helps fund the very same things that make Ubuntu different from everyone else because we get to invest an enormous amount of money in user testing, design, custom engineering and closing deals with OEMs so Ubuntu ends up in the hands of millions of new users every year. I have an unfair advantage over most of you since I've worked at Canonical for over 4 years now and have seen a lot of what it costs in terms of actual dollars. It's not that hard to imagine, though, flying hundreds of people across the globe every 6 months to get together, work and make it feel more like a community, by any simple math it is hundreds of thousands of dollars. That is a lot of money. And when you complain about a feature which you can ultimately disable bothers you and should be removed (or disabled by default, cutting off the actual chance that it'll generate any significant revenue), also take a minute to think that you're saying to Mark he should take that money out of his own pocket instead just so you can feel more comfortable with yourself. I can empathise with people immediately thinking of all the terrible examples of OEMs bundling adware with their computers that annoy people to no end, just to squeeze out every single penny out of each user to bump up their stock. But this is not the same, Mark's been crystal clear that there is a lot being developed to make this a fantastic experience, I have inside knowledge to vouch for that. It is also all free software, it has been for almost 10 years, consistently, and has shown no signs of changing that. In fact, I started writing this because Canonical is trying to make the few bits that aren't fully permeable to the community more open. How fucking awesome is that?
I think it's time to stop, breathe and gain some perspective again.
Last week we organized a local Ubuntu conference in Buenos Aires, Argentina, which we plan on making it a regional conference from now on thanks to the help from our friends in the Uruguay LoCo. The conference was great but by far what stayed with me was a talk and some subsequent conversations with Guillermo Espertino about how a new-ish and small group of designers that used open source software to design professionally had gotten together and started a community called Gráfica Libre. These guys, individually do some very amazing things. As a group they've blown my mind
These are designers who are using 100% no-excuses free software on a daily basis to design and ship professional designs to customers.
These are some of the things they've designed as a group for the conference:
This was done by Lucas Romero
There's a presentation given by Guillermo Espertino (you can see the work his company does with open source in their website http://ohweb.com.ar/) you can download it (it is in spanish, though) and it highlights the challenges they've faced so far in putting together designs in the open and collaboratively. They still feel they have a few iterations to go until they have a settled process, but it certainly does look like they've cracked the hardest part to me.
While a lot of you are at UDS, several Latin American LoCos are working hard to organize a local Ubuntu conference.
Things are going really well, we're 4 weeks away, but we're a little short on funds. Every year the same people who organize it end up having to pay for many things themselves despite have a few generous sponsors, and this year I'd like to change it so I set up a small but valuable fund raising campaign and we could really use your help.
The site is in Spanish, so it may take a bit of blind surfing to get around but it should be fairly easy once you've been sent to PayPal
If you have a some spare change, head on over here: http://www.groofi.com/profile/beuno/projects/ubuconla-2012-conferencia-de-ubuntu-en-argentina
This June 1st and 2nd, we will be holding an all-Ubuntu conference for the second time in Argentina, and with plans to make it regional from now on (next one is in Uruguay!).
Even though it's in Spanish, I'd like to open up the Call for Papers here on planet Ubuntu as well, in case anyone reading is close by
Ubuntu-AR y Ubuntu-UY, grupos locales de Ubuntu para Argentina y Uruguay, convocan a miembros de
la comunidad de software libre internacional y de otros grupos locales de Ubuntu en Latinoamerica a presentar propuestas de charlas para la conferencia anual sobre Ubuntu de Latinoamerica, UbuConLA 2012.
Qué es UbuConLA ?
Un acontecimiento internacional, anual e itinerante para Latinoamerica surgido a partir de una idea común entre miembros de los grupos comunitarios locales de Ubuntu en Argentina y Uruguay, con los siguientes objetivos:
- Difundir la capacidad y experiencias logradas en ambientes empresariales por especialistas de Latinoamérica en proyectos y contextos de diversas características
- Mostrar el grado de madurez alcanzado por Ubuntu GNU/Linux y los profesionales que trabajan con él en ambientes empresariales, ya sea tanto como consultores como también usuarios y responsables de áreas de sistemas
- Integrar técnica y socialmente a usuarios y especialistas de Latinoamérica, tanto sea para adquisición de nuevos conocimientos y habilidades como también para aprovechar y/o generar oportunidades de negocios en la región
- Difundir el espíritu "Ubuntu" de la comunidad Latinoamericana
- Institucionalizar UbuConLA como "El Acontecimiento Ubuntu" anual para Latinoamerica.
Próximas sedes: 2013 - Montevideo, Uruguay. 2014 - Colombia
Dónde, cuándo y cómo
La conferencia se realizará los dias 1 y 2 de Junio 2012 en la sede de la Ciudad de Buenos Aires de la Universidad Austral, en Argentina.
El autor de cada conferencia seleccionada deberá participar presencialmente como orador en el acontecimiento.
Podrán participar como máximo 3 autores por conferencia, que deberá ser expuesta en Español.
Las propuestas deben ser enviadas via e-mail en texto plano con archivo adjunto, en alguno de los formatos indicados más abajo, a email@example.com con la etiqueta [CFC] y a continuación el título de la conferencia a proponer en el Asunto del mensaje.
Las propuestas serán recibidas hasta el día 1 de Mayo 2012 inclusive.
El día viernes será dedicado a empresas y profesionales con una disposición de 3 tracks presentándose en paralelo:
- Track 1: Casos de exito: por qué funcionó la migracion/proyecto - Características del contexto - Consideraciones previas para minimizar riesgos de fracaso
- Track 2: Cómo migrar a Ubuntu en empresas - Metodologías y mejores prácticas aplicadas - Cuándo y por qué usar Ubuntu en PyMES
- Track 3: Soporte corporativo para Ubuntu - Tengo un problema, y ahora qué hago ? - Alternativas locales de soporte
El día sábado estará orientado a entusiastas y comunidad en general, también con 3 tracks presentándose en paralelo:
- Track 1: Casos de exito: Comunitarios
- Track 2: Principiantes - Qué es Ubuntu? - Cómo instalar Ubuntu - Instalé Ubuntu, y ahora? - Migrando de Windows a Ubuntu - Participando en la comunidad (Introducción) - Charlas relámpago (5 minutos)
- Track 3: Usuarios experimentados - Personalizaciones - Ubuntu Server - Unity, por qué? - Cómo reportar bugs en Ubuntu - Ubuntu TV/Android - Charlas relámpago (5 minutos) - Otros temas de software libre - comunidad relacionados con Ubuntu
Las propuestas deberán contener la siguiente información:
- Autor - Nombre completo
- Organización a la que pertenece/representa
- Lugar de residencia
- Extracto/síntesis biográfica del autor
- Teléfono y dirección de correo electrónico de contacto
- Track en el cual quiere presentar su exposición
- Tipo (taller ó charla)
- Descripción (resumen o esquema que permita evaluar su calidad y punto de vista)
- Duración estimada (las charlas son generalmente de 25 minutos)
- Requisitos/recursos necesarios (Equipos Multimedia, Sala de máquinas, equipo de sonido, etc)
- Nivel (básico, intermedio, avanzado)
- Destinatarios (Sociedad, Empresas, Técnica)
- Conocimientos previos de la audiencia.
Una vez evaluada la propuesta, se les informará a los autores el resultado de la selección por las vía de contacto facilitadas.
Formato para las Presentaciones
- ODT (LibreOffice y equivalentes)
- HTML standard
- Texto plano
Deberá especificarse una licencia para las presentaciones que permita a los organizadores distribuir el materia libremente. Cualquier consulta sobre este tema pueden canalizarla via firstname.lastname@example.org.
Agradecemos la difusión de este llamado y del acontecimiento en sí.
They are looking for a round of donations to pay for some more development work, and as of this moment they're $634 USD short. I've just sent $50 their way.
If you've got a few bucks to spare, please send some money their way. Or maybe you want to get into some development work, they have detailed instructions on how to do just that!
It may of been a bit below the radar, but it was announced that for 12.04 LTS, there would be an improved focus on stability throughout the whole development cycle so more people could use it early on and catch problems with more time to fix them. There's a specific team dedicated to making this happen for all subsequent releases from now on.
This release is probably the most important of them all. We're releasing an LTS that will be supported for 5 years, that means it'll be around until 2017!
Different people will help out in making it awesome in different ways, but one we can all help with is upgrading to Precise today. And I do mean today. I've upgraded all my computers, including my work laptop and it's all generally running smoother than 11.10. And if it isn't, file a bug with the relevant information, that's what you upgraded for
So if you've been unsure about upgrading, please take the plunge and help out in making 12.04 a rock-solid release.
During the Community Council meeting yesterday we were talking about the general health and excitement levels of the community, and whether we were loosing a lot of members. I had a vague memory of us (Canonical) having an internal graph of number of members on the ~ubuntumember team, and I dug it up to see what story it told. As it turns out, it's a very positive and healthy one \o/
Here's the graph of number of Ubuntu members over time (there's no data prior to Sept 2007):
Note that the curve starts to really go up around May of 2008, that's when the membership boards took over member approvals from the Community Council.
- June 2013
- March 2013
- February 2013
- October 2012
- June 2012
- May 2012
- April 2012
- February 2012
- December 2011
- November 2011
- October 2011
- June 2011
- May 2011
- April 2011
- March 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- April 2010
- March 2010
- February 2010
- November 2009
- October 2009
- July 2009
- June 2009
- May 2009
- February 2009
- January 2009
- December 2008
- November 2008
- September 2008
- August 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007