news aggregator

The Fridge: Ubuntu Weekly Newsletter Issue 359

Planet Ubuntu - Mon, 2014-03-17 19:48

Welcome to the Ubuntu Weekly Newsletter. This is issue #359 for the week March 10 – 16, 2014, and the full version is available here.

In this issue we cover:

The issue of The Ubuntu Weekly Newsletter is brought to you by:

  • Elizabeth Krumbach Joseph
  • Paul White
  • Emily Gonyer
  • Jim Connett
  • And many others

If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License

Jorge Castro: Introducing Juju Bundles

Planet Ubuntu - Mon, 2014-03-17 14:46

“Rick, I want you to fire up an empty cloud deployment”, said no boss ever.

The various teams who make up “The Ubuntu Server Team” work on various bits. Some work to make OpenStack easy to deploy, some work on packaging, some work on building images for all the public clouds we support. All this is fine and dandy, but at the end of the day, our users deploy things on top of Ubuntu Server, and these workloads are really what it’s all about.

Over the past two years it’s been increasingly obvious to us that orchestrating workloads is becoming one of the most important things we can help users with. What’s the point of an easy to use OpenStack installer if people can’t plop Hadoop, or Cassandra, or their Rails app right on top easily?

One part of this solution is our work on Juju, which makes orchestration simple; we can just manage deployments at the service level while not caring (too much) about individial instances. Some people wanted and needed things to be even highter level. “Look, I’ve got a pile of machines over here, I need a MongoDB cluster” and you don’t have the time! Or more increasingly, you know how to do all these steps, but need a way to make it portable so everyone else in your organization can benefit from your hard work.

So today we announced Juju Bundles. Technically, they’re very simple, it’s a yaml file that describes charms and their relationships to other charms. It can contain machine constraints, or any of the parameters you’d ship in a charm. That means deploying large swaths of services are now one command.

juju quickstart bundle:~charmers/mongodb/cluster juju quickstart bundle:~charmers/hadoop/cluster juju quickstart bundle:~charmers/mediawiki/scalable

There’s a 13 node 3 shard MongoDB cluster, a 7 node starter Hadoop cluster, and a 5 node Mediwiki. All of them can be horizontally scaled out of the box. juju add-unit -n10 hadoop-slavecluster and go to town. Not Bad!

Getting Started

If you’re on Ubuntu Rick has the info in his blog post, you basically:

sudo add-apt-repository ppa:juju/stable sudo apt-get update sudo apt-get install juju-quickstart

Then run one of the commands I mentioned:

juju quickstart bundle:~charmers/mongodb/cluster

Juju will then walk you through setting up an environment. Pick one. AWS, Microsoft Windows Azure, Joyent, HP Cloud, or your own OpenStack or laptop via LXC, then fill out your creds:

Now get a cup of coffee, or watch the console for the magic, maybe read the README.

Now go put that bad boy to work.

Quickstart is not yet available for OSX or Windows (we’re working on it), but if you want to play with it we’ve made a Vagrant box available for you to play with.

The Future

Over the course of the next few weeks as we ramp up to 14.04 we’ll be doing a few things. We’ll be tightening up the URLs to be easier to remember, so something like juju quickstart bundle:mongodb/cluster. Obviously we’d love to see more bundles from the community being submitted.

Check out the documentation for more, and for a more technical description of how bundles work check out Rick’s blog post. We also made a tutorial video on how to make and share your own bundles.

Mark Shuttleworth: ACPI, firmware and your security

Planet Ubuntu - Mon, 2014-03-17 13:05

ACPI comes from an era when the operating system was proprietary and couldn’t be changed by the hardware manufacturer.

We don’t live in that era any more.

However, we DO live in an era where any firmware code running on your phone, tablet, PC, TV, wifi router, washing machine, server, or the server running the cloud your SAAS app is running on, is a threat vector against you.

