Open edward opened 11 years ago
I think the decision was reached because of a fear that MEGACORP GOVERNMENT CONTRACTING, LLC would take the codebase, rebrand it as MEGACORP'S RFP-EZ-er, and not contribute their changes back to the community. I'm aware of the Meteor history, but isn't that kind of a non-issue for a project like this? e.g. Meteor is a framework for building webapps so the implications of the licensing are different than for a complete application like Procure.io. (Feel free to tell me I'm wrong, I'm by no means an expert in any of this.)
Nothing wrong with GPL for procure.io. If you use Meteor as your framework, then all the software you create with Meteor must be GPL (same with Drupal, which is a GPL PHP framework). If you use Procure.io as your procurement software, then ... ?
Why GPL instead of MIT?
Given what happened over Meteor’s license kerfuffle, I’m curious why Procure.io chose to use a license that would encumber its interoperability with other products.