:::: MENU ::::

Goodbye Collabora, Hello phpList

It’s official: I’m the new C.E.O. of phpList Ltd.. After more than a year marketing LibreOffice products and services at Collabora, I’ve moved to managing the leading Open Source email newsletter app.

Following his 15 year term as Founder and Managing Director, Michiel Dethmers has entrusted me with the future of the project as the company reshapes to fulfil new potential.


The Open Source email newsletter and marketing solution

phpList’s history and established position give it a uniquely important role in the future of digital marketing and the promotion of Open Source. For people who value trust and transparency from their email marketing solution, phpList is already the best choice. Currently we send millions of emails each week from our hosted service, and have empowered others to send a further 21 billion messages this year using our software independently.

To have an impact on the norms of digital marketing generally however, we need to grow new services to bring our brand of permission-based marketing to broader audiences.

Fortunately, there’s never been a better time to do this, as email marketing continues to dominate as one of, if not the most, effective forms of digital marketing. The world’s appetite for email marketing services is reaching ever new heights, with The Guardian calling 2015 “The Year of the Email Newsletter“.

Look out for new services on phplist.com taking advantage of these trends in early 2016!

A little history

Back in 2008 I first set up phpList for an early client, Don’t Travel Empty (DTE), the automated vehicle-sharing service for passenger transportation companies. Tens of thousands of emails followed over the next three years while I served as DTE’s Head of Development.

Simple Christmas postcard delivered in 2009 using phpList

Simple Christmas postcard delivered in 2009 while working for a previous company, using phpList

Anna Morris joined phpList as Community Manager in early 2014. A friend and ex-colleague from FSFE, Anna opened a personal connection between me and the firm, and the door to two years of give and take, advice to and from the company, on many aspects of Open Source code, community, and commerce.

Anna Morris, phpList Community Manager, and I on Corby Beach during a visit in 2014

Anna Morris, phpList Community Manager, and I on Corby Beach during a visit in 2014

After helping out at the first phpList code sprint in the summer of 2014, I had a good feel for the project’s plugin system, and by January this year, had undertaken to develop a new REST API.

When a foreign competitor made moves to purchase the company a few months later, I reached out to Michiel, concerned to keep the business in the hands of people who understood and appreciated its Open Source roots. Soon after we hatched a plan for phpList’s new direction, and new C.E.O.. A couple of flights and meetings later, and the paperwork had dried.

Productive friends

With Collabora CloudSuite on the cusp of global launch, it was hard to leave Michael Meeks, Kendy, Andras, Miklos, and the other leading lights of the LibreOffice community who were my colleagues at Collabora. Promoting their amazing work since August last year has been an incredible privilege, as well as the opportunities to announce LibreOffice for Android, and LibreOffice Online.

Open Source business is tough, especially in the enterprise sector, and I’m grateful for the invaluable commercial lessons that Michael and Niall McCarthy have taught me in recent months. These principles are now at work in a new team, and a new market. Roll on the next phase: roll on phpList!

Notes on announcing an Open Source product

When you announce a new product you want your company to be the center of attention. All the time and resources invested in developing it must translate into exposure that you can control, and ultimately convert into business. We Open Sourceres face unique challenges in predicting and shaping public perception about our software. Simply put, we must own our own news.

In the run-up to my announcement of Collabora CloudSuite, the LibreOffice-based Google Docs competitor, the clock was ticking to announce first, and announce loudest, news over which I had little control.

The race to announce

As Jeremy Irons says: “to make a living in this business, you must be first, be smarter, or cheat.” As he concludes in the movie Margin Call, being first is the best out of three. When operating in the open, announcing your work first is critical to set the backdrop, framing, and focus of the news, and to capture all available traffic for yourself (and your lead forms).

Yet public Git repositorious can be accessed by anyone; source code can be built, unstable code tested, and unfair assessments made. Collabora develops LibreOffice in communitiry repositories — in January, journalists knew about LibreOffice for Android before I had announced it. The more astute among them had followed the commits, and responded to my release announcement with “what’s new about that?”.

Pre-emptive statements can be very effective at fertilising the ground of your future work: announcing that work has begun, or your direction has been set, can help establish yourself as the authoritative source for what comes next. Announcing earlier than you’d like to is better than re-announcing yesterday’s news. However this cannot protect you from another threat: your own engineers stealing the limelight. 

We want our engineers to be community leaders, well-known contributors and constant communicators. The coder who routinely showcases their own work in blogs, videos and social media is a powerful asset indeed.