If you read the catalogue of spy tools and digital weaponry provided to us by Edward Snowden, you’ll see that firmware on your device is the NSA’s best friend. Your biggest mistake might be to assume that the NSA is the only institution abusing this position of trust – in fact, it’s reasonable to assume that all firmware is a cesspool of insecurity courtesy of incompetence of the worst degree from manufacturers, and competence of the highest degree from a very wide range of such agencies.

In ye olden days, a manufacturer would ship Windows, which could not be changed, and they wanted to innovate on the motherboard, so they used firmware to present a standard interface for things like power management to a platform that could not modified to accommodate their innovation.

Today, that same manufacturer can innovate on the hardware and publish a patch for Linux to express that innovation – and Linux is almost certainly the platform that matters. If Windows enters this market then the Windows driver model can evolve to give manufacturers this same ability to innovate in the Windows world, where proprietary unverifiable blobs are the norm.

Arguing for ACPI on your next-generation device is arguing for a trojan horse of monumental proportions to be installed in your living room and in your data centre. I’ve been to Troy, there is not much left.

We’ve spent a good deal of time working towards a world where you can inspect the code that is running on any device you run. In Ubuntu we work hard to make sure that any issues in that code can be fixed and delivered right away to millions of users. Bruce Schneier wisely calls security a process, not a product. But the processes for finding and fixing problems in firmware are non-existent and not improving.

I would very much like to be part of FIXING the security problem we engineers have created in our rush to ship products in the olden days. I’m totally committed to that.

So from my perspective:

  • Upstream kernel is the place to deliver the software portion of the innovation you’re selling. We have great processes now to deliver that innovation to users, and the same processes help us improve security and efficiency too.
  • Declarative firmware that describes hardware linkages and dependencies but doesn’t include executable code is the best chance we have of real bottom-up security. The Linux device tree is a very good starting point. We have work to do to improve it, and we need to recognise the importance of being able to fix declarations over the life of a product, but we must not introduce blobs in order to short cut that process.

Let’s do this right. Each generation gets its turn to define the platforms it wants to pass on – let’s pass on something we can be proud of.

Our mission in Ubuntu is to give the world’s people a free platform they can trust.  I suspect a lot of the Linux community is motivated by the same goal regardless of their distro. That also means finding ways to ensure that those trustworthy platforms can’t be compromised elsewhere. We can help vendors innovate AND ensure that users have a fighting chance of privacy and security in this brave new world. But we can’t do that if we cling to the tools of the past. Don’t cave in to expediency. Design a better future, it really can be much healthier than the present if we care and act accordingly.

 

Canonical Design Team: Making ubuntu.com responsive: setting the rules

Planet Ubuntu - Mon, 2014-03-17 11:32

This post is part of the series ‘Making ubuntu.com responsive‘.

The front end framework that powers www.ubuntu.com represents the visual evolution of the site over the past few years: designs have become cleaner, lighter and more open. It was designed without responsiveness in mind, but it has proven flexible, robust and great for our needs: user experience designers can quickly create wireframes for new and updated pages based on existing patterns and developers can create new pages that look good with little input from designers.

Web style guide front page.

Even though the framework uses a fixed-width container to wrap the content, the containers within it were built to percentages, which means that if that surrounding container were to be removed, the site would become fluid.

One page of the current site without a wrapping container.

We didn’t want to lose the work that has been put into this style guide. After a long discussion, we agreed that even though we were going to convert the CSS powering the site into mobile-first — so the media queries would be added for larger screen sizes instead of the other way around —, we were going to keep the desktop version as it was initially defined in the style guide.

This is likely a restriction that many other teams share: where there is a will and need to make an existing site responsive, but no budget and/or resources to start from scratch.

We decided that it would be a good idea if our developers, Anthony, Graham, and Karl, could sit in a room for a few days and create a ‘quick and dirty’ prototype of what our current site, using the current styles, would look like in a responsive world.

The main goals of this exercise were:

  1. To see how disastrous, or indeed how well, the style guide would play when a handful of responsive guidelines were applied
  2. To give the developers a better understanding of the effort required and issues involved in converting the existing stylesheets into a mobile-first, responsive format

We created a Google doc, structured in the same way as our style guide, where we laid out some rules that would get the developers started on the prototype.

