Planet Ubuntu

Subscribe to Planet Ubuntu feed
Planet Ubuntu - http://planet.ubuntu.com/
Updated: 39 min 47 sec ago

Sebastian Kügler: “Killing the Cashew” done right.

Wed, 02/18/2015 - 05:29

Plasma Desktop’s Toolbox

One of the important design cornerstones of Plasma is that we want to reduce the amount of “hidden features” as much as possible. We do not want to have to rely on the user knowing where to right-click in case she wants to find a certain, desktop-related option, say adding widgets, opening the desktop settings dialog, the activity switcher, etc.. For this, Plasma 4.0 introduced the toolbox, a small icon that when clicked opens a small dialog with actions related to the desktop. To many users, this is an important lifeline when they’re looking for a specific option.

In Plasma 4.x, there was a Plasmoid, provided by a third party, that used a pretty gross hack to remove the toolbox (which was depicted as the old Plasma logo, resembling a cashew a bit). We did not support this officially, but if people are deliberately risking to break their desktop, who are we to complain. They get to keep both pieces.

During the migration to QML (which begun during Plasma 4.x times), one of the parts I had been porting to QtQuick was this toolbox. Like so many other components in Plasma, this is actually a small plugin. That means it’s easy to replace the toolbox with something else. This feature has not really been documented as its more or less an internal thing, and we didn’t want to rob users of this important lifeline.

Some users want to reduce clutter on their desktop as much as possible, however. Since the options offered in the toolbox are also accessible elsewhere (if you know to find them). Replacing the toolbox is actually pretty easy. You can put a unicorn dancing on a rainbow around your desktop there, but you can also replace it with just an empty object, which means that you’re effectively hiding the toolbox.

For users who would rather like their toolbox to be gone, I’ve prepared a small package that overrides the installed toolbox with an empty one. Hiding the toolbox is as easy as installing this minimal package, which means the toolbox doesn’t get shown, or even get loaded.

I would not recommend doing this, especially not as default, but at the same time, I don’t want to limit what people do with their Plasma do what we as developers exactly envision, so there you go.

Download this file, then install it as follows:


plasmapkg2 -t package -i emptytoolbox.plasmoid

Now restart the Plasma Shell (either by stopping the plasmashell process, or by logging out and in again), and your toolbox should be gone.

If you want it back, run

plasmapkg2 -r org.kde.desktoptoolbox

Then restart Plasma and it’s back again.

Even more than just removing the toolbox, I’d like to invite and encourage everybody to come up with nice, crazy and beautiful ideas how to display and interact with the toolbox. The toolbox being a QtQuick Plasmoid package, it’s easy to change and to share with others.

Sam Hewitt: Plagiarism in Open Source

Wed, 02/18/2015 - 05:00

Something that I will universally condemn is the purposeful and insidious behaviour that is open source theft.

There's a difference between something being in the public domain and being free and open source. The latter has a license, for one, and a purpose of the license is to preserve credit to the author or authors and if we don't uphold the license then it loses it's effectiveness.

Now most people abide by the licensing of projects but there are a select few who think they can simply copy a project and remove the licensing and either redistribute under a different license or with out one at all, usually unbeknownst to the authors of the original project.

For instance, if in a project the GPL preamble is in every file that contains code, it takes effort and intent to remove from most if not all of them. If they were truly in the spirit of open source they'd acknowledge the work done by an original author and preserve the license when releasing their fork or modified version in a befitting manner.

Now granted most of this occurs on a pretty low scale –no one's out there copying the Linux kernel and passing it off as their own work. But we as proselytisers of open source also have to be guardians of it. We need to hold plagiarists accountable for their actions or, at least, call them out on the fact that what they are doing is wrong.

Listen to this rant instead:

Thomi Richards: Updated gitg packages for Ubuntu Utopic

Wed, 02/18/2015 - 04:00

