Next in Kubuntu:
Improved on-demand installation and notifications for localization, as well as improved internal handling to increase reliability of things.Click to view slideshow.
There’s been a lot of talk about Ubuntu’s phone and tablet development over the last year, and it’s great that it’s getting so much attention, but people have been getting the name of it all wrong. Now, to be fair, this is a problem entirely of our own making, we started off talking about the phone (and later tablet) developments as “Ubuntu Touch”, and put most of the information about on our wiki under a page named Touch. But there is no Ubuntu Touch! It’s not a separate OS or platform, there is only one OS and it’s simply called Ubuntu.
What people are referring to when they say Touch or Ubuntu Touch, is really just Ubuntu with Unity 8. Other than the shell (and display server that powers it), it’s the same OS as you get on your desktop.
Everything under the hood is the same: same tools, same filesystem, even the same version of them, because it’s all built from the same source. Calendar data is stored in the same place, audio and video is played through the same system, even the Unity APIs are shared between desktop and phone.
So why is the name important? Not only is it more accurate to call them both Ubuntu, it’s also one of the (in my opinion) most exciting things about having an Ubuntu phone. You’re not getting a stripped down embedded Linux OS, or something so customized for phones that it’s useless on your desktop. You’re getting a fully featured, universal operating system, one that can do everything you need from a phone and everything you need from a desktop.
This is the key to Ubuntu’s convergence strategy, something that nobody else has right now. Android makes a terrible desktop OS. So does iOS. Chrome OS won’t work for a phone either, nor OSX. Even Microsoft has built two different platforms for mobile and desktop, even if they’ve slapped the same interface on both.
But with Ubuntu, once Unity 8 comes to the desktop, you will have the same OS, the same platform, on all of your devices. And while you will run the same version of Unity on both, Unity 8 is smart enough to change how it looks and how it works to meet the needs and capabilities of what you’re running it on. Better still, Unity will be able to make these changes at run time, so if you dock your convertible tablet to a keyboard, it will automatically switch from giving you a tablet interface to a desktop interface. All of your running apps keep running, but thanks to the Ubuntu SDK those too will automatically adjust to work as desktop apps.
So while “Ubuntu Touch” may have been a useful distinction in the beginning, it isn’t anymore. Instead, if you need to differentiate between desktop and mobile versions of Ubuntu, you should refer to “Unity 8″ if talking about the interface, or “Ubuntu for phones” (or tablet) if you’re talking about device images or hardware enablement. And if you’re a developer and you are talking about the platform APIs or capabilities, you’re talking about the “Ubuntu SDK”, which is already available on both desktop and mobile installs of Ubuntu.
This last weekend I was in LA at SCALE12x and gave a presentation providing a detailed update of much of the work going on as we build a convergent Ubuntu. As I have mentioned before, there is lots of other foundational pieces being built as part of this work (app insulation, SDK, click packages, developer.ubuntu.com, platform services etc), and this presentation covered where we stand today in this work.
Obviously a lot more of you couldn’t be at SCALE than couldn’t, so I have recorded the presentation to share online. You can see it below or click here to watch it. Enjoy!
Welcome to the Ubuntu Weekly Newsletter. This is issue #356 for the week February 17 – 23, 2014, and the full version is available here.
In this issue we cover:
- Canonical announces first partners to ship Ubuntu phones around the globe
- Welcome New Members and Developers
- Ubuntu Stats
- Xubuntu: Xubuntu Marketing with StartUbuntu Flyer
- Dustin Kirkland: Random Seeds in Ubuntu 14.04 LTS Cloud Instances
- Elizabeth Krumbach Joseph: 5 ways to get involved today: Ubuntu Advocacy & Wrap up
- Kubuntu Wire: One of the reasons Kubuntu rocks
- Mark Shuttleworth: #12 – Ubuntu is the majority of public cloud workloads
- Jono Bacon: Today’s Ubuntu News
- Michael Hall: Winning the 1%
- Stephen M. Webb: Locally Integrated Menus for Ubuntu 14.04 LTS
- Ubuntu GNOME: Artwork Team Weekly Report
- Pasi Lallinaho: Logging in with Ubuntu One
- Ubuntu Classroom: Reminder: Documentation Day in the Classroom is just a week away!
- Other Community News
- Canonical News
- In The Blogosphere
- Other Articles of Interest
- Featured Audio and Video
- Weekly Ubuntu Development Team Meetings
- Upcoming Meetings and Events
- Updates and Security for 10.04, 12.04, 12.10 and 13.10
- And much more!
The issue of The Ubuntu Weekly Newsletter is brought to you by:
- Elizabeth Krumbach Joseph
- Paul White
- Emily Gonyer
- Jim Connett
- And many others
Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License
I spent nearly 7 hours in the same cinema seat this weekend. The BBC and the BFI were celebrating the return of several missing episodes of Doctor Who to the archives by holding a marathon screening at the Prince Charles cinema in Leicester Square. All twelve episodes of “The Enemy of the World” and “The Web of Fear” were shown back-to-back, with only two short comfort breaks. That’s a lot of Doctor Who, even for me.
The panel after the screening was expertly moderated by Toby Hadoke. Deborah Watling and Frazer Hines were joined by Ralph Watson, who played Captain Knight in “The Web of Fear,” the role that was originally going to be played by Nicholas Courtney before he was promoted to play the Brigadier. Ralph was certainly talkative and brought some fresh stories and recollections, particular about his working relationship with Douglas Camfield. Michael Troughton was also on stage to reminisce about his father’s dual roles in “The Enemy of the World” and his visit to the London Underground set with the yetis.
I think the BBC and the BFI were using this event to see if there is sufficient interest in screenings now that the anniversary year celebrations are over. I hope they are convinced, although I would happily settle for a single six episode story rather than two! It was great to geek out with James from the Doctor Who Podcast again.
The Prince Charles cinema, which is slightly smaller than NFT1 at the BFI Southbank, is a great choice of venue for this sort of cult screening. However, the availability of cinema snacks, combined with the duration of the screening, meant there was a lot more rustling going on than at the BFI. But I can live with that if I get to see more Doctor Who on the big screen.
When your service over a period of several days is unavailable (or at least very flacky) for a number of users, it would really be appreciated if you would at least give some kind of acknowledgement of the problem, and a time frame for when you would expect the problem to be fixed.
I enjoy my Ubuntu One file storage, but when a problem is happening for four days, without any information given to the users, I start looking around for alternatives. We all know they are out there…
(Yes, I did file a bug report…)
It is no surprise that big projects like Debian and Fedora are all back again.
On the other hand, I am delighted to announce that the Ganglia project is participating this year. We have started publishing a list of project ideas and we are keen to start having discussion with potential students and anybody who would like to participate in our mentoring team. We have also invited the RRDtool community to be part of this big adventure because RRDtool is such a critical element of Ganglia's success.
I've also published a couple of project ideas on the Debian wiki before the organisations were confirmed:
- Recursively building Java dependencies from source (automatically)
- WebRTC portal for the Debian community
As I am part of the admin team for Ganglia, these Debian projects can only go ahead if there are some additional mentors willing to participate in them. Please contact me if either of these projects is interesting for you. You don't have to be a Debian Developer to be a mentor for Debian. Given the highly generic nature of these projects, particularly the Java one, they could also be mentored under the umbrella of another organisation. The Java project is particularly suitable for any Linux distribution or project relying on many JARs and all distributions and Java users are likely to extract some benefit from it.Deadlines approaching
GSoC works on a strict calendar, please see the dates here if you would like to participate as a mentor, co-mentor or student.
From Wednesday through Sunday, I was in Los Angeles for the Southern California Linux Expo (Scale12x) held at the Hilton LAX. This was my first Scale12x and this was the second year that Mozilla had official presence.
To be honest, I’m not totally sure what I was expecting when going to Scale12x. I thought it was going to be a typical regional linux expo but Scale12x was a larger event then I could have imagined.
Thursday, I spent a lot of time meeting with Firefox Users and people from other open source projects. In the evening, I joined Brandon Burton (Mozilla), Chris Turra (Mozilla), Jordan Sissel (Elasticsearch) and Michael Stahnke (PuppetLabs) for a DevOps Dinner.
On Friday, I took the opportunity to visit a number of talks including Brandon Burton’s lightning talk during the DevOps track. I met up with Casey Becking, a fellow Mozilla Rep, and we hung out, visited some talks, and checked out the expo floor in advance of setup.
That evening myself, Casey Becking and Joanna Mazgaj went out for a Mozilla Group Dinner. We went to a place called Akbar in Marina Del Rey. The dinner was excellent and it was great to get together and spend time with fellow reps before the expo floor opened.
Saturday and Sunday were the days of the expo hall and I woke up about 6:00am and headed down to setup our booth early. By 9:00am we were starting to see the first attendees trickle in. I would estimate in the first few hours we saw close to five hundred attendees and by end of day closer to a thousand.
At one point, a group of students stopped by from L.A.’s Roosevelt High School and I gave them a short overview of Mozilla OpenBadges and discussed how their school could use the platform to recognize students for various achievements. The faculty the accompanied the students said they were very interested in the program.
There was a tremendous amount of interest surrounding Firefox OS I would say 90% or better of attendees that visited the booth demoed Firefox OS or asked questions. Many asked us when they could buy a device in North America.
To my knowledge we were only asked about Directory Tiles on two occasions. Both of those conversations were positive once we explained it some and pointed out Mitchell’s blog post.
Sunday was a bit slower since most attendees has visited the booth although some people who arrived last day for the expo did stop by and some attendees visited us again. All in all, the event was very positive and a lot of buzz was generated in addition to getting information out there about how to contribute to Firefox OS, where a device can be purchased, and the progress of the project.
sudo apt-get install transmission-daemon
sudo nano /etc/init.d/transmission-daemon # Change USER=your_login_user
sudo nano /etc/default/transmission-daemon # Set CONFIG_DIR="/home/username/.config/transmission-daemon"
transmission-daemon -f # Ctrl+C
sudo cp /etc/transmission-daemon/settings.json ~/.config/transmission-daemon/settings.json
sudo chown your_user:your_user ~/.config/transmission-daemon/settings.json
Here, I'll set my parameters:
sudo update-rc.d transmission-daemon defaults
Packages for the release of KDE SC 4.12.2 are available for Kubuntu 12.04LTS, 13.10 and our development release. You can get them from the Kubuntu Backports PPA. It includes an update of kde-workspace to 4.11.6.
For much of the past year I’ve been working on the Ubuntu API Website, a Django project for hosting all of the API documentation for the Ubuntu SDK, covering a variety of languages, toolkits and libraries. It’s been a lot of work for just one person, to make it really awesome I’m going to need help from you guys and gals in the community.
To help smooth the onramp to getting started, here is a breakdown of the different components in the site and how they all fit together. You should grab a copy of the branch from Launchpad so you can follow along by running: bzr branch lp:ubuntu-api-websiteDjango
First off, let’s talk about the framework. The API website uses Django, a very popular Python webapp framework that’s also used by other community-run Ubuntu websites, such as Summit and the LoCo Team Portal, which makes it a good fit. A Django project consists of one or more Django “apps”, which I will cover below. Each app consists of “models”, which use the Django ORM (Object-Relational Mapping) to handle all of the database interactions for us, so we can stick to just Python and not worry about SQL. Apps also have “views”, which are classes or functions that are called when a URL is requested. Finally, Django provides a default templating engine that views can use to produce HTML.
If you’re not familiar with Django already, you should take the online Tutorial. It only takes about an hour to go through it all, and by the end you’ll have learned all of the fundamental things about building a Django site.Branch Root
When you first get the branch you’ll see one folder and a handful of files. The folder, developer_network, is the Django project root, inside there is all of the source code for the website. Most of your time is going to be spent in there.
Also in the branch root you’ll find some files that are used for managing the project itself. Most important of these is the README file, which gives step by step instructions for getting it running on your machine. You will want to follow these instructions before you start changing code. Among the instructions is using the requirements.txt file, also in the branch root, to setup a virtualenv environment. Virtualenv lets you create a Python runtime specifically for this project, without it conflicting with your system-wide Python installation.
The other files you can ignore for now, they’re used for packaging and deploying the site, you won’t need them during development../developer_network/
As I mentioned above, this folder is the Django project root. It has sub-folders for each of the Django apps used by this project. I will go into more detail on each of these apps below.
This folder also contains three important files for Django: manage.py, urls.py and settings.py
settings.py contains all of the Django configuration for the project. There’s too much to go into detail on here, and you’ll rarely need to touch it anyway.
urls.py is the file that maps URLs to an application’s views, it’s basically a list of regular-expressions that try to match the requested URL, and a python function or class to call for that match. If you took the Django project tutorial I recommended above, you should have a pretty good understanding of what it does. If you ever add a new view, you’ll need to add a corresponding line to this file in order for Django to know about it. If you want to know what view handles a given URL, you can just look it up here../developer_network/ubuntu_website/
If you followed the README in the branch root, the first thing it has you do is grab another bzr branch and put it in ./developer_network/ubuntu_website. This is a Django app that does nothing more than provide a base template for all of your project’s pages. It’s generic enough to be used by other Django-powered websites, so it’s kept in a separate branch that each one can pull from. It’s rare that you’ll need to make changes in here, but if you do just remember that you need to push you changes branch to the ubuntu-community-webthemes project on Launchpad../developer_network/rest_framework/
This is a 3rd party Django app that provides the RESTful JSON API for the site. You should not make changes to this app, since that would put us out of sync with the upstream code, and would make it difficult to pull in updates from them in the future. All of the code specific to the Ubuntu API Website’s services are in the developer_network/service/ app../developer_network/search/
This app isn’t being used yet, but it is intended for giving better search functionality to the site. There are some models here already, but nothing that is being used. So if searching is your thing, this is the app you’ll want to work in../developer_network/related/
This is another app that isn’t being used yet, but is intended to allow users to link additional content to the API documentation. This is one of the major goals of the site, and a relatively easy area to get started contributing. There are already models defined for code snippets, Images and links. Snippets and Links should be relatively straightforward to implement. Images will be a little harder, because the site runs on multiple instances in the cloud, and each instance will need access to the image, so we can’t just use the Django default of saving them to local files. This is the best place for you to make an impact on the site../developer_network/common/
The common app provides views for logging in and out of the app, as well as views for handling 404 and 500 errors when the arise. It also provides some base models the site’s page hierarchy. This starts with a Topic at the top, which would be qml or html5 in our site, followed by a Version which lets us host different sets of docs for the different supported releases of Ubuntu. Finally each set of docs is placed within a Section, such as Graphical Interface or Platform Service to help the user browse them based on use../developer_network/apidocs/
This app provides models that correspond directly to pieces of documentation that are being imported. Documentation can be imported either as an Element that represents a specific part of the API, such as a class or function, or as a Page that represents long-form text on how to use the Elements themselves. Each one of these may also have a given Namespace attached to it, if the imported language supports it, to further categorize them../developer_network/web/
Finally we get into the app that is actually generates the pages. This app has no models, but uses the ones defined in the common and apidocs apps. This app defines all of the views and templates used by the website’s pages, so no matter what you are working on there’s a good chance you’ll need to make changes in here too. The templates defined here use the ones in ubuntu_website as a base, and then add site and page specific markup for each.Getting Started
If you’re still reading this far down, congratulations! You have all the information you need to dive in and start turning a boring but functional website into a dynamic, collaborative information hub for Ubuntu app developers. But you don’t need to go it alone, I’m on IRC all the time, so come find me (mhall119) in #ubuntu-website or #ubuntu-app-devel on Freenode and let me know where you want to start. If you don’t do IRC, leave a comment below and I’ll respond to it. And of course you can find the project, file bugs (or pick bugs to fix) and get the code all from the Launchpad project.
- #ubuntu-meeting: ubuntu-server-team, 18 Feb at 16:03 — 16:38 UTC
- Full logs and further details at https://wiki.ubuntu.com/MeetingLogs/Server/20140218
- Review ACTION points from previous meeting
- T Development
- Server & Cloud Bugs (caribou)
- Weekly Updates & Questions for the QA Team (psivaa)
- Weekly Updates & Questions for the Kernel Team (smb, sforshee)
- Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
- Ubuntu Server Team Events
- Open Discussion
- Announce next meeting date, time and chair
This weeks meeting had a focus on addressing items needed before Feature Freeze on Feb 20. This included conversations around high/essential bugs, red high/essential blueprints, and test failures.
Specific bugs discussed in this weeks meeting were:
- 1248283 in juju-core (Ubuntu Trusty) “juju userdata should not restart networking” [High,Triaged] https://launchpad.net/bugs/1248283
- 1278897 in dovecot (Ubuntu Trusty) “dovecot warns about moved ssl certs on upgrade” [High,Triaged] https://launchpad.net/bugs/1278897
- 1259166 in horizon (Ubuntu Trusty) “Fix lintian error” [High,Triaged]
- 1273877 in neutron (Ubuntu Trusty) “neutron-plugin-nicira should be renamed to neutron-plugin-vmware” [High,Triaged]
Specific Blueprints discussed:
- curtain, openstack charms, ceph, mysql alt, cloud-init, openstack (general)
Meeting closed with announcing Marco and Jorge will be at SCALE12x giving a talk, so be sure to stop by if your are going to be at SCALE.Review ACTION points from previous meeting
The discussion about “Review ACTION points from previous meeting” started at 16:04.
16:06 <arosales> gaughen follow up with jamespage on bug 1243076 16:06 <ubottu> bug 1243076 in mod-auth-mysql (Ubuntu Trusty) “libapache2-mod-auth-mysql is missing in 13.10 amd64″ [High,Won't fix] https://launchpad.net/bugs/1243076 16:09 <jamespage> not got to that yet 16:10 <jamespage> working on a few pre-freeze items first 16:10 <arosales> ack I’ll take its appropriately on your radar –thanks 16:10 <jamespage> it is
16:06 <arosales> gaughen follow up on dbus task for bug 1248283 16:06 <ubottu> bug 1248283 in juju-core (Ubuntu Trusty) “juju userdata should not restart networking” [High,Triaged] https://launchpad.net/bugs/1248283
16:07 <arosales> jamespage to follow up on bug 1278897 (policy compliant) 16:07 <ubottu> bug 1278897 in dovecot (Ubuntu Trusty) “dovecot warns about moved ssl certs on upgrade” [High,Triaged] https://launchpad.net/bugs/1278897
16:07 <arosales> smoser update servercloud-1311-curtin bp 16:07 <smoser> i updated it . 16:07 <smoser> i’ll file a ffe today
16:07 <arosales> hallyn follow up on 1248283 from an lxc pov, ping serue to coordinate 16:08 <serue> Done 16:08 <arosales> smoser update cloud-init BP 16:08 <smoser> we’ll say same there.Trusty Development
The discussion about “Trusty Development” started at 16:10.
- Release Bugs (16:11)
- LINK: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#server
- LINK: https://bugs.launchpad.net/maas/+bug/1248283
- LINK: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1259166
- LINK: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1273877
- LINK: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1278897
- ACTION: follow upon bug 1273877
- Blueprints (16:22)
- LINK: http://status.ubuntu.com/ubuntu-t/group/topic-t-servercloud-overview.html
- ACTION: gaughen ensure BPs are updated
The discussion about “Weekly Updates & Questions for the QA Team (psivaa)” started at 16:27.
- LINK: https://code.launchpad.net/~psivaa/ubuntu-test-cases/mod_php-fix/+merge/204273 needs merging
The discussion about “Ubuntu Server Team Events” started at 16:35.
- gaughen ensure BPs are updated
- follow upon bug 1273877
Next meeting will be on Tuesday, February 25th at 16:00 UTC in #ubuntu-meeting.People present (lines said)
- arosales (77)
- jamespage (19)
- psivaa (12)
- smoser (10)
- ubottu (9)
- meetingology (5)
- serue (2)
- zul (2)
- sforshee (1)
- rbasak (1)
- gaughen (1)
- smb (1)
I’ve spent a bit of time this saturday Dockerizing Debile’s slave / workers (for those who don’t know about Debile yet, there are a few posts where I explain it)
Many thanks to Tianon Gravi for his work in helping me out :)
This includes a script to preconfigure the slave worker (OpenPGP keys, username, password) that are passed to it via a tarball generated by debile-remote.
Hopefully this makes deploying debile slaves easier :)
I was able to do a test build of about 300 packages with the dockerized slave, and I think it’s a huge step forward.
I’m glad to announce that Ubuntu GNOME Wiki & Documentation Team has finished all the assigned tasks for Trusty Tahr Cycle and starting from today until the final release of Ubuntu GNOME Trusty Tahr, The Wiki & Documentation Team will go through all the pages and try to polish and improve any page that needs any kind of improvement, if any.
Wiki & Documentation Team Roadmap for Trusty Tahr Cycle:
Wiki & Docs Roadmap for Trusty : Implemented successfully.
Ubuntu GNOME HOWTOs : Implemented successfully.
Accessibility Wiki Page : Implemented successfully.
Installing Ubuntu GNOME Wiki Page : Implemented successfully.
Terminal Tutorial : Deferred.
Very Important Wiki pages to be updated always – Please Note this is not a cycle specific blueprint, hence it is NOT part of any roadmap : Informational.
I’d like to thank Ivan and James for everything – their excellent work, great support and high quality contributions. Thank you so much and keep the great work up!
I have enjoyed working with you. That was a great experience. It might be hard to believe the only 3 of us have done all that in a very short period (considering we do have a real-life) but since we have put our trust in each other and our faith in :
“All of Us Are Smarter Than Anyone of Us.”
What seemed hard to achieve, was an easy mission and fun. That is the power of collaboration.
If you have any feedback, suggestions, notes, etc … please feel free to Contact Us!
Interested to help?
If you have the passion for Wiki and Documentation and/or you like Ubuntu GNOME and would like to do something in return for all the happy moments with this system, you’re more than welcome to join us:
See Also: Getting Involved with Ubuntu GNOME.
As always, thank you for reading this report
Founder and Leader of Ubuntu GNOME Wiki & Docs Team
This is considered as ‘the wrap up report of Ubuntu GNOME Wiki & Docs Team for Trusty Tahr Cycle’ and most likely, we have no more reports to share unless there is something new.
Interested in getting involved with Ubuntu Documentation, but not sure were to begin? On Sunday, March 2nd, the Ubuntu Classroom team is hosting a day of Documentation-related chat (IRC) sessions to get new contributors ready to participate.
Schedule as follows (all times UTC, click on time for link to time conversions):
- 16:00: Introduction to Docs docs by Elizabeth Krumbach Joseph (pleia2)
- 17:00: Getting started contributing to Desktop docs by Kevin Godby (godbyk)
- 18:00: Getting started contributing to Server docs by Doug Smythies (dsmythies)
- 19:00: Getting started contributing to the Wiki docs by Svetlana Belkin (belkinsa)
- 20:00: Getting started contributing to Manual by Kevin Godby (godbyk)
- 21:00: Ubuntu Manual versions explained by Thomas Corwin (tacorwin) and Patrick Dickey (patrickdickey)
Sessions all take place on Internet Relay Chat (IRC). If you want to participate, you just need to join #ubuntu-classroom and #ubuntu-classroom-chat on irc.freenode.net in your IRC client, or just click here for browser-based webchat. The instructor will give the class in #ubuntu-classroom and attendees can chat about the class and ask questions in #ubuntu-classroom-chat.
If you’re unable to attend, logs of each session will be made available following the event.
We hope to see you on Sunday, March 2nd!
Since many new contributors have asked about logging in to various Ubuntu-related sites and services and there hasn’t been a thorough explanation on what and how, I thought it would be useful to post an article explaining some of the stuff happening in the background.
Note: I am only writing of my own experience and knowledge. I haven’t read the source code, or received a technical explanation from anybody who has written, or been involved with setting up the services mentioned, nor do I work for Canonical. Ultimately, your mileage may vary.Definitions
Ubuntu One (formerly Ubuntu Single Sign On, or Ubuntu SSO) is the centralized login service that allows you to login to various services. These services include some cloud services, music streaming, mobile app store and more. However, a Ubuntu One account is also needed to access the developer tools and sites like Launchpad, the Ubuntu wikis, Ubuntu Forums, AskUbuntu and more.
Launchpad is the place where a lot of the contributor community cooperation happens. It is used to file bugs, write blueprints, create PPA’s, manage translations and much more.Sources of information
The Ubuntu One account will only have limited information of you; to be exact, your name and your email address. You will need to input these when you register for a Ubuntu One account. Whether you have contributed to Ubuntu or not, it’s not unlikely to have one.
The Launchpad account requires further information than the information available from Ubuntu One; namely, a username. This is created automatically from your email address, and you can change it later from your Launchpad page, from “Change details”, considering you don’t have any PPA’s enabled.
You can use your existing Ubuntu One account details when logging in to Launchpad. If you or create a new Launchpad account, you will be automatically created a Ubuntu One account that’s linked to your Launchpad account.Sharing information
All information from your Launchpad, or any other service, is available for your Ubuntu One account (including your username and team memberships). When you log in to other sites and services with Ubuntu One, you can either decide to share or not share this information. The other sites and services will then determine what kind of access they will give you. This is what causes the most confusion and frustration of new contributors.
For example, the Ubuntu team wiki requires you to share a username to be able to attribute each edit correctly. Even if you are able to log in to the team wiki without a Launchpad account, or without sharing the username information, you will be unable to edit pages in this case.
Another example is the Ubuntu Developer Summit Etherpad, which requires a user to be a member of a specific Launchpad group team granting them access. If you have contributed more to the project, it’s likely you are a member of that team indirectly via some of your other teams. New contributors who aren’t members in many Launchpad teams yet are less likely to even know about this fact. That said, if you are looking for that information, you will need to join the ~ubuntu-etherpad team; it is moderated so you won’t be automatically approved, but anybody applying for that group will be approved without further questions once the moderators do their usual routines.Setting up accounts
If you have a Ubuntu One account, log in to Launchpad with your Ubuntu One credentials. This will create you a Launchpad username and associate it with your Ubuntu One account. You can change your Launchpad username by changing the “name” field in the Change details page. This will be your username for all Ubuntu One -related sites and services.
If you don’t have a Ubuntu One account, the easiest way to create one and associate a Launchpad account with it is to Create a new Launchpad account. This will automatically create a Ubuntu One account and guide you through creating the Launchpad account. If you want to change the automatically selected username, go to the Change details page.
After you have a Ubuntu One account that has an associated Launchpad account, you are able to log in to other sites and services successfully.Conclusion
If you contribute to Ubuntu and need to access various services, you will need a Ubuntu One account that has an associated Launchpad account. The associated Launchpad account provides your Ubuntu One account additional information like username or team memberships, which are needed to log in to and work on various sites and services.
On Friday, February 21st I gave my talk on 5 ways to get involved with Ubuntu today at the Southern California Linux Expo’s Ubucon.
I had a great audience who I was able to have some wonderful and inspiring chats with following my talk. There’s clearly a lot of interest in further involvement by user-level contributors, so I’m happy that the work I’ve been doing to improve on-boarding for projects I participate in will be valuable.
I’ve uploaded slides from the talk here: 5WaysToGetInvolvedWithUbuntuToday.pdf
You can also browse the companion blog posts I’ve been writing these past couple weeks leading up to the conference:
I really enjoyed the experience, huge thanks to Richard Gaskin for delivering another great Ubucon.
Finally, the Ubuntu booth put on by members of Ubuntu California has really been doing well this weekend, so thanks and congratulations to everyone who has been participating.
I'm not an avid Kickstarter follower (if I were, I'd have gone broke long ago). I tend to wind up backing campaigns that come to my attention via other means (in other words, they're in the process of going viral). That said, I've backed plenty of campaigns over the years, and so I'd like to think I have a little bit of familiarity with how they usually operate.
When Ozobot came to my attention, I found it unusual, because they were pre-promoting their Kickstarter campaign before it opened. To me, this looked like a case of them trying to build hype prior to the campaign opening, which was a new one to me. The whole thing seemed incredibly slick, and I was surprised they were "only" seeking $100K.
The product looked like it'd be something cool for Zoe to play with, so I decided to back it anyway. Then all the updates started flowing in about how well it was being received at various trade shows and whatnot. Yet the amount of dollars flowing into the Kickstarter campaign didn't seem to be reflecting the external hype. I was watching the campaign's dashboard with great interest, because as time marched on, it was looking more and more likely that it wasn't going to make its funding target. This seemed highly unusual to me, given the slickness of the product and purported external interest in it.
And then they pulled the plug on the campaign. Purportedly because they were pursuing equity funding instead. They admitted they'd also read the writing on the wall and it was unlikely they were going to make their funding target. I haven't followed other campaigns to see how much of a last minute funding "pop" they have. Usually I've found they've closed at many multiples of their original target, and hit their target well in advance of their deadline, when they're ridiculously popular. My interpretation of Ozobot's campaign, from a funding perspective, is that Kickstarters gave it a big fat "MEH", which surprised me somewhat.
Then the question comes up: was the Kickstarter campaign a ruse all along? Was it just a new way of pitching for venture capital? The videos seemed pretty slick. The product seemed already complete, and $100K didn't seem like enough to take it to manufacturing.
It'll be interesting to see what becomes of Ozobot now.
Part of our new plan to publish more news about Ubuntu GNOME Team and/or Sub-Teams reports; this week, we would like to share with all of you our weekly report for Ubuntu GNOME Artwork Team.
Just a reminder, Ubuntu GNOME Marketing and Communications Team usually publish monthly reports. And, last week, Ubuntu GNOME Wiki and Documentation Team has published a weekly report for one of the most recent achievements or work done.
Ubuntu GNOME Artwork Team’s Weekly Report
Alfredo Hernández, Artwork Team Leader has shared his team’s report for the last week:
Current Tasks (not yet done):
1. Select wallpaper contest winners. The process will be explained when everything is ready.
2. Review ubiquity slides. Now that we are approaching Beta 1 we are ready to move on and rethink the features we are promoting and how they are described.
3. StartUbuntu: we only need a nice description of Ubuntu GNOME to finish the flyers.
“It may seem lots of work but we’ll make it without problem if we organise well.
Now a general comment on this cycle work:
We’ve made mistakes in our work flow and our external communications, but I’m sure we’ll be a lot more organised for 14.10.”
Thanks to Alfredo and his team for all the work done and we highly appreciate his honesty and for being open. This is the quality we always talked about. Be honest, direct and open and share everything about the project whether it is good or not. The mistakes that Alfredo has mentioned will be avoided with the next cycle because we have addressed these issues and we have learned from that.
Thank you for reading!