The document started with the more broad and general rules:

  • Try to create breakpoints that fit our content, instead of just random device-specific sizes
  • Try to keep breakpoints to a minimum, with fluid designs in between each breakpoint

We then laid out some scaffolding (layout and grid) rules:

  • Content that is divided in half or thirds should convert into single column when it becomes too narrow
  • If the content is divided into quarters, there might be a step in the middle (halfs)
  • In rows that include an image to the left or right of the text, the image should move above or below the text, respectively
  • Hero images might need to be looked at individually rather than a single rule for all
  • Experiment reducing padding inside rows and boxes incrementally as the screen size decreases
  • Remove column dividers at smaller screen sizes

We then moved on to forms rules:

  • Our forms are already quite vertical, at this stage, make sure we are using correct HTML5 input types

And tables rules:

And finally JavaScript rules:

  • No forcing of equal-height boxes
  • Make tabbed content into expanding/collapsing accordion widgets

Many of our styles didn’t need changing at this stage and this was all written down in the doc too.

We also knew that, at this point, we couldn’t look into trickier problems such as the navigation, the typographic scale or how our multiple footers would play in a small screen, so we decided to leave this for later.


Navigation and multiple footers were too complex an issue to be solved at this early stage.

Now it was time for the developers, with this doc in hand, to take a first go at making www.ubuntu.com responsive!

Reading list

Canonical Design Team: Making ubuntu.com responsive: intro

Planet Ubuntu - Mon, 2014-03-17 11:19

We’ve known for a while it was time to convert our main site, www.ubuntu.com, into a responsive site, and we’re now nearing the end of the project!

The main www.ubuntu.com site receives millions of visitors every month and it holds information on the variety of Ubuntu products and services, allowing people to download Ubuntu, get in touch with Canonical or find support.

In an ideal scenario, if you were going to convert a non-responsive site into a responsive one, you would start from scratch and do everything right and perfectly from the beginning. But what would be the fun in that?

In reality, starting from scratch on a site the size of ubuntu.com is just not practical or easily achievable. We evolve, grow and iterate the site constantly for releases, upgrades, launches and design updates. It is a living, breathing site, and we can’t really afford to stop, and start again. We realise other teams will also be faced with this reality, so we want to share the journey we have taken and some lessons we learned along the way.

In this series of posts, we’ll document the process we’re following in making that transition. We hope to give others an insight into what’s going on behind the scenes, the obstacles we’re facing, the solutions we’ve tried, the questions we have, and basically the nitty gritty of a real world responsive retrofitting project.

We will be covering:

  • Setting the rules
  • Making the rules a reality
  • Pilot projects
  • Lessons learnt
  • Scoping the work
  • Approach to content
  • Making our grid responsive
  • Adapting our navigation to small screens
  • Dealing with responsive images
  • Updating font sizes and readability
  • Ensuring performance
  • JavaScript considerations
  • Testing on multiple devices

I’ll update the list above with links to new posts as we go along. We’d love to hear your thoughts, questions and solutions you’ve tried in your own projects, and how we can make this series more useful: leave your comments below, and we hope you enjoy the posts!

Kubuntu: Ladies Polo Shirts Now in Kubuntu Merchandise Shop

Planet Ubuntu - Mon, 2014-03-17 11:02
The Kubuntu Merchandise shop which sells a range of classy polo shirts has been restocked. By popular request it now features a range of ladies fit polo shirts.

Riccardo Padovani: One year later…

Planet Ubuntu - Mon, 2014-03-17 08:00

Lot of things has changed in last year in my life: I changed university, city, I started (and finished) my first course on Coursera, I started to contribute to Ubuntu and to write code, and I achieved the Ubuntu Membership and others fantastic things.

But what happened exatly one year ago? Well, I posted this image in Ubuntu community on Google+:

Seems like another era! How much work the community (and Canonical guys) have done!
This was the first time I did something for Ubuntu, a screenshot on G+. Since then I started to contribute to Ubuntu for Phones: few days later I did my first patch (nazi grammar patch :-P) and since July I started to contribute on an ongoing basis.
It has been an exciting year, I did more than 250 commits for more than 10,000 lines of code; not bad, whereas I had never programmed before and I do it in my free time. I want to continue on this way for long time :-)

But take a look on where we are. This is a screenshot on Ubuntu 14.04, on a smaller screen:

Awesome! In only one year so much improvements!

The convergence strategy is fantastic, we’re building the future :-)

So, why don’t you start to contribute to Ubuntu?

Ciao,
R.

This work is licensed under Creative Commons Attribution 3.0 Unported

Raphaël Hertzog: Kickstart the Arabic Translation of the Debian Handbook

Planet Ubuntu - Mon, 2014-03-17 07:31

I just wanted to highlight that Muhammad Saied, a volunteer translator of the Debian Administrator’s Handbook, is currently running a crowdfunding campaign with Mohamed Amine so that they can complete the Arabic translation that they started.

There’s only 6 days left to collect the last $2500… click here to help spread Debian to the Arabic world.

No comment | Liked this article? Click here. | My blog is Flattr-enabled.

Benjamin Mako Hill: Community Data Science Workshops in Seattle

Planet Ubuntu - Sun, 2014-03-16 18:41

Photo from the Boston Python Workshop – a similar workshop run in Boston that has inspired and provided a template for the CDSW.

On three Saturdays in April and May, I will be helping run three day-long project-based workshops at the University of Washington in Seattle. The workshops are for anyone interested in learning how to use programming and data science tools to ask and answer questions about online communities like Wikipedia, Twitter, free  and open source software, and civic media.

The workshops are for people with no previous programming experience and the goal is to bring together researchers as well as participants and leaders in online communities.  The workshops will all be free of charge and open to the public given availability of space.

Our goal is that, after the three workshops, participants will be able to use data to produce numbers, hypothesis tests, tables, and graphical visualizations to answer questions like:

  • Are new contributors to an article in Wikipedia sticking around longer or contributing more than people who joined last year?
  • Who are the most active or influential users of a particular Twitter hashtag?
  • Are people who participated in a Wikipedia outreach event staying involved? How do they compare to people that joined the project outside of the event?

If you are interested in participating, fill out our registration form here. The deadline to register is Wednesday March 26th.  We will let participants know if we have room for them by Saturday March 29th. Space is limited and will depend on how many mentors we can recruit for the sessions.

If you already have experience with Python, please consider helping out at the sessions as a mentor. Being a mentor will involve working with participants and talking them through the challenges they encounter in programming. No special preparation is required.  If you’re interested,  send me an email.

Shane Fagan: Linux games this year that im looking forward to

Planet Ubuntu - Sun, 2014-03-16 14:06

I try to do 1 of these a year so here is my list of things im waiting on.

Last year I said I can't wait for "Counter Strike Global Offensive". I love the game and am watching the finals of IEM right now on Twitch. I was in the beta but since I don't have a Windows partition since last year I couldn't play it or some other really good games that I am waiting on. Any time now Valve :-/ (side note as of this post its on sale so if you like FPS games and have a computer made in the past 2 years id suggest picking it up)

"Wasteland2" is something im definitely looking forward to playing. I played Fallout1 and my turn based story itch is getting to me since its definitely not a popular genre of games any more the space is definitely there for a game like this. Its already on steam in early access but not out on Linux yet but since its written in Unity3d it is only a matter of time before its out but ill wait to buy it myself, it seems like it will be on Linux in a few weeks given it was just released on MacOS. Side note they also have another game in development called torment tides of numenera which sounds like it won't be out till next year but it looks like a good game too.

"Planetary Annihilation", its a super strange thing to be excited for a game that I already have in my library but im still waiting to actually play it more since last time I had the chance was late alpha. I recently got an AMD R9270x and the game sadly doesn't work correctly on my machine. The even more frustrating part is I was using haswell graphics before that and they didn't work with it either. So I really hope their support gets better so I can actually play it some more but if you have Nvidia hardware go right ahead and play yourself if you like RTS games. This has a really fresh take on the genre of RTS.

