Søren Bredlund Caspersen: Open Source Days 2010

The Danish Ubuntu LoCo team had a community booth at the 2010 Open Source Days in Copenhagen last weekend.

The picture shows us (and the Exherbo guys next to us) setting up early Friday morning. Later in the day a Zebrapig banner joined the Ubuntu banner. All the community booths were located on the first floor, upstairs from the firms and organisations who had a paid booth. I didn’t take that many pictures, and the ones I did take didn’t turn out that great, but Flickr seems to have a nice collection if you are curious.

The new theme for Ubuntu Lucid had just been released the day before, so Friday, when we weren’t talking to people about Ubuntu, we spend a bit of time arguing for and against the new colour scheme.
We managed to hand out all our remaining Ubuntu 9.10 CD’s and Jesper gave a talk about ubuntu-dk.

As always, it was nice to meet up with the other people from the LoCo team. Although we do a lot of work together, it is often via e-mail or irc chat. Putting names to faces is always a pleasure. The beers both Friday and Saturday night were also a pleasure – beer and good company seldom lets you down.

We even managed to do some planning for the coming Ubuntu Global Jam.

Anders is set on doing an entire day of translating Sunday 28 at his place. And the plan is to do some more general bugwork on Friday and Saturday. Location is still to be decided, but properly Jesper or I will open our homes to the masses of Ubuntu volunteers. Stay tuned for more info about the Global Jam in Copenhagen / Denmark.

Related posts:

• Open Source Days – I got my ticket!
• Pictures from Open Source Days 2008
• Open Source Software conference
• Late Global Jam in Copenhagen

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Harald Sitter: Opportunistic KDE/Kubuntu Debugging

Back in the days, we did not have capabilities to find and install debug packages with Dr. Konqi in KDE. But those times are over!

Debug packages are important, well, actually very important. When an application crashes it is in most cases possible to create a so called backtrace. A backtrace ideally provides the developer with the precise location in the source code where the crash happened. Fixing a crash without this kind of information is almost impossible, and the more information are available in the backtrace the better. Debug packages contribute to this in that their content are debug symbols, essentially those are the references that are used in the backtrace. Now, usually you do not need to have this information to use the software, which is the reason a lot of distributions strip the symbols into these seperated debug packages (one can save a big deal of disk space by removing them).

In case you did not yet hear of Dr. Konqi. It is a very useful tool that usually pops up when a KDE application crashes. It then tries to get all information necessary for you to create a perfectly useful bug report.

There is big of a problem, on the one hand you do not want to waste disk space and network traffic for these debug symbols, even though like 99% of the regular users will not need them, and on the other hand you have Dr. Konqi which is trying to obtain a high quality backtrace that enables developers to quickly process a bug report and fix a crash in their software.

Not KDE 4.4not  GNOME 3.0 and not  KDE SC 4.4but  Dr. Konqi 2.1 comes to rescue and now allows distribution developers to create scripts that take care of the find an installing of debug packages, so that the debugging experience becomes a bit better. Well, obviously debugging is not much of a user experience eitherway but at least getting a backtrace is now more barable than it was before.

The system is quite simple. Dr. Konqi calls an executable, passing it all files for which no debug symbols were found for as arguments, then the executable tries to find and install the appropriate packages and returns back to Dr. Konqi. Straight forward really

Since I am, amongst other things, Kubuntu developer and since this blog post is tagged ‘kubuntu’ of course I am only blogging about this because Kubuntu today got support for this fancy new feature . Should you encounter a crash in upcoming Kubuntu 10.04 Dr. Konqi will not only tell you how good the quality of the automatic generated backtrace is, but also show a button with which you can install missing debug symbols.

Additionally I might mention that Kubuntu has a new mantra of using C++ whenever possible (in opposite to the former one, which was to use Python whenever possible), hence the application standing behind this new features is written in C++ and got the fancy name kubuntu-debug-installer.

In case you care, the code is available on launchpad, and fairly simple. It really just creates a thread and uses dpkg -S to find the appropriate packages. In later versions it will also be able to use other means of looking up debug packages and be able to add a super secret Kubuntu repository for debug packages automatically, if necessary.

What I would like to see for future KDE releases is the possibility to directly tie a plugin into Dr. Konqi instead of having to create an independet application. But for now we’ll try to get kubuntu-debug-installer the ability to use different algorithms for finding the appropriate debug packages (also using different tools, since for example apt-file performs better than dpkg-query, but requires an up-to-date cache etc.) and of course support of a special Kubuntu repository that contains debug packages for all and every official Kubuntu package.

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Matt Zimmerman: QCon London 2010: Day 1

