Imagine a few hundred people gathered in a big conference were presentations go from Android on Ubuntu to Making Ubuntu family-friendly to Ubuntu One development to Mastering Unicode to project updates … well you get the point. Oh, and everyone of them is a colleague. The challenge here was to go beyond shaking as many hands as possible and trying to find out what we all had in common to best push Ubuntu forward, while looking at our best shots without losing sight on things to improve and innovate on.
Pfew! If that sounded like an intense few days, it was. I am glad I planned on sleeping very little.
I hope this gives a small insight into how great this big Canonical-family meeting was.
Now UDS follows, although I won’t be attending I trust my many mates will drive this one home too.
NOT A FORK – as soon as I posted this I got a comment about this being a fork, well, it’s not! It’s a collection of modules and a theme, which are managed via a project in Launchpad. This is not a separate fork of Drupal! 🙂
Drupal 5.x and 6.x LoCo Suite Released
That long needed suite of tools has finally been completed.
This suite is designed for any Ubuntu Local Communities wanting to host a website. It is designed to allow any LoCo team to quickly create a website using Drupal for their team.
What this suite offers:
An approved theme for any LoCo
A highly customizable theme
Launchpad OpenID integration
-> Users don’t need to create an account on your site
Launchpad Teams integration
-> Can control access levels in site based on LP team memberships
If the amount of people that called for support for their Dell Mini 9 over the holidays is any indication, we’re bound to see quite a few new users of Ubuntu that own this nice system!
If you know someone that uses a Mini 9, remember there is official documentation for the Ubuntu version (8.04) that ships in it at http://help.ubuntu.com . That may sound obvious but many experienced Ubuntu users don’t refer much to those docs and as a result don’t know it even exists 🙂
I also wanted to share a lot of tips, tricks and known issues as well as useful links (such as where to ask a question in Launchpad Answers) that have been put together at: https://help.ubuntu.com/community/DellMini9
As a (relatively) long time Ubuntu user, occasional bug reporter and support analyst, I often deal with bug reporting and I feel your pain about bug reporting, Matt. This happens in many other free software projects, but I think Ubuntu’s popularity gives its problems more exposure, an opportunity to refine the process and maybe inspire others to learn from its mistakes and success.
Generally speaking it’s always nice if you can dedicate a few dozen minutes (around an hour I would say) to familiarize yourself with how bugs are reported in the project you’re participating with. In Ubuntu it’s the Bug Squad team – perhaps even join it. I view Bug Squad members as the little bee-workers that are front-line organizers and helpers in the fight against bugs.
Think about it. An hour or so is not that much to dedicate to learning and understanding how your contributions will (or not) affect Ubuntu. It will also give you tools and guidance to become helpful and efficient in any bug reporting. I am not saying everyone should join! But those of you who don’t join need to at least understand how a bug report is treated on the receiving end.
I’d like to contribute 10 things to avoid and 10 things you can do if you want to increase the chances of getting good results from bug reporting (meaning a fix or solution). Some of them come from the Best Bug Reporting Practices wiki page.
Look for existing bug reports that match your problem. It saves a tremendous amount of time when several people do this. It helps confirming a bug and tying loose ends 🙂 Checking upstream and linking those is very nice too!
When filing a new bug, mention the ID’s of all bugs that sound similar. use « Bug #XXX », this provides an automatic link. Someone can dupe them together later.
Add missing data (including video, YES VIDEO, screen captures, logs) to an existing bug. In some cases more is better.
Provide context. Consider what is unique about your system, and mention it. Is it brand new out of the assembly line ? Did it stay overnight outside at -40C ? Is your music collection that fails to import in Rhythmbox 40000 files big ? Did you just reinstall ?
Itemize the exact steps that result in the issue. Can you reproduce it at will? This is perhaps the single most important thing. If no one can reproduce your bug, chances are no one will be able to fix it. Providing clear steps dramatically helps.
Follow up on your bugs from time to time, even if they seem ignored. Kindly ask for a follow-up if/when appropriate.
Report if the issue goes away or remains when new Ubuntu’s come out.
Once you’ve reported a bug, or if you have a few that are important to you, give them visibility. Go to forums, mailing lists, or post them in your blog. Not everyone reads bug reports or knows an issue they have is being worked on.
Use IRC. Live chatting with developers on #ubuntu-bugs or #ubuntu-devel and asking a few questions while writing your bug report may help getting better information (like which package the bug should belong to).
Get confirmation (or rejection) as soon as possible. Befriend a developer, expose your bugs, use whatever means to have other people confirm or reject your bugs. Be proactive if you want your bug reports to get some « traction ».
Here are my don’ts:
Do not assume your bug report is more important because you’ve put several hours thouroughly detailing it. I know because I have done that. In many cases I see such reports as a documentation available to others, so they don’t repeat my own mistakes.
Don’t be rude. Whatever the frustration, it’s not helpful to the bug’s resolution. I personally find this is the hardest to do 🙂 When in doubt, read again the Ubuntu Code of Conduct, take a few minutes before ranting.
Don’t cite external links with lenghty discussions – unless you summarize them in one or two sentence. – this multiplies exponentially the time required to assess a bug’s status, importance, etc.
Do not assume « they must already know about this » – no one does. Making assumptions only adds delays while clarifications are obtained.
Don’t add « me too » responses, unless you are giving more details that actually help confirming a bug in its early reporting. It wastes everyone’s time when reviewing a bug (not to mention emails generated).
Don’t post bugs with only a brief description of the problem. « XXXX doesn’t work » will get rejected or will expire. A model number for hardware by itself is not enough detail.
Don’t assume others will « just know » how the bug occurs. Sometimes non-technical details (like « the wireless connection always drop when I pickup my wireless phone ») provide important context.
Don’t fire and forget. Abandoned bugs rarely get fixed. If you are not willing / able to subscribe to your own bug reports and provide feedback, additional information, and even ultimately test possible solutions, make it clear in the bug report or don’t file it.
Don’t post bug reports in other languages than english. This may seem obvious but when you install Ubuntu for someone that will be using it in any other language than english, automatic bug reporting may kick in and give the false impression any reports can be filed in another language. Educate your non-English speaking Ubuntu « customers » about this.
Don’t assume every issue is critical. Between fixing a screensaver that crashes Ubuntu (easily worked around) or fixing a RAID issue that affects all server installs, what do you think should get more attention ? Importance is relative. Not everyone’s emergency is someone else’s too.
EXTRA: Don’t ignore guidelines and procedure. If you know a rule, don’t ask for exceptions!
Last but not least, if your bug concerns business needs and is stopping your business or your customer or any commercial activity, consider actually paying a developer or company to look into it. Part of Canonical’s support services includes bug escalation but there are many other ways to « financially speed up » a bug’s resolution. Citing business concerns in Launchpad to speed up a bug’s resolution is not what I mean here, but actually paying someone to go through the community process for you or your company / organization.
If anyone has other tips to contribute, I’d love to hear them. I am far from a bug reporting expert so I’d love to learn any new tricks and tips here 🙂
Consultant et conférencier en logiciels libres et GNU/Linux basé à Montréal, Québec (Canada)