"Prison architect", wow what a game for something so cheap and such a simple idea. Make a prison and keep the prisoners in there. The game is in early access as well like wasteland and planetary annihilation but is very stable and they are adding new things every month. Its really great to play a game that isn't finished and yet you can sink hours into it and make amazing things, then come back the next month and see whats changed. Go out and get it if you want something to relax and have fun and watch the rioting, fires, escapes and general mayhem that happens. I wouldn't say it would be the greatest game for kids or anything but about 15-50 should get a good laugh from it.

And the last game is "Castle Story", its a pretty simple game kind of along the line of minecraft but its like an RTS mixed with tower defense. I really enjoyed the survival mode a lot and its really cool in general.

Tags: 

Lubuntu Blog: Countdown clock

Planet Ubuntu - Sun, 2014-03-16 13:13
I'd like to thank our friend and collaborator Corbin Davenport for this. Specially when I used to be a pain in the neck, asking for the new clock day after day, and I must say the result is, as always, really amazing (have a look on your right). You can use it on your own website. Just copy and paste this HTML code: <iframe src="http://ubuntuone.com/2mnKK5WN8YIBIS4TCtBBuD" style="width:170px;

Sam Hewitt: Onion Rings

Planet Ubuntu - Sun, 2014-03-16 00:00

I have to get my once-a-month greasy food cravings satiated some way –so I made onion rings a couple days ago.

They're also pretty straightforward to do. One simply dips rings of raw onion into a thin –what could be called pancake– batter, coats that with breadcrumbs and then deep-fries.

    Ingredients
  • 1 large onions (preferrably the "sweet" variety), cut into ~1 cm rings
  • 1-2 cups dry breadcrumbs –just blitz up whatever leftover bread you have around
  • 1 quart deep-frying fat, such as peanut oil, lard, etc.
  • seasoned salt (recipe provided below)
  • Batter Ingredients
  • 1 cup flour
  • 1 teaspoon baking powder
  • 1 teaspoon salt
  • 1 large egg
  • 1.5 cups milk
    Directions
  1. Whisk together the egg and milk, in a bowl.
  2. In a larger bowl, combine the flour, salt and baking powder.
  3. Dredge the raw onion rings in this flour, salt and baking powder mixture, tap away the excess, and set the rings aside.
  4. Add the eggy-milk to the dry ingredients and bring it together into a thin batter –it should drip fairly quickly off a fork. If it's too thin add more flour and if too thick add some more milk.
  5. Arrange the breadcrumbs in a large shallow dish (e.g. a baking sheet).
  6. Dip and lightly coat each onion ring in the batter and then gently toss in the breadcrumbs.
  7. Next, heat your fat/oil in a deep saucepan over medium heat until (if you have a fat thermometer, it's ~325 F/~160 C) or it begins to be visibly moving (I've deep-fried so many times I can tell by looking). Alternatively: use a deep-fryer.
  8. Fry the onion rings in batches until golden brown (~2-3 minutes).
  9. Season with the seasoned salt, if using, and serve hot. Enjoy. :)
Seasoned Salt

For me (and for onion rings) I like to make and use a seasoned salt with the following.

  • 3 tablespoons salt
  • 2 tablespoons chili powder
  • 1 tablespoon celery seed
  • 1 tablespoon paprika
  • 1 tablespoon garlic powder
  • 1 tablespoon onion powder
  • 1 tablespoon ground black pepper
  • 1 tablespoon ground cayenne pepper (optional)

You can vary the spice proportions to your tastes or use entirely different spices altogether. Really, what you decide to flavour salt with is up to you.

Paul Tagliamonte: Pygments 1.6

Planet Ubuntu - Sat, 2014-03-15 23:24

As of Pygments 1.7, there’s support for Hy!

http://pygments.org/docs/lexers/

Please report any bugs you find! This is great!

David Murphy: How GitHub communicates

Planet Ubuntu - Fri, 2014-03-14 21:23