For the first time in several years, I had the opportunity to attend a software conference in the city where I lived at the time. I’ve benefited from many InfoQ articles in the past couple of years, and watched recordings of some excellent talks from previous QCon events, so I jumped at the opportunity to attend QCon London 2010. It is being held in the Queen Elizabeth II Conference Center, conveniently located a short walk away from Canonical’s London office.

Whenever I attend conferences, I can’t help taking note of which operating systems are in use, and this tells me something about the audience. I was surprised to notice that in addition to the expected Mac and Windows presence, there was a substantial Ubuntu contingent and some Fedora as well.

Today’s tracks included two of particular interest to me at the moment: Dev and Ops: A single team and the unfortunately gendered Software Craftsmanship.

Jason Gorman: Beyond Masters and Apprentices

A Scalable, Peer-led Model For Building Good Habits In Large & Diverse Development Teams

Jason explained the method he uses to coach software developers.
I got a bad seat on the left side of the auditorium, where it was hard to see the slides because they were blocked by the lectern, so I may have missed a few points.

He began by outlining some of the primary factors which make software more difficult to change over time:

• Readability: developers spend a lot of their time trying to understand code that they (or someone else) have written
• Complexity: as well as making code more difficult to understand, complexity increases the chance of errors. More complex code can fail in more ways.
• Duplication: when code is duplicated, it’s more difficult to change because we need to keep track of the copies and often change them all
• Dependencies and the “ripple effect”: highly interdependent code is more difficult to change, because a change in one place requires corresponding changes elsewhere
• Regression Test Assurance: I didn’t quite follow how this fit into the list, to be honest. Regression tests are supposed to make it easier to change the code, because errors can be caught more easily.

He then outlined the fundamental principles of his method:

• Focus on Learning over Teaching – a motivated learner will find their own way, so focus on enabling them to pull the lesson rather than pushing it to them (“there is a big difference between knowing how to do something and being able to do it”)
• Focus on Ability over Knowledge – learn by doing, and evaluate progress through practice as well (“how do you know when a juggler can juggle?”)

…and went on to outline the process from start to finish:

1. Orientation, where peers agree on good habits related to the subject being learned. The goal seemed to be to draw out knowledge from the group, allowing them to define their own school of thought with regard to how the work should be done. In other words, learn to do what they know, rather than trying to inject knowledge.
2. Practice programming, trying to exercise these habits and learn “the right way to do it”
3. Evaluation through peer review, where team members pair up and observe each other. Over the course of 40-60 hours, they watch each other program and check off where they are observed practicing the habits.
4. Assessment, where learners practice a time-boxed programming exercise, which is recorded. The focus is on methodical correctness, not speed of progress. Observers watch the recording (which only displays the code), and note instances where the habit was not practiced. The assessment is passed only if less than three errors are noticed.
5. Recognition, which comes through a certificate issued by the coach, but also through admission to a networking group on LinkedIn, promoting peer recognition

Jason noted that this method of assessing was good practice in itself, helping learners to practice pairing and observation in a rigorous way.

After the principal coach coaches a pilot group, the pilot group then goes on to coach others while they study the next stage of material.

To conclude, Jason gave us a live demo of the assessment technique, by launching Eclipse and writing a simple class using TDD live on the projector. The audience were provided with worksheets containing a list of the habits to observe, and instructed to note instances where he did not practice them.

Julian Simpson: Siloes are for farmers

Production deployments using all your team

After a brief introduction to the problems targeted by the devops approach, Julian offered some advice on how to do it right.

He began with the people issues, reminding us of Weinberg’s second law, which is “no matter what they tell you, it’s always a people problem”.

His people tips:

• In keeping with a recent trend, he criticized email as a severely flawed communication medium, best avoided.
• respect everyone
• have lunch with people on the other side of the wall
• discuss your problems with other groups (don’t just ask for a specific solution)
• invite everyone to stand-ups and retrospectives
• co-locate the sysadmins and developers (thomas allen)

Next, a few process suggestions:

• Avoid code ownership generally (or rather, promote joint/collective ownership)
• Pair developers with sysadmins
• It’s done when the code is in production (I would rephrase as: it’s not done until the code is in production)

and then tools:

• Teach your sysadmins to use version control
• Help your developers write performant code
• Help developers with managing their dev environment
• Run your deploy scripts via continuous integration (leading toward continuous deployment)
• Use Puppet or Chef (useful as a form of documentation as well as deployment tools, and on developer workstations as well as servers)
• Integrate monitoring and continuous integration (test monitoring in the development environment)
• Deliver code as OS packages (e.g. RPM, DEB)
• Separate binaries and configuration
• Harden systems immediately and enable logging for tuning security configuration (i.e. configure developer workstations with real security, making the development environment closer to production)
• Give developers access to production logs and data
• Re-create the developer environment often (to clear out accumulated cruft)

I agreed with a lot of what was said, objected to some, and lacked clarity on a few points. I think this kind of material is well suited to a multi-way BOF style discussion rather than a presentation format, and would have liked more opportunity for discussion.

Lars George and Fabrizio Schmidt: Social networks and the Richness of Data

Getting distributed webservices done with Nosql

Lars and Fabrizio described the general “social network problem”, and how they went about solving it. This problem space involves the processing, aggregation and dissemination of notifications for a very high volume of events, as commonly manifest in social networking websites such as Facebook and Twitter which connect people to each other to share updates. Apparently simple functionality, such as displaying the most recent updates from one’s “friends”, quickly become complex at scale.

As an example of the magnitude of the problem, he explained that they process 18 million events per day, and how in the course of storing and sharing these across the social graph, some operations peak as high as 150,000 per second. Such large and rapidly changing data sets represent a serious scaling challenge.

They originally built a monolithic, synchronous system called Phoenix, built on:

• LAMP frontends: Apache+PHP+APC (500 of them)
• Sharded MySQL multi-master databases (150 of them)
• memcache nodes with 1TB+ (60 of them)

They then added on asynchronous services alongside this, to handle things like Twitter and mobile devices, using Java (Tomcat) and RabbitMQ. The web frontend would send out AMQP messages, which would then be picked up by the asynchronous services, which would (where applicable) communicate back to Phoenix through an HTTP API call.

When the time came to re-architect their activity , they identified the following requirements:

• endless scalability
• storage- and cloud-independent
• fast
• flexible and extensible data model

This led them to an architecture based on:

• Nginx + Janitor
• Embedded Jetty + RESTeasy
• NoSQL storage backends (no fewer than three: Redis, Voldemort and Hazelcast)

They described this architecture in depth. The things which stood out for me were:

• They used different update strategies (push vs. pull) depending on the level of fan-out for the node (i.e. number of “friends”)
• They implemented a time-based activity filter which recorded a global timeline, from minutes out to days. Rather than traversing all of the user’s “friends” looking for events, they just scan the most recent events to see if their friends appear there.
• They created a distributed, scalable concurrent ID generator based on Hazelcast, which uses distributed locking to assign ranges to nodes, so that nodes can then quickly (locally) assign individual IDs
• It’s interesting how many of the off-the-shelf components had native scaling, replication, and sharding features. This sort of thing is effectively standard equipment now.

Their list of lessons learned:

• Start benchmarking and profiling your app early
• A fast and easy deployment keeps motivation high
• Configure Voldemort carefully (especially on large heap machines)
• Read the mailing lists of the NoSQL system you use
• No solution in docs? – read the sources
• At some point stop discussing and just do it

Andres Kitt: Building Skype

Learnings from almost five years as a Skype Architect

Andres began with an overview of Skype, which serves 800,000 registered users per employee (650 vs. 521 million). Their core team is based in Estonia. Their main functionality is peer-to-peer, but they do need substantial server infrastructure (PHP, C, C++, PostgreSQL) for things like peer-to-peer supporting glue, e-commerce and SIP integration. Skype uses PostgreSQL heavily in some interesting ways, in a complex multi-tiered architecture of databases and proxies.

His first lesson was that technical rules of thumb can lead us astray. It is always tempting to use patterns that have worked for us previously, in a different project, team or company, but they may not be right for another context. They can and should be used as a starting point for discussion, but not presumed to be the solution.

Second, he emphasized the importance of paying attention to functional architecture, not only technical architecture. As an example, he showed how the Skype web store, which sells only 4 products (skype in, skype out, voicemail, and subscription bundles of the previous three) became incredibly complex, because no one was responsible for this. Complex functional architecture leads to complex technical architecture, which is undesirable as he noted in his next point.

Keep it simple: minimize functionality, and minimize complexity. He gave an example of how their queuing system’s performance and scalability were greatly enhanced by removing functionality (the guarantee to deliver messages exactly once), which enabled the simplification of the system.

