Code Exchange 2.0 – A new and better way to share your code
If you have visited the SAP Developer Center today, you might have noticed a small change…
We’re introducing SAP Code Exchange 2.0…A new and better way to share your code. We have change our landing page and include some new rules that will please most of the developers our there…
If you read carefully, you might notice that if you’re using any of our Developer Center provided tools (meaning that you have a valid license for it), you can actually share your code wherever you want…all we ask from you is the name of your project, the link and a small description. With that, we will able to feature your project on the landing page.
For ABAP based code, you will still need to use Code Exchange 1.0…but of course…we’re working really hard to make things easier for everyone! π
Come on! Share your code! Now it’s easier and better π
Hi Blag,
can you explain, where the points of the "12 Month Leaderboard" came from?
(I like the current board π , but don't know why I am in the lead).
Uwe
To be honest Uwe...I don't have a clue π Blog posts? Answers in the CodeEx forums? Number of submitted projects? SCN is a mystery π
Greetings,
Blag.
Hi Blag,
Appreciate that you're trying to help out the community here.
But... we still can't share ABAP developed on free NW stack outside of code exchange. But we can share java, JavaScript and other already open languages on github.
Hmmm. What has changed? An official link from code exchange to the github repo? That we need to apply for?
What is needed is, as I have said before, abandonment of the code exchange platform, tools to use ABAP with git, new license terms that SAP is happy to allow users to publish code on github,Google code, etc. None of that is easy (Some would suggest that with past struggles in getting code exchange to where it is, impossible), but it is what is needed to attract skill from outside SAP into the ecosystem.
keep struggling! I look forward to some real change here π
I am completely with you here Chris. Github is an excellent code sharing platform and I really find the friction associated with CodEx disappointing. I am not excited about trying to get a project on Codex because it just feels too hard and all the fine print makes in the terms of use makes me feel like a criminal before I even do anything.
We need some serious change here and Chris says the terms of use on the NW Development environments is a good place to start.
Cheers,
Nigel
I am not excited about trying to get a project on Codex because it just feels too hard and all the fine print makes in the terms of use makes me feel like a criminal before I even do anything.
That's why we are doing our best efforts π The least we want is "not excited" people...
Greetings,
Blag.
Hi Chris,
100% d'accord.
SAPlink for ABAP in Eclipse works fine with git (never testet of course because it's not allowed to publish ABAP on git π )
Apropos: can someone point me to the license paragraph, where it's written explicit that I'm not allowed to publish my own ABAP code? (I'm not speaking about the SCN Developer edition, but a "real" suit developer license).
Uwe
Running a local git engine would be a good way to test this. Let me first log into CodeExchange and download SAPLink 4AiE.. Don't think the Code Exchange license is restrictive enough so that it stops me using code found in there to distribute code elsewhere... Just can't distribute the code found there or use it as a base.
NB git != GitHub
Cheers,
Chris
Just noticed the SAPLink 4AiE is provided without any real license whatsoever. A vague wave is made in the directions of the "Current version of the SAP Code Exchange Terms of User". (which is not a license in terms I would understand) And cannot apply since the Eclipse code is hosted at eclipse.saplink.org which is not an SAP domain and thus not valid for Code Exchange under it's onerous licensing.
Then further references are made to "AS is with no guarantee, warranty or support". This again contradicts the CodeEx ToU where the developers indemnify SAP against any damages,
Without a clear license, and with the strange general wave in the direction of the Code Exchange ToU I'll not risk using this tooling to upload code anywhere, not even into a private GitHub repo.
So I'm not going to use the code. Given that the Eclipse pluging code is not ABAP and not hosted on Code Exchange, there is no need to imply the Code Exchange terms. Just be sensible and look after yourself and use an Apache License guys!
You're giving me a headache for sure π I'm not sure but to write here...so I'm just going to keep working and keep trying to make this world a better one...at least in CodeEx terms π
Greetings,
Blag.
That's exactly the difficulty with the current Codeex, you have to differentiate between ABAP and non-ABAP. SAPlink for AiE has two parts, the Eclipse (frontend) part written in JAVA and the backend (ABAP) part.
As we wanted to maintain an Eclipse update site, we had to host the code on our own server.
Regarding the license: currently it is not allowed to use a viral license for the ABAP part. As we don't want (and are not able to) create our own license model, we just refer to the Codex TOU.
I'm going to be really an a** here...it's legal to download something from the Pirate Bay just because it's hosted there? π Don't get angry at me...just kidding π
You can download it code from CodeExchange for sure...because if you can download it...it's because you agree to the CodeEx TOU...so you're fine π
Greetings,
Blag.
I'm looking forward to the blagbert cartoon this inspires π
Downloading from code ex I have no issue with, using a unlicensed/contradictory licensed piece of code is more of a worry. When I'm already treading fuzzy ground by distributing ABAP code outside of SAP (I have a Google code project that uses ABAP developed on my partner instance - could not be placed on code ex due to it having a "viral" license which it must use as it is based on code with an Apache License.) I don't want to do anything that could get me into trouble by manipulation of those very harsh CodeEx tou by SAP's legal team.
And don't get me wrong I understand the effort you are going through, Jergen was pretty clear how hard the internal wrangling is. Appreciate it loads, keep struggling, we will get there eventually!
Cheers, Chris
Uwe:
Well...I'm not really sure about that point...if you own your very own "ERP" system...the one used by every successful business in the world (I know... π I'm using my SAP hat right now)...I guess you should be able to publish it...but everything in this world is complicate... π
Greetings,
Blag.
Chris:
But we can share java, JavaScript and other already open languages on github.
You can share projects made with any SAP tool provided by the SAP Developer Center...ABAP is not there yet...but SAP HANA, SMP, Neo...etc...
Hmmm. What has changed? An official link from code exchange to the github repo? That we need to apply for?
Maybe not too much...but no more CodeEx for any other tool (except ABAP)...and the "official" GitHub repo is intended for SAP employees...of course, anyone else can apply...but it's aimed for SAP people π
keep struggling! I look forward to some real change here π
I will π Our goal is as always, provide the best experience for developers...
Greetings,
Blag.
Dear Alvaro,
Could you please provide the correct link to Code Exchange community:
THis one doesn't work for me.
http://scn.sap.com/community/code-exchange?url_id=text-search-best-best-scn-community-code-exchange
Access to this place or content is restricted. If you think this is a mistake, please contact your administrator or the person who directed you here.
Hello Petr:
Well...As announced via email and on this space, Code Exchange 1.0 is officially closed.
You can contact a.graebe at sap.com from the Developer Relations Team for more information.
Greetings,
Blag.
Development Culture.
Well, could you provide announced Code exchange 2.0 link please?
It looks like the only reference this project is in your post. At least according to Google's request "sap code exchange 2.0"
Thanks.
Petr:
I announced the closing of Code Exchange because my team stop working on external developers...right now the Developer Relations Team is taking care of them...so you better ask them if they have plans or if the have already re-open Code Exchange...because to be honest...I don't know π
Greetings,
Blag.
Development Culture.
Hi,
whatβs the preferred way to share ABAP Code? I canβt found any community to do that.
Are there any league issues to share abap projects?
Regards Wolfgang
Hello Wolfgang:
I have been away from SCN for a long time...but I'm aware of a really nice project π
https://github.com/larshp/abapGit
Greetings,
Blag.
Development Culture.