Enterprise Geeks Podcast – SAP Community Developer License

In big news for the developer community, SAP announced this week the availability of the new SAP Community Developer License. Get the latest scoop here on the Enterprise Geeks as Ed and Thomas put Mario Herger on the hot seat. Mario is on the SAP Technology Standards and Open Source team responsible for the soon available Code Exchange Platform.

This episode was originally planned to cover both the license announcement and the SAP IT Project Roles roundtable with Jon Reed and Leo De Araujo. Both sessions had so much great content, we wanted to make them both available separately in their entirety. Because of this decision, we have split this episode into two separate parts. You can listen to the second half of the episode here.

Dearest eGheads, we need your show ideas. If you have questions, suggestions, or topic ideas for future episodes, give us a shout here. Enjoy!

Running Time: 43 minutes

Talking Points

  1. 00:15 – Intro
  2. 07:53SAP Community Developer License with Mario Herger
    • 09:07 Mario gives the scoop
    • 11:56 What’s the difference in the Trial License and the Community License?
    • 14:24 Can you “upgrade” your existing installed trial license to a community license without doing a reinstall?
    • 17:22 Do you still have to renew your license every 90 days?
    • 18:30 So what’s really changed?
    • 21:54 Do you have to use SAP Code Exchange with the new license?
    • 25:20 When can we expect the public availability of Code Exchange?
    • 27:34 Can we expect to see the promotion of other platforms or Code Exchange only?
    • 32:17 Shedding some light on the definition of what is or is not an Add-on
    • 36:40 What is the future of the Subscription License?
  3. 39:43 – Closing thoughts

4 responses to “Enterprise Geeks Podcast – SAP Community Developer License”

  1. dan mcweeney says :

    You can totally do what you want in Soundbooth, it does so much, I think I know what you want to do and it’s pretty easy just not “obvious”.

    +1 on a “common sense win”, still wish it was an OSI license but baby steps. 🙂

  2. Jon Reed says :

    Guys, while I’m still not enough of an expert on the legal aspects of developer licenses to offer a real formal view on this, I do want to say, first: excellent podcast. Mario and his team get a lot of credit for taking this forward. The obstacles overcome to reach this point were not small. Clearly there is still work to do but this is an important step.

    Hopefully folks are also aware that in terms of dialogue between SAP Mentors and SAP itself on the developer licenses, this was a dialogue that many Mentors put a lot of energy into. Beyond that, countless members of SCN have chimed in over the years on this topic. We should tip our collective hat to that effort, and for those who aren’t aware of this, SAP’s Michael Bechauf (http://twitter.com/mbechauf) has done a truly outstanding job of having honest, detailed, sometimes when necessary, highly technical/legal discussions with SAP Mentors and others in the Twitter/SAP community on this topic. I’ve been inspired by Michael’s willingness to jump in the fray and listen, rethink, push ahead – and be direct when needed about SAP’s options, and in some cases, current limitations.

    Having said all that, I am of the opinion, and this is just me talking here, that the future of SAP’s success in the next ten years is more dependent on the ability to harness individual developer talent in the “ecosystem” than ANY other single factor. I know that’s a strong statement, but clearly the platforms companies like Sales force and Apple have built to encourage third party innovation have shown their power.

    The SAP Community Developer License is but a small step on this path but it’s an important one and I for one am hopeful that the momentum for this will only build.

    – Jon

  3. dan mcweeney says :

    Jon –

    I disagree with the notion that it will be “individual developer talent” that will help SAP succeed. I don’t think there is much influx of external talent into the problem space to make much of a difference. What I mean by that is there isn’t much incentive for current thought leaders to spend cycles working on SAP problems or products. Most of those people work on projects that they can own and license as they see fit.

    I think what the developer license allows is people already in the ecosystem to work more together. I believe that the most likely change coming from this license is enabling companies that don’t compete ( Exxon and P&G ) to work together to build new SAP solutions / fix existing issue. At the very least it could help to further streamline support costs as customer band together to fix issues instead of going directly to the support organization, basically an organic expansion of what we have today.

Trackbacks / Pingbacks

  1. Enterprise Geeks Podcast – Project Roles Puzzler - April 3, 2013

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: