Re: SAPlink in Code Exchange vs. SAPlink under GPL (Was: [saplink] Re: ENHO Plugins?)

[Gregor Wolf]

Dear Kevin,

I've reached out to everyone who committed code to the Google Code SVN
Repository of SAPlink. They all agreed to move the project to Code
Exchange and publish it under the SAP Code Exchange Terms of Use. I
think that is OK as otherwise no project can switch i.E. from the
GPLv2 to GPLv3. Also there is the limitation of the license you accept
with the NetWeaver Developer Editions. This license allows you to
publish only on SAP Code Exchange.

I think with the help of SAPlink SAP Code Exchange was able to take
of. As you might know that the first SAP Code Exchange project was
included into SAP Standard
(http://scn.sap.com/community/support/downloads-widgets-and-code-exchange-support/blog/2012/07/02/first-sap-code-exchange-project-reaches-sap-standard).
I think that is a big accomplishment. Based on that I hope that SAP
moves on to a real open environment. Already in 2009 I've published
this Blog: Simon Phipps 4 phases of Open Source adoption - What phase
is SAP in? http://scn.sap.com/community/open-source/blog/2009/03/06/simon-phipps-4-phases-of-open-source-adoption--what-phase-is-sap-in.

And you can already see that SAP is moving. The Developer License for
HANA and SUP (http://developer.sap.com/). It allows you to do whatever
you want with the code. You can commercialize or publish it under the
GPL. Let's hope SAP keeps moving into this direction.

Best regards
Gregor


P.S.: @Rui: Here is the Link to the whole discussion
https://groups.google.com/forum/?fromgroups#!topic/saplink/-2zKZkH0RQ4[1-25]