chunk_id stringlengths 36 36 | source stringclasses 35
values | source_url stringlengths 0 290 | upstream_license stringclasses 1
value | document_id stringlengths 36 36 | chunk_index int64 0 324k | retrieved_at stringclasses 2
values | chunker_version stringclasses 4
values | content_hash stringlengths 15 64 | content stringlengths 50 44.7k | namespace stringclasses 9
values | source_name stringclasses 35
values | raw_text stringlengths 50 44.7k | cleaned_text stringlengths 50 44.7k | tags stringclasses 49
values | collection_name stringclasses 11
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2ccbaf3e-272c-48d8-bb0f-549da35020de | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 52 | opea-semantic-v1 | cb40ac776d665969 | #### Pull Request Template
When you submit a PR, you'll be presented with a PR template that looks
something like this: | ai_ref_knowledge | OPEA Documentation | #### Pull Request Template
When you submit a PR, you'll be presented with a PR template that looks
something like this: | #### Pull Request Template
When you submit a PR, you'll be presented with a PR template that looks
something like this: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2d6fa277-51b5-4ae5-a393-60a0786fe1de | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 39 | opea-semantic-v1 | b7381a9e75b33316 | ### Proposing New Features
OPEA communities use the RFC (request for comments) process for collaborating on substantial changes to OPEA projects. The RFC process allows the contributors to collaborate during the design process, providing clarity and validation before jumping to implementation. | ai_ref_knowledge | OPEA Documentation | ### Proposing New Features
OPEA communities use the RFC (request for comments) process for collaborating on substantial changes to OPEA projects. The RFC process allows the contributors to collaborate during the design process, providing clarity and validation before jumping to implementation. | ### Proposing New Features
OPEA communities use the RFC (request for comments) process for collaborating on substantial changes to OPEA projects. The RFC process allows the contributors to collaborate during the design process, providing clarity and validation before jumping to implementation. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
2f771489-a19e-4995-894d-b6cfdbbf0fa8 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 0 | opea-semantic-v1 | 08132e86d0e4c2da | # Contribution Guidelines
Thanks for considering contributing to OPEA project. The contribution process is similar with other open source projects on Github, involving an amount of open discussion in issues and feature requests between the maintainers, contributors and users. | ai_ref_knowledge | OPEA Documentation | # Contribution Guidelines
Thanks for considering contributing to OPEA project. The contribution process is similar with other open source projects on Github, involving an amount of open discussion in issues and feature requests between the maintainers, contributors and users. | # Contribution Guidelines
Thanks for considering contributing to OPEA project. The contribution process is similar with other open source projects on Github, involving an amount of open discussion in issues and feature requests between the maintainers, contributors and users. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
30efbc0b-2aca-4d36-a247-d3c47ea5695b | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 11 | opea-semantic-v1 | bbddf8f25e01f16c | tests. For completeness, submit a PR to the OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) to illustrate customizing the ChatQnA example application. [See the full documentation for greater detail](https://github.com/opea-project/docs/blob/main/community/add_vectorDB.md).
### Contribute... | ai_ref_knowledge | OPEA Documentation | tests. For completeness, submit a PR to the OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) to illustrate customizing the ChatQnA example application. [See the full documentation for greater detail](https://github.com/opea-project/docs/blob/main/community/add_vectorDB.md).
### Contribute... | tests. For completeness, submit a PR to the OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) to illustrate customizing the ChatQnA example application. [See the full documentation for greater detail](https://github.com/opea-project/docs/blob/main/community/add_vectorDB.md).
### Contribute... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
314200a5-b155-4453-b5a9-1a2c2f54fbdc | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 8 | opea-semantic-v1 | 0ae23f96ccf97311 | ensure CICD evaluates components correctly. - `README.md`: at minimum it should include: microservice description, build, and start commands and a curl command with expected output.
4. Now you have created all the required files, and validated your service. Last step is to add a `src/README_[interation_type].md` at the... | ai_ref_knowledge | OPEA Documentation | ensure CICD evaluates components correctly. - `README.md`: at minimum it should include: microservice description, build, and start commands and a curl command with expected output.
4. Now you have created all the required files, and validated your service. Last step is to add a `src/README_[interation_type].md` at the... | ensure CICD evaluates components correctly. - `README.md`: at minimum it should include: microservice description, build, and start commands and a curl command with expected output.
4. Now you have created all the required files, and validated your service. Last step is to add a `src/README_[interation_type].md` at the... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
315e8fe6-120b-4615-b95a-fa878024d2db | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 7 | opea-semantic-v1 | 3c467edecac2007c | dependencies for opea component and all integrations - `src/Dockerfile`: Used to generate the service container image. - `tests/[microservices type]/` : contains end-to-end test for microservices.
Please follow naming convention:`test_[microservice type]_[integration type].sh` or `test_[microservice type]_[integration ... | ai_ref_knowledge | OPEA Documentation | dependencies for opea component and all integrations - `src/Dockerfile`: Used to generate the service container image. - `tests/[microservices type]/` : contains end-to-end test for microservices.
Please follow naming convention:`test_[microservice type]_[integration type].sh` or `test_[microservice type]_[integration ... | dependencies for opea component and all integrations - `src/Dockerfile`: Used to generate the service container image. - `tests/[microservices type]/` : contains end-to-end test for microservices.
Please follow naming convention:`test_[microservice type]_[integration type].sh` or `test_[microservice type]_[integration ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
38336588-2e4d-454f-bd40-b92e35ad5859 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 3 | opea-semantic-v1 | 42abb129a1417534 | a brand new microservice type, you need to define and contribute first its API specification. Please start by submitting an RFC to get community feedback.
GenAIComps
├── comps
│ ├── __init__.py
│ ├── agent
│ ├── animation
│ ├── asr
│ ├── chathistory
│ ├── cores
| │ ├── common
│ │ ├── mega # orche... | ai_ref_knowledge | OPEA Documentation | a brand new microservice type, you need to define and contribute first its API specification. Please start by submitting an RFC to get community feedback.
GenAIComps
├── comps
│ ├── __init__.py
│ ├── agent
│ ├── animation
│ ├── asr
│ ├── chathistory
│ ├── cores
| │ ├── common
│ │ ├── mega # orche... | a brand new microservice type, you need to define and contribute first its API specification. Please start by submitting an RFC to get community feedback.
GenAIComps
├── comps
│ ├── __init__.py
│ ├── agent
│ ├── animation
│ ├── asr
│ ├── chathistory
│ ├── cores
| │ ├── common
│ │ ├── mega # orche... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3eb56478-1269-494e-9e72-f9e2f65f4e0f | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 34 | opea-semantic-v1 | 3e50dfda00a5cfcb | at https://github.com/opea-project. Alternatively, they can send an email to [info@opea.dev](mailto://info@opea.dev) or subscribe to [X/Twitter](https://twitter.com/opeadev) and [LinkedIn Page](https://www.linkedin.com/company/opeadev/posts/?feedView=all) to get latest updates about the OPEA project.
### Documentation | ai_ref_knowledge | OPEA Documentation | at https://github.com/opea-project. Alternatively, they can send an email to [info@opea.dev](mailto://info@opea.dev) or subscribe to [X/Twitter](https://twitter.com/opeadev) and [LinkedIn Page](https://www.linkedin.com/company/opeadev/posts/?feedView=all) to get latest updates about the OPEA project.
### Documentation | at https://github.com/opea-project. Alternatively, they can send an email to [info@opea.dev](mailto://info@opea.dev) or subscribe to [X/Twitter](https://twitter.com/opeadev) and [LinkedIn Page](https://www.linkedin.com/company/opeadev/posts/?feedView=all) to get latest updates about the OPEA project.
### Documentation | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
40b7cbc5-7302-4aa4-8f29-611e01e16be0 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 56 | opea-semantic-v1 | 3af7203e738ef3da | #### Pull Request Review You can tag or add reviewers from [the code owners list](https://github.com/opea-project/docs/blob/main/community/codeowner.md) to your PR.
## Support | ai_ref_knowledge | OPEA Documentation | #### Pull Request Review You can tag or add reviewers from [the code owners list](https://github.com/opea-project/docs/blob/main/community/codeowner.md) to your PR.
## Support | #### Pull Request Review You can tag or add reviewers from [the code owners list](https://github.com/opea-project/docs/blob/main/community/codeowner.md) to your PR.
## Support | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
411770f7-48c2-4d0e-9efd-f79cc9176cee | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 46 | opea-semantic-v1 | 98d12bab8a3b6415 | ```{literalinclude} rfcs/rfc_template.txt
- Submit the proposal to the `Issues` page of the corresponding OPEA GitHub repository. - Reach out to your RFC's assignee if you need any help with the RFC process. - Amend your proposal in response to reviewer's feedback. | ai_ref_knowledge | OPEA Documentation | ```{literalinclude} rfcs/rfc_template.txt
- Submit the proposal to the `Issues` page of the corresponding OPEA GitHub repository. - Reach out to your RFC's assignee if you need any help with the RFC process. - Amend your proposal in response to reviewer's feedback. | ```{literalinclude} rfcs/rfc_template.txt
- Submit the proposal to the `Issues` page of the corresponding OPEA GitHub repository. - Reach out to your RFC's assignee if you need any help with the RFC process. - Amend your proposal in response to reviewer's feedback. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
44b0c504-5f56-4fc3-9fdd-40869a48a878 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 57 | opea-semantic-v1 | acd2f1546aef3042 | ## Support
- Feel free to reach out to [OPEA maintainers](mailto://info@opea.dev) for support. - Submit your questions, feature requests, and bug reports to the GitHub issues page. | ai_ref_knowledge | OPEA Documentation | ## Support
- Feel free to reach out to [OPEA maintainers](mailto://info@opea.dev) for support. - Submit your questions, feature requests, and bug reports to the GitHub issues page. | ## Support
- Feel free to reach out to [OPEA maintainers](mailto://info@opea.dev) for support. - Submit your questions, feature requests, and bug reports to the GitHub issues page. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
457e4b3d-11e2-46bd-99bc-d98dbb3b46df | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 24 | opea-semantic-v1 | e97085c6d44d1fa9 | - Follow the folder structure in the ChatQnA example below:
├── Dockerfile
├── Dockerfile.guardrails
├── Dockerfile.without_rerank
├── README.md
├── assets
│ └── img
├── benchmark
│ ├── accuracy
│ │ ├── README.md
│ │ ├── eval_crud.py
│ │ ├── eval_multihop.py
│ │ ├── process_crud_dataset.p... | ai_ref_knowledge | OPEA Documentation | - Follow the folder structure in the ChatQnA example below:
├── Dockerfile
├── Dockerfile.guardrails
├── Dockerfile.without_rerank
├── README.md
├── assets
│ └── img
├── benchmark
│ ├── accuracy
│ │ ├── README.md
│ │ ├── eval_crud.py
│ │ ├── eval_multihop.py
│ │ ├── process_crud_dataset.p... | - Follow the folder structure in the ChatQnA example below:
├── Dockerfile
├── Dockerfile.guardrails
├── Dockerfile.without_rerank
├── README.md
├── assets
│ └── img
├── benchmark
│ ├── accuracy
│ │ ├── README.md
│ │ ├── eval_crud.py
│ │ ├── eval_multihop.py
│ │ ├── process_crud_dataset.p... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
50e3f827-2f98-4d49-88ca-f0c9ee73ee8d | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 20 | opea-semantic-v1 | e5277413129082b6 | %% Data Preparation flow %% Ingest data flow direction LR Ingest[Ingest data] -->|a| UI UI -->|b| DP DP <-.->|c| TEI_EM
%% Questions interaction
direction LR
a[User Input Query] -->|1| UI
UI -->|2| GW
GW <==>|3| ChatQnA-MegaService
EM ==>|4| RET
RET ==>|5| RER
RER ==>|6| LLM | ai_ref_knowledge | OPEA Documentation | %% Data Preparation flow %% Ingest data flow direction LR Ingest[Ingest data] -->|a| UI UI -->|b| DP DP <-.->|c| TEI_EM
%% Questions interaction
direction LR
a[User Input Query] -->|1| UI
UI -->|2| GW
GW <==>|3| ChatQnA-MegaService
EM ==>|4| RET
RET ==>|5| RER
RER ==>|6| LLM | %% Data Preparation flow %% Ingest data flow direction LR Ingest[Ingest data] -->|a| UI UI -->|b| DP DP <-.->|c| TEI_EM
%% Questions interaction
direction LR
a[User Input Query] -->|1| UI
UI -->|2| GW
GW <==>|3| ChatQnA-MegaService
EM ==>|4| RET
RET ==>|5| RER
RER ==>|6| LLM | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
52cd830c-4f70-4660-a352-04d289a4b42a | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 53 | opea-semantic-v1 | 85ceb91eb9e54eff | The OPEA projects use GitHub Action for CI test.
| Test Name | Test Scope | Test Pass Criteria |
|--------------------|-------------------------------------------|--------------------|
| DCO | Use `git commit -s` to sign off | PASS |
| Code Format Scan | pre-commit.ci [Bot] | PASS |
| Code Security Scan | Bandit/Hadoli... | ai_ref_knowledge | OPEA Documentation | The OPEA projects use GitHub Action for CI test.
| Test Name | Test Scope | Test Pass Criteria |
|--------------------|-------------------------------------------|--------------------|
| DCO | Use `git commit -s` to sign off | PASS |
| Code Format Scan | pre-commit.ci [Bot] | PASS |
| Code Security Scan | Bandit/Hadoli... | The OPEA projects use GitHub Action for CI test.
| Test Name | Test Scope | Test Pass Criteria |
|--------------------|-------------------------------------------|--------------------|
| DCO | Use `git commit -s` to sign off | PASS |
| Code Format Scan | pre-commit.ci [Bot] | PASS |
| Code Security Scan | Bandit/Hadoli... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5336db3b-373c-4dfe-8e78-9fbb51db7ba6 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 36 | opea-semantic-v1 | 755cfc85c13006fc | documentation can have a huge impact on its success. We reply on OPEA maintainers and contributors to build clear, detailed and update-to-date documentation for user.
### Reporting Issues | ai_ref_knowledge | OPEA Documentation | documentation can have a huge impact on its success. We reply on OPEA maintainers and contributors to build clear, detailed and update-to-date documentation for user.
### Reporting Issues | documentation can have a huge impact on its success. We reply on OPEA maintainers and contributors to build clear, detailed and update-to-date documentation for user.
### Reporting Issues | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
53e600da-0136-4714-8da9-fb7d9ca67f99 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 2 | opea-semantic-v1 | 3557cb817f3d2ca4 | ### Contribute a GenAI Component
1. Navigate to [OPEA GenAIComps](https://github.com/opea-project/GenAIComps) and locate the component folder your integration belongs to. If the microservice type already exists, review the [OPEA microservice API](https://opea-project.github.io/latest/developer-guides/OPEA_API.html#opea... | ai_ref_knowledge | OPEA Documentation | ### Contribute a GenAI Component
1. Navigate to [OPEA GenAIComps](https://github.com/opea-project/GenAIComps) and locate the component folder your integration belongs to. If the microservice type already exists, review the [OPEA microservice API](https://opea-project.github.io/latest/developer-guides/OPEA_API.html#opea... | ### Contribute a GenAI Component
1. Navigate to [OPEA GenAIComps](https://github.com/opea-project/GenAIComps) and locate the component folder your integration belongs to. If the microservice type already exists, review the [OPEA microservice API](https://opea-project.github.io/latest/developer-guides/OPEA_API.html#opea... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
53f68e60-aebb-4eb6-8cbf-4c294e39a69b | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 31 | opea-semantic-v1 | f7c6503b31d8b925 | You will need additional steps to configure the CI/CD to first test and then deploy the GenAIComp or GenAIExample you merged.
- Connect hardware into OPEA GitHub Actions ([GHA](https://docs.github.com/en/actions)) as a self-hosted runner
- Contribute test scripts for the new hardware
- Dockerfile for the Component (i,e... | ai_ref_knowledge | OPEA Documentation | You will need additional steps to configure the CI/CD to first test and then deploy the GenAIComp or GenAIExample you merged.
- Connect hardware into OPEA GitHub Actions ([GHA](https://docs.github.com/en/actions)) as a self-hosted runner
- Contribute test scripts for the new hardware
- Dockerfile for the Component (i,e... | You will need additional steps to configure the CI/CD to first test and then deploy the GenAIComp or GenAIExample you merged.
- Connect hardware into OPEA GitHub Actions ([GHA](https://docs.github.com/en/actions)) as a self-hosted runner
- Contribute test scripts for the new hardware
- Dockerfile for the Component (i,e... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
61d4ce6c-f4f3-45dc-b134-5bdae3f9f175 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 29 | opea-semantic-v1 | bc12f0b25d8e9703 | naming convention: - Docker compose test: `tests/test_compose_on_[hardware].sh` - K8s with GMC test: `tests/test_gmc_on_[hardware].sh` - `ui`: (optional) - `assets`: nice to have an application flow diagram
#### Additional steps if your contribution is Hardware Specific | ai_ref_knowledge | OPEA Documentation | naming convention: - Docker compose test: `tests/test_compose_on_[hardware].sh` - K8s with GMC test: `tests/test_gmc_on_[hardware].sh` - `ui`: (optional) - `assets`: nice to have an application flow diagram
#### Additional steps if your contribution is Hardware Specific | naming convention: - Docker compose test: `tests/test_compose_on_[hardware].sh` - K8s with GMC test: `tests/test_gmc_on_[hardware].sh` - `ui`: (optional) - `assets`: nice to have an application flow diagram
#### Additional steps if your contribution is Hardware Specific | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
63b8038e-7c2f-454c-bfd9-3069f54ace51 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 9 | opea-semantic-v1 | e594337e77a366b4 | PR! Once your PR is merged, in the next release the project release maintainers will publish the Docker Image for the same to Docker Hub.
5. After your component has been merged, you are likely interested in building an application with it, and perhaps contributing it also to OPEA! Please continue on to the [Contribute... | ai_ref_knowledge | OPEA Documentation | PR! Once your PR is merged, in the next release the project release maintainers will publish the Docker Image for the same to Docker Hub.
5. After your component has been merged, you are likely interested in building an application with it, and perhaps contributing it also to OPEA! Please continue on to the [Contribute... | PR! Once your PR is merged, in the next release the project release maintainers will publish the Docker Image for the same to Docker Hub.
5. After your component has been merged, you are likely interested in building an application with it, and perhaps contributing it also to OPEA! Please continue on to the [Contribute... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
66d692b3-dd2e-4f00-b32e-296896494a81 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 19 | opea-semantic-v1 | f1565c3ac80ae433 | TEI_RER{{Reranking service<br>}} TEI_EM{{Embedding service <br>}} VDB{{Vector DB<br><br>}} R_RET{{Retriever service <br>}} DP([Data Preparation<br>]):::blue LLM_gen{{LLM Service <br>}}
%% Data Preparation flow
%% Ingest data flow
direction LR
Ingest[Ingest data] -->|a| UI
UI -->|b| DP
DP <-.->|c| TEI_EM | ai_ref_knowledge | OPEA Documentation | TEI_RER{{Reranking service<br>}} TEI_EM{{Embedding service <br>}} VDB{{Vector DB<br><br>}} R_RET{{Retriever service <br>}} DP([Data Preparation<br>]):::blue LLM_gen{{LLM Service <br>}}
%% Data Preparation flow
%% Ingest data flow
direction LR
Ingest[Ingest data] -->|a| UI
UI -->|b| DP
DP <-.->|c| TEI_EM | TEI_RER{{Reranking service<br>}} TEI_EM{{Embedding service <br>}} VDB{{Vector DB<br><br>}} R_RET{{Retriever service <br>}} DP([Data Preparation<br>]):::blue LLM_gen{{LLM Service <br>}}
%% Data Preparation flow
%% Ingest data flow
direction LR
Ingest[Ingest data] -->|a| UI
UI -->|b| DP
DP <-.->|c| TEI_EM | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6a94f51e-fe9c-4336-b89d-c648daa223eb | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 28 | opea-semantic-v1 | 841c64c255b90af2 | provide an E2E test with Docker Compose. If you are contributing a K8s Helm Chart or GMC yaml, you should also provide tests for those.
Please follow this naming convention:
- Docker compose test: `tests/test_compose_on_[hardware].sh`
- K8s with GMC test: `tests/test_gmc_on_[hardware].sh`
- `ui`: (optional)
- `asse... | ai_ref_knowledge | OPEA Documentation | provide an E2E test with Docker Compose. If you are contributing a K8s Helm Chart or GMC yaml, you should also provide tests for those.
Please follow this naming convention:
- Docker compose test: `tests/test_compose_on_[hardware].sh`
- K8s with GMC test: `tests/test_gmc_on_[hardware].sh`
- `ui`: (optional)
- `asse... | provide an E2E test with Docker Compose. If you are contributing a K8s Helm Chart or GMC yaml, you should also provide tests for those.
Please follow this naming convention:
- Docker compose test: `tests/test_compose_on_[hardware].sh`
- K8s with GMC test: `tests/test_gmc_on_[hardware].sh`
- `ui`: (optional)
- `asse... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7084319d-719a-4d82-bb19-edba7ada20e5 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 50 | opea-semantic-v1 | d075f798adfd75bf | ##### Step-by-Step guidelines
- Star this repository using the button `Star` in the top right corner. - Fork the corresponding OPEA repository using the button `Fork` in the top right corner. - Clone your forked repository to your pc by running `git clone "url to your repo"`
- Create a new branch for your modifications... | ai_ref_knowledge | OPEA Documentation | ##### Step-by-Step guidelines
- Star this repository using the button `Star` in the top right corner. - Fork the corresponding OPEA repository using the button `Fork` in the top right corner. - Clone your forked repository to your pc by running `git clone "url to your repo"`
- Create a new branch for your modifications... | ##### Step-by-Step guidelines
- Star this repository using the button `Star` in the top right corner. - Fork the corresponding OPEA repository using the button `Fork` in the top right corner. - Clone your forked repository to your pc by running `git clone "url to your repo"`
- Create a new branch for your modifications... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
743bfef6-b4e6-44fa-a11c-37c9b4136a02 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 43 | opea-semantic-v1 | f1c3dd545234ea27 | - Changes to core workflow. - Changes with significant architectural implications. - changes which modify or introduce user facing interfaces.
It is not necessary for changes like: | ai_ref_knowledge | OPEA Documentation | - Changes to core workflow. - Changes with significant architectural implications. - changes which modify or introduce user facing interfaces.
It is not necessary for changes like: | - Changes to core workflow. - Changes with significant architectural implications. - changes which modify or introduce user facing interfaces.
It is not necessary for changes like: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7a84415d-16ee-43c8-b9af-ebb8c54982f1 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 6 | opea-semantic-v1 | 5a2093d2680a27db | ├── wav2lip | │ └── whisper ├── tests │ └── embeddings | ├── test_embeddings_multimodal_bridgetower.sh | ├── test_embeddings_multimodal_bridgetower_on_intel_hpu.sh | ├── test_embeddings_predictionguard.sh | └── test_embeddings_tei.sh └── README.md
- **File Descriptions**:
- `deployment/docker_compose` and `deployment/... | ai_ref_knowledge | OPEA Documentation | ├── wav2lip | │ └── whisper ├── tests │ └── embeddings | ├── test_embeddings_multimodal_bridgetower.sh | ├── test_embeddings_multimodal_bridgetower_on_intel_hpu.sh | ├── test_embeddings_predictionguard.sh | └── test_embeddings_tei.sh └── README.md
- **File Descriptions**:
- `deployment/docker_compose` and `deployment/... | ├── wav2lip | │ └── whisper ├── tests │ └── embeddings | ├── test_embeddings_multimodal_bridgetower.sh | ├── test_embeddings_multimodal_bridgetower_on_intel_hpu.sh | ├── test_embeddings_predictionguard.sh | └── test_embeddings_tei.sh └── README.md
- **File Descriptions**:
- `deployment/docker_compose` and `deployment/... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7ba00bf5-3320-48fe-88fc-cd227ae5d1f2 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 51 | opea-semantic-v1 | 42ea6be84995b1ab | -s -m "This is my commit message"` and push `git push origin new-branch`. - Create a `pull request` for the project you want to contribute.
#### Pull Request Template | ai_ref_knowledge | OPEA Documentation | -s -m "This is my commit message"` and push `git push origin new-branch`. - Create a `pull request` for the project you want to contribute.
#### Pull Request Template | -s -m "This is my commit message"` and push `git push origin new-branch`. - Create a `pull request` for the project you want to contribute.
#### Pull Request Template | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7bfc26d4-4237-47d2-9dc6-c9a7acd64ace | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 14 | opea-semantic-v1 | 4bc4b3ba5f069cba | recommend submitting an RFC first in this case to the doc sub-project to discuss your new application and potentially get suggestions and collect fellow travellers.
- Before stitching together all the microservices to build your application, let's make sure all the required building blocks are available!. Take a look a... | ai_ref_knowledge | OPEA Documentation | recommend submitting an RFC first in this case to the doc sub-project to discuss your new application and potentially get suggestions and collect fellow travellers.
- Before stitching together all the microservices to build your application, let's make sure all the required building blocks are available!. Take a look a... | recommend submitting an RFC first in this case to the doc sub-project to discuss your new application and potentially get suggestions and collect fellow travellers.
- Before stitching together all the microservices to build your application, let's make sure all the required building blocks are available!. Take a look a... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7fec001e-3768-49d1-ac91-5329cf38948b | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 54 | opea-semantic-v1 | f6cd40c920a91e8b | Unit Test | Unit test under test folder | PASS | | End to End Test | End to end test workflow | PASS |
- [Developer Certificate of Origin (DCO)](https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin), the PR must agree to the terms of Developer Certificate of Origin by signing off each of commits with `-s`, e.g... | ai_ref_knowledge | OPEA Documentation | Unit Test | Unit test under test folder | PASS | | End to End Test | End to end test workflow | PASS |
- [Developer Certificate of Origin (DCO)](https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin), the PR must agree to the terms of Developer Certificate of Origin by signing off each of commits with `-s`, e.g... | Unit Test | Unit test under test folder | PASS | | End to End Test | End to end test workflow | PASS |
- [Developer Certificate of Origin (DCO)](https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin), the PR must agree to the terms of Developer Certificate of Origin by signing off each of commits with `-s`, e.g... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8d87b30e-e2a4-4207-84d3-d52fc8622b67 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 35 | opea-semantic-v1 | 16c5cb4cdc1ac28a | ### Documentation
The quality of OPEA project's documentation can have a huge impact on its success. We reply on OPEA maintainers and contributors to build clear, detailed and update-to-date documentation for user. | ai_ref_knowledge | OPEA Documentation | ### Documentation
The quality of OPEA project's documentation can have a huge impact on its success. We reply on OPEA maintainers and contributors to build clear, detailed and update-to-date documentation for user. | ### Documentation
The quality of OPEA project's documentation can have a huge impact on its success. We reply on OPEA maintainers and contributors to build clear, detailed and update-to-date documentation for user. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8f4f767a-9ff6-4ae9-8eca-f8357186485e | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 45 | opea-semantic-v1 | 559f347aabf16f9c | Bug fixes and optimizations with no semantic change. - Small features which doesn't involve workflow or interface change, and only impact a narrow use case.
#### Step-by-Step guidelines | ai_ref_knowledge | OPEA Documentation | Bug fixes and optimizations with no semantic change. - Small features which doesn't involve workflow or interface change, and only impact a narrow use case.
#### Step-by-Step guidelines | Bug fixes and optimizations with no semantic change. - Small features which doesn't involve workflow or interface change, and only impact a narrow use case.
#### Step-by-Step guidelines | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
97d71cae-25f2-4ba8-b6d5-87a99377c242 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 30 | opea-semantic-v1 | 149cf7f590e3feb7 | #### Additional steps if your contribution is Hardware Specific
You will need additional steps to configure the CI/CD to first test and then deploy the GenAIComp or GenAIExample you merged. | ai_ref_knowledge | OPEA Documentation | #### Additional steps if your contribution is Hardware Specific
You will need additional steps to configure the CI/CD to first test and then deploy the GenAIComp or GenAIExample you merged. | #### Additional steps if your contribution is Hardware Specific
You will need additional steps to configure the CI/CD to first test and then deploy the GenAIComp or GenAIExample you merged. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9ab8a858-073a-4423-a66d-e4b17bc6b2c9 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 44 | opea-semantic-v1 | 1d25844b9c764c9a | It is not necessary for changes like:
- Bug fixes and optimizations with no semantic change. - Small features which doesn't involve workflow or interface change, and only impact a narrow use case. | ai_ref_knowledge | OPEA Documentation | It is not necessary for changes like:
- Bug fixes and optimizations with no semantic change. - Small features which doesn't involve workflow or interface change, and only impact a narrow use case. | It is not necessary for changes like:
- Bug fixes and optimizations with no semantic change. - Small features which doesn't involve workflow or interface change, and only impact a narrow use case. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9b19adc6-90db-45c1-9e12-458d4023ee69 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 10 | opea-semantic-v1 | 6434884b4c2288e1 | likely interested in building an application with it, and perhaps contributing it also to OPEA! Please continue on to the [Contribute a GenAI Example](#contribute-a-genai-example) guide.
### Contributing A New Vector Database to OPEA
To contribute a new Vector Database to OPEA, you would need to modify minimally the OP... | ai_ref_knowledge | OPEA Documentation | likely interested in building an application with it, and perhaps contributing it also to OPEA! Please continue on to the [Contribute a GenAI Example](#contribute-a-genai-example) guide.
### Contributing A New Vector Database to OPEA
To contribute a new Vector Database to OPEA, you would need to modify minimally the OP... | likely interested in building an application with it, and perhaps contributing it also to OPEA! Please continue on to the [Contribute a GenAI Example](#contribute-a-genai-example) guide.
### Contributing A New Vector Database to OPEA
To contribute a new Vector Database to OPEA, you would need to modify minimally the OP... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9d5262a5-90f5-42a3-89d7-add15c46caa8 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 12 | opea-semantic-v1 | e94b904944d99bba | ### Contribute a GenAI Example
Each of the samples in OPEA GenAIExamples is a commonly used solution. They each have scripts to ease deployment, and have been tested for performance and scalability with Docker Compose and Kubernetes. When contributing an example, a Docker Compose deployment is the minimum requirement. ... | ai_ref_knowledge | OPEA Documentation | ### Contribute a GenAI Example
Each of the samples in OPEA GenAIExamples is a commonly used solution. They each have scripts to ease deployment, and have been tested for performance and scalability with Docker Compose and Kubernetes. When contributing an example, a Docker Compose deployment is the minimum requirement. ... | ### Contribute a GenAI Example
Each of the samples in OPEA GenAIExamples is a commonly used solution. They each have scripts to ease deployment, and have been tested for performance and scalability with Docker Compose and Kubernetes. When contributing an example, a Docker Compose deployment is the minimum requirement. ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9ea620b0-c19d-4c13-bb2e-aa76794ca8d8 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 47 | opea-semantic-v1 | 38bb55790849da6b | - Reach out to your RFC's assignee if you need any help with the RFC process. - Amend your proposal in response to reviewer's feedback.
### Submitting Pull Requests | ai_ref_knowledge | OPEA Documentation | - Reach out to your RFC's assignee if you need any help with the RFC process. - Amend your proposal in response to reviewer's feedback.
### Submitting Pull Requests | - Reach out to your RFC's assignee if you need any help with the RFC process. - Amend your proposal in response to reviewer's feedback.
### Submitting Pull Requests | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a2b18978-f1ff-4bdf-8ddd-cd826bc983cf | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 16 | opea-semantic-v1 | 3b86618c6aef1b78 | config: flowchart: nodeSpacing: 100 rankSpacing: 100 curve: linear theme: base themeVariables: fontSize: 42px
flowchart LR
%% Colors %%
classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orchid fill:#C26D... | ai_ref_knowledge | OPEA Documentation | config: flowchart: nodeSpacing: 100 rankSpacing: 100 curve: linear theme: base themeVariables: fontSize: 42px
flowchart LR
%% Colors %%
classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orchid fill:#C26D... | config: flowchart: nodeSpacing: 100 rankSpacing: 100 curve: linear theme: base themeVariables: fontSize: 42px
flowchart LR
%% Colors %%
classDef blue fill:#ADD8E6,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orange fill:#FBAA60,stroke:#ADD8E6,stroke-width:2px,fill-opacity:0.5
classDef orchid fill:#C26D... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
a6426752-387a-4c60-9b89-138851763cf5 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 18 | opea-semantic-v1 | 6f6de1adc758c07a | X([OPEA Micsrservice]):::blue Y{{Open Source Service}} Z([OPEA Gateway]):::orange Z1([UI]):::orchid end
TEI_RER{{Reranking service<br>}}
TEI_EM{{Embedding service <br>}}
VDB{{Vector DB<br><br>}}
R_RET{{Retriever service <br>}}
DP([Data Preparation<br>]):::blue
LLM_gen{{LLM Service <br>}} | ai_ref_knowledge | OPEA Documentation | X([OPEA Micsrservice]):::blue Y{{Open Source Service}} Z([OPEA Gateway]):::orange Z1([UI]):::orchid end
TEI_RER{{Reranking service<br>}}
TEI_EM{{Embedding service <br>}}
VDB{{Vector DB<br><br>}}
R_RET{{Retriever service <br>}}
DP([Data Preparation<br>]):::blue
LLM_gen{{LLM Service <br>}} | X([OPEA Micsrservice]):::blue Y{{Open Source Service}} Z([OPEA Gateway]):::orange Z1([UI]):::orchid end
TEI_RER{{Reranking service<br>}}
TEI_EM{{Embedding service <br>}}
VDB{{Vector DB<br><br>}}
R_RET{{Retriever service <br>}}
DP([Data Preparation<br>]):::blue
LLM_gen{{LLM Service <br>}} | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
abac740e-63fd-4129-b177-181f30b760f2 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 5 | opea-semantic-v1 | ef7d4dbf74b6a1b2 | 2. Follow the folder structure in the TEI embedding component below:
GenAIComps
├── comps
│ └── embeddings
| | ├── deployment
| | │ ├── docker_compose
| | │ │ └── compose.yaml
| | │ └── kubernetes
| | │ ├── README.md
| | │ └── cpu-values.yaml
| | └── src
| | ├── Dockerfile
| | ├── README.md # cou... | ai_ref_knowledge | OPEA Documentation | 2. Follow the folder structure in the TEI embedding component below:
GenAIComps
├── comps
│ └── embeddings
| | ├── deployment
| | │ ├── docker_compose
| | │ │ └── compose.yaml
| | │ └── kubernetes
| | │ ├── README.md
| | │ └── cpu-values.yaml
| | └── src
| | ├── Dockerfile
| | ├── README.md # cou... | 2. Follow the folder structure in the TEI embedding component below:
GenAIComps
├── comps
│ └── embeddings
| | ├── deployment
| | │ ├── docker_compose
| | │ │ └── compose.yaml
| | │ └── kubernetes
| | │ ├── README.md
| | │ └── cpu-values.yaml
| | └── src
| | ├── Dockerfile
| | ├── README.md # cou... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b6fa8a46-e92e-47c0-a79f-d833fbdc9902 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 58 | opea-semantic-v1 | 97c46592036ee80a | - Feel free to reach out to [OPEA maintainers](mailto://info@opea.dev) for support. - Submit your questions, feature requests, and bug reports to the GitHub issues page.
## Contributor Covenant Code of Conduct | ai_ref_knowledge | OPEA Documentation | - Feel free to reach out to [OPEA maintainers](mailto://info@opea.dev) for support. - Submit your questions, feature requests, and bug reports to the GitHub issues page.
## Contributor Covenant Code of Conduct | - Feel free to reach out to [OPEA maintainers](mailto://info@opea.dev) for support. - Submit your questions, feature requests, and bug reports to the GitHub issues page.
## Contributor Covenant Code of Conduct | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
bb01abc5-c4b9-4cef-923c-a3630daec740 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 41 | opea-semantic-v1 | 87da1e59f893b0a1 | *When the RFC process is needed?*
The RFC process is necessary for changes which have a substantial impact on end users, workflow, or user facing API. It generally includes: | ai_ref_knowledge | OPEA Documentation | *When the RFC process is needed?*
The RFC process is necessary for changes which have a substantial impact on end users, workflow, or user facing API. It generally includes: | *When the RFC process is needed?*
The RFC process is necessary for changes which have a substantial impact on end users, workflow, or user facing API. It generally includes: | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c0b5d4dd-623b-4c94-b430-29824b008c86 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 37 | opea-semantic-v1 | 88edf1f071f51e3c | ### Reporting Issues
If you run into unexpected behavior, please report it using the `Issues` page under the corresponding GitHub project but first check if there is already a similar existing issue. If not, please follow the Bug Report template and supply as much information as you can. It's helpful if the issue submi... | ai_ref_knowledge | OPEA Documentation | ### Reporting Issues
If you run into unexpected behavior, please report it using the `Issues` page under the corresponding GitHub project but first check if there is already a similar existing issue. If not, please follow the Bug Report template and supply as much information as you can. It's helpful if the issue submi... | ### Reporting Issues
If you run into unexpected behavior, please report it using the `Issues` page under the corresponding GitHub project but first check if there is already a similar existing issue. If not, please follow the Bug Report template and supply as much information as you can. It's helpful if the issue submi... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c2ebbf4f-c608-4402-afee-4b67c00b0751 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 21 | opea-semantic-v1 | b0b9414d5131dc72 | %% Questions interaction direction LR a[User Input Query] -->|1| UI UI -->|2| GW GW <==>|3| ChatQnA-MegaService EM ==>|4| RET RET ==>|5| RER RER ==>|6| LLM
%% Embedding service flow
direction TB
EM <-.->|3'| TEI_EM
RET <-.->|4'| R_RET
RER <-.->|5'| TEI_RER
LLM <-.->|6'| LLM_gen | ai_ref_knowledge | OPEA Documentation | %% Questions interaction direction LR a[User Input Query] -->|1| UI UI -->|2| GW GW <==>|3| ChatQnA-MegaService EM ==>|4| RET RET ==>|5| RER RER ==>|6| LLM
%% Embedding service flow
direction TB
EM <-.->|3'| TEI_EM
RET <-.->|4'| R_RET
RER <-.->|5'| TEI_RER
LLM <-.->|6'| LLM_gen | %% Questions interaction direction LR a[User Input Query] -->|1| UI UI -->|2| GW GW <==>|3| ChatQnA-MegaService EM ==>|4| RET RET ==>|5| RER RER ==>|6| LLM
%% Embedding service flow
direction TB
EM <-.->|3'| TEI_EM
RET <-.->|4'| R_RET
RER <-.->|5'| TEI_RER
LLM <-.->|6'| LLM_gen | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c3bd0dd1-db1a-4ebb-9b8a-7006a18026e8 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 38 | opea-semantic-v1 | 7b9536880d58b506 | supply as much information as you can. It's helpful if the issue submitter can narrow down the problematic behavior to a minimal reproducible test case.
### Proposing New Features | ai_ref_knowledge | OPEA Documentation | supply as much information as you can. It's helpful if the issue submitter can narrow down the problematic behavior to a minimal reproducible test case.
### Proposing New Features | supply as much information as you can. It's helpful if the issue submitter can narrow down the problematic behavior to a minimal reproducible test case.
### Proposing New Features | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d25ba05b-2f8c-4743-aa47-b81831c531d6 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 33 | opea-semantic-v1 | 53f09dd263934bcb | ### Community Discussions
Developers are encouraged to participate in discussions by opening an issue in one of the GitHub repos at https://github.com/opea-project. Alternatively, they can send an email to [info@opea.dev](mailto://info@opea.dev) or subscribe to [X/Twitter](https://twitter.com/opeadev) and [LinkedIn Pag... | ai_ref_knowledge | OPEA Documentation | ### Community Discussions
Developers are encouraged to participate in discussions by opening an issue in one of the GitHub repos at https://github.com/opea-project. Alternatively, they can send an email to [info@opea.dev](mailto://info@opea.dev) or subscribe to [X/Twitter](https://twitter.com/opeadev) and [LinkedIn Pag... | ### Community Discussions
Developers are encouraged to participate in discussions by opening an issue in one of the GitHub repos at https://github.com/opea-project. Alternatively, they can send an email to [info@opea.dev](mailto://info@opea.dev) or subscribe to [X/Twitter](https://twitter.com/opeadev) and [LinkedIn Pag... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d555ad3a-3edf-4db2-bebf-456269956494 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 13 | opea-semantic-v1 | ecd4fa56e90da326 | requirement. However, since OPEA is intended for enterprise applications, supporting Kubernetes deployment is highly encouraged. You can find [examples for Kubernetes deployment](https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/kubernetes/helm#readme) using Helm Charts.
- Navigate to [OPEA GenAIExamples]... | ai_ref_knowledge | OPEA Documentation | requirement. However, since OPEA is intended for enterprise applications, supporting Kubernetes deployment is highly encouraged. You can find [examples for Kubernetes deployment](https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/kubernetes/helm#readme) using Helm Charts.
- Navigate to [OPEA GenAIExamples]... | requirement. However, since OPEA is intended for enterprise applications, supporting Kubernetes deployment is highly encouraged. You can find [examples for Kubernetes deployment](https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/kubernetes/helm#readme) using Helm Charts.
- Navigate to [OPEA GenAIExamples]... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d9d15c47-d634-40c3-abb1-f3b19403d640 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 26 | opea-semantic-v1 | 061b954823df3fa9 | ├── test_compose_pinecone_on_xeon.sh │ ├── test_compose_qdrant_on_xeon.sh │ ├── test_compose_tgi_on_gaudi.sh │ ├── test_compose_tgi_on_xeon.sh │ ├── test_compose_without_rerank_on_gaudi.sh │ ├── test_compose_without_rerank_on_xeon.sh │ ├── test_gmc_on_gaudi.sh │ ├── test_gmc_on_xeon.sh └── ui
- **File Descriptions**:
... | ai_ref_knowledge | OPEA Documentation | ├── test_compose_pinecone_on_xeon.sh │ ├── test_compose_qdrant_on_xeon.sh │ ├── test_compose_tgi_on_gaudi.sh │ ├── test_compose_tgi_on_xeon.sh │ ├── test_compose_without_rerank_on_gaudi.sh │ ├── test_compose_without_rerank_on_xeon.sh │ ├── test_gmc_on_gaudi.sh │ ├── test_gmc_on_xeon.sh └── ui
- **File Descriptions**:
... | ├── test_compose_pinecone_on_xeon.sh │ ├── test_compose_qdrant_on_xeon.sh │ ├── test_compose_tgi_on_gaudi.sh │ ├── test_compose_tgi_on_xeon.sh │ ├── test_compose_without_rerank_on_gaudi.sh │ ├── test_compose_without_rerank_on_xeon.sh │ ├── test_gmc_on_gaudi.sh │ ├── test_gmc_on_xeon.sh └── ui
- **File Descriptions**:
... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
ecc9a27f-303b-410f-989a-b19167c31739 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 15 | opea-semantic-v1 | 8746703d4156ea4c | all the microservices to build your application, let's make sure all the required building blocks are available!. Take a look at this **ChatQnA Flow Chart**:
```mermaid | ai_ref_knowledge | OPEA Documentation | all the microservices to build your application, let's make sure all the required building blocks are available!. Take a look at this **ChatQnA Flow Chart**:
```mermaid | all the microservices to build your application, let's make sure all the required building blocks are available!. Take a look at this **ChatQnA Flow Chart**:
```mermaid | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fc472d47-36c8-4903-88ba-a0d343d2e540 | OPEA Documentation | file://datasets/opea-docs/community/CONTRIBUTING.md | unknown | f2a8e60a-8777-4c8b-80d6-1ff816806cb5 | 22 | opea-semantic-v1 | 82d9183f63ed4d29 | %% Embedding service flow direction TB EM <-.->|3'| TEI_EM RET <-.->|4'| R_RET RER <-.->|5'| TEI_RER LLM <-.->|6'| LLM_gen
direction TB
%% Vector DB interaction
R_RET <-.->|d|VDB
DP <-.->|d|VDB | ai_ref_knowledge | OPEA Documentation | %% Embedding service flow direction TB EM <-.->|3'| TEI_EM RET <-.->|4'| R_RET RER <-.->|5'| TEI_RER LLM <-.->|6'| LLM_gen
direction TB
%% Vector DB interaction
R_RET <-.->|d|VDB
DP <-.->|d|VDB | %% Embedding service flow direction TB EM <-.->|3'| TEI_EM RET <-.->|4'| R_RET RER <-.->|5'| TEI_RER LLM <-.->|6'| LLM_gen
direction TB
%% Vector DB interaction
R_RET <-.->|d|VDB
DP <-.->|d|VDB | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
68583837-4b4a-40c0-a57c-aff2e8c4d32c | OPEA Documentation | file://datasets/opea-docs/community/SECURITY.md | unknown | e8ab9f13-af17-45fc-b8cc-6d54b595fd01 | 0 | opea-semantic-v1 | 8e9626281aec5933 | ## Script Usage Notice
SCRIPT USAGE NOTICE: By downloading and using any script file included with the associated software package (such as files with .bat, .cmd, or .JS extensions, Dockerfiles, or any other type of file that, when executed, automatically downloads and/or installs files onto your system)
(the “Script F... | ai_ref_knowledge | OPEA Documentation | ## Script Usage Notice
SCRIPT USAGE NOTICE: By downloading and using any script file included with the associated software package (such as files with .bat, .cmd, or .JS extensions, Dockerfiles, or any other type of file that, when executed, automatically downloads and/or installs files onto your system)
(the “Script F... | ## Script Usage Notice
SCRIPT USAGE NOTICE: By downloading and using any script file included with the associated software package (such as files with .bat, .cmd, or .JS extensions, Dockerfiles, or any other type of file that, when executed, automatically downloads and/or installs files onto your system)
(the “Script F... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
0b71340d-aa90-461d-9ffe-ce04b3e5045e | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 6 | opea-semantic-v1 | f2e565401cae3f8a | 1. **Update [OPEA data prep vector database readme file](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep#readme)**<br> Follow the pattern *option name with link to a readme file.*
 | ai_ref_knowledge | OPEA Documentation | 1. **Update [OPEA data prep vector database readme file](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep#readme)**<br> Follow the pattern *option name with link to a readme file.*
 | 1. **Update [OPEA data prep vector database readme file](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep#readme)**<br> Follow the pattern *option name with link to a readme file.*
 | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
30456590-6350-42e2-9647-5fcfda90eb09 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 11 | opea-semantic-v1 | 9a7769a0c16ee3fd | vector database service is up and running 1. This could be a Docker ps or Kubernetes pod list command and what to look for 2.
Provide troubleshooting tips if you are aware of common problems (like port in use or a missing dependency or needing a token to access a private registry etc)
- **Instructions on how to use th... | ai_ref_knowledge | OPEA Documentation | vector database service is up and running 1. This could be a Docker ps or Kubernetes pod list command and what to look for 2.
Provide troubleshooting tips if you are aware of common problems (like port in use or a missing dependency or needing a token to access a private registry etc)
- **Instructions on how to use th... | vector database service is up and running 1. This could be a Docker ps or Kubernetes pod list command and what to look for 2.
Provide troubleshooting tips if you are aware of common problems (like port in use or a missing dependency or needing a token to access a private registry etc)
- **Instructions on how to use th... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
382eece1-2b92-4aeb-9242-fadaffe5bd1b | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 4 | opea-semantic-v1 | bee1ebfaf56f3428 | launch it, 3. determine whether the service is up and running, 4. use it, 5. and provide test scripts for integration into the OPEA CICD.
*We indicate below which files need to be provided and in which directories they must land to ensure users and developers can find them easily.* | ai_ref_knowledge | OPEA Documentation | launch it, 3. determine whether the service is up and running, 4. use it, 5. and provide test scripts for integration into the OPEA CICD.
*We indicate below which files need to be provided and in which directories they must land to ensure users and developers can find them easily.* | launch it, 3. determine whether the service is up and running, 4. use it, 5. and provide test scripts for integration into the OPEA CICD.
*We indicate below which files need to be provided and in which directories they must land to ensure users and developers can find them easily.* | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
41631fb6-981c-4d0b-b166-464817e57a13 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 0 | opea-semantic-v1 | 31f3fb2b73b61ccf | # Contributing A New Vector Database to OPEA
The [Open Platform for Enterprise AI (OPEA)](https://opea.dev) is an open source project under Linux Foundation AI and Data that seeks to reduce the barriers to GenAI adoption in enterprises by bridging AI and cloud native technologies through sample application blueprints, ... | ai_ref_knowledge | OPEA Documentation | # Contributing A New Vector Database to OPEA
The [Open Platform for Enterprise AI (OPEA)](https://opea.dev) is an open source project under Linux Foundation AI and Data that seeks to reduce the barriers to GenAI adoption in enterprises by bridging AI and cloud native technologies through sample application blueprints, ... | # Contributing A New Vector Database to OPEA
The [Open Platform for Enterprise AI (OPEA)](https://opea.dev) is an open source project under Linux Foundation AI and Data that seeks to reduce the barriers to GenAI adoption in enterprises by bridging AI and cloud native technologies through sample application blueprints, ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
4bc6b4c4-c487-40d8-b230-577d4405f2ea | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 2 | opea-semantic-v1 | 9cd8af7b153c665b | completeness, submit a PR to the OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) to illustrate customizing the ChatQnA example application. We cover each of these in greater detail below.
## Contributing a new Vector Database to GenAIComps
**The OPEA dataprep service leverages a vector d... | ai_ref_knowledge | OPEA Documentation | completeness, submit a PR to the OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) to illustrate customizing the ChatQnA example application. We cover each of these in greater detail below.
## Contributing a new Vector Database to GenAIComps
**The OPEA dataprep service leverages a vector d... | completeness, submit a PR to the OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) to illustrate customizing the ChatQnA example application. We cover each of these in greater detail below.
## Contributing a new Vector Database to GenAIComps
**The OPEA dataprep service leverages a vector d... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
4da617a8-fbc6-48ce-a3d6-fe2b7e4acc4a | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 8 | opea-semantic-v1 | fb7491571d3ec98c | README_\<vector database name\>_\<toolchain\>.md.**<br> Neo4J has two READMEs, one for LangChain and the other for LlamaIndex.<br> Here are some examples: - [README_redis.md](https://github.com/opea-project/GenAIComps/blob/main/comps/dataprep/src/README_redis.md) - [README_qdrant.md](https://github.com/opea-project/Gen... | ai_ref_knowledge | OPEA Documentation | README_\<vector database name\>_\<toolchain\>.md.**<br> Neo4J has two READMEs, one for LangChain and the other for LlamaIndex.<br> Here are some examples: - [README_redis.md](https://github.com/opea-project/GenAIComps/blob/main/comps/dataprep/src/README_redis.md) - [README_qdrant.md](https://github.com/opea-project/Gen... | README_\<vector database name\>_\<toolchain\>.md.**<br> Neo4J has two READMEs, one for LangChain and the other for LlamaIndex.<br> Here are some examples: - [README_redis.md](https://github.com/opea-project/GenAIComps/blob/main/comps/dataprep/src/README_redis.md) - [README_qdrant.md](https://github.com/opea-project/Gen... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
5f4d9dd1-7176-4bfa-ac3a-fa54c9096951 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 5 | opea-semantic-v1 | 6d86344756f22426 | *We indicate below which files need to be provided and in which directories they must land to ensure users and developers can find them easily.*
1. **Update [OPEA data prep vector database readme file](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep#readme)**<br>
Follow the pattern *option name with... | ai_ref_knowledge | OPEA Documentation | *We indicate below which files need to be provided and in which directories they must land to ensure users and developers can find them easily.*
1. **Update [OPEA data prep vector database readme file](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep#readme)**<br>
Follow the pattern *option name with... | *We indicate below which files need to be provided and in which directories they must land to ensure users and developers can find them easily.*
1. **Update [OPEA data prep vector database readme file](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep#readme)**<br>
Follow the pattern *option name with... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7136db2d-ac21-4f83-a86d-12c2d62fdcb1 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 14 | opea-semantic-v1 | 28c1903f34bb1366 | AMD’s ROCm), in environments such as Docker and Kubernetes, including how to customize an application pipeline through the use of different vector database backends. 1.
**Provide ChatQnA docker compose file**<br>
Navigate to the [GenAIExamples](https://github.com/opea-project/GenAIExamples) OPEA subproject to provide a... | ai_ref_knowledge | OPEA Documentation | AMD’s ROCm), in environments such as Docker and Kubernetes, including how to customize an application pipeline through the use of different vector database backends. 1.
**Provide ChatQnA docker compose file**<br>
Navigate to the [GenAIExamples](https://github.com/opea-project/GenAIExamples) OPEA subproject to provide a... | AMD’s ROCm), in environments such as Docker and Kubernetes, including how to customize an application pipeline through the use of different vector database backends. 1.
**Provide ChatQnA docker compose file**<br>
Navigate to the [GenAIExamples](https://github.com/opea-project/GenAIExamples) OPEA subproject to provide a... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
740ae65d-cb0f-436a-bb18-db14c6e0abe0 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 13 | opea-semantic-v1 | fb3fcb14255b4de5 | How to delete the service in Docker or Kubernetes 2. How to verify that the service is no longer running and that resources are recouped.
## ChatQnA GenAIExample Vector Database Usage
The OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) houses multiple GenAI RAG sample applications such ... | ai_ref_knowledge | OPEA Documentation | How to delete the service in Docker or Kubernetes 2. How to verify that the service is no longer running and that resources are recouped.
## ChatQnA GenAIExample Vector Database Usage
The OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) houses multiple GenAI RAG sample applications such ... | How to delete the service in Docker or Kubernetes 2. How to verify that the service is no longer running and that resources are recouped.
## ChatQnA GenAIExample Vector Database Usage
The OPEA sub-project [GenAIExamples](https://github.com/opea-project/GenAIExamples) houses multiple GenAI RAG sample applications such ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7e624b5e-6fd1-4afd-bacd-f8d96176065a | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 16 | opea-semantic-v1 | 785712d98511d537 | See examples: - [chatQnA docker compose using the pinecone vector database](https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/docker_compose/intel/cpu/xeon/compose_pinecone.yaml) - [chatQnA docker compose using the qdrant vector database](https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/doc... | ai_ref_knowledge | OPEA Documentation | See examples: - [chatQnA docker compose using the pinecone vector database](https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/docker_compose/intel/cpu/xeon/compose_pinecone.yaml) - [chatQnA docker compose using the qdrant vector database](https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/doc... | See examples: - [chatQnA docker compose using the pinecone vector database](https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/docker_compose/intel/cpu/xeon/compose_pinecone.yaml) - [chatQnA docker compose using the qdrant vector database](https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/doc... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
86b89862-8c03-4529-99ee-70ed6ad81849 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 3 | opea-semantic-v1 | a22fbd9567753c44 | multi-modal input, indexing schemes available, ability to auto re-index (in response to underlying datastore updates), whether open source and/or offered as a commercially supported service.
Your Pull Request (PR) to [GenAIComps](https://github.com/opea-project/GenAIComps) must cover how to:
1. install your vector data... | ai_ref_knowledge | OPEA Documentation | multi-modal input, indexing schemes available, ability to auto re-index (in response to underlying datastore updates), whether open source and/or offered as a commercially supported service.
Your Pull Request (PR) to [GenAIComps](https://github.com/opea-project/GenAIComps) must cover how to:
1. install your vector data... | multi-modal input, indexing schemes available, ability to auto re-index (in response to underlying datastore updates), whether open source and/or offered as a commercially supported service.
Your Pull Request (PR) to [GenAIComps](https://github.com/opea-project/GenAIComps) must cover how to:
1. install your vector data... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
896af47d-b745-45d3-a2eb-82ac8408c465 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 9 | opea-semantic-v1 | 8e3d9425cb5e5bb4 | 3. **Add the README file to the vector database readme directory**<br> [https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep/src](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep/src)
4. **The Vector Database README needs to cover:**
- **A brief introduction** to the vector database s... | ai_ref_knowledge | OPEA Documentation | 3. **Add the README file to the vector database readme directory**<br> [https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep/src](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep/src)
4. **The Vector Database README needs to cover:**
- **A brief introduction** to the vector database s... | 3. **Add the README file to the vector database readme directory**<br> [https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep/src](https://github.com/opea-project/GenAIComps/tree/main/comps/dataprep/src)
4. **The Vector Database README needs to cover:**
- **A brief introduction** to the vector database s... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9f2c7805-3e17-48ca-aed7-39db286c7b33 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 12 | opea-semantic-v1 | e27ec530ddc582be | when. - **Share examples of service calls** 1. Include a link to a sample document (word, pdf, url, image) that the user can upload ..
this helps to illustrate/lock down exactly what output is to be expected. 2. Curl or other call to upload the document and expected response
3. Curl or other call to retrieve similar d... | ai_ref_knowledge | OPEA Documentation | when. - **Share examples of service calls** 1. Include a link to a sample document (word, pdf, url, image) that the user can upload ..
this helps to illustrate/lock down exactly what output is to be expected. 2. Curl or other call to upload the document and expected response
3. Curl or other call to retrieve similar d... | when. - **Share examples of service calls** 1. Include a link to a sample document (word, pdf, url, image) that the user can upload ..
this helps to illustrate/lock down exactly what output is to be expected. 2. Curl or other call to upload the document and expected response
3. Curl or other call to retrieve similar d... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
cb7c6644-f1fe-4e0a-b749-42c061a80851 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 1 | opea-semantic-v1 | feb7e3e2f74f223c | enterprises by bridging AI and cloud native technologies through sample application blueprints, a rich set of microservice components including Vector Databases, deployment options and more.
To contribute a new Vector Database to OPEA, you would need to modify minimally the OPEA sub-project [GenAIComps](https://github.... | ai_ref_knowledge | OPEA Documentation | enterprises by bridging AI and cloud native technologies through sample application blueprints, a rich set of microservice components including Vector Databases, deployment options and more.
To contribute a new Vector Database to OPEA, you would need to modify minimally the OPEA sub-project [GenAIComps](https://github.... | enterprises by bridging AI and cloud native technologies through sample application blueprints, a rich set of microservice components including Vector Databases, deployment options and more.
To contribute a new Vector Database to OPEA, you would need to modify minimally the OPEA sub-project [GenAIComps](https://github.... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
d46347dc-d253-48a3-808e-5e24c0d12491 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 15 | opea-semantic-v1 | 4bffbe7b1364b03f | [docker compose files for ChatQnA application variants running on CPUs](https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/docker_compose/intel/cpu/xeon) contains docker compose file variants that span, among other things, using different vector database backends.
See examples:
- [chatQnA docker compose u... | ai_ref_knowledge | OPEA Documentation | [docker compose files for ChatQnA application variants running on CPUs](https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/docker_compose/intel/cpu/xeon) contains docker compose file variants that span, among other things, using different vector database backends.
See examples:
- [chatQnA docker compose u... | [docker compose files for ChatQnA application variants running on CPUs](https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/docker_compose/intel/cpu/xeon) contains docker compose file variants that span, among other things, using different vector database backends.
See examples:
- [chatQnA docker compose u... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e5bc6530-e3b0-4a2f-ae7d-436e233a4736 | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 7 | opea-semantic-v1 | 17f09f7d9b579b28 | 
2. **Create a README_\<vector database name\>.md or README_\<vector database name\>_\<toolchain\>.md.**<br>
Neo4J has two READMEs, one for LangChain and the other for LlamaIndex.<br>
Here are some examples:
- [README_redis.md](https://github.com/opea-project/GenAICom... | ai_ref_knowledge | OPEA Documentation | 
2. **Create a README_\<vector database name\>.md or README_\<vector database name\>_\<toolchain\>.md.**<br>
Neo4J has two READMEs, one for LangChain and the other for LlamaIndex.<br>
Here are some examples:
- [README_redis.md](https://github.com/opea-project/GenAICom... | 
2. **Create a README_\<vector database name\>.md or README_\<vector database name\>_\<toolchain\>.md.**<br>
Neo4J has two READMEs, one for LangChain and the other for LlamaIndex.<br>
Here are some examples:
- [README_redis.md](https://github.com/opea-project/GenAICom... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f0b60743-9660-43a4-963a-2c1295ef239e | OPEA Documentation | file://datasets/opea-docs/community/add_vectorDB.md | unknown | 72018a53-e038-4945-ac62-59568f1437cf | 10 | opea-semantic-v1 | 52e758893a21351f | how to launch the same in a Kubernetes environment 1. **Necessary environment variables** 2. **Mention any namespace** that needs to be defined and used 3.
**Image**
- Or Image download path (repository url, image name, tag)
- Or build from source instructions
4. **Deployment collateral:** Helm chart or docker file... | ai_ref_knowledge | OPEA Documentation | how to launch the same in a Kubernetes environment 1. **Necessary environment variables** 2. **Mention any namespace** that needs to be defined and used 3.
**Image**
- Or Image download path (repository url, image name, tag)
- Or build from source instructions
4. **Deployment collateral:** Helm chart or docker file... | how to launch the same in a Kubernetes environment 1. **Necessary environment variables** 2. **Mention any namespace** that needs to be defined and used 3.
**Image**
- Or Image download path (repository url, image name, tag)
- Or build from source instructions
4. **Deployment collateral:** Helm chart or docker file... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
10c85c69-922c-48c1-8a82-43a9160e94e1 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 15 | opea-semantic-v1 | e839e6fa80bba09d | a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies will apply for all Collaborators in the Project. 3.
When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site a... | ai_ref_knowledge | OPEA Documentation | a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies will apply for all Collaborators in the Project. 3.
When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site a... | a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies will apply for all Collaborators in the Project. 3.
When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site a... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
1eab3c64-73b6-46e1-b7a7-b28416eab4b7 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 1 | opea-semantic-v1 | 2d6548929b9b4510 | All contributors (including committers, maintainers, and other technical positions) and other participants in the Project (collectively, “Collaborators”) must comply with the terms of this Charter.
## 1. Mission and Scope of the Project | ai_ref_knowledge | OPEA Documentation | All contributors (including committers, maintainers, and other technical positions) and other participants in the Project (collectively, “Collaborators”) must comply with the terms of this Charter.
## 1. Mission and Scope of the Project | All contributors (including committers, maintainers, and other technical positions) and other participants in the Project (collectively, “Collaborators”) must comply with the terms of this Charter.
## 1. Mission and Scope of the Project | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
26b9dad2-7f94-4ac3-8089-18a6339533dd | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 11 | opea-semantic-v1 | ae3fe6eadb3f979b | ## 3. TSC Voting
1. While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move forward, the voting members of the TSC will vote on a one vote per voting member basis. 2. Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be pres... | ai_ref_knowledge | OPEA Documentation | ## 3. TSC Voting
1. While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move forward, the voting members of the TSC will vote on a one vote per voting member basis. 2. Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be pres... | ## 3. TSC Voting
1. While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move forward, the voting members of the TSC will vote on a one vote per voting member basis. 2. Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be pres... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
26d7bcfc-823e-4e09-b13c-cd0ba0b05433 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 13 | opea-semantic-v1 | b1967217c3a72ca9 | be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution.
## 4. Compliance with Policies | ai_ref_knowledge | OPEA Documentation | be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution.
## 4. Compliance with Policies | be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution.
## 4. Compliance with Policies | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
27aaa0c7-a8f2-40d4-a222-5d5552f1a941 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 8 | opea-semantic-v1 | a25d08fc63fe2fda | TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC.
The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and LF AI & Data Foundation, a directed fund of The ... | ai_ref_knowledge | OPEA Documentation | TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC.
The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and LF AI & Data Foundation, a directed fund of The ... | TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC.
The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and LF AI & Data Foundation, a directed fund of The ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
375365df-0621-471e-b68a-597cacb486cc | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 21 | opea-semantic-v1 | d94fe3c5b9c1c2c9 | ## 6. General Rules and Operations.
1. The Project will:
1. engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, Joint Development Foundation and other partner organizations in the open source communi... | ai_ref_knowledge | OPEA Documentation | ## 6. General Rules and Operations.
1. The Project will:
1. engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, Joint Development Foundation and other partner organizations in the open source communi... | ## 6. General Rules and Operations.
1. The Project will:
1. engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, Joint Development Foundation and other partner organizations in the open source communi... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3f5f572d-de28-46c1-889e-861226dbc1af | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 4 | opea-semantic-v1 | 6dae32e59f82fcaf | ## 2. Technical Steering Committee
1. The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project. 2. The TSC voting members are initially those individuals listed as voting members of the TSC in the GOVERNANCE.MD file in the Project’s governance repo (moved t... | ai_ref_knowledge | OPEA Documentation | ## 2. Technical Steering Committee
1. The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project. 2. The TSC voting members are initially those individuals listed as voting members of the TSC in the GOVERNANCE.MD file in the Project’s governance repo (moved t... | ## 2. Technical Steering Committee
1. The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project. 2. The TSC voting members are initially those individuals listed as voting members of the TSC in the GOVERNANCE.MD file in the Project’s governance repo (moved t... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
50ba41e1-ed21-4246-9aa4-f72dddc11042 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 6 | opea-semantic-v1 | c190a3aadbab7212 | to be open to the public, and can be conducted electronically, via teleconference, or in person. 3. TSC projects generally will involve Contributors and Maintainers.
The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:
1. Contributors include anyo... | ai_ref_knowledge | OPEA Documentation | to be open to the public, and can be conducted electronically, via teleconference, or in person. 3. TSC projects generally will involve Contributors and Maintainers.
The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:
1. Contributors include anyo... | to be open to the public, and can be conducted electronically, via teleconference, or in person. 3. TSC projects generally will involve Contributors and Maintainers.
The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:
1. Contributors include anyo... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
562ab97b-9b27-4bf0-baad-1c4b02bdbd9b | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 28 | opea-semantic-v1 | a1c13d567df6aee2 | ## 8. Amendments
1. This charter may be amended by a two-thirds vote of each of the entire TSC and is subject to approval by LF Projects. | ai_ref_knowledge | OPEA Documentation | ## 8. Amendments
1. This charter may be amended by a two-thirds vote of each of the entire TSC and is subject to approval by LF Projects. | ## 8. Amendments
1. This charter may be amended by a two-thirds vote of each of the entire TSC and is subject to approval by LF Projects. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
6188eca9-60f2-4f4e-a478-754173d9f028 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 23 | opea-semantic-v1 | 6ffac3d9ed752938 | ## 7. Intellectual Property Policy
1. Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project. 2. Except as described in Section 7.c.... | ai_ref_knowledge | OPEA Documentation | ## 7. Intellectual Property Policy
1. Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project. 2. Except as described in Section 7.c.... | ## 7. Intellectual Property Policy
1. Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project. 2. Except as described in Section 7.c.... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
63e16082-aec5-41c7-885f-e19efff53b24 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 18 | opea-semantic-v1 | c7c13bb457ba2232 | ## 5. Community Assets
1. LF Projects will hold title to all trade or service marks used by the Project (“Project Trademarks”), whether based on common law or registered rights. Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by Coll... | ai_ref_knowledge | OPEA Documentation | ## 5. Community Assets
1. LF Projects will hold title to all trade or service marks used by the Project (“Project Trademarks”), whether based on common law or registered rights. Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by Coll... | ## 5. Community Assets
1. LF Projects will hold title to all trade or service marks used by the Project (“Project Trademarks”), whether based on common law or registered rights. Project Trademarks will be transferred and assigned to LF Projects to hold on behalf of the Project. Any use of any Project Trademarks by Coll... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7348fba2-eb4d-4914-a451-7a78edccb1c3 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 19 | opea-semantic-v1 | 53c60fe0cfa0145d | such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community. 3.
Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status... | ai_ref_knowledge | OPEA Documentation | such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community. 3.
Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status... | such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community. 3.
Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
74524ac3-05e4-4f19-b823-768817be390e | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 24 | opea-semantic-v1 | bf2562aab92829d1 | following: 1. All new inbound code contributions to the Project must be made using Apache License, Version 2.0 available at http://www.apache.org/licenses/LICENSE-2.0 (the “Project License”). 2.
All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate... | ai_ref_knowledge | OPEA Documentation | following: 1. All new inbound code contributions to the Project must be made using Apache License, Version 2.0 available at http://www.apache.org/licenses/LICENSE-2.0 (the “Project License”). 2.
All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate... | following: 1. All new inbound code contributions to the Project must be made using Apache License, Version 2.0 available at http://www.apache.org/licenses/LICENSE-2.0 (the “Project License”). 2.
All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
77c8d90e-e2d4-4232-a019-058f4e8747de | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 16 | opea-semantic-v1 | 8ad6e761e622785b | individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TSC, regardless of competitive interests.
Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than... | ai_ref_knowledge | OPEA Documentation | individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TSC, regardless of competitive interests.
Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than... | individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TSC, regardless of competitive interests.
Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
7913a2c3-b09f-401d-8538-2989da03bc9a | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 26 | opea-semantic-v1 | c019d652f39eae7a | justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC. 4.
Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file. | ai_ref_knowledge | OPEA Documentation | justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC. 4.
Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file. | justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC. 4.
Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
8f876cb7-6463-4d64-b07b-5ec9161b285f | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 5 | opea-semantic-v1 | 433a0c144987e5af | approach for determining the voting members of the TSC, and any such alternative approach will be documented in the GOVERNANCE file (now the [TSC.rst](TSC.rst) file).
The Project intends to determine additional details on composition of the TSC to enable increased diversity of organizations represented on the TSC withi... | ai_ref_knowledge | OPEA Documentation | approach for determining the voting members of the TSC, and any such alternative approach will be documented in the GOVERNANCE file (now the [TSC.rst](TSC.rst) file).
The Project intends to determine additional details on composition of the TSC to enable increased diversity of organizations represented on the TSC withi... | approach for determining the voting members of the TSC, and any such alternative approach will be documented in the GOVERNANCE file (now the [TSC.rst](TSC.rst) file).
The Project intends to determine additional details on composition of the TSC to enable increased diversity of organizations represented on the TSC withi... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9472cf78-0da6-460f-9391-ee6bd62cd615 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 7 | opea-semantic-v1 | 103e790a3751fdf7 | a Maintainer by a majority approval of the existing Maintainers. A Maintainer may be removed by a majority approval of the other existing Maintainers. 4.
Participation in the Project through becoming a Contributor and Maintainer is open to anyone so long as they abide by the terms of this Charter. 5. The TSC may (1) es... | ai_ref_knowledge | OPEA Documentation | a Maintainer by a majority approval of the existing Maintainers. A Maintainer may be removed by a majority approval of the other existing Maintainers. 4.
Participation in the Project through becoming a Contributor and Maintainer is open to anyone so long as they abide by the terms of this Charter. 5. The TSC may (1) es... | a Maintainer by a majority approval of the existing Maintainers. A Maintainer may be removed by a majority approval of the other existing Maintainers. 4.
Participation in the Project through becoming a Contributor and Maintainer is open to anyone so long as they abide by the terms of this Charter. 5. The TSC may (1) es... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
98f0ec93-01cd-4a55-b6fa-3dc03ea0220b | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 12 | opea-semantic-v1 | fc9be7b3795d8143 | attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. 4.
In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution. | ai_ref_knowledge | OPEA Documentation | attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. 4.
In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution. | attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. 4.
In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9bd17103-fff1-4b6f-86d8-35d0a5573d9c | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 9 | opea-semantic-v1 | bdef2a453c06240f | and removing sub-projects; 4. creating committees or working groups (for example, an executive or architectural committee or end-user advisory committee) to support the Project; 5.
appointing representatives to work with other open source or open standards communities;
6. establishing community norms, workflows, issui... | ai_ref_knowledge | OPEA Documentation | and removing sub-projects; 4. creating committees or working groups (for example, an executive or architectural committee or end-user advisory committee) to support the Project; 5.
appointing representatives to work with other open source or open standards communities;
6. establishing community norms, workflows, issui... | and removing sub-projects; 4. creating committees or working groups (for example, an executive or architectural committee or end-user advisory committee) to support the Project; 5.
appointing representatives to work with other open source or open standards communities;
6. establishing community norms, workflows, issui... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
9d03f73d-16eb-43a6-916a-f500f5bc819e | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 10 | opea-semantic-v1 | 858d1c01348b6683 | necessary, voting on technical matters relating to the code base that affect multiple sub-projects; and 9. coordinating any marketing, events, or communications regarding the Project.
## 3. TSC Voting | ai_ref_knowledge | OPEA Documentation | necessary, voting on technical matters relating to the code base that affect multiple sub-projects; and 9. coordinating any marketing, events, or communications regarding the Project.
## 3. TSC Voting | necessary, voting on technical matters relating to the code base that affect multiple sub-projects; and 9. coordinating any marketing, events, or communications regarding the Project.
## 3. TSC Voting | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b12f5edd-3221-4f0b-a299-3b401d625874 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 27 | opea-semantic-v1 | 2b2aa4d5f5741a60 | Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.
## 8. Amendments | ai_ref_knowledge | OPEA Documentation | Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.
## 8. Amendments | Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.
## 8. Amendments | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
b4e3fcec-d7dc-4b6d-827b-7c9d8082f531 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 17 | opea-semantic-v1 | a1edddd010c522c7 | and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the Series Manager.
## 5. Community Assets | ai_ref_knowledge | OPEA Documentation | and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the Series Manager.
## 5. Community Assets | and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the Series Manager.
## 5. Community Assets | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
badaf7c0-3fa7-4b14-a0c8-6088b6f4ef9b | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 14 | opea-semantic-v1 | 4f5ecc713e3bd920 | ## 4. Compliance with Policies
1. This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.or... | ai_ref_knowledge | OPEA Documentation | ## 4. Compliance with Policies
1. This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.or... | ## 4. Compliance with Policies
1. This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.or... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
c0e7e9b2-2c6c-405d-8fd7-329a4ea69aba | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 0 | opea-semantic-v1 | 5637bc08ae77f998 | Adopted April 12, 2024
This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OPEA open source project, which has been established as OPEA a Series of LF Projects, LLC (the “Project”). LF Projects, LLC (“LF Projects”) is a Delaware series limited liability compa... | ai_ref_knowledge | OPEA Documentation | Adopted April 12, 2024
This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OPEA open source project, which has been established as OPEA a Series of LF Projects, LLC (the “Project”). LF Projects, LLC (“LF Projects”) is a Delaware series limited liability compa... | Adopted April 12, 2024
This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OPEA open source project, which has been established as OPEA a Series of LF Projects, LLC (the “Project”). LF Projects, LLC (“LF Projects”) is a Delaware series limited liability compa... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
da2f64e5-6189-4ff4-8d03-28a7e5959598 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 3 | opea-semantic-v1 | 954930488cc0cc31 | the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project.
## 2. Technical Steering Committee | ai_ref_knowledge | OPEA Documentation | the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project.
## 2. Technical Steering Committee | the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project.
## 2. Technical Steering Committee | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e971566e-414a-47a3-8684-8ee1a406afe9 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 25 | opea-semantic-v1 | d75c814707df442c | Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). 5. The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”).
In such cases, the Project will conform to all license requirements of the Upstream Projects, including ... | ai_ref_knowledge | OPEA Documentation | Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). 5. The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”).
In such cases, the Project will conform to all license requirements of the Upstream Projects, including ... | Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). 5. The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”).
In such cases, the Project will conform to all license requirements of the Upstream Projects, including ... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
f29c64a9-71cb-46c5-a6b9-898d8f2fefed | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 2 | opea-semantic-v1 | 22d5565cc34d5bb5 | ## 1. Mission and Scope of the Project
1. The mission of the Project is to develop an ecosystem orchestration framework to efficiently integrate performant GenAI technologies and workflows leading to quicker GenAI adoption and business value. 2. The scope of the Project includes collaborative development under the Proj... | ai_ref_knowledge | OPEA Documentation | ## 1. Mission and Scope of the Project
1. The mission of the Project is to develop an ecosystem orchestration framework to efficiently integrate performant GenAI technologies and workflows leading to quicker GenAI adoption and business value. 2. The scope of the Project includes collaborative development under the Proj... | ## 1. Mission and Scope of the Project
1. The mission of the Project is to develop an ecosystem orchestration framework to efficiently integrate performant GenAI technologies and workflows leading to quicker GenAI adoption and business value. 2. The scope of the Project includes collaborative development under the Proj... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fd8ddf9e-b9df-48ca-969b-846c7cc72b01 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 22 | opea-semantic-v1 | f21eff996b3fd55c | and other partner organizations in the open source community; and 2. respect the rights of all trademark owners, including any branding and trademark usage guidelines.
## 7. Intellectual Property Policy | ai_ref_knowledge | OPEA Documentation | and other partner organizations in the open source community; and 2. respect the rights of all trademark owners, including any branding and trademark usage guidelines.
## 7. Intellectual Property Policy | and other partner organizations in the open source community; and 2. respect the rights of all trademark owners, including any branding and trademark usage guidelines.
## 7. Intellectual Property Policy | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fe408e8c-50f5-4503-ae51-2c7cf34dc0a8 | OPEA Documentation | file://datasets/opea-docs/community/charter.md | unknown | e172fd6a-2d37-46da-9de3-17a929295752 | 20 | opea-semantic-v1 | 17e9fa1377c72ee2 | on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of the Joint Development Foundation or LF Projects, LLC.
## 6. General Rules and Operations. | ai_ref_knowledge | OPEA Documentation | on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of the Joint Development Foundation or LF Projects, LLC.
## 6. General Rules and Operations. | on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of the Joint Development Foundation or LF Projects, LLC.
## 6. General Rules and Operations. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
3fad8de6-f807-4f8b-9a01-2988c47ed873 | OPEA Documentation | file://datasets/opea-docs/community/codeowner.md | unknown | b3d3ad71-948b-42fc-93d7-6a4f0112afa5 | 1 | opea-semantic-v1 | 04ca3a9419136185 | documentation in a repository. They are automatically requested for review when someone opens a pull request (PR) that modifies code or documentation that they own.
Select or contact the corresponding area owner for a PR review or questions
about content within a repository. | ai_ref_knowledge | OPEA Documentation | documentation in a repository. They are automatically requested for review when someone opens a pull request (PR) that modifies code or documentation that they own.
Select or contact the corresponding area owner for a PR review or questions
about content within a repository. | documentation in a repository. They are automatically requested for review when someone opens a pull request (PR) that modifies code or documentation that they own.
Select or contact the corresponding area owner for a PR review or questions
about content within a repository. | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
75161466-2c67-4c25-b8b8-633b9499e0d5 | OPEA Documentation | file://datasets/opea-docs/community/codeowner.md | unknown | b3d3ad71-948b-42fc-93d7-6a4f0112afa5 | 3 | opea-semantic-v1 | cd23f803d2b94d8b | <!-- codeowners.txt is generated at docbuild time from the CODEOWNERS files from each repo --> ```{include} codeowners.txt
## Continuous Integration (CICD) owners | ai_ref_knowledge | OPEA Documentation | <!-- codeowners.txt is generated at docbuild time from the CODEOWNERS files from each repo --> ```{include} codeowners.txt
## Continuous Integration (CICD) owners | <!-- codeowners.txt is generated at docbuild time from the CODEOWNERS files from each repo --> ```{include} codeowners.txt
## Continuous Integration (CICD) owners | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e072796e-280d-41ce-a00a-83da2f2a6caf | OPEA Documentation | file://datasets/opea-docs/community/codeowner.md | unknown | b3d3ad71-948b-42fc-93d7-6a4f0112afa5 | 0 | opea-semantic-v1 | e48446135a48681e | # OPEA Project Code Owners
These tables list the GitHub code owners, as found in the CODEOWNERS file in the
corresponding OPEA repository. Code owners are responsible for code and
documentation in a repository. They are automatically requested for
review when someone opens a pull request (PR) that modifies code or
docu... | ai_ref_knowledge | OPEA Documentation | # OPEA Project Code Owners
These tables list the GitHub code owners, as found in the CODEOWNERS file in the
corresponding OPEA repository. Code owners are responsible for code and
documentation in a repository. They are automatically requested for
review when someone opens a pull request (PR) that modifies code or
docu... | # OPEA Project Code Owners
These tables list the GitHub code owners, as found in the CODEOWNERS file in the
corresponding OPEA repository. Code owners are responsible for code and
documentation in a repository. They are automatically requested for
review when someone opens a pull request (PR) that modifies code or
docu... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
e2f3d3c4-2782-4453-b3ed-c945693df141 | OPEA Documentation | file://datasets/opea-docs/community/codeowner.md | unknown | b3d3ad71-948b-42fc-93d7-6a4f0112afa5 | 2 | opea-semantic-v1 | 5aad38d0be3d40c7 | Select or contact the corresponding area owner for a PR review or questions about content within a repository.
<!-- codeowners.txt is generated at docbuild time from the CODEOWNERS files from each repo -->
```{include} codeowners.txt | ai_ref_knowledge | OPEA Documentation | Select or contact the corresponding area owner for a PR review or questions about content within a repository.
<!-- codeowners.txt is generated at docbuild time from the CODEOWNERS files from each repo -->
```{include} codeowners.txt | Select or contact the corresponding area owner for a PR review or questions about content within a repository.
<!-- codeowners.txt is generated at docbuild time from the CODEOWNERS files from each repo -->
```{include} codeowners.txt | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
22c146f1-f7d6-4e11-a5c4-546112f01b8d | OPEA Documentation | file://datasets/opea-docs/community/codeowner_emeritus.md | unknown | 551c310d-06af-4bfd-ad53-cde9be400173 | 0 | opea-semantic-v1 | 517d62d8b4c489c7 | # OPEA Emeritus Code Owners
The table below acknowledges the OPEA code owners who have left, and whose valuable contributions were crucial to the project's success. We are deeply grateful! | ai_ref_knowledge | OPEA Documentation | # OPEA Emeritus Code Owners
The table below acknowledges the OPEA code owners who have left, and whose valuable contributions were crucial to the project's success. We are deeply grateful! | # OPEA Emeritus Code Owners
The table below acknowledges the OPEA code owners who have left, and whose valuable contributions were crucial to the project's success. We are deeply grateful! | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation | |
fdaebe3e-2f5f-4a40-8c1e-766ce90af4af | OPEA Documentation | file://datasets/opea-docs/community/codeowner_emeritus.md | unknown | 551c310d-06af-4bfd-ad53-cde9be400173 | 1 | opea-semantic-v1 | 77ff9d44e882a95d | The table below acknowledges the OPEA code owners who have left, and whose valuable contributions were crucial to the project's success. We are deeply grateful!
| Repo | Path | Emeritus Owner |
|-----------------------------|-------------------------------|-------------------------------------|
| docs | `*` | david.b.k... | ai_ref_knowledge | OPEA Documentation | The table below acknowledges the OPEA code owners who have left, and whose valuable contributions were crucial to the project's success. We are deeply grateful!
| Repo | Path | Emeritus Owner |
|-----------------------------|-------------------------------|-------------------------------------|
| docs | `*` | david.b.k... | The table below acknowledges the OPEA code owners who have left, and whose valuable contributions were crucial to the project's success. We are deeply grateful!
| Repo | Path | Emeritus Owner |
|-----------------------------|-------------------------------|-------------------------------------|
| docs | `*` | david.b.k... | opea, enterprise-ai, genai, docs, P1 | OPEA Documentation |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.