- 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)
- Ubuntu Server Team Events
- Open Discussion
- Announce next meeting date, time and chair
- ACTION: meeting chair (of this meeting, not the next one) to carry out post-meeting procedure (minutes, etc) documented athttps://wiki.ubuntu.com/ServerTeam/KnowledgeBase
Pretty straightforward meeting given 14.04 release is still pretty fresh in our minds, and ODS was last week. Great Demo at UDS! Utopic Unicorn is underway way (https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule) the first Alpha release scheduled for June 26th, and vUDS on June 12th. Server team blueprints are also in progress with the topic blueprint (https://blueprints.launchpad.net/ubuntu/+spec/topic-u-server_ already created and dependencies being posted to it.
The Bugs we covered were:
- Launchpad bug 1319555 in ec2-api-tools (Ubuntu Utopic) “update out-dated ec2-api-tools for 12.04″ [High,New]
- Launchpad bug 1315052 in lxc (Ubuntu Utopic) “lxc-attach from a different login session fails” [High,Triaged]
- Launchpad bug 1317587 in clamav (Ubuntu Utopic) “ClamAV 0.98.1 is Outdated” [High,In progress]
- Launchpad bug 1317811 in linux (Ubuntu) “Dropped packets on EC2, “xen_netfront: xennet: skb rides the rocket: x slots”" [Medium,In progress]
Next meeting will be on Tuesday, May 27th at 16:00 UTC in #ubuntu-meeting.
Additional logs @ https://wiki.ubuntu.com/MeetingLogs/Server/20140520
Since it would briefly come back to life if allowed to rest for awhile unplugged, I bought a backup hard drive of the proper sort (with its own power supply), and plugged it in. However, the DVR died before backing up commenced.
This DVR is leased, so Dish sent along a new one, asking that I return the broken one within 10 days. Yesterday a technician showed up to be sure that everything was working, since the new machine had taken quite long to get a watchable image. I asked him if it was possible to move the old hard drive into the new machine and do the backup, before sending the old machine back? He said yes, although he couldn't do it for us.
So, new challenge: remove the old hard drive from the old DVR. I found a wikibook about the DVR here: en.wikibooks.org/wiki/VIP_922/Dish_Network. There the author says,
With no A/C power connected - from the old 922, pull the internal hard drive and set it aside. To do this remove 4, back cover screws (black,) then slide the cover back about 1/2 inch and tilt upwards to remove.Well now, here was my first problem. Screws, no biggie. But "slide the cover back"? It simply would not move for me. However, teamwork to the rescue. My husband Bob used the straight-slot screwdriver and pried with a bit more power than I would have used, and slide, it did. From there on out, the problem was redimensionated (thank you genii for that beautiful term!) and it was only a matter of more screws, unhooking the power and motherboard connection, and sliding out.
After using my husband again to help me slide out the TV cabinet and photograph and then remove the DVR hookups, I used the same procedure again. Remove the cover, then the HD, and then switched the old HD into its place. I left off the cover, and then Bob hooked up the new machine again, and we turned it on to wait. After the backup hard drive was plugged in, this slow beast restarted again, but we had a new option: backup. Just to be safe, we selected only the Doctor Who eps. If there is room once that's done, I'll select the rest of what I want. The backup is now proceeding, and the readout reports that it will take another 10 hours. OMG, usb is slow!
So, redimensionating is cool. I'm going to try to remember to do it more often. Also, many thanks to the dish tech and wikibook author who both shared their information freely, and my husband who supplied support, muscle, and didn't give up!
Welcome to the Ubuntu Weekly Newsletter. This is issue #369 for the week May 19 – 25, 2014, and the full version is available here.
In this issue we cover:
- Ubuntu is the leading OpenStack distribution
- Ubuntu Stats
- Ubuntu 14.04 Presentations at FeltonLUG and BALUG
- Ubuntu Ohio Team Update: May 22, 2014
- Cloudbase Solutions Partnership
- Ubuntu Cloud Documentation – 14.04LTS
- Xubuntu: Screen locking in Xubuntu 14.04
- Jono Bacon: Goodbye Canonical, Hello XPRIZE
- Sebastian Kugler: Locale changes in Plasma Next
- Michael Hall: App Developer Sprint
- Svetlana Belkin: Ubuntu Scientists Team Update: May 23, 2014
- Lubuntu Blog: LXQt-Admin: System admin tools for LXQt arrived
- Ubuntu Women: Phase 2 of ProjectHarvest
- Unity8 & Mir update May 20, 2014
- Canonical News
- In The Blogosphere
- Other Articles of Interest
- Ubuntu Podcast from the UK LoCo: S07E08 – The One with the Yeti
- Weekly Ubuntu Development Team Meetings
- 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 K. Joseph
- Paul White
- Diego Turcios
- 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
Pasta is a wonderful thing. However many unwonderful things are done to pasta when it's being cooked. Consider this post a how-to about improving your pasta eating experience.
A sub-par pasta experience is one that involves overcooked & bland pasta, with the sauce slopped on top. However, this very easy to avoid.How to Improve Your Pasta Experience
Whether boxed or fresh pasta, following (and remembering) these few things will improve your pasta cooking abilities and your life as well as impress your friends & lover(s).*
*these claims may be exaggerated.1. Use enough salt
Something I see done frequently by people is they boil water for their pasta and either don't salt their water or put only a pinch in.
Salt is crucial to giving your pasta flavour & lowering the overall amount of salt needed for your dish.
Also, if you've heard that salted water cooks food faster (because of its higher boiling temperature), those claims are a bit exaggerated; the amount of salt you're adding is only enough to raise the temperature about 1 degree.2. Don't add oil
There's a bad practice of adding oil to the pasta cooking liquid to keep it from sticking. This only achieves one thing: oily pasta & oily pasta means sauce won't cling to it or be absorbed, which equals flavourless pasta.
Adding oil may also keep the pasta water from bubbling up and boiling over the rim, but this can also be achieved by using a large enough pot and also by reducing the heat a little (but still maintaining a boil).3. Stir
During the first minute or two of cooking, give the pasta a good stir to keep it from sticking together.
This is the crucial, since during this time the pasta is coated with sticky starch. If you don't stir, pieces of pasta that are touching one another literally cook onto one another.4. Avoid rinsing
Rinsing the pasta after cooking, will cool the pasta and prevent the absorption of a sauce. Not to mention it can wash away any remaining surface starch, which is advantageous to your cooking of the pasta. This small amount of starch left on the pasta by the cooking water can thicken your sauce slightly when you do encorporate the pasta.5. Cooking al dente
The term al dente is simply culinary-speak for pasta that is just slightly undercooked, which is considered by many to be the optimal mouthfeel for pasta.
As cooking times vary for various pasta shapes, the only way to truly know is to sample one of the cooking pasta and see if it has just a little bite to it when you chew it –this is al dente and considered cooked.6. Finish cooking in sauce
As it cools, the starch in the pasta crystallizes and becomes insoluble, therefore the pasta won't absorb as much sauce. As such, I always prepare the sauce first in a large skillet, regardless of it's simplicity, before cooking the pasta.
The moment the pasta is done, I scoop it out of the water with a spider and let it drain over the pot for a few seconds. Then I dump it into the hot sauce, stir well, & cover it to let the pasta absorb the sauce for a minute or two, before serving.Bonus: Quick Tomato Sauce Recipe
It would be appropriate of me to provide a sauce recipe after all of that, so here's a quick tomato sauce.
- 1 large (28 oz.) can tomatoes, diced or whole (uncooked)
- 1 can (12 oz.) tomato paste
- 1 bulb of garlic (10-12 cloves), minced or thinly sliced
- 1 onion, diced
- 1-2 tablespoons, olive oil
- 2 bay leaves
- 2 tablespoons dry oregano
- 250-300mL red wine
- salt, to taste
- 1 bag, baby spinach
- 1 box dry pasta, such as penne or farfalle (bowties)
- Preheat your skillet over med-high.
- Add olive oil and saute the garlic & onion for a few minutes.
- Add the wine, canned tomatoes & tomato paste. Stir.
- Add the bay leaves & oregano. Season with salt. Simmer for 8-10 minutes.
- Cook your pasta and encorporate into sauce. Cover & let it absorb the sauce for a few minutes.
- Place the bag of spinach atop the encorporated pasta-sauce mixture & cover –the remaining heat will be enough to wilt the spinach.
- When spinach is wilted, serve and garnish with grated Parmesan, if desired.
I had no idea that innocuous little blog post would result in a friendship with the author, Daniel Suarez, himself. Daniel, and his publicist, Michelle, would send me an early preview print of the sequel to Daemon, Freedom™, as well as his next two books, Kill Decision and Influx over the subsequent 6 years.
I read Influx in December 2013, a couple of months before its official release, on a very long flight to Helsinki, Finland.
Predictably, I thoroughly enjoyed it as much as each of Daniel's previous 3 books. One particular story arch pays an overt homage to one of my favorite books of all time -- Alexandre Dumas' Count of Monte Cristo. Influx succeeded in generating even more tension, for me. While it's natural for me to know, intuitively, the line between science and fiction for the artificial intelligence, robotics, and computer technology pervasive in Daemon, Freedom™, and Kill Decision, Influx is in a different category entirely. There's an active, working element of new found thrills and subconscious tension not found in the others, built on the biotechnology and particle physics where I have no expertise whatsoever. I found myself constantly asking, "Whoa shit man -- how much of that is real?!?" All in all, it makes for another fantastic techno-thriller.
After 5+ years of email correspondence, I actually had the good fortune to meet Daniel in person in Austin during SxSW. My friend, Josh (who was the person that originally game me my first copy of Daemon back in 2008), and I had drinks and dinner with Daniel and his wife.
It was fun to learn that Daniel is actually quite a fan of Ubuntu (which made a brief cameo on the main character's computer in Kill Decision). Actually, Daniel shared the fact the he wrote the majority of Influx on a laptop running Ubuntu!
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 firstname.lastname@example.org 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: email@example.com
Join us on IRC in #uupc on Freenode
Leave a voicemail via phone: +44 (0) 203 298 1600, sip: firstname.lastname@example.org 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.