He also shared some organizational learnings, which I appreciated. Maybe my filters are playing tricks on me, but it seems as if more and more discussion of software engineering is focusing on organizing people. I interpret this as a sign of growing maturity in the industry, which (as Andres noted) has its roots in a somewhat asocial culture.

He noted that architecture needs to fit your organization. Design needs to be measured primarily by how well they solve business problems, rather than beauty or elegance.

He stressed the importance of communication, a term which I think is becoming so overused and diluted in organizations that it is not very useful. It’s used to refer to everything from roles and responsibilities, to personal relationships, to cultural norming, and more. In the case of Skype, what Andres learned was the importance of organizing and empowering people to facilitate alignment, information flow and understanding between different parts of the business. Skype evolved an architecture team which interfaces between (multiple) business units and (multiple) engineering teams, helping each to understand the other and taking responsibility for the overall system design.

Conclusion

Overall, I thought the day’s talks gave me new insight into how Internet applications are being developed and deployed in the real world today. They affirmed some of what I’ve been wondering about, and gave me some new things to think about as well. I’m looking forward to tomorrow.

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Jono Bacon: I Never Realized...

…that this part of my desktop could feel so sleek:

Ubuntu 10.04 Lucid Lynx, we are ready for you.

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Jono Bacon: System 76 Lemur Review

This blog entry represents the views of me, myself and I, and does not represent the views of my employer (Canonical) or System 76. While I have decided to write a review of this specific machine, there are many vendors out there who ship Ubuntu on their machines and this review does not favor System76 over these other vendors. Heck, I am happy to review their machines too if they want.

Recently I got one of these new System 76 ultra-thin laptops, the Lemur:

System76 are well known in the Open Source community for shipping Ubuntu on their machines, being active community members and for helping LoCo teams with machines too. I have never owned a System76 box so I thought this was a good opportunity to give it a ride and share some feedback.

So first, the specs:

• Display: 14.0″ HD WXGA Super Clear Ultra-Bright LED backlit (1366 x 768)
• Graphics: Intel GMA 4500MHD graphics
• Audio Output: Intel High Definition Audio
• Networking: Gigabit LAN (10/100/1000), WiFi
• Wireless: 802.11 agn
• Expansion: Express Card 34 slot
• Ports: HDMI, VGA, 3 x USB 2.0, Headphone Jack, Microphone Jack, SD Reader
• Camera: Built-In 1.3 MP Webcam
• Security: Kensington ® Lock
• Power Management: Suspend & Hibernate
• Battery: Lemur UltraThin Li-Polymer Battery Pack
• AC Adapter: includes one AC adapter
• Dimensions: 13.38″ x 9.09″ x 0.90″ (WxDxH)
• Weight: 3.5 lbs

The machine I got has an Intel Core 2 Duo SU7300 1.3 GHz 800 MHz FSB 3 MB L2 (10 Watt), 4GB RAM (DDR3 1066 MHz 1 DIMM) and a 80 GB Intel X25-M Solid State Drive.

Now, in the interests of full disclosure: I don’t really do reviews, so this is going to be a quick run through the details, not a 150-picture unboxing and War And Peace epic of every minor detail of the machine. I just wanted to get my experience down as quickly as possible so I could share my feedback with others.

The Machine

OK, let’s zip through the summary:

The machine is a really sleek looking bit of kit. The first thing that struck me is how well designed it feels: it doesn’t feel like a randomly thrown together collection of components. It is thin and incredibly light, and has a very Apple-ish feel to it. It passed what I am calling the Lost Test: that is, when laid in bed at night watching Lost on Hulu with said laptop rested on your chest (for that IMAX effect), how many episodes can you get though before you feel like your heart is about to overheat and stop working. It’s lightness and lack of heat helped it pass with flying colors.

The screen looks great, doesn’t seem to smudge easily and is nice and bright. I like the fact it is a widescreen, something I miss with my current Thinkpad.

The keyboard is pretty much ok: it ain’t no Thinkpad keyboard, but of all the laptops I have owned and that are buried in my laptop graveyard, the Lemur’s keyboard feels better than most. The keys are wide enough and I love the fact that there is no Windows key, but instead an Ubuntu key. I want to see more of that, yes I do.

The trackpad is long and feels pretty good, and the buttons don’t look like buttons but instead areas on the trackpad near the bottom where you can push down: this makes it look really sleek. Unfortunately at first the buttons are a little hard to press, but I have noticed that they are getting easier, so I think they just need breaking in a little.