I love the promise of the git revision control system: It's fast, it's free, it can handle huge workloads, and sites like github have made git the de facto standard. However, I absolutely hate the command line interface. I find it inconsistent, unfriendly, and generally difficult to work with. The UI and the documentation have an air of smug superiority about them (or perhaps that's my own inferiority complex): they seem to say "If you can't understand the internal data structures git uses, you're too stupid to use this tool".

I'm clearly not the only person frustrated by this: Kim Silkebækken created the amusing git man page generator, which uses markov chains to generate random (but plausible) git documentation. In a similar vein, Jonathan Hartley explains git using spatial analogies (or doesn't).

My difficulties aren't due to it being a command line tool either: I spend 90% of my working life in a terminal emulator. Nor is it due to git being a revision control system: I learned to use the bzr command line UI with ease. My suspicion is that the git developers didn't have anyone else in mind when designing and implementing their UI. In the early days of git, who could have predicted the success of the tool, or the wide audience it would attract?

I'm slowly learning the command line UI, but sometimes I just want to "get stuff done", and the command line is too frustrating to use: I need a GUI application to use alongside the command line. After considering the alternatives, it seems like gitg is the most appropriate choice for a Linux system. There's a problem though: the version packaged in Ubuntu Utopic is 0.2.7, the latest upstream release is 3.15.1. I know the rudiments of debian packaging, so I thought I'd spend some time updating the gitg package to the latest upstream version. I had no idea what I was getting myself in for.

In the end, I ended up rebuilding libgit2, libgit2-glib, webkit2gtk, and gitg. All the packages are in my 'gitg' PPA. If you'd like to try it out, enter these commands in a terminal:

$ sudo add-apt-repository ppa:thomir/gitg $ sudo apt-get update $ sudo apt-get install gitg

Warning: This PPA includes a newer version of libgit, which may cause other applications that use the same library to break. As such, it is extremely experimental. If these packages cause you to lose data, don't say I didn't warn you!

The new gitg application seems to work well though:

I'll try and keep this PPA up to date, and will build Vivid packages once Vivid is released. If you have any questions, please don't hesitate to contact me.

Didier Roche: Ubuntu Make community releases 0.6 with 5 new supported platforms

Wed, 02/18/2015 - 02:37

What always inspires me in my work is that community participation is at heart of what we are doing, and that’s what help us waking up everyday. Anybody can dive and fix small typos, bugs, or even bring big features to the table! This is exactly what happened with this new Ubuntu Make 0.6 release, entirely backed by community participation!

In addition to zsh support, you will find 5 new jetbrains IDE supported into the “ide” Ubuntu Make category, which are: RubyMine, PyCharm educational edition, PyCharm professional, WebStorm and PhpStorm! Those new ones align nicely and complete the already supported 10 platforms in Ubuntu Make, totalising thus (if I can do maths) 15 of them! Remember we started the vivid cycle with only one platform supported as it was about building solid foundations and helpers in the tool so that such contributions can exist. I guess there has never been a better time to be a developer using Ubuntu as their OS!

I was delighted to see such big contributions being posted as a pull requests by Anton Antonov without much more to do afterwards than slight adjustments. This testified that the overall frameworks (and tests infra as well) is easy enough to grock and that’s a huge source of satisfaction for us! I was even more excited to see that another community member who did a lot of work on Ubuntu Make (Tin Tvrtković) helped on the review and gave great advice!

Great work team! That’s the kind of things that made my day. All those niceties and excellent contributions are available as of now in Ubuntu Make 0.6 in Vivid, as well, through its ppa, to 14.04 LTS and 14.10 ubuntu releases.

Maybe you can be the next awesome contributor? Our issue tracker is full of ideas and opportunities, and pull requests remains opened for any issues or suggestions! For all the various form of contributions and how to give an hand, you can refer to this post!

Ronnie Tucker: End of the m0n0wall project

Tue, 02/17/2015 - 22:20

Manuel Casper the creator of m0n0wall project officially announce on 15 February 2014 that the project has officially ended and no development will be done anymore, and there will be no further releases. Here is his announcement,

“Dear m0n0wall enthusiasts,

on this day 12 years ago, I have released the first version of m0n0wall to the public. In theory, one could still run that version – pb1 it was called – on a suitably old PC and use it to control the Internet access of a small LAN (not that it would be recommended security-wise). However, the world keeps turning, and while m0n0wall has made an effort to keep up, there are now better solutions available and under active development.”

 

