Good libraries come with good documentation. It is therefore essential for KDE Frameworks to provide comprehensive online and offline documentation.
- kgenapidox: Generate documentation for a single framework
- kgenframeworksapidox: Generate documentations for all frameworks as well as the landing page which lets you list and filter frameworks by supported platforms
- depdiagram-prepare and depdiagram-generate: Generate dependency diagrams (requires CMake and Graphviz)
In this post I am going to talk about kgenapidox, which is the tool you are most likely to run by yourself. While it is often good enough to read documentation online through api.kde.org, it is also useful to be able to generate documentation offline, for example because your Internet access is slow or you are currently offline, or because you want to improve the existing documentation. kgenapidox is the tool you want to use for this.Installing
The first thing to do is to install KApidox. The code is hosted in a Git repository on KDE infrastructure. Get it with:git clone git://anongit.kde.org/kapidox
KApidox tools are written in Python. In addition to Doxygen, you need to have the pyyaml and Jinja2 Python modules installed. If your distribution does not provide packages for those modules, you can install them with:pip install --user pyyaml jinja2
KApidox itself can be installed the standard Python way using python setup.py install. You can also run KApidox tools directly from the source directory.Generating Documentation
You are now ready to generate documentation. Go into any checkout of a framework repository and run kgenapidox:$ kgenapidox 19:08:48 INFO Running Doxygen 19:08:49 INFO Postprocessing 19:08:50 INFO Done 19:08:50 INFO Doxygen warnings are listed in apidocs/doxygen-warnings.log 19:08:50 INFO API documentation has been generated in apidocs/html/index.html
As you can see from the command output, the documentation is generated by default in the apidocs/html directory. You can now open the documentation with your preferred browser. kgenapidox can also tell Doxygen to generate man pages or Qt compressed help files. Run kgenapidox --help for more details.Improving the Documentation
If you maintain a framework, contribute to the KDE Frameworks project or want to get involved, open the warning file generated in apidocs/doxygen-warnings.log and start fixing! Improving the documentation of a framework can make it much more useful, so it is a very welcome contribution.
Vim tip: The warnings file can be loaded in the quickfix list with :cfile apidocs/doxygen-warnings.log.
Wow. Just wow.
Last week I went to a Canonical Sprint, in Malta. The track was about the Client, and we focus on how make the Ubuntu for Phones even better.
We discussed also about some new features and some new designs we will introduce in next weeks. Stay tuned! During the week I fixed many bugs, and wrote a lot of code.
But I think the Sprint isn’t (only) about codes and features. IMO it’s much more about networking. You know, we work mainly via IRC and mailing lists, and for how wonderful can be an online friendship, it will be never as drink some beers together!
So, first of all thanks to Canonical for the invite, and for the awesome adventure I’m living in this last year.
But mainly thanks to all the guys I met. This week allows me to understand that people I working with are not only cool as developers, but also awesome as people!
We were 6 of community that joined the sprint: other than me, there were Nik, my roommate, who is making clock app rocking; Victor and Andrew, which develope the music app, Kunal, our wizard of calendar, and Adnane, who works on the HTML5 SDK. It’s an honour to code side by side with these guys.
Then, there was the Canonical Community Team: Alan and David are my mentors, my point of contact in Canonical, it was a pleasure to meet them and to have a beer (or 2, maybe 3…) together! Michael is the man who keeps update developer.ubuntu.com (and he does a lot of other things) and when I report a bug I know that in five minutes will be fixed. Nicholas is a cool guy, but he wants I use autopilot. No one is perfect. There was also Daniel. I worked with him only for few patches in december, so I had no possibility before this week to speak with him. And know what? He’s so funny! Last but not least, Jono: we had some time to talk, and I’m very happy about this: thanks for all your work in Canonical, and good luck for your future!
But all other Canonical employers were very gentle, and I met some guys which I want to see soon, and now I know who ping on IRC to have a bug in the SDK fixed ;-)
Also, other guys I used to know only on IRC (boiko, elopio, mardy, zsombi and others) now have a face! And new guys, from Design and QA and online account teams!!!
Was a wonderful week, and I have no words to say how much I’m happy, and to say thanks to all!
So, thanks for all guys, hope to see you all soon, and continue to make Ubuntu rocking!
This work is licensed under Creative Commons Attribution 3.0 Unported
I managed to spend a few hours doing Debian stuff again today, which was great.
Today I learned about blhc, which is sadly not mentioned in the wiki page on hardening, which I always refer to. It turns out that it is mentioned in the walkthrough wiki page linked off it though. I'd not read that page until today. Many thanks to Samuel Bronson on IRC for pointing out the tool to me.
Initially I didn't think the tool told me anything I didn't already know, but then I realised it was saying that the upstream Makefile wasn't passing in $(CPPFLAGS) and $(LDFLAGS) when it invoked the compiler. Know that I know all of that, the build warning also mentioned in the PTS made a whole lot more sense. Definitely a case of "today I learned..."
So I made a simple patch to the upstream Makefile.in and simpleproxy is now all appropriately hardened. I'm very happy about that, as it was annoying me that it wasn't Lintian-clean.
I was able to use the same technique to similarly fix up sma. It's somewhat entertaining when you maintain a package for almost 7 years, and the upstream homepage changes from being the software author's website to what appears to be erotic fiction advertising for London escorts... That made for some entertaining reading this morning.
I've now managed to give all my packages a spring clean. I might do another pass and convert them all to debhelper 9 as a way of procrastinating before I touch isc-dhcp.
I’ve been playing with qemu-user-static a bit to create a set of porterboxes for my Deb-o-Matic build farm. After reading gregoa’s post on how to create cross-chroot with qemu-debootstrap, I was immediately able to create armel, armhf and powerpc boxes with very little efforts.
I tried to extend the number of porterboxes available by adding mips* and s390x, in order to have all the Linux-based architectures supported in Jessie, but with no luck. Here’s a summary of my attempts.
Chroot creation fails under both mips and mipsel trying to configure libuuid1. The problem is due to the fact libuuid1′s postinst script calls groupadd and useradd. Those two utilities rely on NETLINK sockets, which apparently are not handled by QEMU at the moment. I raised the question upstream to see whether it is possible to solve this problem.
Chroot creation used to fail with a SIGSEGV. This particular bug has been fixed recently, but it seems it’s not enough to have a working chroot. It fails with some gzip errors, probably because some portions of dpkg-deb are not fully covered by qemu-s390x-static.
Preparing to unpack .../base-files_7.3_s390x.deb ...
Unpacking base-files (7.3) ...
dpkg-deb (subprocess): decompressing archive member: internal gzip read error: '<fd:5>: incorrect data check'
/bin/tar: Unexpected EOF in archive
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
dpkg-deb: error: subprocess tar returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives/base-passwd_3.5.33_s390x.deb (--install):
subprocess dpkg-deb --control returned error exit status 2
INSTALAR JAVA 7 (REQUISITO PREVIO)
Para saber si lo tenemos instalado, abrimos una Terminal y ejecutamos: "java -version":
costales@dev:~$ java -version
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) Client VM (build 24.55-b03, mixed mode)
Si no tenemos instalado JAVA podemos hacerlo ejecutando esto en la misma Terminal:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
INSTALAR PROGRAMA PADRE
Ya con JAVA instalado, descargamos el programa PADRE desde la página oficial o más cómodo desde la Terminal que ya tenemos abierta:
Ahora convertimos ese fichero en ejecutable:
chmod +x Renta2013_unix_1_21.sh
Y lo ejecutamos:
Ya sólo nos queda seguir el asistente y en la 3ª ventana marcar: No crear enlaces simbólicos.
Paso 3: Marcar No crear enlaces simbólicos
El programa PADRE ejecutándose en Xubuntu 14.04 Trusty
The Ubuntu Women team has decided that Harvest will be re-started and the project is now at Phase 2, code-named Seeking Out Developers.
The Harvest system aggregates information about low-hanging fruit and aims to visualise which packages of the Ubuntu distribution are in a good and which are in a bad shape.
Harvest is a Django-based web application written in Python, code is available here: https://code.launchpad.net/harvest
Over the next few weeks we’ll be working to get instructions up for developers to stand up test environments and getting our roadmap defined for the project based on recent feedback and other outstanding bug reports.
What we need now is you! Python developers who are interested in helping us improve Harvest. Please contact Svetlana Belkin at email@example.com if you’re interested in helping out.
Today, the Ubuntu Scientists team had their first meeting. As I said, this team is fairly new and we finally were able to have a meeting. I was the chair and two others, Aleo and balachmar, were there. Even though it was just three people, I would say that we got a lot of work done. When I started the team, I had no idea on what to have on the team wiki pages but after the meeting along with the help from the others, I know what to write/place.
As a three person team, we have planed for:
- Monthly Meetings on the same day of the month but the time might be different, and also rotating times/days were looked at
- We might do a vUDS 14.06 track
- We are working on the first and last goals, since they are the easiest
- We have an idea on what pages we should add on our team pages
The main goal for the next meeting is to the get some of the wiki team pages planned and written out. And to get some contacts from outside organizations that deal with science in the FOSS world.
I’ve just finished the last day of a week long sprint for Ubuntu application development. There were many people here, designers, SDK developers, QA folks and, which excited me the most, several of the Core Apps developers from our community!
I haven’t been in attendance at many conferences over the past couple of years, and without an in-person UDS I haven’t had a chance to meetup and hangout with anybody outside of my own local community. So this was a very nice treat for me personally to spend the week with such awesome and inspiring contributors.
It wasn’t a vacation though, sprints are lots of work, more work than UDS. All of us were jumping back and forth between high information density discussions on how to implement things, and then diving into some long heads-down work to get as much implemented as we could. It was intense, and now we’re all quite tired, but we all worked together well.
I was particularly pleased to see the community guys jumping right in and thriving in what could have very easily been an overwhelming event. Not only did they all accomplish a lot of work, fix a lot of bugs, and implement some new features, but they also gave invaluable feedback to the developers of the toolkit and tools. They never cease to amaze me with their talent and commitment.
It was a little bitter-sweet though, as this was also the last sprint with Jono at the head of the community team. As most of you know, Jono is leaving Canonical to join the XPrize foundation. It is an exciting opportunity to be sure, but his experience and his insights will be sorely missed by the rest of us. More importantly though he is a friend to so many of us, and while we are sad to see him leave, we wish him all the best and can’t wait to hear about the things he will be doing in the future.
This post is part of the series ‘Making ubuntu.com responsive‘.
If you’re transitioning a fixed-width website into a responsive one with several time and resource constraints, updating all your content to be mobile-friendly will likely not be an option.
It’s important to understand what your constraints are and work within them. This is what makes a good designer great — you could even say it’s the definition of our jobs.
This was certainly our case: very early in the process of converting ubuntu.com into a responsive site we knew we wouldn’t be able to edit the existing content. We did, however, follow a few ‘content rules’, and this is something you can define within your projects too.Evergreen content
We created the Ubuntu Insights site to hold dated content like case studies, news and white papers, and to keep a constant influx of fresh content into ubuntu.com and other Ubuntu sites. Not only did creating Ubuntu Insights allow us to keep ubuntu.com fresh, it gave us a place to move a lot of the detailed content that previously existed on the main site to. We end up with fewer pages and also with shorter pages, which is one of the challenges of converting a site to be responsive with no content updates: the pages become too long.
The latest iteration of Ubuntu Insights.
We’ve been working on this project for a few months now, and will be releasing its final update soon, which will include a dedicated press area.No content or information architecture updates
Once you go back to work you’ve completed some time ago, it’s natural that you start seeing lots of things, big and small, you want to improve. However, when the scope of a project is really tight (and which project isn’t?), it’s important not to fall into temptation.
Updating the structure and content of the website in preparation for making it responsive was not an option for us, as that would involve a fair number of people and time that were not at our disposal.
We decided to flag anything we’d want to look at again in the future, but moving things around was out of the question.
A couple of sections of the site were going to suffer some changes that might impact content and information architecture, but those had been flagged at earlier stages, and we knew to only start reviewing and working on those later on in the responsive project.No hidden content
A decision we made early on was that we weren’t going to hide any content from small screens.
We could still use common patterns like accordions and tabs to show content in a more digestible format, but all content should be available in small screens, just as it would in larger screens.
Accordions chunk the content nicely at smaller screen sizes.Future plans
Improving the content on ubuntu.com will be a gradual process. As new pieces of content are added and updated, we’re now making sure that content is optimised for a smaller screen experience, being mindful of endless scrolling and keeping the message clear and focused on each page and section of the site.
Looking at mobile first has already pushed us towards simplifying our content. We’re trying to think about shorter, more carefully written text that relies less on images and animations. This includes paring down on charts, cutting out text that really is there to support images, and considering the reason for existence of any new fourth-level pages.
In the future, we’ll likely want to do a content revamp of the entire site, but that’s a huge project on its own and probably one that deserves its own series of posts.
We’d love to hear about your experiences and tips on improving content for a responsive iteration of your sites: add your thoughts in the comments section!Reading list
- Uncle Sam Wants You (to Optimize Your Content for Mobile)
- Karen McGrane’s “content strategy” posts
- The Discipline of Content Strategy
- COPE: Create Once, Publish Everywhere
- Content Modularity: More Than Just Data Normalization
- Content Portability: Building an API is not Enough
- Don’t Just COPE. Call The COPS On Your Content.
- Sports Refresh: Dynamic Semantic Publishing
- Content Parity
We’re back with Season Seven, Episode Six of the Ubuntu Podcast! Alan Pope, Mark Johnson, Tony Whitmore, and Laura Cowen are drinking tea and eating birthday cake (like this one) from Laura’s Mum in Studio L.Download OGG Download MP3 Play in Popup
In this week’s show:
- We interview Graham Morrison from Linux Voice.
- We also discuss:
- We share some Command Line Lurve: betty
A command line Siri. Kinda.
- And we read your feedback
We’ll be back next week, so please send your comments and suggestions to: firstname.lastname@example.org
Join us on IRC in #uupc on Freenode
Leave a voicemail via phone: +44 (0) 203 298 1600, sip: email@example.com and skype: ubuntuukpodcast
Follow us on Twitter
Find our Facebook Fan Page
Follow us on Google+
On the behalf of Stephen Michael Kellat (skellat), the Ubuntu Ohio Team has an update to share:
Due to Stephen Michael Kellat’s job and the stress that it produces, he has given the three deputies (under the Delegation of Authority) admin status of the team. Any issues that arise should be e-mailed to the three deputies, not Stephen Michael Kellat.
We’re fast approaching the summer, and the first few sunny days have already arrived in London. The web team cannot slow its pace though…
In the last few weeks we’ve worked on:
- Responsive ubuntu.com: we’ve had a sprint to clean up our processes and CSS files after the big responsive release last month
- Ubuntu.com: we’ve updated our Jumpstart service to include the exciting new Orange Box Micro-cluster and Your cloud product pages in preparation for the OpenStack Developer Summit
- Juju GUI: we’ve finished creating new personas
- Ubuntu OpenStack Interoperability Lab: we’ve completed the report design
- Ubuntu OpenStack Installer: the installer was presented at the OpenStack Developer Summit last week, and we’ve done iterations on the designs based on recent user research
- Fenchurch: we’ve moved Fenchurch into a proper Django project, nearly completed the first phase of a new asset server with a new Juju charm, and set up a new Fenchurch instance for the new legal website
- Ubuntu Insights: we’ve made the move from Ubuntu Resources to Ubuntu Insights, and launched the desktop version of the site
- Las Vegas sprint: we worked on updated, mobile-first bundle and charm details pages and started planning for the next cycle
- Partners: we’ve completed the final UX and copy for this new Ubuntu website
And we’re currently working on:
- Responsive ubuntu.com: we’re now in the process of updating our web style guide documents before the public release of the new styles
- Ubuntu Insights: we’re adding the final touches before launching the press centre in the next few weeks
- Juju GUI: we’re planning the work for the next cycle
- Fenchurch: we’re working on getting the Juju charms in production for the new legal site, finishing up the asset server and planning the development of our new partners website
- Partners: we’re currently building the new partners website
- Legal pages: we’re now in the process of building the new hub that will hold all our legal information
- Chinese website: we’ve finalised UX and copy for this upcoming Ubuntu site
If you’d like to join the web team, we are currently looking for experienced user experience and web designers to join the team!
The design team getting ready to move desks, at the end of April.
Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.
This past week I’ve had the opportunity to join two separate Linux Users Groups (LUGs) to give presentations on the Ubuntu 14.04.
The talks were a full talk version of the mini talk I gave at the release party in San Francisco last month, covering:
- Unity Desktop
I’m a member of the Xubuntu team and use it primarily myself, which is why that flavor got special treatment ;)
The first talk was on Saturday for FeltonLUG down near Santa Cruz. Since I had a series of laptops already installed and set up from when we did the release party , I packed them up and brought them along with me.
We had a small group, so the meeting was a bit more on the informal side and folks had a lot of great questions and comments throughout the presentation. Given the group size it was also possible to have everyone give my Nexus 7 with Ubuntu on it a try, which folks had a lot of questions about.
Thanks to Bob Lewis and Larry Cafiero for being such great hosts, at their scenic drive recommendation my husband and I had a wonderful trip up route 1 along the coast on our way home.
Last night I joined BALUG here in San Francisco. I brought along my trusty tahr and pile of demo laptops for this presentation as well.
In addition to the great questions about the direction of Ubuntu in general (desktops! servers! clouds! tablets! phones!) I was really happy to have server folks in my audience for this talk who were eager to hear about the changes to virtualization technologies and such on the server side. I even was able to have a chat with a sysadmin who is doing a lot of virtualization and told me that her team is looking at deploying OpenStack in the near future.
Slides from both presentations are available online, the BALUG one includes some screenshots from Xubuntu since I was using a Unity-based laptop to present there:
The .odp versions of these slides are also available, just swap out .pdf for .odp in each url.
Kudos to all the speakers, panellists, designers and engineers who made ODS Atlanta such a great event last week. And thanks in particular to the team at Canonical that helped pull together our keynote, I had a very large number of compliments that really belong to all of you!
For those that didn’t make it, here are a few highlights.
First, Ubuntu is the leading OpenStack distribution, with 55% of all production are using Ubuntu, nearly 5x the number for RHEL. There is a big squabble at the moment between vendors in the RHEL camp; for the record, Canonical is happy to work with vendors of alternative OpenStack distributions on Ubuntu as long as we have a commercial agreement that enables us to support users. Nonetheless, the standard way to do OpenStack starts with Ubuntu followed by the addition of Canonical’s cloud archive, installing OpenStack using those packages.
Second, vendors are focused on interoperability through Canonical’s OpenStack Interop Lab (OIL). We build OpenStack thousands of ways every month with permutations and combinations of code from many vendors. Bring us a Juju charm of your work, sign up to the OIL program and we’ll tell you which other vendors you need to do more work with if you want to be interoperable with their OpenStack offerings.
Third, Juju and MAAS are growing support for Windows and CentOS, with other operating systems on the horizon too (patches welcome!). Thanks to contributions from CloudBase Solutions, you’ll get amazing orchestration of Windows and Linux apps on any cloud or bare metal. If you have a Windows app that you want charmed up, they are the guys to talk to! We did a live on-stage install of OpenStack with Ubuntu KVM and Windows Hyper-V with the beta code, and expect it to land in production Juju / MAAS in the coming weeks.
I’m particularly excited about a new product we’ve announced, which is a flat-fee fully managed on-premise OpenStack solution. Using our architecture and tools, and your hardware, we can give you a best-of-breed OpenStack deployment with SLA for a fixed fee of $15 per server per day. Pretty amazing, and if you are considering OpenStack, definitely an option to evaluate. Give us a call!
Nothing new to report this week
Release Metrics and Incoming Bugs
Release metrics and incoming bug data can be reviewed at the following link:
Milestone Targeted Work Items
Here’s our todo list until we formulate a better plan for tracking work
next week at our team sprint:
Status: Utopic Development Kernel
We have uploaded our first v3.15 based kernel, 3.15.0-1.5, to the Utopic
archive. It is currently based on the v3.15-rc5 upstream kernel.
Important upcoming dates:
Mon-Wed June 9 – 11, vUDS (~3 weeks away)
Thurs Jun 26 – Alpha 1 (~5 weeks away)
Fri Jun 27 – Kernel Freeze for 12.04.5 and 14.04.1 (~5 weeks away)
- NOTE: The PrecisePangolin/ReleaseSchedule notes Kernel Freeze as Aug 9. I believe this should be amended to Jun 27.
The current CVE status can be reviewed at the following link:
Status: Stable, Security, and Bugfix Kernel Updates – Trusty/Saucy/Precise/Lucid
Status for the main kernels, until today (May. 20):
- Lucid – Prep week
- Precise – Prep week
- Quantal – Prep week
- Saucy – Prep week
Trusty – Prep week
Current opened tracking bugs details:
For SRUs, SRU report is a good source of information:
cycle: 18-May through 07-Jun
16-May Last day for kernel commits for this cycle
18-May – 24-May Kernel prep week.
25-May – 31-May Bug verification & Regression testing.
01-Jun – 07-Jun Regression testing & Release to -updates.
Open Discussion or Questions? Raise your hand to be recognized
No open discussion.
Hey we're heading towards summer, it's time to make ice cream. Okay, you may not be as adventurous as that –sorbet is less work & equally enjoyable.
Now, you may not have an ice cream machine (and neither do I) but a food processor or blender is a way to cheat that.
You can use these methods with almost any fruit (or combinations of fruit), I just happened to have & use fresh strawberries.
- 1 pound / 0.5 kg fresh strawberries, leafy parts removed
- 1/2 a lemon, juice of
- 150 mL simple syrup or 250 mL strawberry preserves
- pinch of salt
Makes about 1 litre
- In a food processor blend the strawberries, preserves, lemon juice & salt until smooth.
- Transfer to a shallow dish, cover & freeze until completely solid, depending on your freezer: 3-4+ hours.
- Break up the frozen sorbet and return to the food processor. Blend until light and smooth.
- Return to dish, cover and place back in freezer to set.
- If it is too hard before serving, let thaw for 15 minutes or so in your fridge.
As the number of Juju users has been rapidly increasing over the past year, so has the number of new solutions in the form of charms and bundles. To help users assess and choose solutions we felt it would be useful to improve the visual presentation of charm and bundle details on manage.jujucharms.com.
While we were in Las Vegas, we took advantage of the opportunity to work with the Juju developers and solutions team to find out how they find and use existing charms and bundles in their own deployments. Together we evaluated the existing browsing experience in the Juju GUI and went through JSON-files line by line to understand what information we hold on charms.
We used post-its to capture every piece of information that the database holds about a bundle or charm that is submitted to charmworld.
We created small screen wireframes first to really focus on the most important content and how it could potentially be displayed in a linear way. After showing the wireframes to a couple more people we used our guidelines to create mobile designs that we can scale out to tablet and desktop.
With the grouped and prioritised information in mind we created the first draft of the wireframes.
In order to verify and test our designs, we made them modular. Over time it will be easy to move content around if we want to test if another priority works better for a certain solution. The mobile-first approach is a great tool for making sense of complex information and forced us to prioritise the content around user’s needs.
First version designs.
Ganglia has been granted funding for five students in the 2014 Google Summer of Code
The names of the students chosen for the program were announced on 21 April and the official coding period has started this week.
The students are:Project Student Data science Plamen Dimitrov NVIDIA GPU monitoring Md Ali Ahsan Rana Ganglia/Nagios integration Chandrika Parimoo JMXetric Ng Zhi An Internal Ganglia metrics Oliver Hamm
and the mentoring team consists of Rajat Phull, Bernard Li, Nick Satterly, Robert Kovacs and Daniel Pocock.
The whole Ganglia community congratulates the students on their selection for GSoC this year and is very excited about working with them. We would also like to thank O'Reilly for generously providing the GSoC students with copies of the book Monitoring with Ganglia
If any other member of the community would like to assist formally or informally in the mentoring program, testing any of the projects or anything else please just get in touch with us through the Ganglia developers mailing list or #ganglia on freenode
Welcome to the Ubuntu Weekly Newsletter. This is issue #368 for the week May 12 – 18, 2014, and the full version is available here.
In this issue we cover:
- The Orange Box
- Ubuntu 12.10 (Quantal Quetzal) End of Life reached on May 16 2014
- Ubuntu Stats
- Trusty DVD parcels
- Vagrant boxes with Juju now available
- Ronnie Tucker: Ubuntu AIO DVD Has All Ubuntu 14.04 LTS Flavors on One Disk
- Jono Bacon: Announcing Ubuntu Pioneers
- Jonathan Riddell: Next Generation Edges Closer
- Ubuntu App Developer Blog: Announcing Ubuntu Dual Boot with enhanced upgrades and more!
- Valorie Zimmerman: Today’s catch-up meeting with the Ubuntu Community Council
- Kubuntu Wire: Univention Corporate Client 2.0 – First milestone released
- Svetlana Belkin: Stuck With Ubuntu Touch!
- Canonical News
- Canonical offers ‘Chuck Norris Grade’ OpenStack private cloud service
- PC Pro Ubuntu 14.04 review
- HP targets China’s post-XP crowd with Ubuntu Kylin
- In The Blogosphere
- Other Articles of Interest
- Featured Audio and Video
- Weekly Ubuntu Development Team Meetings
- Monthly Team Reports: April 2014
- Upcoming Meetings and Events
- Updates and Security for 10.04, 12.04, 13.10 and 14.04
- And much more!
The issue of The Ubuntu Weekly Newsletter is brought to you by:
- Elizabeth Krumbach Joseph
- Paul White
- Emily Gonyer
- Penelope Stowe
- 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