Skip to content

Commit 0d35f87

Browse files
committed
doc(docs): add main contributing page
1 parent 94f15db commit 0d35f87

File tree

1 file changed

+15
-60
lines changed

1 file changed

+15
-60
lines changed

‎docs/contributing/contributing.md‎

Lines changed: 15 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,14 @@ permalink: /contributing
1414
{: .warning}
1515
> Have you found a security issue? Then please jump to [Security Vulnerabilities](#security-vulnerabilities).
1616
17+
On this page, we provide information ``llmware`` contributions.
18+
There are **two ways** on how you can contribute.
19+
The first is by making **code contributions**, and the second by making contributions to the **documentation**.
20+
Please look at our [contribution suggestions](#how-can-you-contribute) if you need inspiration, or take a look at [open issues](#open-issues).
21+
1722
Contributions to `llmware` are welcome from everyone.
1823
Our goal is to make the process simple, transparent, and straightforward.
19-
20-
On this page, we provide information for people interested in contributing to ``llmware``.
21-
This includes information on contribution areas and the contribution process.
22-
24+
We are happy to receive suggestions on how the process can be improved.
2325

2426
## How can you contribute?
2527

@@ -46,62 +48,10 @@ Here is a non exhaustive list of contributions you can make.
4648
11. Answer questions in our [Discord channel](https://discord.gg/MhZn5Nc39h), especially in the [technical support forum](https://discord.com/channels/1179245642770559067/1218498778915672194)
4749
12. Post projects in which you use ``llmware`` in our Discord forum [made with llmware](https://discord.com/channels/1179245642770559067/1218567269471486012), ideially with a link to a public GitHub repository
4850

49-
We briefly describe some of the important modules of ``llmware`` next, so you can more easily navigate the code base.
50-
For newcomers, we embed links to our [fast start series from YouTube](https://www.youtube.com/playlist?list=PL1-dn33KwsmD7SB9iSO6vx4ZLRAWea1DB).
51-
52-
### Core modules
53-
54-
#### Library
55-
<iframe width="560" height="315" src="https://www.youtube.com/embed/2xDefZ4oBOM?si=IAHkxpQkFwnWyYTL" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
56-
In ``llmware``, a *library* is a collection of documents.
57-
A library is responsible for parsing, text chunking, and indexing.
58-
59-
#### Embeddings
60-
<iframe width="560" height="315" src="https://www.youtube.com/embed/xQEk6ohvfV0?si=GAPle5gVdVPkYKWv" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
61-
In ``llmware``, an *embedding* is a vector store and an embedding model.
62-
An embedding is responsible for applying an embedding model to a library, storing the embeddings in a vector store, and providing access to the embeddings with natural language queries.
63-
64-
#### Prompts
65-
<iframe width="560" height="315" src="https://www.youtube.com/embed/swiu4oBVfbA?si=rKbgO3USADCqICqr" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
66-
In ``llmware``, a *prompt* is an input to model.
67-
68-
#### Model Catalog
69-
In ``llmware``, a *model catalog* is a collection of models.
70-
71-
72-
## Code contributions
73-
74-
### New or Enhancement to existing Features
75-
You want to submit a code contribution that adds a new feature or enhances an existing one?
76-
Then the best way to start is by opening a discussion in our [GitHub discussions](https://github.com/llmware-ai/llmware/discussions).
77-
Please do this before you work on it, so you do not put effort into it just to realise after submission that
78-
it will not be merged.
79-
80-
### Bugs
81-
If you encounter a bug, you can
82-
83-
- File an issue about the bug.
84-
- Provide a self-contained minimal example that reproduces the bug, which is extremely important.
85-
- Provide possible solutions for the bug.
86-
- Submit a pull a request to fix the bug.
87-
88-
We encourage you to read [How to create a Minimal, Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example) from the Stackoverflow helpcenter, and the tag description of [self-container](https://stackoverflow.com/tags/self-contained/info), also from Stackoverflow.
89-
90-
## Documentation contributions
91-
There are two ways to contribute to the ``llmware`` documentation.
92-
The first is via docstrings in the code, and the second is what you are currently reading.
93-
In both areas, you can contribute in a lot of ways.
94-
Here is a non exhaustive list of these ways.
95-
96-
1. Add documentation (e.g., adding a docstring to a function)
97-
2. Update documentation (e.g., update a docstring that is not in sync with the code)
98-
3. Simplify documentation (e.g., formulate a docstring more clearly)
99-
4. Enhance documentation (e.g., add more examples to a docstring or fix typos)
100-
10151
## Open Issues
10252
If you're interested in existing issues, you can
10353

104-
- Look for issues with the `good first issue` label as a good place to get started.
54+
- Look for issues, if you are a new to the project, look for issues with the `good first issue` label.
10555
- Provide answers for questions in our [GitHub discussions](https://github.com/llmware-ai/llmware/discussions)
10656
- Provide help for bug or enhancement issues.
10757
- Ask questions, reproduce the issues, or provide solutions.
@@ -117,7 +67,7 @@ Please follow the process at [Reporting a Vulnerability](https://github.com/llmw
11767

11868
## GitHub workflow
11969

120-
Generally, we follow the [``fork-and-pull``](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) Git workflow.
70+
We follow the [``fork-and-pull``](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) Git workflow.
12171

12272
1. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the repository on GitHub.
12373
2. Clone your fork to your local machine with `git clone git@github.com:<yourname>/llmware.git`.
@@ -134,5 +84,10 @@ git fetch upstream
13484
git checkout upstream/main -b my-topic-branch
13585
```
13686

137-
## Do you have questions or just want to bounce around an idea?
138-
Questions and discussions are welcome in our [GitHub discussions](https://github.com/llmware-ai/llmware/discussions)!
87+
## Community
88+
Questions and discussions are welcome in any shape or form.
89+
Please fell free to join our community on our discord channel, on which we are active daily.
90+
You are also welcome if you just want to post an idea!
91+
92+
- [Discord Channel](https://discord.gg/MhZn5Nc39h)
93+
- [GitHub discussions](https://github.com/llmware-ai/llmware/discussions)

0 commit comments

Comments
 (0)