This is the Special Interest Group for Architecture (sig-architecture) within the Eclipse Tractus-X project. Our primary aim is to document the overall architecture from Tractus-X. Also this repository is a place were Tractus-X Architects can align and document the different design decisions that affect the Tractus-X Product as a whole.
- define architecture guidelines for Eclipse Tractus-X Products
- document the architecture and how all the products come together as a whole
- document the design decisions of the project itself, regarding other dataspaces and organizations
- document the relationships in between products, aligning and keep things running in between the dependencies
- enable a fluid and synchronized integration of the Eclipse Tractus-X Dataspace, having a big picture how it comes together.
- easy the understanding for external technical viewers who want to learn how Tractus-X has been built from architectural point of view.
- Get onboarded: Getting started. Join the Eclipse Tractus-X open source community as a contributor!
- Use your official Architecture Feature Request template to document your business case, issue or enhancement.
- Attend the official community office hours and raise your issue!
🚀 You can also use our official Architecture Feature Request and please detail as most as possible your feature, so you can help us understand it to decide on it.
👀 If you have identified a bug or want to fix an existing documentation, feel free to create a new issue at our project's corresponding GitHub Issues page
🙋 Assign to yourself - Show others that you are working on this issue by assigning it to yourself.
To do so, click the cog wheel next to the Assignees section just to the right of this issue.
📣 If you want to share an idea to further enhance the project, please feel free to contribute to the discussions, otherwise create a new discussion
Please follow the Security Issue Reporting Guidelines if you come across any security vulnerabilities or concerns.