Mastodawn

Habe zum Testen zwei Repositories von GitHub zu Codeberg umgezogen, ein VSCode und ein abapGit Projekt. Das ging viel einfacher als ich befürchtet hatte, und nach ein paar Tagen testen kann jetzt der Rest auch noch rüber.

Abgesehen von einem guten Gefühl wieder etwas Big Tech weniger zu nutzen, finde ich Codeberg auch viel aufgeräumter sowie, gerade wenn man nicht täglich als Power User damit arbeitet, leichter zu bedienen. Und auch wenn wir bei GitHub nur Free Accounts hatten, denke ich das ist eine Fördermitgliedschaft beim Codeberg e.V. wert 🙂

#GitHub #Codeberg #abapGit #abap

Uwe Fetzer Apr 22

New #SAP #API Policy published.
Comments welcome here:
https://www.linkedin.com/posts/marianzeis_sap-is-forbidding-api-use-outside-of-sap-activity-7452736272026021888-hbrh
#abapGit

SAP is forbidding API use outside of SAP Business Accelerator Hub or official product documentation. That is the core message of SAP’s new API Policy: if an interface is not published, not… | Marian Zeis | 22 comments

SAP is forbidding API use outside of SAP Business Accelerator Hub or official product documentation. That is the core message of SAP’s new API Policy: if an interface is not published, not documented, or marked internal/private, customers and partners must not access it. And that has a serious implication for ADT-based tooling. A lot of newer AI tooling in the SAP space talks directly to ADT endpoints like "/sap/bc/adt/*" to read repository objects, inspect metadata, or trigger development-related actions. But SAP documents ADT as ABAP Development Tools for Eclipse, and even SAP community guidance states that the underlying ADT REST APIs are not documented. If you combine that with the new API Policy, the conclusion is uncomfortable: direct use of ADT endpoints by external AI tools looks very hard to justify unless SAP explicitly treats that usage as published and documented. That is an inference from the policy text, but it is a very obvious one. So this is not just about random hidden APIs anymore. It potentially hits a whole wave of SAP AI tooling built on top of interfaces that were technically reachable, but never really released as supported external APIs. And many companies already depend on exactly that. This is not just a policy update. It is an architecture, compliance, and product-strategy problem for parts of the SAP ecosystem. SAP Customers are restricted on how to use their own system. | 22 comments on LinkedIn

fr-g Apr 18, 2024

Sitze in einem Workshop, in dem es auch um #abapgit geht, und draußen fährt ein LKW mit der Aufschrift "CTS" vorbei ^^

Ich fand's lustig.

#abap

Jim Spath Jan 27, 2024

Still tuning the SEO on the #SAPCommunityRevamp

An ABAPer is also an ABaptist? Who knew?

#ABAPgit

Kjetil Kilhavn Mar 5, 2023

I'm sponsoring Lars Hvam because the #abapGit project (in particular) is well worth sponsoring.
https://github.com/sponsors/larshp?sp=kjetil-kilhavn
#SAP #ABAP #git #opensource

Sponsor @larshp on GitHub Sponsors

Open source within the ABAP programming language

GitHub

Uwe Fetzer Feb 17, 2023

7 ways #abapGit can transform your development approach for internal development | #SAP Blogs #abap
https://blogs.sap.com/2023/02/16/7-ways-abapgit-can-transform-your-development-approach-for-internal-development/comment-page-1/#comments

7 ways abapGit can transform your development approach for internal development | SAP Blogs

To the existing SAP development audience – git and abapGit can be curious things. Why did SAP ABAP need to have git when CTS has reliably moved and tracked changes across SAP environments for years?

Show thread