It is possible to allow Views to show only content that has child terms from a taxonomy?
Yes, it is. This is similar but slightly different to our tutorial on using Views to show only child terms.
Well we want to freeze later this year so I started with the axing now. Maybe a bit premature like Mattia pointed out correctly in #debian-qa, because we've some maintained plugins for xchat around.
cwirc a morse code via IRC plugin
xchat-xsys system statistics output to a channel Update: There is a xsys plugin included with hexchat.
I can survive without them, so I'd be fine with another three RM bugs. Now feel free to flame me, I promise to wear my finest asbestos underwear.
Des pas sur la neige ("Footprints in the Snow") is a beautiful piano piece from Debussy which I had the chance to orchestrate in the context of my music composition program at the university. I've received a few critics and some kind words about this work, so last year I decided to publish it somewhere.
Then I completely forgot. Then this week I watched Youth, from Paolo Sorrentino, who's known for chosing lovely music for his lovely movies, and Debussy was there. I've got then some motivation and after a few adjustments here and there I uploaded the final score here.
I've been using MuseScore, a free (libre) software for all my music work, even for less traditional notation.
One OSTraining member asked us this question:How can I set the filter criteria so that Views shows only the second level in of a taxonomy?
We've had that question from other members before, so here's a tutorial explaining how it's done.
First, you need a taxonomy that has parent and child terms, as in this example:
What happened in the reproducible builds effort between January 3rd and January 9th 2016:Toolchain fixes
The following packages have become reproducible due to changes in their build dependencies: aggressive-indent-mode, circe, company-mode, db4o, dh-elpa, editorconfig-emacs, expand-region-el, f-el, geiser, hyena, js2-mode, markdown-mode, mono-fuse, mysql-connector-net, openbve, regina-normal, sml-mode, vala-mode-el.
The following packages became reproducible after getting fixed:
- avrdude/6.2-5 by Milan Kupcevic.
- ca-certificates/20160104 by Michael Shuler, original patch by Reiner Herrmann.
- cryptsetup/2:1.7.0-1 uploaded by Jonas Meurer, original patches (#780864, #794106) by Dhole and Valentin Lorentz.
- gpaw/0.11.0.13004-3 by Graham Inggs.
- graphite2/1.3.4-2 uploaded by Rene Engelhard, original patch by Reiner Herrmann.
- manpages/4.04-0.1 uploaded by Tobias Quathamer, original patch by Lunar.
- medicalterms/20160103-1 uploaded by Tobias Quathamer, reported by Daniel Kahn Gillmor.
- metview/4.5.7-3 uploaded by Alastair McKinstry, original patch by Reiner Herrmann.
- oasis3/3.mct+dfsg.121022-7 uploaded by Alastair McKinstry, original patch by Reiner Herrmann.
- postgresql-9.5/9.5.0-1 by Christoph Berg.
- python-caja/1.12.0-1 uploaded by Mike Gabriel, original patch by Chris Lamb.
- qutemol/0.4.1~cvs20081111-5 by Graham Inggs.
- robocode/188.8.131.52-1 by Markus Koschany.
- rungetty/1.2-16 by Rhonda D'Vine, original patches (#777447, #793717) by Chris Lamb and akira.
- t-prot/3.4-4 by Rhonda D'Vine.
- tetrinet/0.11+CVS20070911-2 by Rhonda D'Vine, original patch by Chris Lamb.
- tworld/1.3.2-2 by Rhonda D'Vine, original patch by Chris Lamb.
- visp-images/3.0.0-2 uploaded by Fabien Spindler, original patch by Chris Lamb.
- xblast-tnt-levels/20050106-3 by Rhonda D'Vine, original patch by Chris Lamb.
- xblast-tnt-models/20050106-4 by Rhonda D'Vine, original patch by Chris Lamb.
- xblast-tnt-musics/20050106-3 by Rhonda D'Vine, original patch by Chris Lamb.
- xblast-tnt-sounds/20040429-3 by Rhonda D'Vine, original patch by Chris Lamb.
Some uploads fixed some reproducibility issues, but not all of them:
- ace-of-penguins/1.5~rc1-1 by Markus Koschany, original patch by Reiner Herrmann.
- disque/1.0~rc1-4 by Chris Lamb.
- elki/0.7.0-4 by Erich Schubert.
- xnecview/1.35-8 by Tobias Frost, original patch by Chris Lamb.
Patches submitted which have not made their way to the archive yet:
- #809780 on flask-restful by Chris Lamb: implement support for SOURCE_DATE_EPOCH in the build system.
- #810259 on avfs by Chris Lamb: implement support for SOURCE_DATE_EPOCH in the build system.
- #810509 on apt by Mattia Rizzolo: ensure a stable file order is given to the linker.
Add 2 more armhf build nodes provided by Vagrant Cascadian. This added 7 more armhf builder jobs. We now run around 900 tests of armhf packages each day. (h01ger)
The footer of each page now indicates by which Jenkins jobs build it. (h01ger)diffoscope development
diffoscope 45 has been released on January 4th. It features huge memory improvements when comparing large files, several fixes of squashfs related issues that prevented comparing two Tails images, and improve the file list of tar and cpio archive to be more precise and consistent over time. It also fixes a typo that prevented the Mach-O to work (Rainer Müller), improves comparisons of ELF files when specified on the command line, and solves a few more encoding issues.Package reviews
134 reviews have been removed, 30 added and 37 updated in the previous week.
20 new “fail to build from source” issues were reported by Chris Lamb and Chris West.
When I was thinking about using Ghost, I did read the installations guide and then I just closed the browser window.
I didn't wanted to install npm, yet another package manager, and just hack init scripts. Not speaking about updating Ghost itself.
Some weeks later I did think about using Ghost again. It has a nice Markdown Editor and some nice other features. Since everybody is jumping on the Docker band wagon actually and I had used it for some tests already, I thought trying the Ghost Docker image might be a good idea.
If you are interested into how I did that, read on.
Just in case you didn't, you need to (re)start docker to work with service docker restart# docker pull ghost Making Ghost (container image) run forever
This will start your container on start and even is looking for a new Docker image and is fetching it, if needed. If you don't like this behavior, just comment out the line in the config and reread it with systemctl daemon-reload.
Now you should have listening something on port 2368:# netstat -tapn | grep 2368 tcp6 0 0 :::2368 :::* LISTEN 7061/docker-proxy
Update: Joël Dinel did send me a mail, that starting your Docker container with --restart always will take care that it is brought up again if Docker or (even) the whole system will get restarted. For real I used that before and might be a lightweight solution, but I liked the systemd unit file solution a lot more.Persistent Data
Thanks to the Docker mount option you can find all your data in /srv/docker/ghost/. So your blog will still have content, even if the ghost Docker images is updated:# ls /srv/docker/ghost/ apps config.js data images themes Accessing the container
To kick your ghost into production, it might be useful if you make it available on port 80 at least. This can be done for example by changing your Docker publish configuration or adding a DNAT to your firewall.
But I would recommand using a proxy in front of your Docker container. This might be part of one of my next articles.
While I fully realize it’s not fair to compare a major turning point at an organization to one in an existential battle over the future of the civilized world, Winston Churchill was clearly onto something. At this point, the news is out that Sean is leaving ThinkShout. I still wince when I see those words, although we’re all getting used to the idea.
In my mind, the "beginning" in this case is the early stages of a company started by a couple of guys with a vague notion of wanting to do well by doing good. At this point, ThinkShout is so much more. It is 22 intelligent, compassionate, talented, and dedicated professionals. It is a collection of accumulated knowledge and processes that allow us to partner with organizations like the Southern Poverty Law Center that we look upon with awe and respect. It is the combined innovation of 60,000 websites running on our contributions. It is the experience and insights we can offer on how to best use those tools.
As we built this company, Sean and I were often challenged by mentors and our leadership team on what our goals were for ThinkShout. The answers varied over the years, but one key point was consistent: we both dreamed of building an organization that was much more than either of us, that could live on when we inevitably moved on.
For Sean, that time is now. And, even though he’s incredibly humble and won’t say it himself, he’s leaving with his head held high, incredibly proud of having accomplished what he set out to do.
I can’t thank him enough for going on this journey with me these past 6 years. I don’t want to sugarcoat things. There have plenty of challenges, as there are in any relationship, but Sean’s been a wonderful business partner. He’s challenged me in countless ways, supported me when I’ve been down, and done the dirty work to make the business run when I’ve played the prima donna engineer role. In short, he’s set ThinkShout up for amazing success as he moves on. And for that, we’re all grateful.
Alright, so that’s the beginning. What’s next?
As part of Sean’s transition, we’ve made a number of promotions that were already under consideration that I’m incredibly proud to announce here.Brett Meyer, Chief Strategy Officer
Brett will run point on our business development efforts, as well as continue to lead our strategy and UX teams. He will work closely with Stephanie Gutowski, who was recently promoted to Marketing Manager. He will also support Natania LeClerc, who will lead ThinkShout’s new digital fundraising practice area. We’re also growing our strategy team, with an immediate opening for a Senior UX Designer and more to come. Brett has been pivotal in getting ThinkShout to where it is today and his ascension to this leadership position is well deserved. He crafts our solutions in the sales process and during discovery, leads our UX and IA practice, and is a well-recognized thought leader in the nonprofit technology community. Just try getting a seat during one of his talks at the Nonprofit Technology Conference.Alex MacMillan, Chief Operating Officer
In her role as Director of Project Management, Alex has led our PM team, defined our project delivery process, and managed resource allocation. In her 2 years with us, she has become the heartbeat of our projects, drastically increasing client satisfaction and project success rates. As COO, she’ll also take on oversight over the financial health of individual projects and the company as a whole. We’re also growing our project management team, looking for another senior project manager to partner with our clients to help them have a positive impact.
With Alex’s new role, Krista Van Veen, who has been our Operations Manager, has a new title: Manager of Culture and People. This represents her focus on HR, recruiting, and community engagement, although she’ll continue to play a critical role in managing ThinkShout’s finances. Krista has worked hard to convert our vision and values into actual cultural changes, as demonstrated by her leadership in attaining our recent B Corp certification.Tauno Hogue, Chief Technology Officer
Tauno is ThinkShout’s most senior employee, having been with us, quite literally, since the beginning. In that time, he’s grown from a talented developer into the leader of our engineering team. He takes on some of our most complex technical challenges, provides mentorship, and helps define our development workflow. In his new role as CTO, he’ll continuing doing more of the same, along with ensuring that we continue to offer innovative open source solutions for our forward-thinking clients. And, you guessed it, we’re also hiring on the engineering side of things.
Given that I had the title of CTO, clearly something else has to change. I am assuming Chief Executive Officer (CEO) responsibilities. This will entail setting the strategic direction of the company in partnership with the leadership team, along with being an external representative of ThinkShout. Most importantly to me, I will remain very actively involved in crafting innovative technical solutions for the challenges facing our clients. But, really, my biggest job will be to stay out of the way of the amazing leadership that we now have in place.
"To improve is to change; to be perfect is to change often."- Winston Churchill
Sticking with the Churchill theme, it’s important to note that this is far from the end of the changes that we expect to see at ThinkShout in the coming months.
First, and I mean this sincerely, there is absolutely nothing that we are doing perfectly. Far from it. We’ll continue to iterate on everything, including our organizational structure. We’re going to get some stuff wrong, and we’ll adjust accordingly.
But, on the whole, I have never been more confident in, and excited for, the future. We’re due to kick off our largest project yet with an organization that we’ve all dreamed of working with. We have four Drupal 8 projects lined up to kick off in Q1. We’re launching a new Digital Fundraising practice area. We’re welcoming five new team members over the next few months.
None of this would be possible without everything that Sean has put into ThinkShout up to this point. For that, we thank him. And we wish him luck on his next grand adventure – which, rumor has it, might involve pickling or waxed canvas accessories... Stay tuned, I know it will be great.
While the details about how to join the set of paid contributors have always been public (here) we did not advertise this fact very much outside of the people already interested in LTS (and thus subscribed to firstname.lastname@example.org). But right now we would like to have a few more paid contributors on board and I’m thus posting this call for volunteers.Who can apply?
You need to meet those requirements:
- you are Debian Developer or a Debian Maintainer;
- you have some prior experience with providing security updates in Debian (at least on your own packages);
- you have good programming skills and know multiple languages (to be able to backport security fixes);
- you can emit invoices to Freexian;
- you accept the rules defined for this project:
- you must respect the privacy of any customer data;
- you must prepare a public monthly report of the work done on paid time;
- you must respect the Debian code of conduct and respond to queries about your work from fellow community members;
- you must do your best to meet the high-quality standards set by the Debian security team.
Even though Freexian is located in France and requires you to provide invoice in EUR, there are no conditions on your nationality or country of residence. For contributors outside of the Euro zone, Freexian is using Transferwise to pay them with minimal currency conversion costs (Paypal is also possible if nothing else works).
The rate offered to paid contributors is the same for all (75 EUR/hour), it’s based on a correct rate for independent contractors in western Europe. If the rate is very high for your own country, then be happy to be able to invoice Freexian at this rate and use this opportunity to work less (for money) and contribute more to Debian on your (now copious) free time.How does the work look like?
If you apply, you will have to send us an SSH key so that you can have access to the internal git repository used for work. It contains a ledger file to track the hours funded by sponsors and how they have been dispatched to the various contributors. You can always know how many hours are assigned to you, how many can be invoiced, and so on. You will have to update it once a month to record the work you did (and indicate us where the report has been published).
The repository also contains a README with many explanations about the workflow (how hours are dispatched, the delay you have to publish your report, etc) and a small helper script (./find-work) to match up the pending updates (registered in dla-needed.txt) with the popularity of the package among the sponsors.
Now the work itself is relatively well documented in the LTS wiki. You will have to provide updates for packages that need an update.
You have some freedom in selecting the packages but at some point you will have to work on packages that you don’t know that are written in a language that you have almost not used. So you must be able to go out of your comfort zone and still do a good work. You must also be able to multi-task because in some cases you will get stuck on a particular update and you will have to seek help from the upstream developer (or from the Debian package maintainer). Don’t expect to be able to do all your work hours in a single run… thus don’t wait until the last days of the month. Start early and dispatch your work hours over the month.
From time to time, you will also have to handle the “LTS frontdesk” for one week. During this week, you need to spend a bit of time every day to triage the new CVE, to respond to questions on the mailing list, and to sponsor updates prepared by volunteers who do not have upload rights.Questions?
Ask your questions in the comments and I will update this section with your questions and our answers.What if I have no prior experience with security updates?
Start getting some experience. The LTS and security teams are open for anyone to join. Read their documentation and provide some updates that other contributors can sponsor.
Before accepting you as paid contributor, we generally ask you to prepare one or two DLA on your free time just to make sure that you know the workflow and that you are up to the task.What if I have only X hours available for paid LTS work?
In the git repository there’s a file where you document how many work hours you can handle. You might get less than this amount, but we generally never assign less than 8 hours (to make sure that you can handle one complicated update from start to end, or your possible week of LTS frontdesk).
You can adjust it each month or even opt-out if you are not available for whatever reason. But once you have been assigned work hours, it’s important to actually do the work that you requested!How do I apply?
Get in touch with me (as documented).
This week we have gone international with @MortenDK, who may or may not have an actual last name. He resides and is joining us from Denmark! Mario will be talking about all things front end with him while the rest of us nod our heads and pretend to understand. We have actual content in the Mail Drop, some of the great Drupal news that happened over the holidays, and of course, Ryan wraps this all up on the Final Bell.
As most of my friends and colleagues in the Drupal and nonprofit technology communities know, I joyously became a dad about a year and a half ago. Stepping into fatherhood involved a move to Denver, away from our Portland-based team at ThinkShout. Since then, I’ve flown over 100,000 miles, juggling my responsibilities as CEO at ThinkShout with those as a parent in Colorado. It’s been tricky to say the least. I am incredibly thankful for the support of my team, especially that of my thoughtful and always encouraging business partner, Lev Tsypin.
That said, it’s time for a change. It’s time for me to be fully present in Colorado, focused on my family, embracing this new community.
After a lot of conversation with Lev over the past few months, I have decided to step down as CEO at ThinkShout. I have handed over my ownership for an incremental buyout that keeps the company in a strong place financially.
I will continue to serve this team and our clients through this transition for the next three to six months as our Director of Sales. Then, I look forward to taking a break from the world of professional services and technology to try some new things. (Honest to goodness, professional pickling is on my short list. Let’s chat more about that over a beer.)
I will always be an advocate for this incredible team.
I am sad to leave right as we start tackling a new wave of technology challenges with the release of Drupal 8, as we begin to serve exciting new clients like the Humane Society, and as we kick off a new digital fundraising practice area.
At the same time, I could not feel more confident in the future of this company. We have invested heavily the last two years in our management team, organizational structure, and processes. We have attracted talented engineers, project managers, designers, and strategists. While hopefully some folks on staff will notice that I’m gone, as a team, ThinkShout will not miss a beat in serving its mission-driven clients.
ThinkShout will continue telling stories of good people making lasting change. Now I just get to tell ThinkShout’s story as fan and supporter in Colorado.
(My son Ernie is a big fan of ThinkShout, too.)
Valuebound: Free Drupal Training by Valuebound, Bangalore on Drupal Global Training Days on Feb 6th 2016
We are happy to announce that we are running Drupal training sessions on Saturday, Feb 6th 2016 as part of the Global Training Days. The initiative is run by the Drupal Association to introduce newcomers to Drupal.
Come and join us to learn about what Drupal does and how it can help you. We will learn about Drupal and build our first website live.What is a Drupal Global Training Day?
Drupal Global Training Days is a worldwide initiative to increase the adoption of Drupal. All across the world, people are teaching and learning Drupal, and sharing that open source love.What is it?
It's a full dayRead more
Valuebound: Free Drupal Training by Valuebound, Bangalore on Drupal Global Training Days on Feb 6th 2016
Yesterday I've finally donated to become a Conservancy Supporter http://sfconservancy.org/supporter/.
The reasons to donate have already been explained many times both on Planet Debian http://planet.debian.org/ and elsewhere; a few weeks ago I wrote a post (in Italian) on the Ninux community blog https://blog.ninux.org/2015/12/03/causa-vmware-per-violazione-gpl-sponsor-ritirano-fondi-a-software-freedom-conservancy/ to spread the word about it.
So, why I haven't donated earlier?
Trying to donate via PayPal from Italy (and, it seems, from Europe in general) requires a PayPal account, which I don't have and don't want to have, so I contacted them to ask for bank transfer instructions.
The first instructions I received were too complex for my online-only bank account, so I asked my bank for help, there was an exchange of emails, further simpler instructions from their bank, a small donation to test everything and time passed.
Finally, the good news: it is possible to donate to Conservancy from Italy (and probably from elsewhere in EU) using a SEPA transfer with minimal commissions and usually available from the home banking websites, so that it doesn't require significantly more effort than using paypal.
You can contact Conservancy via e-mail mailto:email@example.com to get the relevant payment data.
(Conservancy has an account in EUR which is then used to pay for expenses in EUR, so no currency conversion commission are involved.)
One OSTraining member wanted to allow site admins to show the content created by different users.
For example, the admins wanted to see all the articles written by a particular user, or all the orders they made in the store.
I'm going to make this happen by creating a search page using Views.
One of our members wondered if it was possible to automatically calculate the number of results displayed in a View.
Yes, this is definitely possible. To make this work, you will need Views, plus also the Token module installed.
Start with a long list of entries in a View, as in the image below:
Yes again, I like it that way. Twice! Anyway, we have here what is called Serbian New Year (it is again, Orthodox by Julian calendar).
So, if you missed or think you can do better New Year's resolutions - feel free to join the party (just a notice, besides firework we have a lot of gun fire here during that time. A LOT.).
Advice for everyone's resolution list: be better version of yourself, have more happy days.
Cheers. (oh, yes, get more involved in Debian)
Regular readers may have possibly noticed my unhealthy obsession with single board computers. I have recently rehomed all the systems into my rack which threw up a small issue of powering them all. I had been using an ad-hoc selection of USB wall warts and adapters but this ended up needing nine mains sockets and short of purchasing a very expensive PDU for the rack would have needed a lot of space.
Additionally having nine separate convertors from mains AC to low voltage DC was consuming over 60Watts for 20W of load! The majority of these supplies were simply delivering 5V either via micro USB or DC barrel jack.
Initially I considered using a ten port powered USB hub but this seemed expensive as I was not going to use the data connections, it also had a limit of 5W per port and some of my systems could potentially use more power than that so I decided to build my own supply.
A quick look on ebay revealed that a 150W (30A at 5V) switching supply could be had from a UK vendor for £9.99 which seemed about right. An enclosure, fused and switched IEC inlet, ammeter/voltmeter with shunt and suitable cables were acquired for another £15
A little careful drilling and cutting of the enclosure made openings for the inlets, cables and display. These were then wired together with crimped and insulated spade and ring connectors. I wanted this build to be safe and reliable so care was taken to get the neatest layout I could manage with good separation between the low and high voltage cabling.
The result is a neat supply with twelve outputs which i can easily extend to eighteen if needed. I was pleasantly surprised to discover that even with twelve SBC connected generating 20W load the power drawn by the supply was 25W or about 80% efficiency instead of the 33% previously achieved.
The inbuilt meter allows me to easily see the load on the supply which so far has not risen above 5A even at peak draw, despite the cubitruck and BananaPi having spinning rust hard drives attached, so there is plenty of room for my SBC addiction to grow (I already pledged for a Pine64).
Overall I am pleased with how this turned out and while there are no detailed design files for this project it should be easy to follow if you want to repeat it. One note of caution though, this project has mains wiring and while I am confident in my own capabilities dealing with potentially lethal voltages I cannot be responsible for anyone else so caveat emptor!