But the affect can be powerfully antagonistic when uncoordinated with a new product announcement. Finding an impromptu preview of a hot unannounced feature in my G+ timeline more than once elicited a “wow” followed by “oh shit”, followed by rapid-fire emails to the esteemed hacker responsible. Keeping engineers aligned with announcement timelines is a critical ongoing task to encourage their valuable engagement without compromising wider goals.

Working in the open entails giving up control that proprietary software companies enjoy. It’s nigh on impossible to keep big secrets among a large developer community. But by working harder, planning better, and managing relationships more closely than closed source rivals, Open Source product announcements can impact the right people at the right time.

Interview on Collabora deal with UK Government

UK Authority, a publication dedicated to digital public sector news, published an article this evening after interviewing me by telephone in the afternoon. Happy to be quoted in this decent piece:

Crown Commercial Service strikes deal for open source office suite

Agreement with Collabora provides fresh momentum to use of open source in public sector

Sam Tuke, marketing manager for Collabora, told UKAuthority that the deal is similar to those previously arranged by the CCS with proprietary software suppliers such as Microsoft and Oracle.

This follows several articles yesterday which picked up yesterday’s press release, including:

  • The Register (“Oh dear, Microsoft: UK.gov signs deal with LibreOffice”)
  • The Inquirer (“UK government deals blow to Microsoft with LibreOffice love-in”)
  • Silicon Angle (“U.K. gov embraces Libre Office, kicks Microsoft into touch”)
  • Golem (“UK authorities to license commercial LibreOffice”)
  • Pro-Linux (“Great Britain relies on LibreOffice”)
  • OCS Mag (“LibreOffice officially made available for all UK Government agencies nationwide”)


Serious baggage: the best laptop backpacks for professionals

I don’t usually write posts like this. Product reviews etc. are outside of my Open Source realm. Over the last month however, my quest for an elite laptop backpack has revealed a chasm between the best that the market has to offer, and the bags that review websites typically recommend.

Screw PCAdvisor. To hell with T3. Thule, HerschelFjällräven, and Wenger all make nice bags. But for a certain class of commuter, aesthetic articulation and identity originality are just as important as inspired design and practical features.

Perhaps it’s because they’re newly released. Maybe it’s because those who’ve discovered them guard their secret. But for some reason, the following bevy of bags lack the coverage that they deserve. Thanks to John Ngo for pointing me at several of the products below.

My criteria

I use my backpack virtually every day of the year. Whether fetching groceries, hauling gymwear, stowing shirts for a conference on the continent, or ferrying laptop, headphones, ergonomic peripherals, and myriad cables to the office, my backpack is my stalwart companion, on foot, on train, and on bicycle. Therefore I  judge the bags on the following merits (in no particular order):

  • Airflow to one’s back (for comfort and sweat)
  • Reflective panels / night visibility
  • Quality of craftsmanship
  • Quality of materials (especially zips)
  • Aesthetic design
  • Distinctive appearance
  • Layout originality
  • Easy access pockets (e.g. for water bottle and umbrella)
  • Multiple large compartments (to separate clothing from tech)
  • Waterproofing
  • Comfort of wear
  • Multiple carry options (e.g additional carry handles / packable straps)
  • Balance of size and capacity
  • Secure accommodation of laptops of multiple sizes

My best backpacks

Booq Cobra Squeeze

Beautiful and distinctive bag made from high quality recycled materials, with good access, excellent size to capacity ratio, and good laptop compartment padding. Unfortunately it’s made for macbooks only with a very tight fit. My Dell XPS 15 didn’t stand a chance; the bag went back.

Book Cobra Squeeze

Book Cobra Squeeze

Côte&Ciel Isar Twin Touch

Incredible, distinctive design from one of the highest quality backpack companies around. I generally prefer vegan wearables, but the calf leather frame on this beauty is in a class of its own.

Côte&Ciel Isar Twin Touch

Côte&Ciel Isar Twin Touch

Mission Workshop Arkiv VX /R8

A striking, militaristic bag with extreme practicality, with the unique benefit of customisability via velcro accessory system. “Build your own bag” and attach and detach components as necessary. From the Mission District of San Francisco (their store is a thing to behold).

Mission Workshop Arkiv VX /R8

Mission Workshop Arkiv VX /R8

Incase Halo Courier

Incase had to have a bag here, but choosing which was hard. Customers rave about their design and attention to detail, and clearly this company is doing many things right (especially their EO range — see their brilliant but boxy offering in the honourable mentions). Unfortunately aesthetics have been lacking across their range however, with square monochrome bags coupled with limited colour choices. This bag however breaks from this trend with a flash of neon yellow, and though the ICON and City bags offer more structure and better size to capacity ratio, the Halo Courier introduces the critical component: handsome looks.

