Mozilla a récemment annoncé en collaboration avec OpenTok la disponibilité de Firefox Hello dans la version bêta de Firefox actuellement disponible en ligne pour téléchargement.
C’est une annonce importante, dans un contexte où beaucoup de communications en ligne dépendent de logiciels privateurs comme Skype, qu’on sait restreints, censurés et espionnés sans répercussions pour leurs éditeurs.
Firefox Hello permet grâce à WebRTC, définit comme « un canevas logiciel avec des implémentations précoces dans différents navigateurs web pour permettre une communication en temps réel. la communication audio et vidéo en temps réel à même le navigateur web » sur Wikipédia.
J’explique ici comment installer Firefox bêta sous Debian (j’ai testé sous Debian 7 et sous Debian Testing) pour qu’il co-existe avec IceWeasel et qu’il puisse être utilisé en simultané, afin de faire l’essai de Firefox Hello. Ces instructions devraient aussi fonctionner pour Trisquel et Ubuntu, deux distributions GNU/Linux dérivées de Debian. Si vous utilisez une de ces distributions et que ces instructions manquent une précision ou autre détail, faites-moi signe pour les corriger.
Des versions 32 ou 64 bits de Firefox Bêta sont disponibles pour téléchargement à partir de Mozilla.org, j’utilise dans cet exemple la version 64 bits pour GNU/Linux, en français.Installation
- À partir du répertoire où l’application a été téléchargée, décompressez l’archive:
magicfab@lap-x230:~/Téléchargements$ tar -xjf -C ~ firefox-34.0b8.tar.bz2
- -xjf: x pour extraire les fichiers, j pour le format bzip2, f pour spécifier le nom de l’archive
- -C ~: indique que les fichiers à extraire seront dans le dossier personnel (home)
Cette commande fera l’extraction des fichiers vers ~/firefox (répertoire firefox dans votre dossier personnel). Les meilleures pratiques sous GNU/Linux (selon le Linux Standard Base) seraient de mettre cette installation sous /usr/local/ ou sous /opt, mais étant donné la courte durée de vie de mes tests, j’ai préféré la faire dans mon répertoire personnel.
- Lancez l’application Menu principal, choisissez Internet > Nouvel élément:
- Indiquez les informations pour choisir l’icône et le fichier de démarrage:
L’icône se trouve dans ~/firefox/browser/icons. Le fichier de démarrage se trouve dans ~/firefox mais il faudra ajouter l’option -P pour créer un profil séparé d’utilisateur et -no-remote pour qu’elle puisse être éxécutée en simultané à IceWeasel:
/home/magicfab/firefox/firefox -P --no-remote
- Une fois l’information complétée, cliquez sur Valider, puis Fermer dans l’application Menu principal.
Lors du premier lancement, Firefox Bêta demandera quel profil utiliser:
Il faudra choisir Créer un profil pour en faire un nouveau, appelé « Firefox Beta », par exemple. Assurez-vous de choisir ce profil et cliquez sur Démarrer Firefox.Attention à vos données personelles!
Vous pouvez activer ou désactiver ce comportement à tout moment avec cette procédure:
- Cliquez sur le bouton menu et sélectionnez Préférences
- Sélectionnez le paneau Avancé.
- Sélectionnez l’onglet Données collectées.
- Cochez ou décochez la case à côté de Activer la télémétrie.
- Cliquez sur Fermer pour fermer la fenêtre Préférences
Pour ma part je laisse ces options activées car Firefox Bêta n’est pas mon navigateur par défaut, mais vous pouvez choisir quel comportement est le plus approprié pour vous.Ajouter Firefox Hello dans votre barre d’outils
Le boutton Firefox Hello n’est pas visible dans la barre d’outils ni dans le menu. Pour l’ajouter à la barre d’outils:
- Choisissez Personnalisez dans le menu
- Glissez l’icône Firefox Hello vers la barre d’outils
- Cliquez sur Quitter la personalisation
Voilà! Vous êtes prêts à inviter quelqu’un à essayer Firefox Hello!
Vous pouvez aussi vous inscrire à Firefox Accounts pour gérer une liste de contacts, en cliquant sur S’inscrire ou se connecter:
N’hésitez pas à me contacter si vous voulez en faire l’essai, le jour (heure de l’est) je suis souvent branché et disponible entre 10h et 15h.
Pas de contributions.
Donnez l'exemple!Faites un don / Make a donation
Si vous appréciez cet article ou fichier, encouragez-moi en faisant un don. Si vous voulez faire un don en Bitcoin (c'est quoi?), utilisez le code QR à gauche avec votre téléphone intelligent ou l'adresse suivante:
On Thursday, November 13 2014, the Ubuntu Women Project participated in the Ubuntu Online Submit. These were the topics that were covered:
- Getting a final version the Orientation Quiz matrix finalized and ready to test
- Having a sprint to test Harvest Bugs
- Creating a “Resource List” that will hold projects looking for women and resources for projects looking for women
Thanks to everyone who participated and we’re looking forward to continuing discussions and work on all these items in the coming months.
Please note that there is no video for this since those who came decided on doing it all via IRC.
Amir Sanjar, our resident and charming big data guy, spoke to all humans today in his "Big Data and Juju" session.
Highlights? Why not?
- We're generating data with everything we do.
- The landscape of solutions is complex and becoming more so.
- Juju vastly simplifies the deployment of big data solutions.
- Juju extends the sidewalk of solutions, i.e. you can connect other (non-big-data) charms to your solution.
- Amir presented a big data Charms status report and roadmap.
- We need more help, especially charmers, to create solutions for missing pieces of the big data puzzle
Would you like to help solve big (data) problems? The team would love to hear from you.
You can reach out to Amir on his Launchpad page, https://launchpad.net/~asanjar or join the discussion on the Juju mailing list.
You can also contact me. (Consider me your concierge.) I can be reached at randall AT ubuntu DOT com
Check out the whole session here:
Banner cc-by-sa by author. Use it. Spread it everywhere.
Every web developer loves to wail on Internet Explorer but we need to act now if we want to stop the history of IE6 repeating itself with IE8. The longer we don't, the longer we agree to limit ourselves to not using new and exciting features that make the internet better and our lives easier.
Internet Explorer 8 is 35 years old! Okay, okay, it's only 5½ but consider that in Internet Years. When IE8 was released in 2009, neither Android or Twitter were mainstream... and people still found BlackBerrys desirable. In digital terms, IE8 was released a million years ago.
A large part of being a web developer is supporting crappy old browsers. We spend all day with Mozilla and Chrome splashing their fancy new features around in our faces before we remember that we're not allowed to have fun; we need cross-browser support.
Even remembering that 5 years is forever in tech years, the volume of stuff IE8 doesn't support is astounding. It's not just fancy HTML5+CSS stuff. It doesn't support TLS Server Name Indication which means you need a unique IP for every SSL certificate you deploy. That sort of stuff just makes me furious because IPv4 isn't infinite and its addresses are rationed. Even stupidly simple things like box-shadow aren't supported, and made doubly infuriating because proprietary crap like DXImageTransform.Microsoft.DropShadow exists... That's right, IE8 is able to render a drop-shadow but Microsoft were too arrogant to make it available through [draft] standard CSS.
I think we've established that kaka kaka IE8 is awful... And yet 5-10% of the Internet is still using it.If IE9 has been around for 3 years, why hasn't everybody and their dog upgraded already?!
There are a couple of things going on.
IE8 was the last version of IE8 that Microsoft made for Windows XP so XP users either stick with IE8, use another browser or an upgrade to Windows Vista, 7 or 8. Even if they know this is the case, some people will just they wait for their computers to die of natural causes rather than upgrade. Things lag.
My assumption had always been that all IE8 users were on Windows XP. Windows Vista and 7 users could upgrade to IE9 and IE10 respectively so they'd never be an issue... But looking at my web statistics, 45% of IE8 users are using Windows 7, they just haven't updated IE. This is all down to the Microsoft's awful approach to upgrades. Despite stories to the contrary, if you want to upgrade IE, you have to go into Windows Update and manually select the upgrade. This same stupid "feature" was what left us with IE6 for all those years. People just didn't know they needed to upgrade. So didn't.
That does still have 55% of users down as computing dinosaurs who refuse to upgrade their machines. Since neither XP or IE8 get security updates any more, they're bumbling around the internet picking up every bit of malware known to man. They'll inevitably be recruited into a botnet at some point. They're frankly as much a risk to us as they are themselves.
And there are two groups the buck all other trends: Large enterprise IT departments are occasionally filled with lazy and largely incompetent jobsworths figuring out the paths of least resistance to make their lives easier. And China because there's so much piracy there (and therefore so little working Windows Update). Seriously, ~5% of China is using IE6 and ~13% on IE8.But we're just web developers, what could we possibly do to influence the great unwashed?
Enterprise IT and China can both go swivel on it. There's nothing we or Microsoft can do to influence them; they're lost causes. If you need to support them, I guess that's that. We'll see you in 2020 when they've finally upgraded. For everybody else...
Education is going to be the easiest issue to solve. Unfortunately Windows computers don't explode when something on them leaves its support period. This is a major design flaw which keeps people oblivious people using ancient software indefinitely. Let's just tell them what the score is. Knowing is half the battle, right?
So if you own a website, you can make your IE8 users aware their browser is ancient. There are numerous solutions out there but it can be as simple as just adding a conditional header to your main template. You can highlight a few things:
- IE8 is ancient in technology terms.
- IE8 will become vulnerable to exploits.
- Developers have to work extra hard to support IE8. They'd like to use that time to make other things better.
- Enumerate or link to the steps they need to take to upgrade or change browser.
Here's my simple example using conditional comments. It's fairly low impact but won't annoy too many people.<!--[if lt IE 9]> <p class="alert">Thanks for visiting my website. The browser you're using is <em>ancient</em>. Even Microsoft has stopped supporting it which means it's quite <strong>dangerous</strong> to keep using it. It also means I have to take extra steps to make sure this site works on your ancient browser.</p> <p class="alert">Do the Internet a favour and <a href="http://windows.microsoft.com/internet-explorer/">upgrade to the latest Internet Explorer</a>... or use another browser like Chrome or Firefox. If you're on Windows XP, your whole operating system is putting you and others at risk. Please upgrade.</p> <![endif]-->
I use a shorter one in my template but my IE8 users are pretty few already. The next step is to actively stop supporting IE8 and start using the things you've been holding back from. When people notice their browser isn't offering them the experience they want, they'll get the message.But this didn't work for IE6, did it? Why would it work for IE8?
It did work but it took us forever to notice there was a problem. We expected IE6 to die naturally. It didn't.
Our rationale was that new versions of Windows were generally considered good upgrades and computer hardware was also improving at pace. Every couple of years, everybody would chuck out their old desktop and bring in this shiny new thing with a new copy of Windows. When Vista came out and was slated, people stopped upgrading. Hardware development pace has also slowed and with it (and a shift to mobile) people's enthusiasm for expensive Hardware+Windows has evaporated.
Once developers realised XP and IE6 would never die organically and started to lose their shit, banners and tools like sevenup started popping up to tell IE6 users of their insolence. Within a few years, IE6 dropped under 5%. Then the big sites like Google started dropping support and usage flew below 2% within a year. IE6 usage is currently around 1% and largely unusable on the modern internet; the way it should be.
We need to start the wheel turning for IE8. Just hoping it'll go away doesn't work because that's just not what happens with software.What's next? What will the deaths of IE9 and IE10 bring?
Until Microsoft fix how they upgrade Internet Explorer —so major versions are little more than an automatic update like in Chrome, or packaged up separately from the core OS as in Ubuntu— we're destined to go through this cycle of uptake, decline and venomous hatred every couple of years. I already hate IE9, I just hate IE8 more.
Can I Use has a great search function that allows you to compare dinosaurs like IE9 and IE10 against the development builds of Chrome and Firefox. I'm personally looking forward to using FlexBox for layouts but I know a lot of people want decent 3D transforms.
The internet of tomorrow is going to be a beautiful thing to develop on, but only if we can get rid of the crappy old browsers that hold us back.
Victor and Andrew are two inspiring Community developers that have devoted their spare time to contribute to the Ubuntu Touch Music App team. I sat down with them during the Washington Device Sprint in October where they told us how they drew inspiration from the Design Team, and what drives them to contribute to Ubuntu.
Hey guys, so when did you first get involved with Ubuntu?
Victor: “I started to contribute to the Ubuntu platform in March/April 2013 where I noticed there was no music app, so I started putting one together. It was pretty sketchy to start with, but it worked. I didn’t have a device to test it on so I mostly tested it using the platform on my desktop – so things were a bit hit and miss.
There was also another developer doing a music app, and at the time there was no core capability of playing music through an application for the proposed devices. Michael Hall (Open Source Software Developer) and Alan Pope (Engineering Manager) pulled Dale Hall and I together, where we merged our core bases and started the music core app.
We didn’t have as much time as other applications, so we more or less sprinted like we are now to get things done. It was very spec driven and specific, which was helpful but sometimes it was hard to put together a full vision of what the designers wanted. So now we are redoing it from the feedback we have gathered, and it’s going pretty well. A little more agile than it was previously as to do thing faster, but it’s been fun the whole time. It’s nice to work on an application that people need and gets visibility, never get sick of hacking at it.”
Andrew: “I’m from North London, where I’m currently studying Software Engineering at Oxford Brookes University. I was working on my own music app where I just taught myself how to do things using my own framework, then I saw that these guys at Ubuntu had a similar problem to me, and so I thought I’d provide a patch. This then built up from there, and now here I am!”
Steph: “It’s amazing that someone can be in their bedroom writing codes and then suddenly your app is on a phone!”
Victor: “The other great thing about it is the Community Managers make it easy and apparent that you can contribute to different projects.”
Andrew: “Yeah someone just got in contact with me and asked me if I wanted to join the team and told me how open source projects work.”
What inspired you to contribute?
Victor: “A lot of my original inspiration was from what the Design Team had previously done. The previous iteration design spec was very large for the music app and it wasn’t as future driven, more just visually pleasing.”
Do you find it hard to implement some designs?
Victor: “We try to make it as close to the designs as we can, but obviously there’s compromises. There was some very flow driven things such as: sized cover arts that were hard to implement, but we can implement them now. It’s nice because they use the same pattern from other applications.”
Andrew: “Usually we just tell the designer that this is just not possible.”
What is it about open source that you like?
Victor: “I have been a user since 2006, but I have never been a large open source developer myself. It is hard to get involved with when you don’t know what you want to contribute to.”
Andrew: “Most applications are so developed already, so you would have to learn the existing code base and develop on it, whereas if you start a new you know everything from the get-go. Seeing your application on the device and knowing it can be on other devices too, is pretty exciting!”
How does it fit into your lifestyles?
Victor: “I’m a software engineer as well, so I write a lot of code. I haven’t really done QML or QT until I started doing these applications with the Ubuntu platform, so it has been a learning experience. I am learning something new from experienced people.”
Have you made any other applications for Ubuntu?
Victor: I’ve made a few games like Piano Tiles, and another that’s kind of like a clone of that but in QML – It’s a simple app but a good time waster haha.”
How much time does it take you to develop an app?
Victor: “It took me like a day. Andrew made a game last night! In 2 hours…”
Andrew: “Yeah we did! Loads of us at the sprint just got together in a room and made a few games.”
So you’re used to working remotely, does that put a barrier against things?
Andrew: “It sometimes delay things. However, you start to build this image of a person, so when you actually get to meet them you start to understand how they are and what makes them tick.
Victor: “Depends on how personal it really needs to be. If you are collaborating together and it’s mostly writing code and coming up with ideas, it doesn’t necessarily need to be face-to-face. It is obviously nicer, but you also get the benefit if the other person is a night owl in a different country where sometimes our hours overlap, two different chunks of time we’re working in.
Andrew: “There’s usually someone on IRC to speak to, it’s like a 24 hour operation haha.”
What’s the vibe like in the Community at the moment?
Victor: “It’s a pretty small Community at the moment, with close ties. Everyone is receptive to feedback, so if it was larger Community I don’t think it would be as receptive.”
Steph: “Thanks for your time guys!”Here’s a sneaky preview of the music app, more will be revealed soon:
This is a week full of exciting events in the Ubuntu world! Following on the series of Ubuntu Scopes Workshops for the Ubuntu Scopes Showdown, we’re thrilled to announce more Scopes Workshops sessions as part of the Ubuntu Online Summit.Scopes workshops: learn more and ask your questions
In order to support participants of the Scope Showdown, we’re organizing a series of workshops around different topics on writing scopes. These will be 1 hour hands-on sessions where the presenter will be demonstrating the topic live on video, with real code and using the Ubuntu SDK.
These are also meant to be interactive, so during and after the session the presenter will be answering the questions posted in real time by developers on the chat widget on each session page. Here’s the schedule for the workshops:Workshop Time Presenter Online Accounts for Scopes Developers Thursday, 13th Nov at 14:00UTC Alberto Mardegan Scope Development How-Tos Thursday, 13th Nov at 15:00UTC Thomas Strehl & the Unity API Team
In a nutshell:
- WHAT: Scopes workshops at the Ubuntu Online Summit
- WHEN: Thursday, 13th November, starting at 14:00 UTC
- WHERE: At the Ubuntu Online Summit
Looking forward to seeing you there!
Departments are a way for the user to navigate the data source exposed by a scope. A music scope can use them to allow browsing by genre, a Youtube scope could list channels and playlists, a news scope could use them for listing topics, etc. Departments can also display a full hierarchy of sub-departments.
In this tutorial, you are going to learn how to create and add them to your scope.
The Developer Edition is exactly what it says on the tin: a browser built around the needs of web developers.
The Firefox team set out to bring together tools needed to keep developers productive across a multi-device and multi-platform environment, “creating a focal point to streamline your development workflow.” Though the Firefox Developer Edition has a touch of the familiar, the rejigged UI and features make it a formidable development environment while still the fully capable browser Firefox users know and love.
The biggest change you’ll notice is the dark UI of the slick inspector applied to the rest of the browser. Not your style? You can revert to the familiar light theme by heading into the Customize options at the bottom of the “hamburger” menu and clicking “Use Firefox Developer Edition Theme”.
Submitted by: Sam Tran
Most important news first…
After a lot of hard work and a substantial grilling in #ubuntu-meeting
I have finally achieved official Kubuntu Developer status!
In other news.. I backported Plasma 5.1.1 to Utopic and you can find it
in the backports ppa.
Add to your sources.list
then do a full upgrade.
Command line for 14.10:
sudo add-apt-repository ppa:kubuntu-ppa/backports
sudo apt update
sudo apt full-upgrade
Back in the dark days of computing (pre Ubuntu), people were referred to as "users" to essentially frame the industry into a small group that was in a position of power and privilege and one that was not. The vast numbers of unprivileged people could only consume or use. Great for industry and profit, but poor for creating an inclusive society.
I found this photo on a photo sharing service and it is evidently a photo of a user.
Note that when we call people that enjoy Ubuntu's products users, we run the risk of putting them in the same negative box. Why do some people insist on calling people that enoy computers and technology "users"?
I'm sorry but people who enjoy and run Ubuntu are not "users". We're past that. It's over. Did you come from a proprietary technology company that called people users? You're past that. It's over.
Can we as a community agree to drop the term? It's predatory.
Here are some suggestions for replacement words:
Try something like this:
"A person that enjoys Ubuntu."
"A human that runs Ubuntu."
"A fan of Ubuntu."
Image by nosferatu9000
There was this idea proposed by Stuart Langridge a long time ago about creating a store to share components amongst app developers. Personally, I think that the idea is ingenious! Unfortunately the idea did not gain traction due to lack of volunteers and was eventually forgotten.
If you are wondering, what's the need for such a component store? How does it benefit me? Let me explain. To best describe the relevance of a component store, let me first describe an issue that is currently cropping up in the ubuntu app dev community.
Some time back, I created an application called Flashback which came with a welcome wizard. The welcome wizard was well appreciated by other developers and started to make its appearance in some well known applications like Project Dashboard, Guitar Chords and Jupiter Broadcasting. I am personally flattered that it is being used in other apps since it is a testimony to doing something right. The open source culture encourages learning and being inspired by the work done by others. We help one other improve the base line quality of apps in the community.
If one were to implement the welcome wizard in their application, one can do so in two ways,
- Implement the feature from scratch
- Borrow it from another place
Both the approaches are bad since the first encourages code duplication while the other creates a messy situation of having to constantly keeping a tab on the upstream code for improvements, bug fixes and does not encourage collaboration. There is also the issue of documentation. It is difficult to borrow a component if it doesn't have much documentation explaining how to use it.
Can't we be more smart about this? And that's precisely what the Ubuntu Component Store (UCS) aimes to solve.
The Ubuntu Component Store (UCS) is intended to be a library hosting a collection of components/modules that app developers can use in their application without too much of a fuss.
What if I told you that installing/updating a component would be as simple as invoking a simple magic command?ucs install ComponentName ucs update ComponentName
I have a working prototype that I would like to show you all :-) Want to learn more? If interested, join us on Friday, November 14th, 18:00 UTC at #ubuntu-uds-appdev-1 Ubuntu Online Summit. Here is the link to the session.
Mark Shuttleworth, our founder, spoke to all humans today in his Q&A Session.
Highlights? You betcha!
Ubuntu for Humans
- Mark talked about our project's "big rocks".
- We are a project for human beings, and that's a strong part of our ethos.
- Ubuntu benefits our communities.
- People care about helping humanity get over its challenges and griefs.
- Exciting times are ahead!
- We have a phone, the images are coming along beautifully, we're getting solid feedback, release-to-manufacturing (RTM) is on track, and the team is working furiously
- This place (Ubuntu) will be the only place in the world where you can watch a phone being created in front of your eyes
- Our scope challenge is underway
- We want to make people feel that the Ubuntu phone is the fastest path to the net
- Scopes are the way to do that! Please take a look, and help.
- Scopes are lighter than a traditional application
***TEASER*** We will shortly announce a developer program in partnership with one of the world's biggest telecommunications companies!
- Being an independent phone community is valuable
- Ubuntu on the phone is a platform that can deliver a new kind of trust
- Well done to all that have helped!!
On the convergence plan:
- The official "desktop next" is in Ubuntu 11.10, it's super early though.
- We are taking the experience of the phone and making it a great desktop experience.
- Think of it a a graceful transition, not a phone on a desktop.
- Next-generation silicon (CPU's) that are coming will be able to drive quad HD displays.
- If you care about the desktop, and you want to work on a professional development project, check out "desktop next".
- Mir support has landed in GTK, patches welcome.
- Our goal is to have Unity8 as an option (not default) for 16.04LTS
Ubuntu for the Cloud
- Ubuntu is now on the Google Compute Engine. Check it out.
- Google has a good relationship with Ubuntu.
- Let's try to convince companies to continue to grow the volume of code avalable to innovators all over the world.
- We should be proud that we have catalyzed this change.
- Do you know of other clouds we should be on? Please let us know.
- Getting Ubuntu on clouds is non-trivial, but when we get it there it's to a high standard, and optimized.
- Looking to build your own cloud? Try the OpenStack installer
- It uses Juju and a cloud-friendly GUI.
- Get a couple of (or 5) machines, or a single beefy one and try it.
- Canonical has Autopilot for OpenStack, for our customers.
- MAAS 1.7 will be SRU'd into 14.04 and 14.10. Feedback is welcome.
- MAAS will allow you to install all kinds of OS'es onto clouds, not just Ubuntu.
- Ubuntu has set the pace for the industry with MAAS, and has made it "cool" to do provisioning.
- Docker is everywhere. What are your ideas to support it better?
- We will bring all the major Docker orchestration systems to Juju (kubernetes, etc.)
- We have a Reddit Charm! You can now fork Reddit ;) (Hush hush! Please don't tell anyone.)
- LXD (lex-dee) is a server (daemon) that we released at ODS. Think of it as a container-based hypervisor
Let's end with a question for every human:
What do you think it would take for us to make a really cool Ubuntu for the "Internet of Things"?
Check out the whole session here:
Banner cc-by-sa by author. Use it. Spread it everywhere.
In October 2014, we affected 13.75h works hours to 3 contributors:
- Thorsten Alteholz
- Raphaël Hertzog worked only 10 hours. The remaining hours will be done over November.
- Holger Levsen did nothing (for unexpected personal reasons), he will catch up in November.
Obviously, only the hours done have been paid. Should the backlog grow further, we will seek for more paid contributors (to share the workload) and to make it easier to redispatch work hours once a contributor knows that he won’t be able to handle the hours that were affected to him/her.Evolution of the situation
Compared to last month, we gained two new sponsors (Daevel and FOSSter, thanks to them!) and we have now 45.5 hours of paid LTS work to “spend” each month. That’s great but we are still far from our minimal goal of funding the equivalent of a half-time position.
In terms of security updates waiting to be handled, the situation is a bit worse than last month: while the dla-needed.txt file only lists 33 packages awaiting an update (6 less than last month), the list of open vulnerabilities in Squeeze shows about 60 affected packages in total. This differences has two explanations: CVE triaging for squeeze has not been done in the last days, and the POODLE issue(s) with SSLv3 affects a very large number of packages where it’s not always clear what the proper action is.
In any case, it’s never too late to join the growing list of sponsors and help us do a better job, please check with your company managers. If not possible for this year, consider including it in the budget for next year.Thanks to our sponsors
Let me thank our main sponsors:
- Gold sponsors:
- Silver sponsors:
- AD&D – David Ayers – IntarS Austria
- Domeneshop AS
- Trollweb Solutions
- Université Lille 3
- Bronze sponsors:
Part of Miguel de Icaza article
Today, Scott Guthrie announced that Microsoft is open sourcing .NET. This is a momentous occasion, and one that I have advocated for many years.
.NET is being open sourced under the MIT license. Not only is the code being released under this very permissive license, but Microsoft is providing a patent promise to ensure that .NET will get the adoption it deserves.
The code is being hosted at the .NET Foundation's github repository.
This patent promise addresses the historical concerns that the open source, Unix and free software communities have raised over the years.http://tirania.org/blog/archive/2014/Nov-12.html
What do you think about this?
The Ubuntu Online Summit is an event that allows the Ubuntu community to contribute to the development of the operating system by taking part in discussions with the developers. It features a lot of topics regarding the system, some more complex than others, but pretty much all of the aspects of the distribution will be covered.
The current summit is scheduled to take place right after the Ubuntu 15.04 (Vivid Vervet) development cycle has started. Users will be able to find out about the features that are going to be integrated in Ubuntu ahead of time, and they will be able to query the developers about any subject. If you have any questions about Ubuntu (not technical support related), if you want to know why something is implemented in a certain way, or you just want some general information, then the Ubuntu Online Summit is the place to ask them.
Submitted by: Silviu Stahie
I had this thought. Everyone1 wears these fitness wristband things2 now. In the Dresden Files books, Harry Dresden the wizard has a set of magical finger rings which store a little bit of kinetic energy every time he moves his arms. So it’s a tiny bit harder to move them, but not enough that you’d notice, and then he (because he’s a wizard) can release all that energy in one go and use it to do impressive things like punch a car over onto its roof. So, what if you invented a fitness wristband thing which worked like that3 and then you made everyone wear one. Could you use the energy thus accumulated to power the whole of humanity?
We shall leave aside such tedious and boring questions as where all the extra food is coming from to produce this extra energy4, how one collects all the energy thus produced and feeds it into the National Grid5, and whether the wristband company would bother producing Ubuntu drivers. Treat it as a maths problem.
A trick I picked up from the What If xkcd column is Fermi estimation, which Randall correctly uses to mean that you estimate stuff to the nearest order of magnitude to give yourself a rough estimate of an answer, and I am going to misuse to mean making up a bunch of the numbers because maths is a bit annoying. This means that either I’ll be somewhere roughly within the same area6 as the answer (10% chance), or I’ve screwed up some calculation like the number of grams in a kilogram and I’m miles out (90% chance, and feel free to moan at me on twitter if so).
So, basic physics. Raising a 1kg weight 1m requires 10 joules of energy. Let’s imagine that he magic wristband makes moving your arms ten percent harder than it actually is, so when you pick up a 1kg weight and move it 1m it takes you 11J of energy and the extra joule goes into powering humanity so we can stop digging up oil. How much energy do you use moving your arms every day? Well, how much does an arm weigh? An average person weighs about 65kg (it’s around 83kg for men and 70kg for women, but people in the UK are better fed than the world average7, and children weigh less8). The Rule of Nines9 says that each arm weighs about 9% of body weight, as does your head, and legs are 2×9=18%. So an arm weighs about 6kg. I reckon that I move my arm a foot once every 10 seconds or so10, at a guess (this Fermi thing is great, isn’t it?). So that’s 6kg × 0.3m × 6 × 60 ≅ 650J/hour. There are seven billion people in the world, and everyone stays awake for, let’s say, twelve hours a day11, which means that our energy wristbands would collect somewhere around:7.125 billion people × 650 J/person/hour ≅ 5×1012 J/h ≅ 5×1016 J/year
That’s not actually that bad! 50 petajoules/year of energy just from magic wristbands! Is that enough?
No. World energy consumption figures get disputed a lot, but we are apparently using over 500 exajoules per year. That’s 5×1020 joules, or four orders of magnitude out. That’s not four times as much, that’s ten thousand times as much. That’s the difference between12 shaking Simon Cowell’s hand and hitting him in the face as hard as you can with a croquet mallet. Dammit. I shall not solve the energy crisis today. Back to the drawing board, I suppose.
- by which I mean Dan Newns ↩
- I don’t, but Dan is wearing enough for both of us, and a netball team besides ↩
- how? I don’t know, it’s magic. Imagine that the extra energy is because of friction against the luminiferous aether ↩
- from Philpotts the sandwich shop, if there’s any justice ↩
- transmission through the luminiferous aether, clearly; Star Trek did this, they just called it “subspace” ↩
- by a pretty loose definition of “area” ↩
- because we have Philpotts ↩
- because they don’t eat enough sandwiches ↩
- which I think I picked up from an old Dragon Magazine ↩
- spare me the jokes ↩
- if they’re lazy, which statistically a few of them must be ↩
- although not the most serious consequence of ↩
Over a week ago, we announced the Ubuntu Scope Showdown: a competition to write a scope for Ubuntu on phones in 5 weeks and win exciting prizes.
Scopes are Ubuntu’s innovative take at revolutionizing the content and services experience. For users, they provide quick and intuitive access to content without the need of loading an app. For developers and operators, scopes provide an easy path to surface their content and customize the UX in a way that is very flexible and integrated.
After the initial contest kickoff, we’ve already had a number of participants blogging, sharing updates and teasers about their work. Here’s a peek at some of their progress.A variety of scopes
In the words of Robert Schroll, of Beru fame, e-mail apps are just passé. So much that he decided to explore an interesting concept: reading your e-mail with a scope. With a nice extra touch: Ubuntu Online accounts integration.
You don’t know where to eat tonight? No worries, Sam Segers has you covered. Check out his Google places scope to easily find somewhere new to go.
Riccardo Padovani is bringing the dark horse -or well, duck?- of search engines into Ubuntu. Armed with the DuckDuckGo scope, get results like a pro with “real privacy, smarter search and less clutter”.A wishlist of scopes
- 8tracks scope: I love music, and I love mixes. 8tracks is a music streaming service to listen to the mixes their community members create and to get creative submitting mixes. As an avid mixer and listener, I’d be using this all of the time, especially if it came with Online Accounts integration that showed me content relevant to my interests.
- Ask Ubuntu scope: the biggest Ubuntu Q&A site. I regularly check the ‘application-development‘ tag there to see any new questions and if I can help a fellow Ubuntu developer (and you should too). It’d be absolutely awesome to get those updates easily on my phone screen, with settings to filter on tags and the ability to upvote/downvote questions and answers.
Not sure what to write a scope for yet? Well, check out the ideas over at the Showdown reddit, or let your imagination run wild with a comprehensive list of APIs to get more inspiration!A prize for your scopes
It’s not too late to enter the Showdown, you too can write a scope and win prizes! Here are some tips to get started:
- Get familiar with the contest rules
- Get started with the scopes tutorials
- Watch the Scopes Workshops
- Stay tuned for more workshops at the Ubuntu Online Summit
- Ask your questions and get help on scopes development on Ask Ubuntu, G+, Reddit, IRC, or the Ubuntu phone mailing list
Looking forward to seeing the next batch of scopes participants come up with!
Before I start, let's recap two words that you may have heard recently if you've been around Ubuntu people. I promise this will be the only jargon in this article.
Ok, with that out of the way...
I've posted a few times recently about Juju which is in my (slightly biased) opinion, the best and easiest way to get tools that solve real problems deployed onto a "cloud".
But what is a cloud? There are too many definitions out there that unfortunately don't make it any easier for people to visualize what a "cloud" is. And, as if to add insult to injury, a bunch of buzzwords and "thickets of gobbledygook "(1) cloud our understanding of "clouds".
Juju simplifies this immensely. But, what if, as a pure thought experiment, we made the canvas that is presented in Juju and that is designed to show the substrate (or fabric) that the "cloud" is built upon a little more representative of the physical reality? In reality, "clouds" are just collections of computers (and things that connect to computers). Maybe we should attempt to depict some of this.
Admittedly, I'm no 3-D artist, but I love to visualize and do mock-ups. In the spirit of giving humans that are building solutions with Juju a more representative view of their canvas what if we displayed something that looked a little more like this?
In this depiction, computers (and computing resources generally) could be represented roughly to scale as 3-D boxes. Height can represent how powerful they are. area might represent how much they cost, or some other measurement. "Big" resources are easily discernible from "small" resources.
Imaine dragging your Juju Charm onto this canvas and then resizing the Charm to cover the resources that you want it to consume. Grab more "small" resources, or grab some of the "big" ones. (In other words, scale out, or scale up.)
What do you think? Does this idea have merit? Does this make is easier for humans to visualize and to understand the "cloud"?
(1) I'll write more on "thickets of gobbledygook" later, but now you know my term for it. And, if you're creating these thickets, please cut it out.
Image by author. Please help him improve it ;)
The speeds are horrible with this when you are at a distance from the router; like 20 feet away. Here is proof:
Before (on G network):
After (with it on G network):
What’s funny is that when I connect to a N network the speeds really drop!
I learned my lesson, do your homework and read the reviews on items before buying. I hope there is a way to increase those speeds on Linux or it’s just the product itself on Linux.