Contributors to Debian can now monitor their list of pending activities using iCalendar clients on their desktop or mobile device.
Thanks to the tremendous work of the Debian QA team, the Ultimate Debian Database has been scooping up data from all around the Debian universe and storing it in a PostgreSQL back-end. The Debian Maintainer Dashboard allows developers to see a summary of outstanding issues across all their packages in a range of different formats.
With today's update, an aggregated list of Debian tasks and to-dos can now be rendered in iCalendar format and loaded into a range of productivity tools.Using the iCalendar URL
For UDD iCalendar feeds, the URLs look like this:https://udd.debian.org/dmd/?format=ics&email1=daniel%40pocock.pro
You can also get the data by visiting the Debian Maintainer Dashboard, filling out the form and selecting the iCalendar output format.Next steps
Currently, the priority and deadline attributes are not set on any of the tasks in the feed. The strategy of prioritizing issues has been raised in bug #777112.
iCalendar also supports other possibilities such as categories and reminders/alarms. It is likely that each developer has their own personal preferences about using these features. Giving feedback through the Debian QA mailing list or the bug tracker is welcome.Screenshots
INT. RONNIE’S APARTMENT - NIGHT
Ronnie is on the phone. Vanessa is on her iPad, chuckling.
RONNIE: (into phone) Jeremy, calm down – I understand. You need the "Baby Steps" column in three days. No problem, man, I'm on it... Okay. Cool. (he disconnects) Damn. (to Vanessa) What’s so funny?
VANESSA: This comic I follow on Twitter.
RONNIE: Did you know that Twitter is built on Drupal? So is YouTube and Facebook and –
VANESSA: – Glad to see you’re getting somewhere.
RONNIE: Hey, I already downloaded a WAMP server.
VANESSA: A what?
RONNIE: WAMP. It’s an acronym for Windows... Apache... MySQL... PHP.
VANESSA: Which means?
RONNIE: I have no idea.
VANESSA: You’re procrastinating.
RONNIE: No! Yeah. I didn't realize, when I proposed writing the column, how complicated Drupal is. You want coffee?
VANESSA: It's eleven o'clock. I'm going to bed.
RONNIE: I'll just watch one of the instructional videos they have.
VANESSA: Like last night?
VANESSA: You watched Pulp Fiction for the hundredth time.
RONNIE: Pulp Fiction has always been an inspiration.
VANESSA: And the night before that, American Psycho.
RONNIE: Also inspiring.
VANESSA: Goodnight. Don't wake me up.
She’s gone. Ronnie grabs the remote.
ON TV: The Big Lebowski.
INT. MIRA SUSHI - NIGHT
Ronnie, gloomy, sits at the bar. Polo pours a martini and removes the empty glass.
POLO: She broke up with you?
RONNIE: No, man, we're just... we're on, like... a hiatus. Until I have my website built.
As Ronnie slurps down most of his drink –
Last week, we launched our new company site built in Drupal 8. Previously, it was a Drupal 6 site built ages ago and in high need of a redesign anyway. So, with Drupal 8 around the corner, what better way to learn Drupal 8 and help development at the same time?
We started exploring around the time of the first beta, and decided to write up all the bumps in the road we encountered along the way. Overall, it was a great experience and we even managed to squeeze in a patch or two to fix some bugs. Drupal 8 clearly has a lot of improvements for everybody: developers will enjoy the solid framework, frontend people get Twig, and I can't wait to show clients the quick edit functionality.
As part of a long-term collaborative partnership with the University of Victoria's Geography Department, Chocolate Lily has been working on producing a customized version of Open Outreach suitable for community mapping. In a nutshell, we have been able to take the work we produced on a customized site build in 2013 and bundle those features into a new distribution called StoriedMaps.
and finaly I have packaged, tested and uploaded otrs 4.0.5-1 to Debian experimental. :-)
Much fun with it!
A new package of mine just got to CRAN in its very first version 0.0.1: drat. Its name stands for drat R Archive Template, and an introduction is provided at the drat page, the the GitHub repository, and below.
drat builds on a core strength of R: the ability to query multiple repositories. Just how one could always query, say, CRAN, BioConductor and OmegaHat---one can now adds drats of one or more other developers with ease. drat also builds on a core strength of GitHub. Every user automagically as corresponding github.io address, and by appending drat we are getting a standardized URL.
to register my drat. Now install.packages() will work using this new drat, as will update.packages(). The fact that the update mechanism works is a key strength: not only can you get a package, but you can gets its updates once its author replaces them into his drat.
How does one do that? Easy! For a package foo_0.1.0.tar.gz we dolibrary(drat) insertPackage("foo_0.1.0.tar.gz")
The default git repository locally is taken as the default ~/git/drat/ but can be overriden as both a local default (via options()) or directly on the command-line. Note that this also assumes that you a) have a gh-pages branch and b) have it currently active. Automating this / testing for this is left for a subsequent release. Also available is an alternative unexported short-hand function:drat:::insert("foo_0.1.0.tar.gz", "/opt/myWork/git")
show here with the alternate use case of a local fileshare you can copy into and query from---something we do at work where we share packages only locally.
So that's it. Two exported functions, and two unexported (potentially name-clobbering) shorthands. Now drat away!
In An Introduction to Git Part 4, you le