Incase Halo Courier

Incase Halo Courier

Honourable mentions

These bags didn’t quite make the cut, whether because they prioritise good looks a bit too much (in the case of the Côte&Ciel Nile), not enough (the Osprey Nebula 34), or have too much, or too little capacity (the EO Travel / Evoc Commuter, and Boa Squeeze respectively). They are noteworthy nevertheless, and deserving of your attention.

What stops small Open Source businesses selling to UK Government?

On June 26th Open Source leaders met in London for a gathering called by the Community for Open Interoperability Standards — the UK arm of Open Forum Europe, the European Open Source software advocacy group. At a beautiful venue beside the Museum of London, we were hosted by Worshipful Company of Information Technologists at Barbican station.

Ostensibly intended to determine the organisation’s top political goals following the victory of a majority Conservative Government after the general election last in May, themes covered a number of areas where Open Source has made progress, and should make more.

Time Title Speaker
10:20-10:30 Introduction Chris Francis, Chairman, OFE/COIS, Government Relations, SAP
10:30-10:50 Digital Single Market Common Themes EC/UK Graham Taylor, CEO OFE
10:50-11:10 Local Government IT: Future Directions John Jackson, Assistant Director (ICT) Camden Council ICT
11:10-11:30 Small and medium enterprise role in Government IT Sam Tuke, Marketing Manager, Collabora
11:30-11:50 Education IT: Future Directions Matthew Dovey, Principal Consultant, Jisc, Chair, EGI Council/Executive Board
11:50-12:10 The role of CCS in Open IT Standards Richard Archer, Deputy Chairman, OFE/COIS, CEO Bramble Hub
12:10-13:00 Round Table: Conclusions/Future Plans of OFE/COIS Chris Francis, Chairman, OFE/COIS, Government Relations, SAP

I spoke mid-morning, identifying hurdles currently preventing small and medium enterprise successfully selling to the British Government, highlighting opportunities presented by these challenges, using my experience of marketing LibreOffice products at Collabora Productivity as an example.

I concluded that by working together we can overcome some of the most serious barriers to UK public sector contracts, such as the current government’s “cloud-first” strategy, and buyers continued preference for solutions from incumbent ventures. You can find my slides below.

My presentation on SMEs role in UK Government

My presentation on SMEs role in UK Government


Whitelisting subdirectories using Git’s .gitignore

Git’s handling of directories and wildcards doesn’t follow bash conventions. First glance at a .gitignore file can easily mislead you into thinking that typical directory references will work recursively and allow whitelisting of many directories at a time. But directories don’t really exist for Git, or at least not as you’d expect.

Here’s how to whitelist a subdirectory multiple directories deep in your file-structure, keeping all other files and directories blacklisted.

The problem

Assume that we’re working on a WordPress plugin on a local development server, and that we want Git to only track changes to our plugin, and not to WordPress core files, or other installed plugins. Note the following directories (all paths are relative to the repository root):
wp-includes # we want to ignore this core wordpress dir
wordpress/wp-content/ # a parent of the dir we want to track
wordpress/wp-content/plugins/ # also a parent of the dir we want to track
wordpress/wp-content/plugins/my-new-plugin # the dir we want to track

