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
The Github iCalendar feed has now been updated to scan issues in all of your repositories.
It is no longer necessary to list your repositories in the configuration file or remember to add new repositories to the configuration from time to time.Screenshot
Notice in the bottom left corner that I can switch each of my feeds on and off just by (un)ticking a box.
Since the last Drupal Core Update on January 12th, the Drupal Association awarded the first round of the new D8 Accelerate grants; nominations for the Drupal Association Director at Large have opened (and there are already some candidates); and, in spite of the blizzard raging outside, the contributors at the Drupal 8 core critical issues sprint at DrupalCamp NJ fixed 12 critical issues, 4 major issues, plus moved another 7 criticals and 7 majors forward, and more in the Drupal 8 menu links system!
Some other highlights of the month were:
- Drupal turned 14; and Joe Saylor posted the results of the recent community survey.
- The Drupal.org team posted the Drupal.org usage statistics for 2014.
- Amazee Labs launched their first Drupal 8 customer website!
- Pantheon hired long-time Drupal contributors Greg Anderson and Kate Klingman as dedictaed Open Source Contributors!
- The Promoted to front page and Sticky at top of lists checkboxes and their descriptions were re-worded to be less-technical and easier to understand.
- On the front-end, breadcrumbs were removed from the page template and put into a block, linking to a file from a Twig template was made easier, and HTML classes were moved from preprocess functions into templates.
- On the back-end, format_plural() was removed, and comments now use entity validation.
- On and off the island, a number of third-party libraries were updated: Symfony, CKEditor, PHPUnit, jQuery UI, html5shiv, normalize.css and jQuery Touch Punch; and it became easier to install Drupal to the correct folder with Composer.
- On the performance front, Route enhancers are now run lazily, page caching code was moved to the middleware, and drupalSettings.ajaxPageState was optimized.
- Sascha Grossenbacher (Berdir) made a script that run tests on all the contributed modules with D8 branches and testing enabled and displays the results.
See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.
Even if you're not yet familiar with Drupal 8's code, we need people with Drupal 7 skills to make changes to Drupal.org's infrastructure and fix contribution barriers so that Drupal.org is ready for Drupal 8's release. Check out the meeting notes for more information.
We're also looking for more contributors to help compile these posts. Contact xjm if you'd like to help!Drupal 8 In Real Life
- DrupalCon Latin America 2015 is coming up fast! It starts on February 10th! If you're looking to buy a ticket, you need to do so before February 8th if you want to take advantage of regular ticket pricing! The price goes up USD$36 if you wait to buy your tickets at the door!
- The MidWest Developers Summit is happening on August 12—15. More details later this year.
Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!
Accessibility matters. For everyone. For those of us who build the web, and for those who use it too. All of us.
Here's a couple of great resources that caught my attention in recent days.
Anne Gibson writes that "Web accessibility means that people can use the web." in an article on List Apart about Reframing Accessibility for the Web. It's really good. She advocates creating a test matrix for accessibility and putting the focus back on the technology available, rather than the abilities of the people who use it. This is strong, clear practical advice we should all consider.
Discovering these two resources pushed me to reframe some recent conversations about meeting these guidelines. We often get stuck debating compliance details, when really we should be thinking about setting our content free as flexibly and cleanly as possible. We're not just ticking boxes. At least, I hope we're not.
Drupal is one of the best content platforms for web accessibility, but it still has shortcomings. Unfortunately, many people who lack the deep understanding of what makes accessibility important still build sites that don't meet WCAG guidelines. I think it's up to all of us to spend a bit more time getting up to speed on the intricacies, and build it into our practice, and not just meet those guidelines, but exceed them!
[Image from from the W3C's Web Accessibility Initiative Guidelines and Techniques page - Read a description of this image ]
This is the last post this blog sees; professional content will continue to be posted on the Tag1 Consulting blog, personal ramblings will disappear. I already asked for this blog to removed. I would like to say in closing: the future of Drupal blog post was not meant to be a critique of Acquia who puts several people full time on Drupal core and contributes more money on top. The future of Drupal blog post was -- or tried to be -- about what I feel the future of the Drupal is: an enterprise-y software with a formal governance on top of the community. Not for the first time my intentions and what people managed to read out of my words are clashing so wildly that it's better not to post more here or the issue queue. Work still requires me to do the latter but I will try to stay away from architecture decisions and any such controversial topics.
I met Ian Read, Front End Development Team Leader at TSO/Williams Lea Public Sector at Drupal Camp Brighton, where I found out that he has recently been involved in a subject close to my heart: Drupal and government. He was part of the team that designed and built the attractive, responsive, and very functional London Borough of Croydon's new council website. In our conversation, we touch on the value that the Drupal community provides to everyone involved; Drupal and innovation in government digital services; the thought process, needs, design and more that went into the new Croydon Council Drupal website; and more!
Thanks to akira for the confetti to celebrate the occasion!