-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
210 additions
and
95 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,56 @@ | ||
## Quick Start | ||
## 🚀 Getting Started | ||
To get started, check the [Issues Section] for tasks labeled "Good First Issue" or "Help Needed". These issues are perfect for new contributors or those looking to make a valuable impact quickly. | ||
|
||
You can quickly get started with contributing by searching for issues with the labels **"Good First Issue"** or **"Help Needed"** in the [Issues Section]. If you think you can contribute, comment on the issue and we will assign it to you. | ||
If you find an issue you want to tackle: | ||
|
||
To set up your development environment, please follow the steps mentioned below : | ||
Comment on the issue to let us know you’d like to work on it. | ||
Wait for confirmation—an admin will assign the issue to you. | ||
💻 Setting Up Your Development Environment | ||
To start working on the project, follow these steps: | ||
|
||
1. Fork the repository from dev, We don't allow direct contribution to main | ||
1. Fork the Repository: Begin by forking the repository from the dev branch. We do not allow direct contributions to the main branch.</b> | ||
2. Clone Your Fork: After forking, clone the repository to your local machine.</b> | ||
3. Create a New Branch: For each contribution, create a new branch following the naming convention: feature/your-feature-name or bugfix/your-bug-name.</b> | ||
|
||
## 🛠️ Contributing Guidelines | ||
🔍 Reporting Bugs | ||
If you find a bug, here’s how to report it effectively: | ||
|
||
## Contributing Guidelines | ||
|
||
### 🔍 Reporting Bugs | ||
Title: Use a clear and descriptive title, with appropriate labels. | ||
Description: Provide a detailed description of the issue, including: | ||
Steps to reproduce the problem. | ||
Expected and actual behavior.</b> | ||
|
||
Any relevant logs, screenshots, or additional context. | ||
Submit the Bug Report: Open a new issue in the [Issues Section] and include all the details. This helps us understand and resolve the problem faster. | ||
|
||
1. Title describing the issue clearly and concisely with relevant labels | ||
2. Provide a detailed description of the problem and the necessary steps to reproduce the issue. | ||
3. Include any relevant logs, screenshots, or other helpful information supporting the issue. | ||
## 🐍 Contributing to Python Code | ||
If you're contributing to the Python codebase, follow these steps: | ||
|
||
1. Create an Independent File: Write your code in a new file within the python folder. </b> | ||
2. Build with Maturin: After writing your code, use maturin build to build the package. </b> | ||
3. Import and Call the Function: | ||
4. Use the following import syntax: | ||
from embed_anything.<Library_name> import * </b> | ||
5. Then, call the function using: | ||
from embed_anything import <function_name> </b> | ||
Feel free to open an issue if you encounter any problems during the process. | ||
|
||
If you are Contributing in python; | ||
1. Please write an independent file, in the python folder given. | ||
2. Then you can maturin build | ||
3. Then call it with from embed_anything.Library_name import * | ||
4. then call the function, from embed_anything import the function_name | ||
🧩 Contributing to Adapters | ||
To contribute to adapters, follow these guidelines: | ||
|
||
Please open any issues if you have. | ||
1. Implement Adapter Class: Create an Adapter class that supports the create, add, and delete operations for your specific use case. </b> | ||
2. Check Existing Adapters: Use the existing Pinecone and Weaviate adapters as references to maintain consistency in structure and functionality. </b> | ||
3. Testing: Ensure your adapter is tested thoroughly before submitting a pull request. | ||
|
||
## To contribute in Adapters, | ||
|
||
All you need is to add Adapter class for your create, add, delete indexes. Kindly check the already existing pinecone and weaviate file. | ||
### 🔄 Submitting a Pull Request </b> | ||
Once your contribution is ready: </b> | ||
|
||
Push Your Branch: Push your branch to your forked repository.</b> | ||
|
||
Submit a Pull Request (PR): Open a PR from your branch to the dev branch of the main repository. Ensure your PR includes:</b> | ||
|
||
1. A clear description of the changes.</b> | ||
2. Any relevant issue numbers (e.g., "Closes #123").</b> | ||
3. Wait for Review: A maintainer will review your PR. Please be responsive to any feedback or requested changes. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
Use this section to tell people about which versions of your project are | ||
currently being supported with security updates. | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 0.2.x | :white_check_mark: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
## Blog | ||
|
||
# `Embed-anything== 0.3.0 🎉` | ||
|
||
1. `Code Refactored: All the major functions are refactored, making calling models more intuitive and optimized. Check out our docs and usage.` | ||
2. `Better folder management for Python and Rust. In the past, we have seen confusion regarding how to contribute to Python. Here is a guide on how to do it.` | ||
3. `Async and fix image streaming` | ||
4. `Vector Streaming by chunks allows you to stream embeddings as a set of chunks.` | ||
5. `Adapters Examples for Weaviate, Pinecone, and Elastic and adding more…` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.