With the current configuration of processor and RAM, this thing is shit off a shovel fast. It zips along like no-ones business, and Ubuntu is up and running in a matter of seconds. While I didn’t test any hardcore 3D games on there, it runs Compiz great with the extra effects switched on.

Sounds works great, the speakers sound surprisingly good and the built-in webcam works well too. Finally, the battery life seems fine in terms of life, but not outstanding. Then again, I am used to my extra-long-life Thinkpad batteries.

My only real gripe believe it or not is the packaging the machine comes in: it visually looks cheap with a large generic “notebook” logo and doesn’t reflect the swishness of the machine encased inside it. I spoke to Carl Richell, founder of System76 about this and he has acknowledged it is an issue and they are keen to fix it: he said they really want every essence of the System76 experience to feel sleek. Good man.

The Default Install: Ubuntu 9.10 Karmic Koala

It is just incredible driving back from picking up a computer from the UPS warehouse and knowing that it already has Ubuntu pre-installed. I have never bought a pre-installed Ubuntu computer before, so I was curious to see how it looked. I got it home, switched it on and it threw up the installer’s configuration settings: I entered my details and the system was ready to roll. I was left with pretty much a default installation of Ubuntu: there is not the horrible bundled collection of software you don’t want and ugly vendor wallpaper that you find if you buy a typical Windows pre-loaded machine. Good work System76 on shipping what I consider a great representation of Ubuntu.

Other than that, nothing much to say: everything just works as you would expect.

Running Lucid

Being part of the Ubuntu development team, I was keen to get Lucid on there. I used Update Manager to update to Lucid and installation was smooth. Once again everything works: any bugs that I have found have not been specific to this machine, but replicated on my other Lucid machine. What is really noticeable is boot speed on the SSD: it is bonkers fast.

Conclusion

In conclusion, I think the Lemur is a beautiful machine, and combined with what I consider a beautiful Operating System, particularly with the new fit and finish of Lucid. When running the Lemur it really feels like great design in hardware and software meeting well. I would happily recommend this machine to others.

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

The Fridge: 1st Annual Ubuntu Women Project "How I discovered Ubuntu." International Women's Day Competition Winners announced

March 8, 2010 - 1st Annual Ubuntu Women Project "How I discovered Ubuntu." International Women’s Day Competition

The Competition which was announced back in January, asked women and girls who use Ubuntu to submit their "How I discovered Ubuntu" stories. We as a Project acknowledge that there is no one definite answer to "How do you get women to use Ubuntu?", but wanted a way to highlight some of the various ways that women become Ubuntu users, contributors, and developers and at the same time not only have those stories as examples but also as a growing gift of encouragement and inspiration to women.

In order for events/competitions to be successful it takes community participation, and a heart felt thank you to all those who participated by submitting their personal "How I discovered Ubuntu." stories, those who took the time to vote, those who helped promote, and those who supported this initiative as well as offer encouragement to those might not have submitted their stories otherwise. I am grateful for everyone involved in the Ubuntu Women Project and greater Ubuntu Community as a whole who are continually helping to provide both the platform and encouragement for women to contribute to Ubuntu.

The winners of an awesome prize pack are: Elvira Martinez and Karen Y. Perez with honorable mention going to Jen Phillips as well. CONGRATULATIONS!!!! Here are there stories:

***Elvira Martinez "tatica1" ***

Today my Honduran team mate Diego Turcios shared with me this link to Amber’s blog that excited me to finally write about how I met Ubuntu. I wanted to share this a while ago but I feel motivated about doing it through Ubuntu-women and not just for the sole interest in participating in the contest. I think it will be very interesting to hear how other women became interested in Ubuntu and others may be interested in my experience, specially considering that I am not the “computer girl” precisely.

After nearly 20 years after my high school graduation in Colombia Lycée Français Paul Valery, I found again one of my classmates through Facebook (I guess) Fabian Rodriguez known as MagicFab who after asking him what he was doing today, he mentioned Ubuntu as part of his activities. And I say activities, because Ubuntu is much more than an operating system.

I’ve always liked the world of computer science and unfortunately that was not what I studied, but I learned on my own how to manage, fix, clean my home machines. I could say that the world of computers is my passion and when Fabian told me about this, I knew it was no fluke.

