Skip to content

Instantly share code, notes, and snippets.

@ForbesLindesay
Created August 2, 2014 03:22
Show Gist options
  • Save ForbesLindesay/0d404d427034420f934f to your computer and use it in GitHub Desktop.
Save ForbesLindesay/0d404d427034420f934f to your computer and use it in GitHub Desktop.
This is the email I sent to callback@strongloop.com to detail my concerns surrounding their recent aquisitioin of express

Dear Issac Roth,

I am writing, as per you request (https://twitter.com/ijroth/status/495402251490316288) to raise my concerns about the recent handling of express.js by Strong Loop. I understand from reading everything I can find online that TJ Holowaychuk was consulted before the move and that the idea of sponsoring was raised with the maintainer (although the full extent of this move was perhaps not fully understood by everyone). However, there are a few things that still concern me:

  1. No consultation seems to have occurred with the wider community.
  2. In your post announcing the change http://strongloop.com/strongblog/tj-holowaychuk-sponsorship-of-express/ you describe your first order of business as "is to get familiarized with the project’s practices, release processes and get started on more visible community contributions”. This does not appear to correlate well with your actions of immediately transferring ownership of the repo to a strongloop location.
  3. Pull requests are not being handled in a manor consistent with a well maintained open source project (expressjs/express#2266) - note that they used to be.

It is too late to really do anything about point 1, so I will move on from that and trust that Strong Loop have learnt this lesson.

As for the location of the repository (point 2). I think it’s clear from discussions both in GitHub and on Twitter, that the community feels the express repository, and the corresponding repository for the website both belong in the expressjs organisation. This seems like a simple thing to fix that will vastly reduce the animosity that the community feels towards you.

The pull request I referenced in point 3 is perhaps an un-related issue, but I still feel it has not been handled in a way that will ultimately lead to a good resolution. The change appears to have been rejected on grounds that the diff is too large, despite broad support for the change from everyone in the issue tracker. Further, the suggestion of alternative ways to contribute to express are not only unhelpful, but somewhat patronising. By submitting a pull request I have already demonstrated that I have a grasp of how GitHub work, and can browse the issues on my own. The purpose in submitting a pull request was not to raise my profile or feel like I was contributing, it was to fix something that has bugged me for a long time, and is almost certainly also bugging some significant number of other people.

Forbes Lindesay

@Fishrock123
Copy link

We want to make Express easier to use, as you do.

Docs! :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment