Archives par mot-clé : Development

Making new Ubuntu users happier

When you upgrade to Ubuntu after release, or when one of your friends, family or colleagues installs it for the first time, I trust they will like many of the new features or just appreciate finding everything they need in their new Ubuntu installation. I also trust in some cases they will encounter some of the known issues which at this point (1 week before release) may not be fixed and may not make it but we need to know about. Imagine when someone mentions an issue and you can say « Yeah, I know about it. » and « I reported that bug » / « It’s in the release notes » / « We’re working on it » … « This morning’s updates fixes it » !!!

Don’t miss this opportunity !!!

Ok, this is not as exciting as getting your fingerprint reader to work or customizing window close/maximize buttons positions…

If you consider using Ubuntu 10.10 when it releases (or already do), upgrading to it, or suggesting anyone around you doing so, this would be a good time to read the Maverick Technical Overview 🙂 Making new (or existing, upgrading) Ubuntu users happier also means knowing about its issues before hand, and deciding if you stick to 10.04 LTS, wait a bit longer before upgrading, or else. How else can you help improve such knowledge ?

As many may know, most of Canonical workforce is distributed, but we often get together in sprints where we attack a specific subject. During this week at the Montreal Canonical office we’re having a special event around the upcoming Ubuntu 10.10 release. We’re literally sprinting until Friday, on a very busy week during which we’ll wrap-up all the information we have from weeks of testing, bug reporting/triaging, support issues reported by customers, escalated issues, knowledgebase solutions, and more.

Lots of fun! Specially when Boris is around 😉

For our sprint this week in the Montreal support office, my team is focusing on desktop issues within the following areas, among others:

* Networking (wifi, drivers, sharing, printing..)
* Boot / install / post-install issues (upstart, GRUB*, casper..)
* Video (multi-head, setup, legacy drivers..)

Other teams are focusing on server, cloud, and more. It’s interesting Desktop and « other » areas intersect in what most would generally call « corporate » use of Ubuntu – mass deployments, OEM issues, etc. So we’ve also learned to never underestimate even the tiniest Desktop papercuts 🙂

You can see some of the issues and bugs we consider worth knowing before hand in this Delicious bookmarks feed. If you’re interested in contributing to this list, consider using Delicious and tagging with « maverick » and « bug ». We’ve also chosen some more tags representing tasks around them, for example « relnotes » for those issues already in the release notes and « norelnotes » for those without an entry, but which we consider would benefit from being there. Most importantly, please consider filing a bug against the Ubuntu Release Notes project if you feel something should be there to help evaluating going to Ubuntu 10.10.

You will instantly become a better person, I promise.

Back to what we’re doing this week, this is a bit different than most sprints in that we’re not specifically targeting finding a solution for most issues, but rather workarounds or maybe just even making a small note land in the Maverick Technical Overview (which will later become the Release Notes). Given our workflow, we’re also reporting bugs as we go, but I view that mostly as a labor of documenting existing problems, not necessarily advancing their resolution directly – at least not during this week.

So if you have a particular pet peeve that is not in our release notes or Delicious feed, please let me know, I am always interested and curious to share such information.

 

An invitation to join Ubuntu’s Q&A group on Shapado.com

This is an invitation to anyone interested in joining a multi-lingual, freely-licensed Ubuntu Q&A site to check http://ubuntu.shapado.com.

As a disclaimer I should mention that I work at Canonical as a senior support analyst for Ubuntu support (both desktop and server) and I also train other people to provide Ubuntu support. I am also the admin and creator of the Ubuntu group in Shapado (10 months ago). So I constantly switch my community and professional hats 🙂

I use the Answers system in Launchpad extensively (including its FAQ facility) but it lacks two big features:

  • Non-English language support – also known as « l10n » or « localization« . That would be Bug #81419.
  • A reputation / trust system

As you can see that bug report is in an odd deadlock. My interpretation of it is Answers and Launchpad itself were not planned from the beginning to be multilingual. It’s so big now that this can’t be done quickly or easily.

The reputation system or « making Launchpad more social » is a huge feature request too, perhaps traditionally out of scope for such technically-oriented online resources (at least in the traditional Free / Open Source communities). It’s also something I am missing from my daily interactions with customers when providing commercial support.

So when I learned about Shapado I found a nice tool that could complement my advocacy needs, and some more. How is it different than Launchpad’s Answers ? To me, it’s primarily the language support, but many other features are a bonus.

Regarding the recent proposal to have an Ubuntu community in Stack Exchange, see How does Shapado compare to StackExchange ?. I honestly don’t want to join yet another English-only site that runs on non-Free software that I can’t fix or translate myself. I can’t ask anyone around me to do that either. That proposal was forwarded to the LoCo Teams contacts mailing list, asking team contacts to forward it. I am sorry but as an Ubuntu Member and Ubuntu QC contact I won’t do that. I am sticking with my principles for now, and using any free, open source alternative I can get.

So if you’re interested in using Shapado for Q&As in English but also French, Portuguese and Spanish (for now), see http://shapado.com/pages/faq and http://ubuntu.shapado.com.

If you’re interested in setting up your own local, localized Shapado Q&A server, see the installation instructions, the question asking about Ubuntu/Debian packages, and the Shapado « needs-packaging » bug report.

Here is more information on Shapado:

In true dogfood fashion, one can report bugs or make suggestions at http://shapado.com directly, just by using the « bug » or « feature-request » tags 🙂 There is also a more traditional bug tracker.

How does Shapado compare to StackExchange?

 

Nouvelle application Île Sans Fil pour Android

Sorry for the French post. Montreal folks will know what this is about and go straight to the QR code 🙂 Remember this is very beta and not officially approved by ISF.

