Strike action called for 31 October #fairpayinHE

Unite newsflash email: Strike action in Higher Education 31 October
Unite newsflash email: Strike action in Higher Education 31 October

Yesterday I received an email from Unite the Union. of which I am a member, calling me out to strike in favour of fair pay on Thursday 31 October.

I joined Amicus (MSF Clergy and Churchworkers branch) in 2003 which later merged with the TGWU and became Unite the Union. My reason for joining a union began with a letter I received on 11 January 2003 which gave me six weeks to leave my then position as assistant curate, a post that according to canon law requires me to be given three months’ notice. I felt wonderfully supported by the union and their advice was really helpful even if I was made to be felt like a trouble-maker by getting involved with the unions. When I moved from full-time church employment to the university in 2006 I kept my union membership up and simply moved branches from churchworkers to higher education.

A few years ago while the University of St Andrews was merging two units (Business Improvements and IT Services) the three main unions that support those working in higher education: UCU, Unison and Unite were a very present help to those of us caught up in the uncertainty of the restructure.

For the last few years these three unions have been working collaboratively to negotiate better annual pay rises for university employees, with little success. Over the last four years the following offers have been made, to the best of my knowledge:

  • 2009: 0.5%
  • 2010: 0.4%
  • 2011: 0.5%
  • 2012: 1.0%

This year, I believe, the offer was again for a 1.0% pay increase. According to the email from Unite that means “in real terms [pay] has been cut by 13%” during the past five years while the salaries of UK university principals and vice-chancellors has very often gone up. (I received a PDF of vice-chancellors’ remuneration 2011-2012 which showed that while some VCs’ salaries decreased by up to 42%, some had increased by as much as 111%!)

Over the last few years I’ve received ballot papers from Unite asking it we wanted to accept these low pay offers, and if all unions rejected the offer would we be prepared to take matters further with work-to-rule directives or strike action. Each year the vote has returned a ‘no’ to strike action from my union. Until now.

On Thursday 31 October (a week today) the members of Unite, UCU and Unison have been recommended to take strike action at universities across the UK.

There is more information about the strike on the following unions’ websites:

You can also sign the petition.

Given that strike action is such a serious sanction the unions recommend that all members observe the strike. Not doing so rather undermines the bargaining power that the unions have and makes it harder to protect its members.

The union has supported me tremendously over the last ten years, time for me to support them supporting me. So, it looks like I’m going on strike next week.

Installing Node.js on Windows 8

Command line showing node installation
Command line showing node installation

Over the last month I’ve slowly begun exploring Node.js and so far I’m really liking what I’m seeing.

In a nutshell, Node.js (or simply Node) allows you to write server-side JavaScript. In other words, until now JavaScript is normally written to be run within a web browser, on a web page. Node instead allows you to write JavaScript applications that run outside the browser or via the command line.

Node uses Google Chrome’s JavaScript engine, called V8. Perfect if you are used to writing JavaScript for your browser.

This means that you can now write applications, or ‘modules’ that can do stuff outside the scope of a web browser. For example, you could write a simple web server in Node or — and this is what I want to use it for — you could write modules to manipulate web code and automate certain processes related to web development.

Installing Node.js

Installation on Windows 8 could not have been any more straight forward:

  1. Visit nodejs.org
  2. Click the “install” button to download the installer.
  3. Run the installer (make sure you tell the installer to add references to your PATH system variables).
  4. Reboot your PC.
  5. Er…
  6. That’s it!

Command line

Almost everything you do with Node is via a command line. You can use either the standard Windows cmd.exe or Windows PowerShell (or, indeed, any other command line interpreter (CLI) you may have installed).

To use the standard Windows command line:

  1. Press Win + R (for Run)
  2. Type: CMD
  3. Click OK

Checking that Node is installed is as simple as opening a command line and typing:

node --version

Hit enter and you’ll get a result, something like:

v0.10.5

Node Package Manager

One of the great things about the Node installer is that it automatically installs the Node Package Manager. This makes it much easier to install additional applications to extend Node’s capabilities.

Again, you can check the version of NPM by typing the following into your CLI:

npm version

You’ll get an answer, returned as a JSON object:

{ http_parser: '1.0',
  node: '0.10.5',
  v8: '3.14.5.8',
  ares: '1.9.0-DEV',
  uv: '0.10.5',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1e',
  npm: '1.2.18' }

To find out what packages are installed enter the following into your CLI:

npm ls

The result will be formatted as a directory structure, like this:

C:\Users\Gareth
├── [email protected]
└── [email protected]

Obviously, to find out which globally-installed packages are available use the global flag:

npm ls -g

The first application/module that I want to investigate in depth is the CSS pre-processor Less which is used by the Bootstrap project. I will no doubt report back.