Currently, all contributions are incorporated into the Community Components & Extension of the Mobile Design System & SDK – a separate code repository and design kit that extends the common Mobile Design System & SDK.

The SAP Mobile Design System & SDK is divided into two main areas: common and community components.

• Common Components: They are owned and maintained by the Core Design & SDK Team.
• Community Components: They are owned by the respective contributor.

Roles and Responsibilities

• Contributor (Product Teams)
  Anyone within SAP can become a contributor. A contributor is an individual or team that contributes code, UI design, and documentation to the Community Components project, but does not have access to merge code and design directly into the core.
• Core Product Team Members (SDK & Mobile Design System)
  Core product team members of the Mobile Design System and SAP BTP SDK review community components – they evaluate components or enhancements to ensure that the overall vision, scope, architecture, and roadmap of the project are maintained when new community components are added to the SDK and Mobile Design System.

The Core Product Team holds the primary responsibility for our Mobile Design System and SAP BTP SDK by governing the product and being responsible for the following:

• Product scope, roadmap, backlog, and prioritization of requirements and tasks (based on the input of all stakeholders, especially contributors, and consumers)
• Overall architecture of the product
• All core product team tasks (see role above)

Documentation

High-quality documentation is as important as the code you ship. Developer documentation is handled as part of the code, whereas UI design documentation is handled as a set of markdown documents in GitHub – this may change over time based on your feedback and demand.