I remember the first thing I said was: Ubuntu what?? How do you eat that?? And then after a brief speach about it and some information he sent to me to read on the subject, dropped his usual phrase, “If you want to install it, I can help you do it now”. Well, two days later, I was harrassing Fabian to help me install Ubuntu after a bunch of questions I had.

Some of my concerns were:

1. If I would be able to use MSN and Skype with camera and audio included.
2. My biggest question was if I could run iTunes on the computer (tool my daughters and my husband use).
3. If Windows had to be removed to use Ubuntu.
4. If I’ll have Office, PowerPoint or Excel with Ubuntu also and if so, would be so easy to use as those.
5. If I was going to be able to install Ubuntu alone, long distance with Fabian’s instructions.

Well, the day I gave a YES myself to Ubuntu, began with a phone call from Fabian from Canada. After downloading into my own computer some files, we start by checking whether they were good and then install it. I remember Fabian told me, don’t install it yet first test it. Then after his explanations that I could partition the computer and leave Windows intact but also have Ubuntu too I said “Let’s do it and install it now”. And so it was, on the phone, with his help, that I installed for the first time in one of my computers Hardy 8.04 and some months later in another Ubuntu 8.10.

When he finally said, “Take a last click and you’re done, finished,” I could not believe it!! First, I had allowed to risk to install another operating system on my computer and two, that I had done through instructions by telephone. That meant that it could be do so easily! That’s how my story began with Ubuntu in June 2008 : D

Months later I bought an Acer Aspire One that came with Linpus and my next challenge was to install Ubuntu on it. It was a laptop (and not a desktop) and needed a version for netbooks so I tried first to fight with LPIA platform with which I ended up frustrated because after installing it did not work and gave me error. Then it was new to me to download an ISO file to my laptop and also install it throught a USB. I think it was two weeks without my computer, sweating and suffering, but with some help of several friends of the Honduran community I finally had Ubuntu on my Acer. I remember I installed 8.10 version which gave me enough slow problems on my laptop, but when I upgraded to 9.10, I was sooo happy;)

From Ubuntu, I further research, looking and learning how to move in the Ubuntu world. As part of that and then again by MagicFab's suggestions I learned how to participate via IRC in different communities, to tell my experiences with applications in Ubuntu, I dared to start my own blog for the first time telling my experience with the Ubuntu Desktop Course (elearning), learned to use my blog as a tool through which I can inform others about Ubuntu, participating in lists of the communities I belong and learned how to handle wiki, blueprint and documentation pages to share information to others.

Today I am part of the community and am in several team where I hope to be able to support as I learn from everyone's experiences too. I am a member in the communities of Ubuntu Honduras, Colombia, Women, Guatemala and El Salvador. Almost daily I am present in IRC channels of Honduras, Colombia and Women getting feedback and contributing wherever I can. I still can not work actively participate in all these media but try to do when I feel more confident about the subject. English is my third language, so I am kind of shy in the ubuntu-women channel.

Today I know that there is Free Software and Ubuntu exists there with all its benefits over other systems. I also know that although I did not study computers, I can handle and learn thousands of things about it and help knowing others that will benefit too.

Today I belong and work hand by hand with others in the Honduras Ubuntu community, promoting Ubuntu in the country, mostly in San Pedro Sula where I currently reside. With the support Fabian gave me, I revived the group that was practically abandoned and we are trying again today to show people of Honduras that Ubuntu is the best choice when it comes to choosing an operating system. Every day I try to learn more and see how I can support other Ubuntu users here and elsewhere. I am very excited to be part of this team and I love to learn and collaborate with this good cause;)

Since I started being part of this community, I had the opportunity to share with others from other distros like Fedora or Debian. There is little that I have experienced them, but for now I'm only interested in Ubuntu.

My name is Elvira Martinez or tatica1 as I I'm known in the community and my main challenge is to convince my daughters and my husband that Ubuntu is the best choice when we talk about operating systems.

***Karen Y. Perez***

