Skip to content

Instantly share code, notes, and snippets.

@dougwilson
Created July 30, 2014 23:06
Show Gist options
  • Star 7 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dougwilson/f68806eea979867c696b to your computer and use it in GitHub Desktop.
Save dougwilson/f68806eea979867c696b to your computer and use it in GitHub Desktop.

I have seen some chatter on Twitter, GitHub and other places talking about the recent change of the Node.js project express moving from visionmedia to strongloop in GitHub and I wanted to share my point of view.

Couple points up-front:

  1. I have nothing against StrongLoop, Inc. (the Delaware corporation) and I'm sure they are very talented and motivated.
  2. I have nothing against TJ and actually think it's really awesome that he got something for a lot of the work he has put into express and related projects over the years.
  3. I have not, nor wish to, receive any money around express.

So, from my side there are a few things. Yes, TJ emailed me regarding StrongLoop sponsoring expressjs.com and writing documentation and tutorials and I welcomed such a sponsorship. There was probably some mis-communication in this regard, as I had interpreted it as we would plaster their Logo on the site and/or repo README in a "Sponsors" or such section in return for some awesome documentation, tutorials, etc.

I was not aware the repositories on GitHub would be moving anywhere, though. If I did, I would of at least done some prep to change links, fix badges, Travis CI setup, Coveralls.io setup, etc. but since StrongLoop did not ask the "Lead Maintainer" anything prior to the move, some basic repository-moving maintenance was of course not even done.

As for why I have not been participating in express since the change, I can simply say that StrongLoop has left me feeling taken advantage of. As far as I can tell, there was some kind of implicit expectation that I would just carry on my merry way with express no matter where it went, for free, of course. I didn't even get a "Hey, Doug, so we bought express from TJ and love what you are doing with the project and would like you to continue to lead and maintain it. How can we make this work?"

I take a lot of time out of my life to not just add commits to express and friends (that's not much time), but to answer completely every single issue and PR that is opened on GitHub and try to work with the folks to resolve their issue. I even idle on #express and answer questions. It's a huge time-sink that I do, and it does not seem like StrongLoop as a new owner wants to put any resources of their own into doing this and would rather the community to just continue to do this on it's own for nothing.

I have not seen anyone from StrongLoop trying to support anything through the issue tracker before the change, still have not seen anyone from StrongLoop helping out in the IRC channel nor the Google Groups mailing list. I would hope that a for-profit company would support something it "owns", as it is gaining value from the project. I'm sure they help people who have questions about their paid products.

@BrunoWinck
Copy link

I'm running a private software vendor business and moved to NodeJS+Express exactly a year ago exactly as Nicholas explains: for express. I use NodeJS for the web server layer of my software. Before I was using LAMP and even before IIS+ASP. It was way to heavy and when I get introduced to NodeJS in a mooc (https://medium.com/@brunowinck/a-studious-summer-52d83dbd77f6) I recognized its value and urged the change. At first a bit reluctant to upgrade to 4.0 I admit it was really worth. Parts of the app can now be modularized, tested on their own. The eco system around expressjs is very interesting. It promotes alternatives implementations and value to the modular, dynamic nature of NodeJS.
Enthousiasted by NodeJS, I built a genereic extension to hook all our c++ modules (the kernel is in c++, reason why I'm not concerned by lack of performance, threading, concurrency). I could see that what's behind is easy to use and in order, portable (v8, libuv) this was one more plus for me. After I started to follow the communities around (google group, etc). i would say that after a year I start to have a decent knowledge of he beast. If I really need to fix something in the whole stack to save my business I know I can do it and I felt I can trust this choice.
I was a bit surprîsed and sad.to read the message from TJ few weeks ago and was wondering how I could help. it's his choice and a different topic. I don't have a lot of time but I was preparing myself to jump and to apply to be a kind of backup maintainer for something. Give back to the community, encourage other 'for profit' to join in. I have the feeling that I got a lot more from Express in one year that I had from the PHP group for 10 years. I suspect that the takeover of Zend on PHP is partially for something.
Now Strongloop comes into play.I've been reading around for the last 3 days. I feel concerned. What I have to bring in is the point of view of 'for profit' user, non maintainer and 25 years of experience in business in all parts of the world.
When irjoth writes "If someone were to purchase StrongLoop, this doesn't change." I laugh .. a lot. i've seen tons of business being bought, sometimes small (my local ISP), large (SUN (MySQL)) and it has always been the story. When you are bought you are precisely bought it means you have no say on what's next. If the presence of strongloop breaks the eco system and it seems it does, we will rely exclusively on strongloop. if for some reason strongloop decides or is pushed to decide that express is no longer its interest there will suddently be a void of maintainers and death or at least stagancy for a long while. Big danger : red flashing signal for someone who depends on it for his living.
After such a bold move of changing the repo (the URI in effect for someone like me) so quickly, on short notice without asking anyone, it will be hard to trust the same people that they are attentive, empathic and careful about the vast group of silent people like me. I'm really surprised by the business attitude of Strongloop. I've rarely seen such a bold move. Let's say it is lack of experience, of tact. You don't leave tracks when you do "npm express" but still you are a user and you watch, you lurk.
Now what is the risk for strongloop to keep going, standing firm on the current situation. Express will shortly loose its traction, we will join effort and start a new branch, if only to gain or keep the competency. V4 is so much different then V3, what about V5. What is sure for me is that after one year of migrating I'm not going to migrate again to ruby next week.
Last if I'm a business (I am) would I trust strongloop to offer some business level support on NodeJS, Express ? based on the attitude, I would have the feeling that I would prefer to keep some distance. Technical ability, capacity is one thing, Sales, communication, tact, confidence, trust is another.

If I was in their place i would place it in expressjs and everyone will forget it ever happened. Deal. Court the group for a while, say what you have to offer, why, for how long, what you pursue with this move etc.. I wish we could all forget about the episode ASAP and restart the whole thing on a fresh mind.
One good thing may come out from this is to push more people like me to come out from the blue and join the collective effort.

Sorry for my interruption

@raymondfeng
Copy link

@nicholaswyoung A minor clarification - expressjs/express#2264 was locked by @jonathanong with good intention to limit conversation to collaborators.

@secretfader
Copy link

@RaymontFeng Thanks for pointing that out. I apparently missed that in the issues thread.

My other points still stand: the community has yet to see a clear path from Strongloop on this, and by contrast, it's pretty clear what the contributors/community want. Express belongs in the /expressjs org. If you want to sponsor development on the project, then do it. If Express will remain a community driven project, listen to the contributors, and put action behind your words.

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