Skip to content

FAQ

1. I'm an SAP Customer, can I use and amend this code for custom business purposes?

Yes. Whether you're looking for automating deployments to kickstart a project, automate regular maintenance tasks, or run tests/sizing as part of business evaluations — under the Apache license you can extend and use for internal purposes without any concerns.

2. I'm an SAP Services Partner, can I use and amend this code to create new products/offerings for customers?

Yes. Any code provided in the SAP LinuxLab initiative can be re-used to create accelerators for Implementation projects and long-term Maintenance engagements. Under the Apache license you can extend and use for commercial purposes without any concerns, although we do hope our SAP Service Partners will provide feedback and contributions back into the projects.

3. How do I contribute code or report issues?

Use the GitHub Issues and Pull Requests on the individual project repository you want to work with. For an overview of the contribution workflow, see Participate in a Project and the Fork a Repository guide in the navigation.

4. How do I request maintainer status or submit a new project?

Use GitHub Discussions on this website repository. Maintainer requests are reviewed by the Governance Board. New project submissions are first reviewed by an existing maintainer to ensure they do not duplicate existing work. For the full checklist and README templates, see Submit a New Repository.

5. What is the difference between Automation Projects and Other Projects?

Automation Projects are Infrastructure-as-Code and Configuration-as-Code solutions — Ansible collections, playbooks, and Terraform templates for deploying and operating SAP landscapes. Other Projects include tools, reference architectures, and documentation that support SAP operations but are not full deployment automation.

6. What license applies to SAP LinuxLab projects?

Projects under the SAP LinuxLab Open-Source Initiative are generally published under the Apache License 2.0. Check the LICENSE file in each individual repository for the exact terms.

7. Who governs the initiative?

A Governance Board with representation from founding member companies approves new contributions, defines naming conventions, and sets roadmap direction. See Governance for more detail on governance and maintainers.