Source:http://m0n0.ch/wall/end_announcement.php

Submitted by:Manuel Kasper

Ubuntu Kernel Team: Kernel Team Meeting Minutes – February 17, 2015

Tue, 02/17/2015 - 15:35
Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20150217 Meeting Agenda


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Status: Vivid Development Kernel

We are in the process of rebasing our Vivid kernel to v3.18.7 upstream
stable. We’ll try to get it uploaded today. We would also like to push
the v3.19 based kernel we have up to the archive asap. We are still
cleaning up some remaining DKMS drivers before we do. For anyone
interested in getting an early preview, we have a v3.19 based kernel
available for testing in our ckt PPA.
—–
Important upcoming dates:
Thurs Feb 19 – 14.04.2 Point Release (~2 days away, yes this was
delayed)
Thurs Feb 26 – Beta 1 Freeze (~1 weeks away)
Thurs Mar 26 – Fina l Beta (~5 weeks away)
Thurs Apr 09 – Kernel Freeze (~7 weeks away)


Status: CVE’s

The current CVE status can be reviewed at the following link:

  • http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html


Status: Stable, Security, and Bugfix Kernel Updates – Utopic/Trusty/Precise/Lucid

Status for the main kernels, until today:

  • Lucid – Verification
  • Precise – Verification
  • Trusty – Verification
  • Utopic – Verification

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://kernel.ubuntu.com/sru/sru-report.html

    Schedule:

    Current cycle had ended. Waiting for next cycle to start on Feb. 08.

    cycle: 06-Feb through 28-Feb
    ====================================================================
    06-Feb Last day for kernel commits for this cycle
    08-Feb – 14-Feb Kernel prep week.
    15-Feb – 28-Feb Bug verification; Regression testing; Release


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Jono Bacon: Video Phone Review and Wider Thoughts

Tue, 02/17/2015 - 10:26

I recorded and posted a video with a detailed review of the bq Aquaris E4.5 Ubuntu phone, complete with wider commentary on the scopes and convergence strategy and the likelihood of success.

See it below:

Can’t see it? See it here.

Ubuntu Server blog: Server team meeting minutes: 2015-2-10

