We just created a new Ubuntu mailing list called ubuntu-community-team.
As we didn’t have a place like this before, we created it so we can
- have discussions around planning community events
- start all kinds of initiatives around Ubuntu
- allow enthusiasts of the Ubuntu community to kick around new ideas
- bring people from all parts of our community together so we can learn from each other
- hang out and have fun
We are looking forward to seeing you on the list as well, sign up on this page.
Now that the OpenPower sources are available, it's possible to build custom firmware images for OpenPower machines. Here's a little guide to show how that's done.The build process
OpenPower firmware has a number of different components, and some infrastructure to pull it all together. We use buildroot to do most of the heavy lifting, plus a little wrapper, called op-build.
There's a README file, containing build instructions in the op-build git repository, but here's a quick overview:
To build an OpenPower PNOR image from scratch, we'll need a few prerequisites (assuming recent Ubuntu):sudo apt-get install cscope ctags libz-dev libexpat-dev libc6-dev-i386 \ gcc g++ git bison flex gcc-multilib g++-multilib libxml-simple-perl \ libxml-sax-perl
Then we can grab the op-build repository, along with the git submodules:git clone --recursive git://github.com/open-power/op-build.git
set up our environment and configure using the "palmetto" machine configuration:. op-build-env op-build palmetto_defconfig
After a while (there is quite a bit of downloading to do on the first build), the build should complete successfully, and you'll have a PNOR image build in output/images/palmetto.pnor.
If you have an existing op-build tree around (colleagues working on OpenPower perhaps?), you can share or copy the dl/ directory to save on download time.
The op-build command is just a shortcut for a make in the buildroot tree, so the general buildroot documentation applies here too. Just replace "make" with "op-build". For example, we can enable a verbose build with:op-build V=1 Changing the build configuration
Above, we used a palmetto_defconfig as the base buildroot configuration. This defines overall options for the build; things like:
- Toolchain details used to build the image
- Which firmware packages are used
- Which packages are used in the petitboot bootloader environment
- Which kernel configuration is used for the petitboot bootloader environment
This configuration can be changed through buildroot's menuconfig UI. To adjust the configuration:op-build menuconfig
And busybox's configuration interface will be shown:
As an example, let's say we want to add the "file" utility to the petitboot environment. To do this, we can nagivate to that option in the Target Packages section (Target Packages → Shell and Utilities → file), and enable the option:
Then exit (saving changes) and rebuild:op-build
- the resulting image will have the file command present in the petitboot shell environment.Kernel configuration
There are a few other configuration targets to influence the build process; the most interesting for our case will be the kernel configuration. Since we use petitboot as our bootloader, it requires a Linux kernel for the initial bootloader environment. The set of drivers in this kernel will dictate which devices you'll be able to boot from.
So, if we want to enable booting from a new device, we'll need to include an appropriate driver in the kernel. To adjust the kernel configuration, use the linux-menuconfig target:op-build linux-menuconfig
- which will show the standard Linux "menuconfig" interface:
From here, you can alter the kernel configuration. Once you're done, save changes and exit. Then, to build the new PNOR image:op-build Customised packages
If you have a customised version of one of the packages used in the OpenPower build, you can easily tell op-build to use your local package. There are a number of package-specific make variables documented in the buildroot generic package reference, the most interesting ones being the _VERSION and _SITE variables.
For example, let's say we have a custom petitboot tree that we want to use for the build. We've committed our changes in the petitboot tree, and want to build a new PNOR image. For the sake of this example, the git SHA petitboot commit we'd like to build is 2468ace0, and our custom petitboot tree is at /home/jk/devel/petitboot.
To build a new PNOR image with this particular petitboot source, we need to specify a few buildroot make variables:op-build PETITBOOT_SITE=/home/jk/devel/petitboot \ PETITBOOT_SITE_METHOD=git \ PETITBOOT_VERSION=2468ace0
This is what these variables are doing:
- PETITBOOT_SITE=/home/jk/devel/petitboot - tells op-build where our custom source tree is. This could be a git URL or a local path.
- PETITBOOT_SITE_METHOD=git - telsl op-build that PETITBOOT_SITE is a git tree. If we were using a git:// URL for PETITBOOT_SITE, then this variable would be set automatically
- PETITBOOT_VERSION=2468ace0 - tells op-build which version of petitboot to checkout. This can be any commit reference that git understands.
The same method can be used for any of the other packages used during build. For OpenPower builds, you may also want to use the SKIBOOT_* and LINUX_* variables to include custom skiboot firmware and kernel in the build.
If you'd prefer to test new sources without committing to git, you can use _SITE_METHOD=local. This will copy the source tree (defined by _SITE) to the buildroot tree and use it directly. For example:op-build SKIBOOT_SITE=/home/jk/devel/skiboot \ SKIBOOT_SITE_METHOD=local
- will build the current (and not-necessarily-committed) sources in /home/jk/devel/skiboot. Note that buildroot has no way to tell if your code has changed with _SITE_METHOD=local. If you re-build with this, it's safer to clean the relevant source tree first:op-build skiboot-dirclean
This is my monthly summary of my free software related activities. If you’re among the people who made a donation to support my work (65.55 €, thanks everybody!), then you can learn how I spent your money. Otherwise it’s just an interesting status update on my various projects.Distro Tracker
Even though I was officially in vacation during 3 of the 4 weeks of August, I spent many nights working on Distro Tracker. I’m pleased to have managed to bring back Python 3 compatibility over all the (tested) code base. The full test suite now passes with Python 3.4 and Django 1.6 (or 1.7).
From now on, I’ll run “tox” on all code submitted to make sure that we won’t regress on this point. tox also runs flake8 for me so that I can easily detect when the submitted code doesn’t respect the PEP8 coding style. It also catches other interesting mistakes (like unused variable or too complex functions).
Getting the code to pass flake8 was also a major effort, it resulted in a huge commit (89 files changed, 1763 insertions, 1176 deletions).
Thanks to the extensive test suite, all those refactoring only resulted in two regressions that I fixed rather quickly.
Some statistics: 51 commits over the last month, 41 by me, 3 by Andrew Starr-Bochicchio, 3 by Christophe Siraut, 3 by Joseph Herlant and 1 by Simon Kainz. Thanks to all of them! Their contributions ported some features that were already available on the old PTS. The new PTS is now warning of upcoming auto-removals, is displaying problems with uptream URLs, includes a short package description in the page title, and provides a link to screenshots (if they exist on screenshots.debian.net).
We still have plenty of bugs to handle, so you can help too: check out https://tracker.debian.org/docs/contributing.html. I always leave easy bugs for others to handle, so grab one and get started! I’ll review your patch with pleasure.Tryton
I wasn’t able to attend this year but thanks to awesome work of the video team, I watched some videos (and I still have a bunch that I want to see). Some of them were put online the day after they had been recorded. Really amazing work!Django 1.7
After the initial bug reports, I got some feedback of maintainers who feared that it would be difficult to get their packages working with Django 1.7. I helped them as best as I can by providing some patches (for horizon, for django-restricted-resource, for django-testscenarios).
Since I expected many maintainers to be not very pro-active, I rebuilt all packages with Django 1.7 to detect at least those that would fail to build. I tagged as confirmed all the corresponding bug reports.
Looking at https://firstname.lastname@example.org;tag=django17, one can see that some progress has been made with 25 packages fixed. Still there are at least 25 others that are still problematic in sid and 35 that have not been investigated at all (except for the automatic rebuild that passed). Again your help is more than welcome!
It’s easy to install python-django 1.7 from experimental and they try to use/rebuild the packages from the above list.Dpkg translation
With the freeze approaching, I wanted to ensure that dpkg was fully translated in French. I thus pinged email@example.com and merged some translations that were done by volunteers. Unfortunately it looks like nobody really stepped up to maintain it in the long run… so I did myself the required update when dpkg 1.17.12 got uploaded.
Is there anyone willing to manage dpkg’s French translation? With the latest changes in 1.17.13, we have again a few untranslated strings:
$ for i in $(find . -name fr.po); do echo $i; msgfmt -c -o /dev/null --statistics $i; done
1083 translated messages, 4 fuzzy translations, 1 untranslated message.
268 translated messages, 3 fuzzy translations.
545 translated messages.
2277 translated messages, 8 fuzzy translations, 3 untranslated messages.
I made an xsane QA upload (it’s currently orphaned) to drop the (build-)dependency on liblcms1 and avoid getting it removed from Debian testing (see #745524). For the record, how-can-i-help warned me of this after one dist-upgrade.
With the Django 1.7 work and the need to open up an experimental branch, I decided to switch python-django’s packaging to git even though the current team policy is to use subversion. This triggered (once more) the discussion about a possible switch to git and I was pleased to see more enthusiasm this time around. Barry Warsaw tested a few workflows, shared his feeling and pushed toward a live discussion of the switch during Debconf. It looks like it might happen for good this time. I contributed my share in the discussions on the mailing list.Thanks
See you next month for a new summary of my activities.
I've just noticed and read the "Ubuntu Loves Devs" effort and I think that's something that could be addressed, or at least acknowledged. I've filed a bug report about what could be made to make modems and embedded / specialized development tools be less at odds with each other.
If you're interested in embedded development boards or accessing various devices using serial lines I'd like to invite you to join the discussion.
Ubuntu is sponsoring the dConstruct “Living with the network” event on the 5th of September at the Brighton Dome. Stop by for a chat with the team, grab some goodies and enter our competition for a chance to win an Ubuntu Phone.
Ubuntu is one of the best Linux platforms with an awesome desktop for regular users (and soon phone and tablets and more!) and great servers for system administrators and devops. A number of developers are choosing Ubuntu as their primary development system of choice, even if they develop for platforms other than Ubuntu itself, like doing some Android development, web development and so on.
However, even if we fill the basic needs for this audience, we decided a few months ago to start a development and integration effort to make those users completely feel at home. Ubuntu loves developers and we are going to showcase it by making Ubuntu the best available developer platform!Sounds great! What's up then?
We decided to start by concentrating on Android developers. We'll ramp up afterwards on other use cases like Go developers, web developers, Dart… but we want to ensure we deliver a stunning experience for each targeted audience before moving on to the next topic.
After analyzing how to setup an Android development machine on Ubuntu we realized that, depending on the system, it can takes up to 9 different steps to get proper IDE integration and all the dependencies installed. The whole goal was to reduce that to one single command!
Concretely speaking, we created the Ubuntu Developer Tools Center, a command line tool which allows you to download the latest version of Android Studio (beta), alongside the latest Android SDK, and all the required dependencies (which will only ask for sudo access if you don't have all the required dependencies installed already), enable multi-arch on your system if you are on a 64 bit machine, integrate it with the Unity launcher…
As said, we focused on Android Studio (based itself on Intellij IDEA) for now as it seems that’s where Google has been focusing its Android tools development effort for over a year. However, the system is not restrictive and it will be relatively trivial in the near future to add ADT support (Android Development Tools using Eclipse).
Indeed, The Ubuntu Developer Tools Center is targeted as being a real platform for all developer users on Ubuntu. We carefully implemented the base platform with a strong technical foundation, so that it's easily extensible and some features like the advanced bash shell completion will even make more sense once we added other development tools support.Availability
We will always target first the latest Ubuntu LTS version alongside the latest version in development. Yes! It means that people who want to benefit for the extensively tested and strong base experience that a Long Term Support version offers will always be up to date on their favorite developer tools and be first-class citizen. We strongly believe that developers always want the latest available tools on a strong and solid stable base and this is one of the core principle we are focusing on.
For now, the LTS support is through our official Ubuntu Developer Tools Center ppa, but we plan to move that to the backports archive with all the newly or updated libraries. For Utopic, it's already available in the 14.10 Ubuntu archive.Initial available version
Be aware that the Ubuntu Developer Tools Center is currently in alpha. This tool will evolve depending on your feedback, so it's up to you to suggest the direction you want it to go! A blog post on how to contribute will follow in the next days. This initial version is available in English, French and Chinese!
Another blog post will expand as well how we test this tool. For now, just be aware that the extensive test suite is running daily, and it ensures that on all supported platforms we don't break, that the Ubuntu platform itself doesn't break us, or that any 3rd party on which we rely on (like website links and so on) don't change without us spotting it. This will ensure that our tools is always working, with limited downtime.Example: how to install Ubuntu Developer tools and then, Android Studio Ubuntu Developer Tools Center
If you are on Ubuntu 14.04 LTS, first, add the UDTC ppa:
$ sudo add-apt-repository ppa:didrocks/ubuntu-developer-tools-center $ sudo apt-get update
Then, installing UDTC:
$ sudo apt-get install ubuntu-developer-tools-centerHow to install android-studio
$ udtc android
And then, accept the installation path and Google license. It will download, install all requirements alongside Android Studio and latest android SDK itself, then configure and fit it into the system like by adding an Unity launcher icon…
And that's it! Happy Android application hacking on Ubuntu. You will find the familiar experience with the android emulator and sdk manager + auto-updater to always be on the latest.
We welcome any ideas and feedback, as well as contributions as we'll discuss more in the next post. Meanwhile, do not hesitate to reach me on IRC (didrocks on freenode, #ubuntu-desktop as the primary channel to discuss), or on Google+. You can as well open bugs on the launchpad project or github one
I'm excited about this opportunity to work on the developer desktop. Ubuntu loves Developers, and it's all on us to create a strong developer community so that we can really make Ubuntu, the developer-friendly platform of choice!Notes
 android-studio is the default for the android development platform, you can choose it explicitely by executing "$ udtc android android-studio". Refer to --help or use the bash completion for more help and hints
Today my postal vote in the referendum for Scottish independence was sent off. I usually use my personal blog for non technical bits but I thought some readers of my KDE Blog might be interested in this as it does affect the geopolitics of pretty much the whole world.
What's going on?
300 years ago Scotland was broke and England was getting rich from its empire so England gave Scotland a wad of money and created the United Kingdom. That served Scotland pretty well for some centuries as Scots were able to trade and move freely across the empire and plenty of Scots were happy to take part in that (my old school still has a load of Hong Kong gold in its attic as a result). Time passed and the empire was shut down, the UK joined the EU and some oil was found in the sea off the coast of Scotland. After many decades of Scottish public services being run by some people appointed by the UK government, 15 years ago a new Scottish pariament was reconvened to control public services and laws in Scotland, but not tax or anything international.
In Scottish politics we have not liked the Conservative (and Unionist or Tory) party since Margaret Thatcher destroyed Scottish industry. Then Labour went out of fashion after Tony Blair started some random wars and Scottish administration (not even wanting to call itself a government) decided to market Scotland by calling it small. Then their coalition partner party the Liberal Democrats fell out of fashion by getting into the UK government and dropping all their liberal principles (GCHQ has been doing mass surveilance on the population and they haven't said a word against it). So at the last election the only large party left that had not lost all respect, the Scottish National Party, was voted in with a majority and their Scottish Government is now organising this referendum.
What will happen if the vote is Yes?
Both sides have said they will respect the result. If over 50% of people vote yes then the Scottish Government will start to negotiate with the UK government on the details to make Scotland an independent country. Depending on your point of view this is either a new country (Scotland) and a continuing state (rest of UK) or dissolving the 300 year old union to make two new countries. The proposed timetable is to make Scotland independent by March 2016 (which is done to fit in with the election timetable of the Scottish parliament, it's made somewhat more complex by a UK election happening in 2015).
Why vote for Yes?
There is a democracy in Scotland which has been notably different from England and the rest of the UK for some time. The two parties that make up the UK government (Conservative and Liberal Democrat) are the two least popular parties in Scotland. Political borders are circles on a map which can be arbitrary or based on some nasty tribal allegance but here's a redrawing which makes government better follow the demos of the population.
Is this anti-English?
We can be proud in Scotland that independence is being done through a peaceful political process. That was not the case in Ireland were they had effectively a guerrilla civil war until recently over incomprehensible tribal allegances. And it's not the case that Scottish nationalism is in any way anti any other nation, Scotland would continue to be best friends with England and the other counties of the British Isles.
The Yes campaign has sensibly avoided any call to patriotism, kilts and Irn Bru tend to get old quickly. By contrast the No campaign has tried quite a lot of patriotism talking about shared ties and gosh remember the first world war wasn't it glorious? Meanwhile English politics is getting more and more little-Englander. The Prime Minister has said he will give a referendum on membership of the EU, he wants to pull the UK out of the Court of Human Rights and he is making immigration much harder, all good reasons to vote to stay away from that sort of politics.
But isn't it better to work together?
Yes, and Scotland has benefited from the union with England to not have barriers of trade or movement. Now we have a larger union, the EU, to sort out the boring stuff around trade and movement we have no need of that middle layer of government. Scottish independence is an efficiency drive.
Can Scotland afford to be independent?
This is a common worry. Scots are often not very confident in their own country. We're small and need the help of something larger is a common thought. Of course it's not true, Scotland is exactly in the middle if you place it in a list of countries by size or population. We have plenty of industry and natural resources. And then we have the largest oil reserves in Europe. Currently the UK spends all the money that comes in from the oil while any other well run country with oil creates a soverign wealth fund, a common argument against independence is that the oil will run out sometime, my argument for independence is we need to be independent toot sweet so we can start a soverign wealth fund before it runs out.
Will Scotland be allowed to join the EU?
There's no precendent for this happening and no rules governing this process. Those against independence say Scotland would need to apply to join the EU and the Spanish might block it to stop the Catalans getting ideas above their station. Those for independence point out that Scotland is already a member of the EU, that all the citizens have EU citizenship and there is no rule to kick us out. In the end politics will decide and the EU has a good record of welcoming in people rather than shunning them.
What Currency will Scotland use?
Ah, yes, slightly more tricky this and the No campaign has been playing it to the full. The Scottish Government wants to continue to use the pound sterling with a formal currency union with the rest of the UK. The current UK government says this would not happen but it's not clear why the rest of the UK gets to keep it and Scotland not, this does suggest the last 300 years of union have really been a sham. The Scottish Government in response points out that as a freely tradeable currency Scotland can use the pound if it wants and nobody can stop it (this is what Ireland did when it became independent and what the Isle of Man and Gibraltar still do) and without a currency union Scotland would have no need to pay the massive national debt the UK has. Personally I'd like to use the Euro but that doesn't seem very fashionable these days for some reason.
What will happen to the BBC.. to the NHS.. won't the terrorists love it.. will Scotland have to join Schengen.. will immigrants steal our jobs and our women... will the UK get to keep its nuclear bombs?
The Scottish Government published a really long book with answers to all these details. They're just starting positions of course, after any Yes vote there will be lots of negotiation to work out how everything will be set up, but there is little that seems insurmountable.
They want to start a Scottish equivalent of the BBC which would mean we would actually get Scottish news in Scotland, currently half the news shown to use is irrelevant. It would make a formal agreement to allow us to keep important stuff like the World Service and Doctor Who. The National Health Service gives us free use of doctors and hospitals and any politician which says anything against it will be voted out quickly, the NHS is separate in Scotland than that in England so there's no change here, although some no campaign adverts have tried to claim otherwise. There has been some nonsense about terrorists loving it and we won't have MI5 and GCHQ to look after us all, to me the mass surveilance of the spy agencies is very much a reason to get away from that. I'd be all for Scotland joining Schengen and having closer ties with Europe but I expect we'll remain part of the British Isles Common Travel Area, it's only sensible politically. Scotland needs more immigrants for various economic reasons but in England there's a large political wish against it, another good reason to vote Yes. The UK nuclear bombs are kept north of Glasgow and sadly this is the only issue that has interested Slashdot. There is no desire to keep these in Scotland and the Scottish Government has promised to get rid of them mucho rapido, what the rest of the UK does with them is a problem for the rest of the UK.
All very exciting..
The vote is on 18th September and the polls show the No campaign stay steady at a bit below 50% and the Yes campaign started low at 30-odd percent but has been gaining ground as undecided voters move to Yes. There's now only a few points separating them and there are still plenty of undecided voters. The trend is for undecideds to move to Yes so it's very much all to play for. It's fun to live in interesting times.
Welcome to the Ubuntu Weekly Newsletter. This is issue #381 for the week August 25 – 31, 2014, and the full version is available here.
In this issue we cover:
- Ubuntu 14.10 (Utopic Unicorn) beta-1 released!
- Ubuntu Stats
- Need a different architecture? Ask Juju for it!
- Lubuntu Blog: LXPanel 0.7.0 released
- Nicholas Skaggs: Ubuntu Phone Translations Needed
- Xubuntu: Laptop users, Fix available for the black screen on unlock bug
- Zygmunt Krynicki: Checkbox Project Insights
- Daniel Pocock: Welcoming libphonenumber to Debian and Ubuntu
- Kubuntu Wire: Kubuntu on LinkedIn
- Unity8 & Mir update Aug 26, 2014
- Saving ubuntu.com on download day: Caching location specific pages
- NASA’s Kennedy Space Center Uses Ubuntu to Plan for the Exploration of Alien Planets
- Ubuntu Wallpaper Contest Closes, These Are Our 8 Faves
- Canonical Has Yet To Land X.Org Server 1.16 For Ubuntu 14.10
- Full Circle Magazine #88
- Featured Audio and Video
- Weekly Ubuntu Development Team Meetings
- Upcoming Meetings and Events
- Updates and Security for 10.04, 12.04 and 14.04
- And much more!
The issue of The Ubuntu Weekly Newsletter is brought to you by:
- Elizabeth K. Joseph
- John Mahoney
- Jose Antonio Rey
- 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'm looking for one that has side shelves (sometimes called a warming shelf in specs), a thermometer, and is on wheels.Estimated Cost $200Last updated on 09/01/2014 - 16:29 Big house itemsRequested 1Purchased 0
Beginning with the origins of Finnish sauna and how the practice was first brought to North America, and continuing all the way to contemporary design, The Opposite of Cold is an exquisite commemoration of the history, culture, and practice of Finnish sauna in the northwoods. With stunning photographs of unique and historic saunas of the region-including the oldest sauna in North America, incredible surviving saunas from immigrant farmsteads, and the gorgeous contemporary saunas from noted architects-Michael Nordskog and Aaron Hautala unveil the importance and beauty of sauna culture in modern Midwestern life.Estimated Cost $18See www.amazon.com/dp/0816656827See www.barnesandnoble.com/w/the-opposite-of-cold-m...Last updated on 09/01/2014 - 16:18 Nice to haveRequested 1Purchased 0
I’ve been a Debian user since 2002 and got my first package into Debian in 2006. Though I continued to maintain a couple packages through the years, my open source interests (and career) have expanded significantly so that I now spend much more time with Ubuntu and OpenStack than anything else. Still, I do still host Bay Area Debian events in San Francisco and when I learned that DebConf14 would only be quick plane flight away from home I was eager for the opportunity to attend.
Given my other obligations, I decided to come in halfway through the conference, arriving Wednesday evening. Thursday was particularly interesting to me because they were doing most of the Debian Validation & CI discussions then. Given my day job on the OpenStack Infrastructure team, it seemed to be a great place to meet other folks who are interested in CI and see where our team could support Debian’s initiatives.
First up was the Validation and Continuous Integration BoF led by Neil Williams.
It was interesting to learn the current validation methods being used in Debian, including:
From there talk moved into what kinds of integration tests people wanted, where various ideas were covered, including package sets (collections of related packages) and how to inject “dirty” data into systems to test in more real world like situations. Someone also mentioned doing tests on more real systems rather than in chrooted environments.
Discussion touched upon having a Gerrit-like workflow that had packages submitted for review and testing prior to landing in the archive. This led to my having some interesting conversations with the drivers of Gerrit efforts in Debian after the session (nice to meet you, mika!). There was also discussion about notification to developers when their packages run afoul of the testing infrastructure, either themselves or as part of a dependency chain (who wants notifications? how to make them useful and not overwhelming?).
Next up on the schedule was debci and the Debian Continuous Integration project presented by Antonio Terceiro. He gave a tour of the Debian Continuous Integration system and talked about how packages can take advantage of the system by having their own test suites. He also discussed some about the current architecture for handling tests and optimizations they want to make in the future. Documentation for debci can be found here: ci.debian.net/doc/. Video of the session is also available on the meetings-archive.
The final CI talk I went to of the day was Automated Validation in Debian using LAVA where Neil Williams gave a tour of the expanded LAVA (Linaro Automated Validation Architecture). I heard about it back when it was a more simple ARM-only testing infrastructure, but it’s grown beyond that to now test distribution kernel images, package combinations and installer images and has been encouraging folks to write tests. He also talked about some of the work they’re doing to bring along LAVA demo stations to conferences, nice! Slides from this talk are available on the debconf annex site, here: http://annex.debconf.org/debconf-share/debconf14/slides/lava/
On Friday I also bumped into a testing-related talk by Paul Wise during a series of Live Demos, he showed off check-all-the-things which runs a pile of tools against your project to check… all the things, detecting what it needs to do automatically. Check out the README for rationale, and for a taste of things it checks and future plans, have a peek at some of the data files, like this one.
It’s really exciting to see more effort being spent on testing in Debian, and open source projects in general. This has long been the space of companies doing private, internal testing of open source products they use and reporting results back to projects in the form of patches and bug reports. Having the projects themselves provide QA is a huge step for the maturity of open source, and I believe will lead to even more success for projects as we move into the future.
The rest of DebConf for me was following my more personal interests in Debian. I also have to admit that my lack of involvement lately made me feel like a bit of an outsider and I’m quite shy anyway, so I was thankful to know a few Debian folks who I could hang out with and join for meals.
On Thursday evening I attended A glimpse into a systemd future by Josh Triplett. I haven’t really been keeping up with systemd news or features, so I learned a lot. I have to say, it would be great to see things like session management, screen brightness and other user settings be controlled by something lower level than the desktop environment. Friday I attended Thomas Goirand’s OpenStack update & packaging experience sharing. I’ve been loosely tracking this, but it was good to learn that Jessie will come with Icehouse and that install docs exist for Wheezy (here).
I also attended Outsourcing your webapp maintenance to Debian with Francois Marier. The rationale for his talk was that one should build their application with the mature versions of web frameworks included with Debian in mind, making it so you don’t have the burden of, say, managing Django along with your Django-based app, since Debian handles that. I continue to have mixed feelings when it comes to webapps in the main Debian repository, while some developers who are interested in reducing maintenance burden are ok with using older versions shipped with Debian, most developers I’ve worked with are very much not in this camp and I’m better off trying to support what they want than fighting with them about versions. Then it was off to Docker + Debian = ♥ with Paul Tagliamonte where he talked about some of his best practices for using Docker on Debian and ideas for leveraging it more in development (having multiple versions of services running on one host, exporting docker images to help with replication of tests and development environments).
Friday night Linus Torvalds joined us for a Q&A session. As someone who has put a lot of work into making friendly environments for new open source contributors, I can’t say I’m thrilled with his abrasive conduct in the Linux kernel project. I do worry that he sets a tone that impressionable kernel hackers then go on to emulate, perpetuating the caustic environment that spills out beyond just the kernel, but he has no interest in changing. That aside, it was interesting to hear him talk about other aspects of his work, his thoughts on systemd, a rant about compiling against specific libraries for every distro and versions (companies won’t do it, they’ll just ship their own statically linked ones) and his continued comments in support of Google Chrome.
DebConf wrapped up on Sunday. I spent the morning in one of the HackLabs catching up on some work, and at 1:30 headed up to the Plenary room for the last few talks of the event, starting with a series of lightning talks. A few of the talks stood out for me, including Geoffrey Thomas’ talk on being a bit of an outsider at DebConf and how difficult it is to be running a non-Debian/Linux system at the event. I’ve long been disappointed when people bring along their proprietary OSes to Linux events, but he made good points about people being able to contribute without fully “buying in” to having free software everywhere, including their laptop. He’s right. Margarita Manterola shared some stats from the Mini-DebConf Barcelona which focused on having only female speakers, it was great to hear such positive statistics, particularly since DebConf14 itself had a pretty poor ratio, there were several talks I attended (particularly around CI) where I was the only woman in the room. It was also interesting to learn about safe-rm to save us from ourselves and non-free.org to help make a distinction between what is Debian and what is not.
There was also a great talk by Vagrant Cascadian about his work on packages that he saw needed help but he didn’t necessarily know everything about, and encouraged others to take the same leap to work on things that may be outside their comfort zone. To help he listed several resources people could use to find work in Debian:
Next up for the afternoon was the Bits from the Release Team where they fleshed out what the next few months leading up to the freeze would look like and sharing the Jessie Freeze Policy.
DebConf wrapped up with a thank you to the volunteers (thank you!) and peek at the next DebConf, to be held in Heidelberg, Germany the 15th-22nd of August 2015.
Then it was off to the airport for me!
The rest of my photos from DebConf14 here: https://www.flickr.com/photos/pleia2/sets/72157646626186269/
Note: Before I start this post, in my last post, “Why I Use Open Source”, I made a couple of errors based on what they commented on, mainly on the whole, “who had tabbed Internet browsers first”. I will do my homework (read: research) and see who is right.
As I said in, Why I Use Open Source” (link above), I have one more example why I use Open Source and also contribute to it. No, wait! I have two examples and they will be order based on importance to me.
Example One: Sense of Community
This one is the big one for me, more than the recognition factor. I don’t know why I feel a very excellent sense of community within the Ubuntu Community. Maybe it’s the first FOSS/Linux community that I got my head into and was able to get something done. Why am I saying this? I found that because of the checks and balances nature of the Open Source and also the volunteer nature, that the members understand what they are creating and giving away will help the greater good. Also, many of these members are liked-minded and like and like will stick together and care for each other.
Or maybe it’s because throughout the various things that I done with community service (A.K.A. service learning), I have learned that in certain communities, there is a sense of people caring for each other and many of them are like-minded. I think I done about 100 hours of community service where I volunteered at my freshman high school (I went to a school district had freshmen in one building and the 10 -12 graders in another) for a concert band contest to doing 50 hours (I needed 25 hours for a class but ended up doing 50) at a non-profit place that offers free arts and crafts to kids. Even though I wasn’t helping the kids to create their masterpieces, I was working two and half hours, two times a week, to get the materials ready. I didn’t mind being the background worker. But I knew that I gave an impact to the community because I knew that what I was helping to get ready will be given away to kids who want to be creative and want to learn how to create something with there own two hands.
After four years of being an Ubuntu user, I finally gave into the Ubuntu Community and I enjoying so far. After one year of working in the Community, I really do have great sense on how the Community is no matter the size of it. I really want to move on into another one, maybe a Open Science one that doesn’t really require anyone to know how to develop/code.
Example Two: Sense of Recognition
If you read books or articles about community, one consistent theme you will find in almost all of them is the importance of recognizing the contributions that people make. In fact, if you look at a wide variety of successful communities, you would find that one common thing they all offer in exchange for contribution is recognition. It is the fuel that communities run on. It’s what connects the contributor to their goal, both selfish and selfless. In fact, with open source, the only way a contribution can actually stolen is by now allowing that recognition to happen. Even the most permissive licenses require attribution, something that tells everybody who made it.
-Michael Hall, from “Why do you contribute to open source?“
I do agree with this quote above because there won’t be anyone who wants to contribute if they are not recognized for their work.
At least in the Ubuntu Community (I don’t know about other FOSS communities), the biggest way that one can be recognized for their work is the Ubuntu Membership and it’s perks. Even though I’m a community building centred person, I still post news about the teams that am I part of or lessons that I have learned. These posts are useful because they show what I do and how they impact the community.
In my next post I will talk about why I blog since I have talked about here.
Two of the main things I’ve been working on since I started at Xamarin are making it easier for people to try out the latest bleeding-edge Mono, and making it easier for people on older distributions to upgrade Mono without upgrading their entire OS.Public Jenkins packages
Every time anyone commits to Mono git master or MonoDevelop git master, our public Jenkins will try and turn those into packages, and add them to repositories. There’s a garbage collection policy – currently the 20 most recent builds are always kept, then the first build of the month for everything older than 20 builds.
Because we’re talking potentially broken packages here, I wrote a simple environment mangling script called mono-snapshot. When you install a Jenkins package, mono-snapshot will also be installed and configured. This allows you to have multiple Mono versions installed at once, for easy bug bisecting.directhex@marceline:~$ mono --version Mono JIT compiler version 3.6.0 (tarball Wed Aug 20 13:05:36 UTC 2014) directhex@marceline:~$ . mono-snapshot mono [mono-20140828234844]directhex@marceline:~$ mono --version Mono JIT compiler version 3.8.1 (tarball Fri Aug 29 07:11:20 UTC 2014)
The instructions for setting up the Jenkins packages are on the new Mono web site, specifically here. The packages are built on CentOS 7 x64, Debian 7 x64, and Debian 7 i386 – they should work on most newer distributions or derivatives.Stable release packages
This has taken a bit longer to get working. The aim is to offer packages in our Apt/Yum repositories for every Mono release, in a timely fashion, more or less around the same time as the Mac installers are released. Info for setting this up is, again, on the new website.
Like the Jenkins packages, they are designed as far as I am able to cleanly integrate with different versions of major popular distributions – though there are a few instances of ABI breakage in there which I have opted to fix using one evil method rather than another evil method.
Please note that these are still at “preview” or “beta” quality, and shouldn’t be considered usable in major production environments until I get a bit more user feedback. The RPM packages especially are super new, and I haven’t tested them exhaustively at this point – I’d welcome feedback.
I hope to remove the “testing!!!” warning labels from these packages soon, but that relies on user feedback to my xamarin.com account preferably (jo.shields@)
In the morning I got an email:
Dear Marcin Juszkiewicz,
Congratulations on your one-year anniversary with Red Hat! Thank you for your commitment and work over the past year. We hope that it has been everything you expected it to be and look forward to celebrating your future success with the company.
Yes, already year passed since I joined ARM team at Red Hat. It was a good time and I do not plan to change it ;)
What I did during that time? Managed to get several packages built for AArch64, sent many patches upstream (some were easy, other required several updates) and even got one machine to use at home. It was not an easy ride but I am glad that I went that way.
I had some ARMv7a work done but over 80% of time spent with AArch64. First in simulators but then hardware started coming. First shared one with other developers (timezone differences helped a lot), then got remote one for own development use and finally one machine landed under my desk (the only one in Poland at that time). Do I have to add how it simplified work? GVim over X11 just works so the only difference is colorscheme and font used ;D
What next? More AArch64 work. There are still packages which fail to build ;D
Interesting, engaging, and sometimes challenging. My only criticism of the book is that he dwells a bit on fads in academia which are fading, but since he's been extensively challenged by that crowd, I suppose it is forgivable.
I'll quote extensively from the last chapter, but first, Emily Dickinson (quoted in that final chapter):
The Brain--is wider than the Sky--
For--put them side to side--
The one the other will contain
With ease--and you--beside-- The Brain is deeper than the sea--
For--hold them--Blue to Blue--
The one the other will absorb--
As Sponges--Buckets--do-- The Brain is just the weight of God--
For--Heft them--Pound for Pound--
And they will differ--if they do--
As Syllable from Sound--And the beginning of the final chapter:
The Blank Slate was an attractive vision. It promised to make racism, sexism, and class prejudice factually untenable. It appeared to be a bulwark against the kind of thinking that led to ethnic genocide. It aimed to prevent people from slipping into a premature fatalism about preventable social ills. It put the spotlight on the treatment of children, indigenous peoples, and the underclass. The Blank Slate thus became part of secular faith and appeared to constitute the common decency of our age. But the Blank Slate had, and has, a dark side. The vacuum that was posited in human nature was eagerly filled by totalitarian regimes, and it did nothing to prevent their genocides. It perverts education, child-rearing, and the arts into forms of social engineering. It torments mothers who work outside the home and parents whose children did not turn out as they would have liked. It threatens to outlaw biomedical research that could alleviate human suffering. Its corollary, the Noble Savage, invites contempt for the principles of democracy and of "a government of laws not of men." It blinds us to our cognitive and moral shortcomings. And in matters of policy it has elevated sappy dogmas above the search for workable solutions. The Blank Slate is not some ideal that we should all hope and pray is true. No, it is anti-life, anti-human theoretical abstraction that denies our common humanity, our inherent interests, and our individual preferences. Though it has pretensions of celebrating our potential, it does the opposite, because our potential comes from the combinatorial interplay of wonderfully complex faculties, not from the passive blankness of an empty tablet. Regardless of its good and bad effects, the Blank Slate is an empirical hypothesis about the functioning of the brain and must be evaluated in terms of whether or not it is true. The modern sciences of mind, brain, genes, and evolution are increasingly showing that it is not true. The result is a rearguard effort to salvage the Blank Slate by disfiguring science and intellectual life: denying the possibility of objectivity and truth, dumbing down issues into dichotomies, replacing facts and logic with intellectual posturing. The Blank Slate became so deeply entrenched in intellectual life that the prospect of doing without it can be deeply unsettling. ...Is science leading to a place where prejudice is right, where children may be neglected, where Machiavellianism is accepted, where inequality and violence are met with resignation, where people are treated like machines? Not at all! By unhandcuffing widely shared values from moribund factual dogmas, the rationale for these values can only become clearer. We understand *why* we condemn prejudice, cruelty to children, and violence against women, and can focus our efforts on how to implement the goals we value most. ... ... Acknowledging human nature does not mean overturning our personal world views... It means only taking intellectual life out of its parallel universe and reuniting it with science and, when it is borne out by science, by common sense.This book was published in 2002, and I think Pinker and his fellow scientists who investigate human nature are beginning to make headway. This book was a good reminder of some of the nonsense we are now sweeping into the dustbin of history, and new understanding of human nature now coming to light.
New improvement: Choose a custom color
What is Folder Color?
It's an application for changing the color of a folder in Ubuntu with just a right-click. Really useful for easily spotting folders in 12 preconfigured colours!
Easy, fast and useful
Let's see a video with Folder Color in action!
How can you install?
- In a Terminal from the PPA:
sudo apt-get update && sudo apt-get install folder-color
- If you have already installed Folder Color from the PPA, just update your system:
You need to logout from your current session (or kill nautilus with nautilus -q) after the installation.
What do you need?
Just Ubuntu (or derivate) & Nautilus, the file browser by default in Ubuntu :)
+info: Oficial web.
I decided to respond to Michael Hall’s post, “Why do you contribute to open source?“, but first I will explain why I use open source and in the next post, I will explain why I contribute to it. I don’t only use it because it’s almost free to use but for the intuitive sense of things that I see in all of the programs that I use. This intuitive sense matches up with the way that I think and how I do things.
I have three examples why I use Open Source:
Example One: Evernote Ink Notes vs. Xournal- A Shift in My Workflow
This example is a recent thing that happened to me. On Monday, August, 25, 2014 (first day of my last school year of my undergrad years), I was able to restore my Nexus 7 2013 back to Android from Ubuntu Touch since Ubuntu Touch wasn’t worth while to use (for now) as a working tablet. For those who want to know, you need at least 2 GB of RAM to use the ./flash-all.sh command. I only restored my tablet- meaning that I didn’t brother to install a custom ROM on it (don’t ask me why). After I restored, I installed the Evernote app and signed in to it. The hour before I restored my tablet, I was in my eight A.M. class and I took hand-written notes on my netbook, Evernote Ink Notes, and my Wacom Intous 4 pen and tablet. When I opened the notes on my tablet and they looked horrible! Not because I have chicken scratch for my handwriting (it does get bad at times) but because it was zoomed in and I had to finger scroll. I had no way to zoom out. And the UX of the app is just not fun to use.
After that first use of the Evernote, I decided to go back and use my favorite handwritten note-taking program, Xournal, but with some tweaks. One of them being all of my notes for one class is be one file, when possible, which is for my eight A.M. class. The other one is be convert the presentation slides for my second and also last class (I have two this term) into PDF and annotate that PDF.
The only problem with this workflow is that Xournal is X based not Qt based. That means when Mir and Unity 8 comes out, I won’t be able to use my favorite program! But maybe I could work with some developers and get some of the features of Xournal into the Reminders app.
Example Two: Open Source has More Intuitive Minds
I have noticed that many of the programs that I use have features that are latter used in non-open source programs. Who had tabs first in Internet browsers? Firefox. Conversion from a word/spreadsheet/presentation to PDF? OpenOffice. This goes to show that who are more daring to be more intuitive.
When Unity first introduced back in Ubuntu 11.04, it was hard for me to get used to it at first. I think it took me maybe two months to tell myself to that is the change can be good. After I installed 11.04, I saw that Unity increased my productivity. I found that searching in the Dash of Unity was faster than scrolling and clicking through folders on the menu. Unity is quiet intuitive to my mind and it was here before Windows 8. Another example of open source having more intuitive minds.
Example three will be in my next post when I will talk about why I contribute to Open Source. Most likely, I will have a series of posts about why I’m in the FOSS community and other subjects such as why I blog.
A while ago I posted about FOSSETCON (Free and Open Source Software Expo and Technology Conference), but now the time has come. In less than two weeks the conference will be taking place, and I cannot wait to fly over there!
FOSSETCON will start on Thursday, September 11th with day 0. We will have an Ubucon the whole day! Panels, workshops, make sure you don’t miss it. I’ll be flying during that day and hope I can get there at least for the last session.
During the 12th and 13th there will be an expo hall, as well as several talks! I will be with the Ubuntu Florida LoCo Team in the Ubuntu booth. Make sure to visit us there if you want to take a look at the Ubuntu phones and tablets, and maybe get some swag? Who knows.
On the other hand, I will be hosting a 40-minute Juju Charm School during day 1 (September 12th) at 10:30am local time. Make sure to attend if you wanna get a glimpse of what’s up with Juju and all the things you can do with it, including a bit of development.
In case you’re wondering. Yes, I will have the so-loved Orange Box! If you want to see it in action or just give it a hug, make sure to go to FOSSETCON!
You can buy your tickets for FOSSETCON by clicking here. There are three ticket options: the Training Pass, the Conference Pass and the Supporter Pass. You can find more information about each ticket type on the link.
Also, if you have already got your copy of the Official Ubuntu Book, 8th edition and want me to sign it for you, I will be more than happy to.
Don’t be shy and say hi, maybe we can grab a coffee after conference hours. See you all there!
perdiéndose por los mercados callejeros
de sus callesy disfrutando el alma de este pueblocon sus junglas de asfaltoy sus junglas reales(jue con la 'hormiguita')... hasta el infinito y más allá
Del viaje en particular podría destacar muchísimas cosas, las playas, las islas, los pueblos, las ciudades, la gastronomía, incluso el calor sofocante; pero no, no voy a destacar nada de todo eso.
Destaco los momentos únicos con personas únicas, que hicieron de este viaje, un viaje único ;) ¡Gracias a todos/as! ¡Hasta la próxima!
Next station? El destino dirá
Todas las entradas del viaje:
- Welcome on board!
- Cartagena de Indias
- Islas del Rosario
- A un día para la Ubuconla
- Ubuconla, día 1
- Ubuconla, día 2
- Santa Marta
Gracias a todos/as por 'acompañarnos' en este relato
... The end ...