When I was a little girl i saw my dad studying computer science to eventually working on projects. Like most little girls I admire my dad more than anyone in the world and I always tried to be just like him. I read many books like him, I begged for my own laptop and fell in love with space. Since then my passion for science, math and technology developed. There were moments where I loved chemistry more than physics and times where math was better than astronomy. But, my passion for computers never faded once. Each year I pleaded my dad to teach me how to program because his code was like a puzzle i need to understand. So, every so often he would teach me bits and pieces but only enough to keep my curiosity afloat and have me do my own research. One day I stumbled across one of my dad’s Unix books in his library. I didn’t really understand much at the time so I tried my very best to read it and eventually I did some research on-line. While doing my research I read about Linux and I saw what the open source revolution was all about. I taught myself as much as I could and I decided to convert my laptop to Linux for the first time in ‘09. Ubuntu has helped me with my studies in computer science and helped me stay open to new things of course including technologies. The last thing a geek needs is to not want to explore outside of the box. I guess you can say I’m a self pro-claimed fem-geek and I couldn’t imagine life any other way. Although, I am no professional yet I do try to talk to other girls and show them how great of an experience using Linux Ubuntu is as well as many other great “geeky” technologies. I hope to one day show young girls that there is more to life than fashion. That you can be as “fashionable” as Barbie and yet be an astronaut.

***Jen Phillips***

Learning to Fly

Some years ago, I used to travel everywhere by bus. The company that ran it was called Microsoft, and I used the Number 3.1. It generally got me where I needed to be, but it took a bit of an odd route to get there, and it would often stop at seemingly random points. If I fancied a change, I could take my walkman, or a book. It wasn’t the most comfortable ride, but it did ok, and I was used to it. After a while, the company decided to upgrade all their busses and change all the routes - and put the fares up. I went onto the Number 95, and everything looked nice and shiny, although I missed my stop a couple of times because I wasn’t used to the route. After a while I realised that although the route didn’t take the same detours, it took new ones, so I didn’t really get where I was going any faster. The busses all seemed to get a bit dingy after a while, too. Still, I had my CD walkman, and it became familiar again.

Eventually, I took the plunge, and got a car. I loved the freedom - I could go where I wanted to go, when I wanted to go. I wasn’t constrained by having to have the right money, and I didn’t have to stop for the sake of everyone else. It was a SuSE, and it was mine and I loved it. Except, any time anything went wrong I had to ask for help. When the radio stopped working, I had to get someone else to fix it. If i couldn’t find a particular stick or button, I had to get someone to show me where it was. It also wouldn’t play any of my old CDs. In short, it was frustrating. I tried a couple of other cars, but they weren’t any better. I took ages getting my Debian to even start, and somehow had a knack for stalling it before I got to the end of the street. Eventually, I gave up and went back to the bus - the XP route now had air conditioning and contoured seats, and I could cope with the delays (and occasional breakdowns) because it did tend to get me there in the end.

Then one day, something quite miraculous happened: someone gave me a pair of wings. In only a couple of lessons, I was flying! I no longer have to wait for the bus, and I don’t need a mechanic to come and rescue me any more. If I want different music, I can just pick up a media player and set it going. If I want to dye my wings a different colour, that’s easy too. I decide which route to take - I’m not even limited by roads any more. The best thing is that flying feels so natural - like walking only better. I call these wings “Ubuntu”.

These story submissions along with all the others are available on the Ubuntu Women Project wiki pages.

Without the efforts of Ubuntu Women Project team member, Melissa Draper, the competition may have never made it to the community, the time and talent she personally put into this competition by drafting the competition as well as writing the voting submission application was awesome! - Thanks Melissa!

It is also important to say thank you to the sponsors of this competition, Rikki Kite, Associate Publisher, Linux Pro and Ubuntu User Magazines, for donating Linux Pro or Ubuntu User Magazine subscriptions (choice of one per winner), to Canonical for donating the Ubuntu Backpacks, notebooks, pens, lanyards, pins and T-shirts, at last but not least to Jono Bacon for making the announcement of the winners as well as for copies of Art of Community.

Again, Congratulations to the winners of the prize packs as well as all those who submitted your person Ubuntu discovery stories. I can’t wait to read the submissions for the 2nd Annual Ubuntu Women Project “How I discovered Ubuntu.” International Women’s Day Competition, so mark your calendars and work on YOUR personal discovery of Ubuntu to help celebrate 100 years of International Women’s Day.

REMINDER: If you or someone you know would like to find out more information about the Ubuntu Women Project there are several ways to do so - website, mailing list, IRC channel(s), and Ubuntu Women Forums

[Discuss the International Women’s Day Competition Winners on the Forum]

Originally sent to the ubuntu-news-team mailing list by Amber Graner on Tue Mar 9 04:46:28 GMT 2010

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Amber Graner: Hug Day/ Bug Day - Targeting Ubiquity





Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Og Maciel: GNOME Developer Kit, follow up

Just wanted to update everyone who showed interest in the new release of GNOME Developer Kit I announced yesterday. Based on some preliminary statistics I collected in the (less than) last 24 hours, it seems that the VMware image type got the most download, followed closely by the installable ISO format. I guess that was due to VirtualBox being able to use *.vmdk files and some people opting for the free virtualization tool.

Here are the preliminary results so far:

1. VMware image: 42 downloads
2. Installable ISO: 26 downloads
3. RAW filesystem image: 17 downloads

Due to the number of downloads and and comments I received, I felt that I should provide with some background on how to install/remove packages and update your system using the conary package management system. So here you go:

The package management system behind the GNOME Developer Kit is called conary and is considered by many as the next generation package management system when compared to some of the popular options out there. One of the reasons behind this claim is the fact that your entire system is actually completely maintained in a versioned state, and conary is always “aware” of what is installed on your system and what files and dependencies make up the entire “set”. This allows for some pretty nifty operations such as rolling back to a specific state of your system.

In order to check for new updates for your system, open a terminal and run the command sudo conary updateall. conary will then check for updates and prompt you to accept the update or not. Please keep in mind that the first time you run conary for the first time, you will experience a delay as your entire system gets analyzed in preparation for the changes that are to take place. All subsequent actions performed will be much faster, I promise. If after a while you don’t feel like waiting for the prompt, add –no-interactive to the update command to have your system updated automatically.

Now, let’s just say that you decided to install something new, such as Banshee. Easy, just run sudo conary update banshee (remember to add –no-interactive for no-hands updates) and voilá!

Want to know what was actually installed on your system? conary q banshee will tell you what version of banshee was installed. How about what files were installed? conary q –ls banshee will give you a list of all the files that were installed and conary q –lsl banshee will give you the long list with file permissions and modes.

Changed your mind and want to remove banshee from your system? sudo conary erase banshee will take care of that. Want to actually roll your system back to the state it was before you installed banshee instead? sudo conary rollback 1 will rollback your system exactly one transaction. Want to go further back? Just increase that number to represent how many transactions to roll back. Want to rollback but don’t remember what point in time you want to go? sudo conary rblist will display a list of all transactions and what was changed. Note that each transaction is preceded by the letter “r“, so if you want to rollback to the point r.15, then use sudo conary rollback r.15 (and don’t forget that “r” or you’ll rollback exactly 15 transactions instead).

How about searching for a package? If it is something that it is already installed on your system, then conary q [package name] will give you the information you want. If the package is not installed on your system yet, then conary rq [package name] is what you need, though since conary does not yet make use of metadata, you’ll need to know the exact name of what you’re looking for. Now, let’s say you want to find out what package provides the command /sbin/service? Use conary q –path /sbin/service to find out that initscripts:runtime=8.81.2-0.11-1 is responsible for providing it (use rq if you want to search the remote repository).

Well, I think this is enough to get you going. You’ll probably want to install Flash and media codecs to enjoy browsing some sites and listening to your media, so let’s apply what we’ve learned so far and run: sudo conary update flashplayer group-codecs

If you’ve stayed with me until now, you may want to read up on what else conary can do or even consider packaging for GNOME Developer Kit. Your help will be greatly appreciated!

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Richard Johnson: Google Maps Goes Cycling

THIS is an interesting thing done by Google today. They have finally added cycling routes to their maps. This is a really nice feature if you are just a casual rider. I know there are a few of us in the Ubuntu community who are not casual riders and we live for speed, we live for flying past pack fodder, and we aren’t afraid of hills. Well, Google maps new cycling route feature is afraid of hills, and when you use it, Google maps will route you around any hills. BOO!

I am sorry, but if Google was serious about the cycling stuff, they could have learned a lesson or two from Map My Ride. Map My Ride is amazing, as it will map, allow you to design a ride, and track your rides with a great level of detail.

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu

Kees Cook: openssl client does not check commonName

I realize the openssl s_client tool tries to be upper-layer protocol agnostic, but doesn’t everything that uses SSL do commonName checking (HTTP, SMTP, IMAP, FTP, POP, XMPP)? Shouldn’t this be something openssl s_client does by default, maybe with an option to turn it off for less common situations?

Here it doesn’t complain about connecting to “outflux.net” when the cert has a CN for “www.outflux.net”:

echo QUIT | openssl s_client -CApath /etc/ssl/certs \
  -connect outflux.net:443 2>/dev/null | egrep "subject=|Verify"

subject=/CN=www.outflux.net
    Verify return code: 0 (ok)

Categories: Computers | Linux | nix | Planet Ubuntu | Ubuntu