Of these, all should be ignored except for the last — we only need to track changes to files in “my-new-directory/”. The following .gitignore file might be your first attempt. This won’t work:
# contents of .gitignore -- won't work
* # ignore everything
!wp-content/wp-content/plugins/my-new-plugin/* # whitelist the contents

The above will result in all files being ignored, including the ones we want to track.

The solution

Every directory between the repository root and the subdirectory that should be tracked must be whitelisted separately, without recursion, and with trailing slashes, plus an additional recursive path to that subdirectory, in order to whitelist its contents. Here’s what that looks like:
# contents of .gitignore -- works
* # ignore everything
!wp-content # whitelist parent directory
!wp-content/plugins # whitelist the other parent directory
!wp-content/plugins/my-new-plugin # whitelist the actual directory
!wp-content/plugins/my-new-plugin/* # whitelist the contents

Good luck adapting this to your needs; improvements and extensions welcome!

Marketing mechanics: first day at phpList

Today I start a new job writing Open Source marketing tools for phpList – the email newsletter sending app. Like MailChimp and SendGrid, phpList lets users design, write, send, and track emails to large numbers of people from a simple web interface.

Specifically, I’ll be working on a new API to allow other apps to connect to phpList securely and handle subscribers and newsletters, and send mails. Once that’s done, I’ll be implementing the API in new software, but we’re saving those details for later. Suffice to say that managing newsletters using phpList should become increasingly convenient and accessible over the next two months. Stay tuned.

Email marketing

“What is email / newsletter marketing anyway?” you may be asking yourself. “What does Open Source have to do with it?”. Email marketing remains the most effective form of digital marketing, and is a central component of any promotional campaign. That makes it critical to all forms of business, especially when users have actively sought newletter membership. When campaigning for digital rights at FSFE, GnuPG, LibreOffice, and others, I’ve used such tools to spread the word about political developments and engagement opportunities. Hundreds signed up to receive news about the GPG crowdfunding campaign in winter 2013, for example, allowing me to notify them of new rewards and opportunities as the campaign progressed.

The software that performs these functions must be reliable and effective. Furthermore it must be trustworthy, which makes the availability of strong Open Source contenders in this field particularly important. Mailing list managers, as the apps are sometimes called, typically manage hundreds of thousands of email addresses, sometimes with other identifying information as well. This data is valuable – first and foremost to the people it identifies. Information must be stored securely, yet remain transparent and accessible to newsletter subscribers (allowing them to update details or opt-out, for example).

Kicking off

For more than a decade phpList has provided a competitive solution in an Open Source package, allowing organisations to host their own email campaigns and keep their user’s data local. I’ve used it since 2008, and trained companies I’ve worked for to use it too. Having dipped into the codebase in June last year at the API sprint event, I’m grateful to finally have the opportunity to work more consistently on the project and functionality. Let’s say it’s an itch I’ve had for quite some time.

My Linux Audio interview in Ubuntu User

It was months in the making, finally reached news stands last month, and now it’s free to read online. That’s right, you can read my five page interview with Harry van Haaren on the Ubuntu User website. The printed copy looks much prettier however, and also includes a three page guide to using Harry’s suite of audio tools, branded Open Audio Productions.

5 page Ubuntu User article by Sam Tuke

The article printed in Ubuntu User

If you’re into making music on Linux, Harry’s work is really exciting. His apps, like the Luppp looping workstation for live performance, produce quality results regardless of musical genre. They fill an important gap for electronic music fans however, with a wide range of plugins for manipulating sounds for things like side-chain compression (present in most dance and electro tracks), and drum sample playback. Sorcer, his wavetable LV2 synth, is also pretty much the best there is.

You can get your hands on the magazine at your local newsagent for £8 in England, about €10 in Europe, or €13 online (either digital or print).

Fix Firefox fullscreen video bug on Gnome 3

Does this sound like a familiar scenario?: You’ve found your favourite Seinfeld clip, you’ve waited for it to buffer, you’ve clicked fullscreen mode, swiftly alt-tabbed to check your mail (the thousandth time today), switched back into Firefox, clicked fullscreen again, only to find the comedy genius’ face has vacated your screen, or frozen, glass-eyed and unanimated, as the sound plays on? Seinfeld may be impossible to dislike, but this bug certainly isn’t.

Seinfeld clip on TouTube screenshot

Seinfeld’s “The Deal” in Firefox

To put the problem another way, fullscreen video only works the first time it’s attempted, and thereafter fails to show any images at all.

After what feels like years of suffering from this bug, a newbie Fedora convert last week encouraged me to cure the itch. Here’s how to fix it, adapted from Mozilla’s guide for Ubuntu.

The fix

  1. Press the meta (aka “windows”) key then type terminal.
  2. Open the terminal app, then type or paste:

    sudo gedit /usr/share/applications/firefox.desktop

  3. Enter your password, hit enter.
  4. Scroll to the bottom of the text in the editor that should have opened (that’s Gedit), and look for the line that reads Exec=firefox %u
  5. Replace it with this:

    Exec=env LD_PRELOAD=/usr/lib/libGL.so.1 firefox %u

  6. Then save it (ctrl + s), and close gedit (file menu -> close).
  7. Now restart Firefox and the problem should be solved.


What we do here is basically change the command that Linux uses to run Firefox. Instead of running it directly (%u means use the same window if new links are opened, instead of creating new ones), we preload a graphics library first (libGL). That graphics library handles the fullscreen switching properly.

Good luck!

Tip: install Hebrew fonts on Fedora Linux

Here’s a one line command that will install additional Hebrew fonts on Fedora 20. There’s a fair few in here, including a Free version of Hebrew Arial (much sought after). They’re all in repositories already so with yum it’s a breeze:

sudo yum install culmus-* alef-fonts* google-noto-sans-hebrew-fonts