Zach Holman writes about how GitHub communicates:

here’s a look at most of the communication that happened at GitHub on one random recent day: February 4, 2014

The expected methods are all there: chat (Campfire in their case), email, and – of course - GitHub itself.

One thing that piqued my interest was their internal-only social network “Team” which seems very reminiscent of how Automattic use WordPress & P2. Since I learned how Automattic use P2, I’ve been wondering if we could do something similar at Canonical. Perhaps we could use Google+  for this as we already use it for internal HangoutsUbuntu Developer Summit, and to power Ubuntu On-Air. There are ways to limit Google+ communities to members of your Google Apps domain.

(Side note: I hate having two Google+ accounts!)

I really need to finish coalescing my thoughts and put them into their own post…

The other point I noted was that their use of email was both minimal and individual – Team and GitHub itself are their primary ways of disseminating information.

It always interesting to see how others do achieve similar goals to yourself.

The post How GitHub communicates appeared first on David Murphy.

David Murphy: How GitHub communicates

Planet Ubuntu - Fri, 2014-03-14 21:13

Zach Holman writes about how GitHub communicates:

here’s a look at most of the communication that happened at GitHub on one random recent day: February 4, 2014

The expected methods are all there: chat (Campfire in their case), email, and – of course – GitHub itself.

One thing that piqued my interest was their internal-only social network “Team” which seems very reminiscent of how Automattic use WordPress & P2. Since I learned how Automattic use P2, I’ve been wondering if we could do something similar at Canonical. Perhaps we could use Google+  for this as we already use it for internal Hangouts, Ubuntu Developer Summit, and to power Ubuntu On-Air. There are ways to limit Google+ communities to members of your Google Apps domain.

(Side note: I hate having two Google+ accounts!)

I really need to finish coalescing my thoughts and put them into their own post…

The other point I noted was that their use of email was both minimal and individual – Team and GitHub itself are their primary ways of disseminating information.

It always interesting to see how others do achieve similar goals to yourself.

The post How GitHub communicates appeared first on David Murphy.

Nicholas Skaggs: Keeping ubuntu healthy: Core Apps

Planet Ubuntu - Fri, 2014-03-14 01:15
Continuing our discussion of testing within ubuntu, today's post will talk about how you can help the community core apps stay healthy.

As you recall the core apps go through a series of QA before being released to the store. However bugs in the application, or in the platform itself can still be exposed. The end result is that the dashboard contains tests failures for that application. To release a new stable image, we need a green dashboard, and more importantly we need to make sure the applications work properly.

Getting plugged in
So to help out, it's important to first plug into the communication stream. After all, we're building these applications and images as a community! First, join the ubuntu phone group on launchpad and sign up for the phone mailing list. The list is active and discussing all issues pertaining to the ubuntu phone. Most importantly, you will see landing team emails that summarize and coordinate issues with the phone images.

From there you can choose a community core app to help improve from a quality perspective. These applications all have development teams and it's helpful to stay in contact with them. Your merge proposal can serve as an introduction!

Finding something to work on
So what needs fixing? A landing team email might point out a failing test. You might notice a test failure on the dashboard yourself. In addition each application keeps a list of bugs reported against it, including bugs that point out failing tests or testing needs. For example here's the list of all new autopilot tests that need to be written for all of the core apps. Pick an app, browse the buglist, for the app, assign a bug to yourself, and fix it.

For example, here's the list of bugs for music app. As of this writing you can see several tests that need written, as well as a bug for a test improvement.

You can also simply enhance the app's existing testsuite by fixing a flaky test, or improving the test to use best practices, etc. As a bonus for those reading this near it's original publication date, we just had a session @ vUDS covering the core apps and the testing needs we have. Watch the session / browse the pad and pick something to work on.

Fixing things
Look into any failures you find and have a look at the tests. Often the tests can use a little improvement (or maybe an additional test), and you can help out here! Sometimes failures won't happen every run -- this is the sign of a weird bug, or more likely a flaky test.  Fix the test(s), improve them, or add to them. Then commit your work and submit a merge proposal. Follow the guide on the wiki if you need help with doing this.