Tue, 02/17/2015 - 08:33
Agenda
  • Review ACTION points from previous meeting
  • V Development
  • Server & Cloud Bugs (caribou)
  • Weekly Updates & Questions for the QA Team (psivaa)
  • Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
  • Ubuntu Server Team Events
  • Open Discussion
  • Announce next meeting date, time and chair
  • Minutes Meeting Actions

    None

    V Development

    Feb 19th is feature freeze and debian import freeze.
    Progress on OpenStack Kilo features seems to be progressing well

    Server & Cloud Bugs

    None

    Ubuntu Server Team Events

    ODS is coming up

    Open Discussion Agree on next meeting date and time

    Next meeting will be on Tuesday, Feb 17th at 16:00 UTC in #ubuntu-meeting. arosales will chair.

    IRC Log https://wiki.ubuntu.com/MeetingLogs/Server/20150210

    Sam Hewitt: Designers Care About The Little Things

    Tue, 02/17/2015 - 08:00

    Well, at least I do.

    As I see it, design is the summation of the refinement of many little parts that together make a finished product.

    What makes really good design is the paying attention to of all them and in that, when done well, you don't see the parts –everything is cohesive and fits together. This may seem pedantic or obsessive to some, but in reality they all add up.

    For my approach to design –which is an iterative one– I like to use sandpaper or woodworking (a skillset I admire) as an analogy.

    There's a reason there exists different grit sandpapers. Say I've constructed a wooden chair, it has rough edges and the wood is all splintery –it's not nice to look at nor to feel. So, like any logical person, you'd want it smoother and therefore you'd sand it. But to be effective you start big, removing the larger imperfections and each successive pass you switch to a finer and finer approach until everything is smooth. Then, and only then you finally add the veneer.

    Now the veneer is the only part people see. They don't see the rough chair it used to be, they don't see the splinters or the cracks. They see the finished product.

    This is a problem in the design world. Some people's perception of design is that it is just veneer. They don't see the work behind it, nor the imperfections that needed being worked out –to them they didn't exist. Therein lies a paradox. We as designers all strive for as little imperfection as possible, but it remains the case that for most design that this lack of flaws looks easy.

    What's my point here? It's that you too should care about design and if you do care, good. And if you don't and your perception is (or was) that design is just veneer or making things look nice than you should change your perception and open yourself up to the world of design.

    Also, I thought I'd make use of the microphone I was gifted in December and record this little exposition of mine so you may listen to me say my thoughts above instead of just read them.

    Matt Bruzek: Deploy multiple services with Juju Quickstart

    Tue, 02/17/2015 - 07:26

    Juju Quickstart is a plugin that makes setting up an environment in Juju even easier than it already is! The plugin is useful for new users and the experienced developers because it can perform multiple steps so you don't have to type so many commands. Let me tell you about Quickstart and all the cool features!

    Break it down Configuration

    Juju Quickstart can help a new user configure Juju after an initial install. It is a command line tool with an ncurses interface that makes it easier to configure than opening the configuration file in an editor. The interface shows which options are required and lets you get started with the least amount of typing.

    Bootstrap

    After helping you configure an environment Quickstart will conveniently bootstrap that environment for you saving you an extra step. The bootstrap process starts a machine in your cloud environment so that Juju can orchestrate the deployments.

    Graphical User Interface

    By default Quickstart will deploy the Juju Graphical User Interface (GUI) to the same machine as the bootstrap node. If you deployed the juju-gui normally it would be be put on a new machine, but Quickstart uses the --to 0 trick that saves you an instance. In a cloud environment where you pay for each machine this saves you money!

    Bundles

    One of the most powerful features of Quickstart is that it can deploy a bundle.

    Bundles are a collection of Juju charms that can be deployed in a single step. Bundles are simply text files that contain charms, their relations, and configuration in a simple YAML format that is easy for humans to read and write.

    You can explore all the options of Quickstart by typing juju quickstart -h in a terminal. I am going to focus in on the bundle argument. There are several different bundle formats that Quickstart will understand. Meaning there are many different ways to deploy bundles!

    Recommended bundles

    Recommended bundles are sometimes called promulgated bundles. These are bundles that have gone through a review process by Canonical and are stored in launchpad.net. These bundles are available at a special short uniform resource identifier (URI).

    juju quickstart bundle:mediawiki/single Userspace bundles

    Every launchpad account has a personal namespace for charms and bundles. These personal namespace bundles can be deployed by anyone, the URI is just slightly different. To deploy existing a namespace bundle. The URI is bundle:~LAUNCHPAD-USERNAME/BUNDLE-DIRECTORY/BUNDLE-NAME where LAUNCHPAD-USERNAME is a launchpad username, BUNDLE-DIRECTORY is the directory where the bundle is located in launchpad, and BUNDLE-NAME is the name of the bundle in the YAML file.

    juju quickstart bundle:~mbruzek/cakephp/cakephp-bundle

    To create a bundle of your own, save the bundle in a specific directory structure in launchpad account. Push your bundle code to a directory structure like this: ~LAUCHPAD-USERNAME/charms/bundles/BUNDLE-DIRECTORY/bundle where LAUNCHPAD-USERNAME is your user name on launchpad.net and BUNDLE-DIRECTORY is the directory of your bundle. In the example above the cakephp bundle is stored in ~mbruzek/charms/bundles/cakephp/bundle

    jujucharms bundle URL

    The place to find charms and bundles is jujucharms.com. You can deploy bundles directly from jujucharms.com URLs.

    juju quickstart https://jujucharms.com/bundle/mediawiki/scalable/” Any HTTP or HTTPS URL

    You can deploy a bundle directly from a hosted web site giving Quickstart a full URL to the bundle. This means you can deploy from github or your own company website!

    juju quickstart https://raw.githubusercontent.com/mbruzek/docker-bundle/master/bundles.yaml A local path

    The Quickstart plugin will deploy from a local path to a YAML or JSON file that contains a valid bundle structure. This is very useful for developers.

    A local path to a directory

    If Quickstart is given a local directory it will look for a file named "bundles.yaml” and attempt to deploy that file.

    Conclusion

    I know this was a lot of information but it shows how powerful the Quickstart command is. The Quickstart command has many ways to deploy bundles providing all sorts of benefits to the Juju user. If you are the visual type, you can watch a 5 minute Quickstart video.

    If you have any problems using Quickstart, check the bug reports or file a new one so we can improve the experience.

    Ubuntu GNOME: The Final Testing Round for 14.04.2

    Tue, 02/17/2015 - 05:04

    Update: Trusty point release (14.04.2) RC ISOs available

    Hi,

    As you may know, the release of 14.04.2 has been delayed 2 weeks. It was supposed to be released on the 5th of February, 2015 but the release day has been changed to be on the 19th of February, 2015.

    As per Ubuntu ISO Tracker, there are many test cases are not yet covered/tested:Thus, we ask you to kindly help us to make sure Ubuntu GNOME 14.04.2 is solid as rock by covering/testing the other test cases which you can find on the ISO Tracker.

    Please, make sure to use the ISO Tracker:
    http://iso.qa.ubuntu.com/qatracker/milestones/332/builds

    If you are NEW to all the testing process, that’s not a problem at all. This page:
    https://wiki.ubuntu.com/UbuntuGNOME/Testing
    Should help you to get started

    Kindly start testing as soon as you can and contact us for any kind of questions, feedback, questions, etc:
    https://wiki.ubuntu.com/UbuntuGNOME/ContactUs

    Also, we would like to thank our great supporter and tester, Lance for the reminder he sent to the mailing list.

    We are forever thankful for your continuous help and endless support. Together, we become better and all of us are smarter than anyone of us

    Happy Testing!

    The Fridge: Ubuntu Membership Board call for nominations

    Tue, 02/17/2015 - 03:35

    As you may know, Ubuntu Membership is a recognition of significant and sustained contribution to Ubuntu and the Ubuntu community. To this end, the Community Council recruits members of our current membership community for the valuable role of reviewing and evaluating the contributions of potential members to bring them on board or assist with having them achieve this goal.

    We have seven members of our boards expiring from their 2 year terms within the next couple months, which means we need to do some restaffing of this Membership Board.

    We’re looking for Ubuntu Members who can participate either in the 12:00 UTC meetings or 22:00 UTC (if you can make both, even better).

    Both the 12:00 UTC and the 22:00 UTC meetings happen once a month, specific day may be discussed by the board upon addition of new members.

    We have the following requirements for nominees:

    • be an Ubuntu member (preferably for some time)
    • be confident that you can evaluate contributions to various parts of our community
    • be committed to attending the membership meetings
    • broad insight into the Ubuntu community at large is a plus

    Additionally, those sitting on membership boards are current Ubuntu Members with a proven track record of activity in the community. They have shown themselves over time to be able to work well with others and display the positive aspects of the Ubuntu Code of Conduct. They should be people who can discern character and evaluate contribution quality without emotion while engaging in an interview/discussion that communicates interest, a welcoming atmosphere, and which is marked by humanity, gentleness, and kindness. Even when they must deny applications, they should do so in such a way that applicants walk away with a sense of hopefulness and a desire to return with a more complete application rather than feeling discouraged or hurt.

    To nominate yourself or somebody else (please confirm they wish to accept the nomination and state you have done so), please send a mail to the membership boards mailing list (ubuntu-membership-boards at lists.ubuntu.com). You will want to include some information about the nominee, a launchpad profile link and which time slot (12:00 or 22:00) the nominee will be able to participate in.

    We will be accepting nominations through Monday March 9th at 12:00 UTC. At that time all nominations will be forwarded to the Community Council who will make the final decision and announcement.

    Thanks in advance to you and to the dedication everybody has put into their roles as board members.

    Originally posted to the ubuntu-community-team mailing list on Tue Feb 17 10:29:01 UTC 2015 by Elizabeth K. Joseph, on behalf of the Ubuntu Community Council

    The Fridge: Interview with Laura Czajkowski of the Ubuntu Community Council

    Tue, 02/17/2015 - 02:52

    The Ubuntu Community Council is the primary community (i.e., non-technical) governance body for the Ubuntu project. In this series of 7 interviews, we go behind the scenes with the community members who were elected in 2013 serve on this council with Mark Shuttleworth.

    In this, our third interview, we talk with Laura Czajkowski about her work from the Ubuntu LoCo in Ireland to her current role at Couchbase.

    Tell us a little about yourself

    A little about me, I hail from Castleconnell, Co. Limerick Ireland and moved to England 4 years ago and now live in Guildford with my 6 hens and a pug called Bash. I am passionate about open source and communities and will happily talk about these subjects over a beverage or two for hours! By day I’m the Developer Community Manager at Couchbase, where I work with the developer advocate team talking about Couchbase Mobile and Server.

    What was your first computing experience?

    I was given an Amiga 500 as a kid and played games for a chunk of time till I went to secondary school/high School and did Computer Programming in Basic for a year.

    How long have you been involved with Ubuntu?

    I got involved in Ubuntu around ‘06/07 sometime

    What are some of the projects you’ve worked on in Ubuntu over the years?

    I started off being involved in my loco and on IRC and from there just jumped straight in and onto various projects. Ubuntu Ireland Ubuntu UK,Membership board, LoCo Council Ubuntu Leadership (development of leadership), Ubuntu Bug Control, Ubuntu Bugsquad, Ubuntu Accomplishments, NGO project and Ubuntu Women

    There is so much choice out there hopefully you can find something that excites you to get involved.

    What is your focus in Ubuntu today?

    I’m on the Community Council, helping and supporting people where I can. I’m logged on permanently on IRC in various locations czajkowski on freenode if you ever want to talk or bounce ideas about Ubuntu and the community and I’m involved in the loco communities.

    Do you contribute to other free/open source projects? Which ones?

    Couchbase

    If you were to give a newcomer some advice about getting involved with Ubuntu, what would it be?

    We’re a welcoming community, and open to people who have varying experience levels and expertise. Try different things out and find out what works best for you. In Ubuntu there are many ways to contribute to be involved and have fun. Some of my closest friends are those I met from being involved in Ubuntu.

    Always have fun. Always ask for help, and know it’s ok to ask for help. Always know it’s ok to take a break and come back. Always welcome!

    Do you have any other comments else you wish to share with the community?

    Nothing is perfect and everything can always be worked and improved upon. Ubuntu is no different, it’s not perfect but you do have a voice and a community you can talk to on IRC, Forums, Mailing Lists.

    Have fun using Ubuntu and share your experience with others where ever you can.

    New to this series? Check out our previous two Community Council interviews:

    Kubuntu Wire: Netrunner 15 ‘Prometheus’ is here — the best KDE-based Linux distro gets better

    Tue, 02/17/2015 - 02:45

    Beta News reviews Kubuntu derivative Netrunner.  This release of Netrunner comes the Kubuntu packages for Plasma 5 making this a sort of preview for Kubuntu 15.04 and the review continues the trend of good words for the new KDE desktop.  Netrunner likes to make plenty of customisations compared to Kubuntu’s very default KDE setup and the reviewer is impressed.

    I urge you to give this a go. You will be shocked at the beauty and polish; clearly the the Netrunner team cares about its releases

     

    Matthew Helmke: Discontinue Presidents’ Day and replace it with a paid holiday for Election Day

    Mon, 02/16/2015 - 16:44

    Here in the United States, Presidents’ Day was created by combining Lincoln’s Birthday and Washington’s Birthday. However, it is vague, and frankly, not every president has accomplishments that are worthy of celebration.

    Many people in the USA work and find it hard to get to the polls on Election Day. The Federal Government should set an example by creating a paid holiday to encourage and make it easier for everyone to vote.

    Eliminating the first holiday and replacing it with the second enables this action to have no fiscal consequences.

    Anyway, that is my idea. If you are in the USA and want to support the idea, I created a White House petition at http://wh.gov/ibwg0. If you are an American citizen and you think this is a worthwhile idea, please sign and share.

    Fabián Rodríguez: On se voit ce soir au (3L)-Logiciel libre en liberté groupe pour débutant, rencontre de Février

    Mon, 02/16/2015 - 15:09

    Pour plus de détails, consultez l’Agenda du Libre.

    On y présentera un atelier: Les applications de base dans le monde du libre, (ex: suite bureautique, navigateur etc…), La gestion d’une distribution Gnu/Linux, sécurité et mots de passe et autres. Il y aura aussi en seconde partie, des échanges et discussions et résolutions de problèmes (entraide direct ) si il y lieu.

     

    Costales: An unexpected feature, the Ubuntu Phone is the hacking machine! Releasing the beast!

    Mon, 02/16/2015 - 11:42
    I didn't read posts about one of the most amazing feature in Ubuntu Phone...

    sudo apt-get install apache2?   > : )The limit is our imagination!


    Shane Fagan: Getting over the tipping point with gaming

    Mon, 02/16/2015 - 08:17

    I haven't blogged in a long long time about Ubuntu but I'm still around and I'm seriously happy about where gaming specifically has come on the platform. We currently have more games on the platform than the Xbox One and the PS4 but still people complain about their games not being supported. The thing that I see though right now is a tipping point (yes I mean the gameshow). The issue currently is 2 fold, we have great things on the horizon, we have Mantle and glNext and we have new replacements for X11 all of which are great but the simple fact is there are games out there that aren't there and are keeping people off Linux as a platform. Here is the list of them and notice its very very short:

    1. All Blizzard games but Heroes of the Storm. SC2 and WoW are and always have been 2 of the most played games with WINE. WoW runs fine but SC2 has issues nowadays. Then Diablo3 is less important and Hearthstone well that should be ported anyway because they use Unity for their engine which supports Linux OOTB and their Battlenet client supports Linux with the fact that its completely portable because it runs Qt and all the rest are in house Blizzard bits which are also easily portable.
    2. League of Legends, I don't play the game but its hugely popular and isn't very well supported with WINE either.

    Yep that is the list of games that are the most commonly talked about as blockers for switching and they are also commonly requested ports from Linux users too. For instance me, I have spent 400 ish on Blizzard games over the past 15 years. I'm about as dedicated a fan of their games as anyone. But they don't support Linux which actually makes me hugely conflicted and I'm sure a lot of people would say stop giving them money and for the most part I have stopped because of it.

    So onto the solution which I am suggesting. And this is an idea I threw around for actually a few years but its something only Canonical or RedHat could actually do. It will cost some money. What are the problems for a major developer porting to Linux? Well the main problem is they would be supporting a product without many users with an expectation of great quality and the second problem is profit. Why would anyone risk their money when they aren't completely guaranteed profit? These are multi-billion dollar corporations, they don't get there by charity.

    The solution to that is take at least loss away from the equation. If Canonical or RedHat not to leave anyone out could pay for the development cost of the port to Linux as a loan which Blizzard or Riot would pay back when Linux users spend money on their games. This completely takes out the loss from the table and means they would at least be breaking even on the port, then after the loan is paid back they keep the profit. Linux gamers get their game, some people will come over then from Windows who were at the tipping point and there would be 1 less reason for people to have a Windows dual boot in the first place.

    The idea itself is a completely speculative effort but I can't see why Blizzard or Riot wouldn't take them up on the offer. Its potentially a free revenue stream for them and all it takes is just putting a few developers on the port. The benefit for Canonical or RedHat (it would benefit both really) is 1 just instant potential users, 2 marketing because it would definitely make headlines around the internet and 3 most importantly it will make a lot of users very very happy. Mark invests so much money to grow Canonical and keep growing Linux, this idea would do the same. The amazing thing is we already have the other games which people play a lot which are CSGO, TF2, Dota2.

    The trick is even if it loses money specifically so lets say it costs 500k to port a game like that and they pay back 200k of that, its still worth it, why? Because its taking down a barrier to entry which means you would be gaining some unknown number of users at some point. Its a very weird way to look at the problem but its the correct approach.

    Tags: 

    Victor Tuson Palau: Make a scope for your YouTube channel in 5 minutes

    Mon, 02/16/2015 - 07:00

    Not long back Chris Wayne published a post about a scope creator tool.  Last week, I was visiting bq and we decided with Victor Gonzalez  that we should have a scope for Canal bq. The folks at bq do an excellent job at creating “how to” and “first steps” videos, and they have started publishing some for the bq Aquaris E4.5 Ubuntu Edition.

    Here is a few screenshots of the scope that is now available to download from the store:

    The impressive thing is that it took us about 5 min to get a working version of the scope.  Here is what needed to do:

    • First, we followed Chris’ instructions to install the scope creator tool.
    • Once we had it set up on my laptop, we run:
      scopecreator create youtube com.ubuntu.developer.victorbq.canalbq canalbq
    • Next, we configured the scope. The configuration is done in a json file called manifest.json. This file describes the content of what you will publish later to the store. You need to care about: “title”, “description”, “version” and “mantainer”. The rest are values populated by the tool:
      scopecreator edit config
      {
      "name": "com.ubuntu.developer.victorbq.canalbq",
      "description": "Canal bq",
      "framework": "ubuntu-sdk-14.10",
      "architecture": "armhf",
      "title": "Canal bq",
      "hooks": {
      "canalbq": {
      "scope": "canalbq",
      "apparmor": "scope-security.json"
      }
      },
      "version": "0.3",
      "maintainer": "Victor Gonzalez <anemailfromvictor@bq.com>"
      }
    • The following step was to set up the branding: Easy! Branding is define on an .ini file. “Display name” will be the name listed on the “manage” window once installed, and also will be the title of your scope if you don’t use a “PageHeader.Logo”. the [Appearance] section describes the colours and logos to use when banding a scope.
      scopecreator edit branding
      [ScopeConfig]
      DisplayName=Canal bq
      Description=Youtube custommized channel
      Author=Canonical Ltd.
      Art=images/logo.png
      Icon=images/logo.png
      SearchHint=Buscar
      LocationDataNeeded=true
      [Appearance]
      PageHeader.Background=color:///#000000
      PageHeader.ForegroundColor=#FFFFFF
      PreviewButtonColor=#FFFFFF
      PageHeader.Logo=./images/logo.png
    • The final part is to define the departments (drop down menu) for the scope. This is also a json file and it is unique the youtube scope template. You can either use “playlists” or “channels” (or both) as departments. The id PLjQOV_HHlukyNGBFaSVGFVWrbj3vjtMjd corresponds to a play list from youtube, with url= https://www.youtube.com/playlist?list=PLjQOV_HHlukyNGBFaSVGFVWrbj3vjtMjd
      scopecreator edit channels{
      “maxResults”: “20”,
      “playlists”: [
      {
      “id”: “PLjQOV_HHlukyNGBFaSVGFVWrbj3vjtMjd”,
      “reminder”:”Aquaris E4,5 Ubuntu Edition”
      },
      {
      “id”: “PLjQOV_HHlukzBhuG97XVYsw96F-pd9P2I”,
      “reminder”: “Tecnópolis”
      },
      {
      “id”: “PLC46C98114CA9991F”,
      “reminder”: “aula bq”
      },
      {
      “id”: “PLE7ACC7492AD7D844″,
      “reminder”: “primeros pasos”
      },
      {
      “id”: “PL551D151492F07D63″,
      “reminder”: “accesorios”
      },
      {
      “id”: “PLjQOV_HHlukyIT8Jr3aI1jtoblUTD4mn0″,
      “reminder”: “3d”
      }
      ]
      }

    After this, the only thing left to do is replace the placeholder icon, with the bq logo:
    ~/canalbq/canalbq/images/logo.png
    And build, check and publish the scope:
    scopecreator build

    This last command generates the click file that you need to upload to the store. If you have a device (for example a Nexus4 or an emulator ), it can also install it so you can test it.

    It is super simple to create a scope for a youtube channel! so what are you going to create next?


    Pages