Ce matin Claude Chasse nous apprends sur le groupe LinkedIn d’Android Montréal qu’une nouvelle application pour localiser les points d’accès d’Île Sans Fil est disponible pour tester.

Direct link: ilesansfil.apk

Attention cette application est encore en développement – le but est de reccueillir des commentaires.

Je suggère fortement d’envoyer vos commentaires sur le Google Group d’Android Montreal.

Voici quelques captures d’écran pour vous mettre l’eau à la bouche 🙂

Mes premiers commentaires:

  • L’intégration Google Maps serait complète si on pouvait aller directement à « Directions » pour un point d’accès, appeler l’endroit, visiter son site web
  • Une section « Favoris » serait intéressante
  • On voit les point d’accès « down » ! Excellent pour éviter un déplacement
  • L’ajout de l’option « my location » dans les paramètres manque
  • Bonne intégration du blog d’ISF
 

Rogers Canada: how NOT to sell Android

I love Android (the platform, as a colleague put it).

But I hate my cellphone provider, Rogers Canada. I hope that’s clear. Rogers CANADA.

Being a community, people-oriented person, free software activist and open source enthusiast, and on top of that a full time technical trainer and support analyst, last summer when I heard that Rogers Canada would be the first company to sell & support the mighty HTC Dream (known as G1 to T-Mobile customers), I decided I would trust them. In fact I got my HTC Dream the day it came out, on June 2nd. If Google trusted Rogers with their first Android deployment in Canada, I would be OK. Big mistake!

I’ve posted before that Rogers Canada sucks. I’ve thought about documenting my own problems, but it’s getting easier to just gather other similar experiences Android customers have at Rogers:

That’s right, there is a whole blog dedicated to document and share all the mistakes Rogers Canada has made and all the problems they have caused.

When I saw that I started my own Identi.ca group: RogersSucks (or !rs)

As I write this I am waiting for a replacement HTC Magic which was promised once, order « lost », promotion postponed, then secretly available again, then finally ordered on Sunday. I know, it’s Wednesday and we’re only a province away, but the phone hasn’t even shipped. Nevermind it’s only a slightly less outdated phone, I am waiting again to get the Rogers Canada Android Revolution.

Rogers Canada thinks it’s good business practice to suspend data service in order to force customers into upgrading to a firmware that basically locks down my phone. Why is it important it’s unlocked and rootable ? Because otherwise it’s very much useless, or should I say even less useful than a regular cell phone. At least regular cell phones behave well with BT headsets, don’t crash or reboot spontaneously, and don’t lag for >30 seconds when going from one application to the other. Among other things. It used to be possible to use Cyanogen Mod and other custom firmwares to make these phones somewhat usable. Not anymore.

How did Google let this happen ? I have no clue.

A lot of similar mistakes can be made by any company selling devices based on free, open-source software (and yes I know Android devices don’t come with 100% free software). I secretly hope some anonymous person inside such companies learns something from Rogers Canada mistakes. This is truly an example on how NOT to launch and service such a product.

Meanwhile I am gathering details on my own problems and getting all my services with Rogers cancelled without penalty for breach of contract. If that doesn’t happen, small claims court in Quebec should help, and I’ll document this in true free, open fashion so I can help as many people as I can do the same: vote with their money. I am angry such a great platform got such a bad start in Canada.

I guess the Revolution is not going to be available in Canada for some time.

How Rogers Ruined My HTC Dream

 

Thank you Ubuntu Québec and Facebook

Télévision de Radio-Canada is a Canadian French language television network. It is owned by the Canadian Broadcasting Corporation, known in French as Société Radio-Canada, or just « Radio-Canada », for the rest of us. – from Wikipedia

A couple of weeks ago they launched a new web site, tou.tv, making « available » all their TV shows (or most of them)… in Flash 🙁

Never mind it’s 2010 and HTML5, Ogg Theora and in general open standards and formats are the talk of the day on most web development sites… Flash 10 is a bad enough choice as it is, but apparently tou.tv’s team just forgot that Linux existed.

Within hours of the launch Ubuntu Québec team members started complaining on the mailing list and on tou.tv’s Facebook group. We wrote to their admins, provided details, wrote to the ombudsman, got canned replies for all communications. We then put together a Facebook group, and started inviting people to join and we shared our findings (now all on a public wiki). 451 people joined the group which is an amazing number for Quebec province, given the context. I never ever thought I’d use Facebook for open formats and Linux support advocacy in such a way!

Only one programmer from the tou.tv’s team first acknowledged the problem, then asked for testers. That’s it, total silence from the tax-payers-funded TV network and website.

Within hours of the initial launch people on the mailing list had analyzed the streaming protocol, the Javascript code, etc. and ruled out problems there. To our amazement, a single commented line was preventing any shows to be displayed. Someone put together a GreaseMonkey script, someone else tested it… we went online on IRC to coordinate testing + blogging. Bottom line is we came up with a workaround. A week later tou.tv finally applied minimal fixes to unblock the Flash display on Linux systems.

The site is not perfect and now other minor issues subsist, and yes, I wish open formats were an option. For now I just wanted to thank Ubuntu for providing not only an incredible operating system but also an amazing community that made all this possible 🙂 I also wanted to thank the Free Software Foundation as we used several resources from them such as the Defective by Design web site to explain the problems associated to using DRM-like implementations of web TV sites, and the problems of not using open formats, such as Flash.

I also wanted to send a big FAIL to Radio-Canada and tou.tv’s team. To this day they don’t even mention Linux on their FAQ.

You can also find more details about this little victory of ours in my original blog post in French.

Your taxes at work!