Remember, you can iteratively run the tests on your device as you work. Read my post on click-buddy for help with this. If you are lacking a device, run the tests on your desktop instead and a reviewer can test against a real device before merging.

Getting Help
For realtime help, check out #ubuntu-quality and #ubuntu-autopilot on freenode. You'll find a group of folks like yourself working on tests, hacking on autopilot and sharing advice. If IRC isn't your thing, feel free to contact us through another method instead. Happy hacking!

Ubuntu LoCo Council: 14.04 DVDs/CDs: Pre-Orders now open for verified LoCo Teams!

Planet Ubuntu - Thu, 2014-03-13 16:54

Hello, everyone!

As you read it, pre-orders for 14.04 DVDs/CDs are now open for verified LoCo Teams. Only the team contacts should request this DVD/CD pack, which will be sent to the address they specify. These packs contain 150 Desktop DVDs and 25 Server CDs. Packs will start shipping when available, which is estimated to be two (2) weeks after release.

In order to put an order, the team contact needs to go here and place their pre-order.

If you have any questions, please write to us at loco-council@lists.ubuntu.com.

Thomas Ward: nginx-core is now in Ubuntu Trusty 14.04 Main!

Planet Ubuntu - Thu, 2014-03-13 15:58

Thanks to the efforts of myself and others, we have been able to get NGINX into the Ubuntu Main repositories for Trusty 14.04!

Having said this, none of the already-established flavors of nginx are included in Ubuntu Main (nginx-light, nginx-full, nginx-extras, and nginx-naxsi). The Ubuntu Security Team has said that the third-party modules are wildly different in coding and therefore cannot be supported.

To that end, we created a package called nginx-core which has been included in the Main repository. This package contains only the modules that ship with the stock nginx tarball. We do not include any third-party modules with this package, just the modules that come from NGINX upstream.

Thanks to everyone on the MIR an Security teams for all their help in getting nginx into Main!

Canonical Design Team: MWC 2014 – A strong design coherence in everything we do

Planet Ubuntu - Thu, 2014-03-13 12:05

Last month at Mobile World Congress Ubuntu’s presence was stronger than ever. Our third year at MWC and we made some significant design changes to our stand.

In such a large exhibition space, strong branding is key. We designed five large banners – made from fabric and stretched across metal frames – that were suspended above the stand. Each banner was then individually illuminated by a series of spotlights creating maximum impact and high level brand presence, while still maintaining the stands open and welcoming feel.

The back walls and a new hanging aisle banner all featured the folded paper background with large graphics showcasing app and scope designs from the phone and tablet. We also dedicated one wall to the Ubuntu Carrier Advisory Group (CAG).

Continuing our clean and precise design approach we used the Ubuntu shape (the squircle) to create bespoke pods, reception desk and demo unit – with warm white LED down lighting around the top and base and lightboxes to illuminate the Circle of Friends on the reception desk.

Integrating elements from our phone and tablet design across print and 3D environments builds a strong brand/design coherence in everything we do. We’re very happy with the new stand design and feedback from MWC has been very positive.

http://news.softpedia.com/news/Ubuntu-s-Booth-at-MWC-2014-Looks-Spectacular-428834.shtml

Canonical Design Team: New Apps header

Planet Ubuntu - Thu, 2014-03-13 12:03

The new apps header features max. 4 slots that can be arranged and combined in order to fulfil user needs in every screen.

Header’s values

We want to provide our users with the right amount of contextual information for them to know:

1- Where they are at (inside the app, in a particular view).

2- Where they can go inside the app in order to find content (navigate across different views).

3- What they can achieve in any given view (compose a message, crop a picture…).

The new header provides clarity by always showing the user where they are at, consistency by providing a way to navigate across main views inside the apps, and priority by surfacing the most important actions in every screen.

Header’s elements

The elements are the building blocks of the header, the controls that can placed inside the slots mentioned above.

There’s different categories of elements and each of them have to be positioned carefully in the header in order to create slick experiences across our apps.

 

