Pics and news form #GNUHealth at #WSIS 2013 #freesoftware #ehealth #HIS https://t.co/LxtcamhCu3

I think that Firefox should stay as the default browser in Ubuntu for the following reasons:

• Mozilla has a vibrant open source community and many of our contributors are active in both Ubuntu and Mozilla.
• Mozilla’s mission is to promote openness, innovation and opportunity and Firefox encompasses all of those goals.
• Chromium as a package has fell behind in the past while Firefox has team of contributors in the Ubuntu Community who keep it up-to date every cycle.
• Firefox is perhaps one of the most popular open source browsers.
• And most importantly in my opinion Mozilla by default respects user privacy and choice.

Why fix something if it’s not broken? If others prefer Chromium well then “sudo apt-get install chromium-browser” and I guess that’s just my two-cents on the topic.

So I recently created  the bug regarding the Canonical Design Team removing the community link and also blogged about it. I created a thread on forums and whenever I discuss a topic as important as this I try to reflect on whether my intentions will have the appropriate results and also try to keep my emotions in check. Indeed, I am so passionate about open source communities I’m involved in that I feel the need to advocate for the community in the face of all challenges.

But admittedly, I think my individual response to the removal of the community link has fired some people up to think that Canonical is anti-community which it is not. I do think that Canonical is a business and that businesses do sometimes make decisions that suit them best and may not take into regard how it impacts the people surrounding that business. Perhaps that’s what I thought was going on here, but it has become evident that this was not Canonical’s intention.

So, going forward, I will more deeply reflect on blog posts and discussions and try to take into account that sometimes there are benign factors at play that might seem like fire and brimstone at first. I am also conscious of the fact that I need to set a good standard in our community and reaction over this incident was somewhat reactionary, which in turn generates other reactionary responses, not helping to solve the problem, but more get in the way. I want to additionally apologize for this bit which I take full responsibility for: I would like to note that the video did not specifically refer to Canonical.  The same day it was posted, I immediately deleted the video because it was not appropriate for public and I should not have created it.

 

【DEMO】musictrack MT-1EX FreeSoftware: http://t.co/xFN68bsehf @youtubeさんから

Is it time to give Linux another look?: With recent... http://t.co/Z89CgVlr1Z #Article #FreeSoftware #Linux |http://t.co/2rrdwAnwc8

I am part of a team without state. Please don't feel sad for me though. I am part of an amazing community filled with friendly and diverse people. We meet in person and we have developed deep friendships.

Here's a thought experiment:

What if we (the Ubuntu leadership community at large) were to enable and actively encourage Ubuntu teams (groups really) at any geographical level? What if we called them "teams" rather than "sub" teams. What if we "allowed" them to operate autonomously. What if we banished the term "allowed" from our dictionary?

I advocate the removal of geographical team limitations outright. We can and should have teams at the block, neighbourhood, village, town, city, province/state, region, country, super-country (continent), or even planetary level. We already have teams that operate super-country, and others that want to but are actively discouraged from doing so. (Yes, actively.) I can also envision teams smaller than city teams that could flourish if encouraged.

We (briefly) discussed moving toward the "at any geographical level" team structure today at UDS during the Community Roundtable session. I tabled the idea of moving to this model on a *trial* basis to see what (if any) chaos ensues. For an initial trial period, we could try it, say for a single UDS cycle and then measure the result.

My guess is that we (the collective we) are being too fearful of an outcome that would likely never manifest itself. The best way to overcome that fear is with a controlled experiment that results in data. Generally speaking, I propose that we eliminate any artificial barriers to team creation that are not based on data. Any person in a place that has no existing team would be able to form one, or to join another team. Any person not satisfied with a team in their geography would be free, empowered, and encouraged to set up another team, even if the geography overlaps with the existing team. One team in one geography might not be the best thing for Ubuntu, especially if/when that team is out of alignment with Ubuntu.

