Skip to content

Commit 6028daa

Browse files
committed
docs: 📝 add README
1 parent 1185137 commit 6028daa

1 file changed

Lines changed: 78 additions & 0 deletions

File tree

README.md

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
<!----------------------------------------------------------------------------
2+
Copyright 2024 Munich Quantum Software Stack Project
3+
4+
Licensed under the Apache License, Version 2.0 with LLVM Exceptions (the
5+
"License"); you may not use this file except in compliance with the License.
6+
You may obtain a copy of the License at
7+
8+
https://github.com/Munich-Quantum-Software-Stack/Component-Catalog/blob/develop/LICENSE
9+
10+
Unless required by applicable law or agreed to in writing, software
11+
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
12+
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
13+
License for the specific language governing permissions and limitations under
14+
the License.
15+
16+
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
17+
-------------------------------------------------------------------------- -->
18+
19+
<p align="center">
20+
<picture>
21+
<source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Munich-Quantum-Software-Stack/QDMI/develop/docs/_static/mqss_logo_dark.svg" width="20%">
22+
<img src="https://raw.githubusercontent.com/Munich-Quantum-Software-Stack/QDMI/develop/docs/_static/mqss_logo.svg" width="20%">
23+
</picture>
24+
</p>
25+
26+
# MQSS Component Catalog
27+
28+
<p align="center"><a href="https://munich-quantum-software-stack.github.io/Component-Catalog/"><strong>View the Component Catalog</strong></a></p>
29+
30+
This repository provides the source code of the Component Catalog webpage, a collection of all
31+
software components that are part of the Munich Quantum Software Stack (MQSS). Each component is
32+
designed to work together seamlessly, offering comprehensive tools for quantum computing
33+
development, simulation, and optimization.
34+
35+
As software tools are developed and maintained by different teams within the Munich Quantum Valles
36+
(MQV), this catalog serves as a centralized resource for users to explore, understand, and utilize
37+
the various components of the MQSS. At the same time, it provides maintainers with a platform to
38+
showcase their work and facilitate collaboration across teams.
39+
40+
New components can be added easily through the GitHub interface without requiring a single line of
41+
code. This allows for rapid expansion of the catalog as new tools and libraries are developed within
42+
the MQV.
43+
44+
## Adding Components
45+
46+
To add a new component to the catalog, please follow these steps:
47+
48+
1. Open the "Issues" tab in this repository and click on "New Issue".
49+
2. Select the "New Component Request" issue template.
50+
3. Fill out the form with the necessary details about the component.
51+
- Some fields are mandatory (name, maintainers, etc.)
52+
- Other fields are optional but recommended (GitHub link, documentation link, etc.)
53+
- The field "Programming Languages" should include all programming languages the component is
54+
implemented in or supports.
55+
- The field "Built On" should include all frameworks (such as Qiskit) the component is built on
56+
or compatible with.
57+
- Make sure the details are correct, as further changes can only be made through pull requests.
58+
4. Submit the issue. After review by the maintainers, the component will be added to the catalog.
59+
60+
## Updating Components
61+
62+
To update an existing component in the catalog, a pull request is required to edit the component's
63+
details. Please follow these steps:
64+
65+
1. Fork the repository to your GitHub account.
66+
2. Navigate to the `_components` directory and locate the Markdown file corresponding to the
67+
component you wish to update.
68+
3. Make the necessary changes to the component's details in the Markdown file.
69+
4. Commit your changes and push them to your forked repository.
70+
5. Open a pull request from your forked repository to the main repository, describing the changes
71+
you made.
72+
6. After review by the maintainers, your changes will be merged into the catalog.
73+
74+
## Feature Requests and Bug Reports
75+
76+
If you have any feature requests or encounter any bugs, please open an issue in the "Issues" tab.
77+
Use the appropriate issue template to provide detailed information about your request or the bug you
78+
encountered. This will help us address your concerns more effectively.

0 commit comments

Comments
 (0)