Title

One of the main values behind the new header is Clarity: we want the user to be clear about where they are at any moment.

That’s why the only mandatory element for our header is the title; you can leave some other slots empty, but every header has to have a title.

Tabs

A Tab is a control that allow users to navigate across views directly from the header.

The main views of your app are the different faces  in how content is organised and visualised.

Example: 

Our telephone app has two main views: Dialer and Contacts. Placing a tabs on the telephony header, allows users to toggle between this two views quickly.

Tabs placement

Place the tabs right to the title.

According to our interface values “right” means moving forward, and that’s what a tab precisely is, moving forward to the next view represented by the tab icon.

Actions

Actions allow users to accomplish a direct goal in every screen (compose a message , edit, crop a picture…) Give priority to the actions that will be used more often and place them in the header.

Example: Our address book app has a clear primary action which is add a new contact to the list.Placing that action straight to the header will make the user accomplish the goal quicker and smoother.

Actions placement

Place the actions right to the title as well.

In case you want to mix tabs and actions on the same header,  keep the tabs as close to the title as possible, creating a natural block to navigate across the views; place the actions after them.

Back

After the main views of your app, subsequent views will use a back button in the header to navigate back to the main views. Back always returns to the previous view of an app, until the user reaches the main view again.

Example: Our gallery app has 3 main views: Photos, events and albums. Once the user gets to a detail view, the header of that view has a back button that returns the user to them main view where he came from.

Back placement

There’s only one place where you can place the back, and that’s the top left slot. According to our interface values, that’s a place where user has to intentionally stretch the finger and make an effort to trigger.

Drawer

So we’ve already introduced a few elements, but what happens when there’s not enough free slots on the header to place all your tabs and actions? Our solution is the drawer: an overflow where users will find all the controls not available straight on the header.

Example: Our gallery app has 3 main views: Photos, events and albums; and it also has the “take a picture” action on the header. In order to keep the header clear, we’ve decided to place the main views inside a drawer, and surface “take a picture” on the header. In this particular case, the drawer contains the main views of the app.

Inside the drawer

The drawer can contain some of the elements that couldn’t fit in the header’s slots. If  the drawer is placed on the top left slot, then it will contain tabs (main views); if the drawer is placed on the top right slot, then it will contain extra actions.

 

Drawer placement

The drawer works as a metaphorical extension of the header, so placing it at the first or last slot helps reinforce that idea.

 

 

Search

Search is a special action that allows users to rapidly locate a desired piece of content. And since search can be a really important use case in apps, we are providing a special experience for it.Triggering search will refresh the standard header into a search header, displaying the osk at the same time, and removing the focus from the content. (for more information on search read search pattern)

Example: Our notes app presents search as one of the main action in the header. Once the user hits on the search icon the header transitions to the search header.

Search placement

There’s only one place in the header where you can place search: top right slot.

 

 

Implication with the drawer:  In the scenario where you need a back button, a drawer and a search; the search will need to be kept in the top left slot in order to reinforce the search pattern across all our system.

 

Header layout

The four slots on the header can be arranged as follows:

Layout A

1 slot at the left of the title and max. 2 slots on the right

When to use it
  • You need to use a Back button in order to display detail screens for your app content.
  • Your app has a large number of main views and you need the drawer to display all of them.
  • You prefer to use the slots on the right to display actions, then you have to use a drawer to place the main views.
Layout B

max. 3 slots right to the title

 When to use it

  • You don’t need a back button.
  • You want to place tabs at the right for the user to be able to switch views easily.
  • Most of the actions to be performed on the app are contextual (related to the content) and there’s no need to surface those actions on the header.
Behaviour

According to our user interface values, content is always the priority; that’s why the header is just a tool the disappears when users don’t need it. By scrolling down, the header will disappear. By scrolling up  the header will slide in again.

 

It might be scenarios where users will need the header present at all times (i.e. Header with tabs) in that justified case, it’s possible to set the header fixed on the screen.

 

 

 

Pages

Subscribe to Free Software Magazine aggregator