3 ms·

This is what I'm waiting for as well. Hopefully it comes sooner rather then later.

• seiji 11y ago
  It tends to be amazing how certain closed platforms magically get new features right after they get released in open source projects.
  • merb 11y ago
    if elb would use nginx, that wouldn't be a problem. You can sell closed platforms which depending on gpl / agpl code and you would not need to release any code if you don't modify it.
    • singlow 11y ago
      Right, but they don't use nginx. He is either suggesting that it suddenly becomes a priority when they might lose customers because the feature is available elsewhere; or that they go look at the source code of free software to figure out how to implement the feature; and maybe suggesting that they lift some of the free software's code for their own project. The latter would violate AGPL but probably not GPL, as long as they don't distribute a binary.
      • merb 11y ago
        it would not hurt AGPL. If they build software around AGPL which configures the AGPL it won't break it, you wouldn't change any line of code. As long as your project won't depend on the AGPL (the AGPL binary should be replaceable with project XYZ which isn't AGPL). Let's say you build a closed source configuration tool which works for AGPL webserver and a non AGPL webserver, then you wouldn't violate the AGPL as long as the AGPL webserver won't be changed and just be used.