Ubuntu has no country or boundaries. Why impose them? Are we not all stateless after all? Are we Ubuntu?

I say, "Let a thousand flowers bloom!"

@AdrianRedhead #FreeBagels #FreeSoftware #FreeAgave #FreeCarRide #FreeOliveGarden #FreeDogPetting #FreeBunny hahaha <3

REALESTATE #Freesoftware, landing page for wholesalers ,rehabbers investors https://t.co/7NxoBUgNYh

Yesterday, it has been suggested to sunset Ubuntu brainstorm. While the arguments on the surface make a lot of sense, a bigger problem seem to be not as much in the focus of the discussion as they maybe should be.

Ubuntu is in a tremendous danger of losing what is understood to be a "community" distribution. Well, community in the sense of a wider community that is substantially larger than Canonical (it can always be claimed Canonical as being a community :-))

Just a friendly reminder, but Mir is open! Here are some useful links.

Documentation

We’ve put effort into sharing as much as possible and lowering the knowledge-barrier to entry for the project. We want you to understand how your pixels will be painted under Mir. Here’s some good links:

Mir documention: http://unity.ubuntu.com/mir/
This is all generated right from the trunk code (lp:mir’s doc/ folder)
We also generate api documentation on same site: http://unity.ubuntu.com/mir/annotated.html

Code

The code is all available on launchpad: lp:mir
The reviews are all done on out in the open: active reviews
Our continuous integration is on jenkins like the rest of the Ubuntu projects: https://jenkins.qa.ubuntu.com/job/mir-ci/
Lastly there are no secret branches or anything like that anymore. We’re operating fully in the open!

Coordination and Planning

We do all of our coordination surrounding the code on freenode’s #ubuntu-mir channel. Since this is an Ubuntu channel, its logged. Here’s an example: #ubuntu-mir log You’ll see in the logs that we really do our updates, coordination and planning all on this channel.

We have our blueprints out in the open too. You can see our upcoming plans and the upcoming work items that are slated.

We’ve got a mailing list on launchpad too! Join up and stay abreast of all the latest email chains.

Enter The Conqueror - Original & Dubs @HJTheConqueror http://t.co/0eZmwsb1Zs #Rastafari #Reggae #Promo | #Ad : http://t.co/rSYWgTkvbO

RT @MaliciaRogue: Using #FreeSoftware is crucial for ppl to keep control over the tools instead of giving it to govts/companies #LesInterne…

RT @MaliciaRogue: Using #FreeSoftware is crucial for ppl to keep control over the tools instead of giving it to govts/companies #LesInterne…

RT @MaliciaRogue: Using #FreeSoftware is crucial for ppl to keep control over the tools instead of giving it to govts/companies #LesInterne…

RT @MaliciaRogue: Using #FreeSoftware is crucial for ppl to keep control over the tools instead of giving it to govts/companies #LesInterne…

RT @MaliciaRogue: Using #FreeSoftware is crucial for ppl to keep control over the tools instead of giving it to govts/companies #LesInterne…

RT @tuxmetal: "Il faut comprendre le code si on ne veut pas se laisser enfermer" #LesInternets #FreeSoftware

Using #FreeSoftware is crucial for ppl to keep control over the tools instead of giving it to govts/companies #LesInternets

"Il faut comprendre le code si on ne veut pas se laisser enfermer" #LesInternets #FreeSoftware

Hot on the heels of my last post showing Unity 8 running on Mir on a Macbook Pro Retina, there were some folks who were curious about how well Unity and Mir work on a phone.

Well, thanks to your friend and mine, Kevin Gunn, you can see a video of Unity 8 on Mir running on a Galaxy Nexus (which is by no means a super-powerful smartphone these days):

Can’t see the video? See it here!

Again, just to emphasize, this has not been through a round of performance optimizations, so you can expect additional performance improvements in the future, but I think this demonstrates that we are heading in the right direction.

If you are interested in participating in Mir development, click here and if you are interested in participating in Unity 8, click here.