Nginx Patch: SPDY/3.1 protocol implementation

Re:Nginx Patch: SPDY/3.1 protocol implementation by dmix on Monday January 27, 2014 @07:36PM (#7134408)

With help from some companies:

> Three companies that like Google's approach -- Automattic, MaxCDN, and CloudFlare -- are funding Nginx developers to update its SPDY support to version 3.1, CNET has learned. Under the deal, SPDY 3.1 should arrive in Nginx 1.5 in January, a source familiar with the partnership said.

http://news.cnet.com/8301-1023_3-57616193-93/nginx-upgrade-f...

[ Parent | on HN ]

Re:Nginx Patch: SPDY/3.1 protocol implementation by yeukhon on Monday January 27, 2014 @09:41PM (#7134962)

Just out of curiosity, are they paying Nginx Inc or Nginx contributors?

[ Parent | on HN ]

Re:Nginx Patch: SPDY/3.1 protocol implementation by elithrar on Monday January 27, 2014 @09:53PM (#7135012)

The developer who announced this works for Nginx the company, so I would assume (emphasis on the assume!) that Nginx Inc. was paid to undertake this.

I don't think this is a problem given that the patch is being openly pushed into the "public" source immediately. It'd also be extremely challenging to pay "the community" for a patch like this (how do you divvy up the funds? per SLOC?), although technically you could always directly pay a single contributor or two.

Directly engaging Nginx Inc seems to be both the surest way to get something delivered and avoid a lot of PR risk, if you ask me.

[ Parent | on HN ]

Re:Nginx Patch: SPDY/3.1 protocol implementation by cmelbye on Monday January 27, 2014 @11:13PM (#7135272)

Normally if a company wants to take that route, they would hire one of the developers as an employee, and the employee's job would be to work on that open source project.

[ Parent | on HN ]

Re:Nginx Patch: SPDY/3.1 protocol implementation by ORachel on Tuesday January 28, 2014 @06:56AM (#7136557)

Since ~99.5% of contributions to nginx are made by Nginx Inc employees, I think there wasn't two options.

[ Parent | on HN ]