[License-review] Approval request for a New MIT license

Vipin Kumar Vipin.Kumar at optimalpayments.com
Tue Nov 4 16:49:00 UTC 2014 

Hello,



I apologize for the delay in getting back to you: the last email somehow landed in my junk /spam box (I don’t know why); so I just saw it while cleaning my emails . I have now added this email address as "safe sender".



We are not looking to create another type of license / category , but really want to publish our SDK / software under an MIT license; and hence seeking the approval from the OSI review committee (or is it a license type which is pre-approved to be used as long as we use the text from the OSI website?).



Why do we want to use an MIT license type? --> per our research, almost ALL of our competitors ( companies in the same domain, offering the same type of APIs and SDKs for their services) open source the SDKs/ software under MIT license (See Examples below).

Many other companies in other domains also open source their software under MIT license type. We don’t want to be /do any different, nor do we want to go through a process for any new license type (why re-invent the wheel).



Therefore, Can you please confirm:
1.       Whether we can open-source our software under an MIT license , like many others (examples I provided)? MIT appears in the list of OSI-Approved Licenses.
2.       Is there an approval needed from OSI or is it a license type which is OSI pre-approved for us to publish our code as open source, as long as we use the text prescribed for the same on OSI website? I see in the FAQ page on OSI site (link<http://opensource.org/faq#which-license>, see below), that we are free to use MIT as an OSI approved license, and it doesn't need any approval process from OSI, but just wanted to confirm.







Examples:
1.       Company: Stripe Inc. ; link to their SDK under MIT --> https://github.com/stripe/stripe-ruby/blob/master/LICENSE
2.       Company: Braintree  ; link to their SDK under MIT --> https://github.com/braintree/braintree_java/blob/master/LICENSE
3.       Company: Beanstream  ; link to their SDK under MIT --> https://github.com/Beanstream-DRWP/beanstream-java/blob/master/LICENSE
4.       Company Dropbox ; link to their SDK under MIT --> https://raw.githubusercontent.com/dropbox/dropbox-sdk-php/master/License.txt











[cid:image001.png at 01CFF825.51402370]







Thanks & Regards,

Vipin Kumar


________________________________
Vipin Kumar

Product Manager
Tel: 514-380-2752
Fax: 514-380-2760
Email: Vipin.Kumar at OptimalPayments.com<mailto:Vipin.Kumar at OptimalPayments.com>
www.optimalpayments.com<http://www.optimalpayments.com/>

[OP Logo]

________________________________





-----Original Message-----
From: Thorsten Glaser [mailto:tg at mirbsd.de]
Sent: October-22-14 2:23 PM
To: Vipin Kumar
Cc: License submissions for OSI review
Subject: RE: [License-review] Approval request for a New MIT license



Vipin Kumar dixit:



>I am not sure I understood entirely your message below, but we want to

>apply for a new MIT open source license for our SDKs (software



Yes, but: why?



There are enough licences out there already. Every new one means lots of effort (look for the keyword “licence proliferation” e.g.

on the OSI site).



I can’t really say, mind you, being that I wrote The MirOS Licence.

(But I published requirements for a lawyer-written successor.) I wouldn’t write a new licence these days any more either.



bye,

//mirabilos

--

I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them.

If you don't believe in God, just consider God as Nature if you won't deny

existence.                           -- Coywolf Qi Hunt
AVIS IMPORTANT

WARNING


Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L’expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s’il est retransmis sans son autorisation. Si vous n’êtes pas le destinataire visé du présent message ou si vous l’avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l’expéditeur.


This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender.

-- 
WARNING
-------
This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient.  No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message.  If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system.  The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful.  If you have received this e-mail in error, please notify the sender.

AVIS IMPORTANT
--------------
Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé.  L’expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s’il est retransmis sans son autorisation.  Si vous n’êtes pas le destinataire visé du présent message ou si vous l’avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système.  La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux.  Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l’expéditeur.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20141104/73106dc3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 94540 bytes
Desc: image001.png
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20141104/73106dc3/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6488 bytes
Desc: image002.jpg
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20141104/73106dc3/attachment.jpg>

More information about the License-review mailing list