Starting Monday, you can vote for the next at-large director on our board. Before you do, our candidate sessions: https://t.co/B0lUqmUac4
— Drupal Association (@DrupalAssoc) March 4, 2016
Drupal Association Board Elections are around. So what are these elections? How would it matter to anyone in the Drupal community? Why should one vote?
The At-large Director position is Drupal Association’s way to ensure community representation on the Drupal Association board. ie, you could have a share in shaping the future of Drupal Association by voting for the right candidate whom you think would best represent the community’s interests. You can see the list of candidates competing for this here. More about the election process here.
I have decided to vote for Shyamala Rajaram. I met Shyamala for the first time in November 2008 at a Chennai Drupal Meetup, which she had organized. I had just moved into the city, for my job at TATA Consultancy Services. That was my first weekend in Chennai. Didn’t have many friends around and a lot of time to kill. Drupal, at that time to me, was one of the many CMSs that I had freelanced earlier. Although it was my favorite. But I never saw it as a career option. And was surprised to see a meetup happening in Chennai that weekend and thought of dropping by.
But the meetup definitely had a significant impact on my life and career. I had dabbled a lot with Drupal while in my college (Vellore Institute of Technology). Though Drupal was my favorite, I had always seen in as one of the many CMSs that were mushrooming every day in the PHP ecosystem. This specific meetup gave me an opportunity to see that Drupal and its community existed outside of the internet as well ;-)
And what surprised me the most was that the newspaper portal that I read every day then, one of the largest in India, was actually powered by Drupal, and architected by none other than Shyamala and her team!
Being one of the first adopters of Drupal in India, Shyamala has been organizing meetups in and around Chennai since 2007. She has spearheaded many community initiatives, including taking Drupal to Colleges in and around Chennai.
I believe she has the right mix of leadership and technical capabilities and can best represent the Drupal community in general, and India & Asia in specific, on the board of Drupal Association. All the very best Ma’am!
A few weeks ago I had to go through the process of setting up php code sniffer on my new computer, and realised how confusing most of the blog posts out there are and how many loops and posts you have to jump through to get it set up.
I decided to write a quick post with all the commands in one place and small descriptions for most of the commands:Installing Drupal Coding Sniffer
1. Download php code sniffer (source code: https://github.com/squizlabs/PHP_CodeSniffer)
curl -OL https://squizlabs.github.io/PHP_CodeSniffer/phpcs.phar
curl -OL https://squizlabs.github.io/PHP_CodeSniffer/phpcbf.phar
sudo mv phpcs.phar /usr/bin/phpcs
sudo mv phpcbf.phar /usr/bin/phpcbf
sudo chmod a+x /usr/bin/phpc*
Test that it's installed by running phpcs -hand it should output the code sniffer help.
2. Download the Coder module
Note: download the 8.x branch, even if you intend to use it on Drupal 7.
You can download it in any 'normal' folder, but not in a Drupal project.
drush dl coder
It should download the latest version which is 8.x - if it doesn't then add --select to the drush command and choose the 8.x branch.
3. Add Drupal standards to PHP Code Sniffer
Tell phpcs to use the Drupal standards from the downloaded Coder module:
sudo phpcs --config-set installed_paths /folder/where/i/want/coder/coder/coder_sniffer
At this point you have PHP Code Sniffer set up with Drupal coding standards.
You can use it from command line by running:
phpcs --standard=Drupal file/to/check
or add it to your favourite text editor/IDE.Adding code sniffer to Sublime
Here are the few steps you need to follow to add it to Sublime Text 2/3:
1. Download the Sublime Build file from the repo: https://github.com/sirkitree/DrupalCodingStandard
wget https://raw.githubusercontent.com/sirkitree/DrupalCodingStandard/master/DrupalCodingStandard.sublime-build -O ~/.config/sublime-text-3/Packages/User/DrupalCodingStandard.sublime-build
If you don't know where your Sublime installation saves its packages then open Sublime, go to Preferences > Browse Packages, and replace the above path with yours.
2. Activate the Drupal Build file by going to Tools > Build System > DrupalCodingStandard in Sublime.
3. Open any Drupal file and hit Ctrl (Cmd) + B to run the sniffer on that file.Adding code sniffer to PHPStorm
I have recently started using so am slowly getting used to it and setting up features I used to use in Sublime. Adding PHPCS to PHPStorm is simple and only takes a few steps.
Go into the Settings and either search for the keywords 'code sniffer' or go to Languages&Framerworks then Code Sniffer under the PHP section.
In the Development environment I have chosen Local and clicked on the ... next to the drop down. Add your /usr/bin/phpcs path to the phpcs path and click Validate to make sure it picks it up.
Now that you have phpcs added as a code sniffer we need to tell the 'Inspections' to use it.
In the same settings window, either search for 'code sniffer' again, or go directly to Editor > Inspections. Tick the box for PHP Code Sniffer validation under PHP and then choose the 'Coding standard' from the right hand pane. If the only values in the drop down are 'Custom' or you cannot find 'Drupal' in there then hit the little 'refresh' button next to the drop down and it should pull all the coding standards added to your php code sniffer. Then choose 'Drupal' from the drop down and you are good to go.
The code sniffer will start adding errors/warnings inline in Drupal files, or you can run a code inspection manually by going to Code > Inspect Code and choosing either the whole project or the current file.
This time, three talks were given:
- Kentaro is "groonga"(an open-source fulltext search engine and column store) upstream author and package maintainer in Debian and Fedora. This talk is about his experience how to use Debian "porterbox" for non-DDs.
- "Porting Debian to tilegx" by @wskoka
- About his experience porting Debian to tilegx architecture, multicore processor family by Tilera. He is not porting expert ("I'm sale person", he said :), but did try&error and now apt is working on that machine.
- "Introduction to Debian Ports" by John Paul Adrian Glaubitz
- Adrian comes from Germany(!) and gave a talk about debian-ports.
During break time, did some discussion, GPG keysigning and enjoyed coffee and sweets provided by Cybozu, thanks!
And thanks for all participates!
We have a made numerous changes to Rblpapi since the previous release 0.3.2 in early December. You can see the commits, or look at the ChangeLog or NEWS.Rd to get an indea of the changes. We have new functions, improved internals, bug fixes and more.
In order to facilitate more widespread testing, I have just placed source and (Windows) binaries in the ghrr drat repo from which you can install the new version simply viadrat:::add("ghrr") # if you have drat installed install.packages("Rblpapi") # uses the drat version b/c higher version number than release
Alternatively you can also dodrat:::add("ghrr") # if you have drat installed update.packages() # refresh all packages against all repos
We would appreciate wider testing, and feedback / bug reports / ... via the issue tracker. PRs with unit test suggestions would also be most welcome -- we now use RUnit and run the tests if a file ~/.R/rblpapiOptions.R exists which sets the options() values for automatic connection (see help(blpConnect)) as well as the blpUnitTests=TRUE option. This is needed to 'opt-in' as standard test setups at [Travis])(https://travis-ci.org/) or CRAN will not have access to a Bloomberg terminal.
It took nearly a year, but today a new ftpsync version got released. Most of the work for this release was done by weasel, with one new feature submitted by waldi, my work was mostly style fixes and a bit of documentation. And of course the release now.
If you run a mirror, you will find the new version at the usual place, that is the project/ftpsync/ subdirectory. You may also want to subscribe to the debian mirrors mailinglist, as the mirror team will post more information about changes in ftpsync there.
Shortly after starting with the porting I resented not having a live preview of my work. I guess I got addicted to it with staticsite.
Actually, staticsite does preview interlinked Markdown files. I wonder if GitHub supports cross-linking between Markdown files in the same repo? It does, and incidentally it uses the same syntax as staticfile.
It shouldn't take long to build a different front-end on top of the staticsite engine just for this purpose. Indeed it didn't take long: here it is: mdpreview.
So, as you are editing the README.md of your project, you can now run mdpreview in the project directory, and you get live preview on your browser. If your README.md links to other documentation in your project, those links will work, too.
mdpreview uses the same themes as staticsite, so you can even tweak its appearance. And if you need to render the documentation and put it online somewhere, then staticsite can render it for you.
I experimented with it splitting staticsite's documentation into several parts, a I had great fun with it.
So, you want live preview of your project's Markdown documentation? mdpreview
When you are happy with it you can commit it to GitHub and it will show just fine.
You want it to show on your website instead? Build it with staticsite.
I'm considering merging staticsite and mdpreview somehow. Maybe mdpreview could just be a different command line front-end to staticsite's functionality. That's food for though for the next days.
Would you prefer to preview something else instead of Markdown? There is actually nothing markup specific in staticsite, so you can take this file as inspiration and implement support for the markup language of your choice in this whole toolchain. Except maybe for GitHub's website: that doesn't run on staticsite (yet).
It's time once again for the annual 7 Day Roguelike Challenge. I know I said I wasn't going to take part again until I properly finished one of my previous entries but I've thought of an interesting and novel game mechanic that I'm eager to try out so what the hell.
If you are interested in following my progress, I will blog about it here starting from Monday and (hopefully successfully) finishing on the following Sunday.
Of course the best part of it is coming up with names. Here are this years choices:
- Make Narnia Great Again
- Thane of Groans
- I Am The Black Wizards