Merge branch 'main' into develop

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: 🗯 Community Discussions
-    url: https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g
-    about: Our Slack Community loves to discuss Argilla and NLP topics
+    url: http://hf.co/join/discord
+    about: Our Discord Community loves to discuss Argilla and NLP topics

.github/pull_request_template.md

@@ -20,7 +20,7 @@ Closes #<issue_number>
 <!--  Please go over the list and make sure you've taken everything into account -->
 
 - I added relevant documentation
-- follows the style guidelines of this project
+- I followed the style guidelines of this project
 - I did a self-review of my code
 - I made corresponding changes to the documentation
 - I confirm My changes generate no new warnings

CONTRIBUTING.md

@@ -13,7 +13,7 @@ However you choose to contribute, please be mindful and respect our
 
 ## Need some help?
 
-We understand that getting started might be scary and difficult, therefore, we provide a guided contributor mentorship program. Feel free to schedule a meeting [here](https://calendly.com/david-berenstein-huggingface/30min) to get you started. Alternatively, you can start with [joining our Slack](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g) and reaching out in our [contributor channel](https://rubrixworkspace.slack.com/archives/C05BCGM277B).
+We understand that getting started might be a bit difficult, therefore, you can join our discord channel [#argilla-general](https://discord.gg/hugging-face-879548962464493619) by selecting *Argilla* in *Channels and Roles* after joining the Discord.
 
 ## Want to work on your own?
 

README.md

@@ -27,8 +27,8 @@
 <a href="https://www.linkedin.com/company/argilla-io">
 <img src="https://img.shields.io/badge/linkedin-blue?logo=linkedin"/>
 </a>
-<a href="https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g">
-<img src="https://img.shields.io/badge/slack-purple?logo=slack"/>
+<a href="http://hf.co/join/discord">
+<img src="https://img.shields.io/badge/Discord-7289DA?&logo=discord&logoColor=white"/>
 </a>
 </p>
 
@@ -61,7 +61,7 @@ We are an open-source community-driven project and we love to hear from you. Her
 
 - [Community Meetup](https://lu.ma/embed-checkout/evt-IQtRiSuXZCIW6FB): listen in or present during one of our bi-weekly events.
 
-- [Slack](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g): get direct support from the community.
+- [Discord](http://hf.co/join/discord): get direct support from the community in #argilla-general and #argilla-help.
 
 - [Roadmap](https://github.com/orgs/argilla-io/projects/10/views/1): plans change but we love to discuss those with our community so feel encouraged to participate.
 

argilla-frontend/README.md

@@ -26,8 +26,8 @@
 <a href="https://www.linkedin.com/company/argilla-io">
 <img src="https://img.shields.io/badge/linkedin-blue?logo=linkedin"/>
 </a>
-<a href="https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g">
-<img src="https://img.shields.io/badge/slack-purple?logo=slack"/>
+<a href="http://hf.co/join/discord">
+<img src="https://img.shields.io/badge/Discord-7289DA?&logo=discord&logoColor=white"/>
 </a>
 </p>
 

argilla-frontend/docs/snippets/start_page.md

@@ -4,7 +4,7 @@
 
 ## Argilla is a platform for building high-quality AI datasets
 
-If you need support join the [Argilla Slack community](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g)
+If you need support join the [Argilla Discord community](http://hf.co/join/discord)
 
 </div>
 

argilla-server/README.md

@@ -26,8 +26,8 @@
 <a href="https://www.linkedin.com/company/argilla-io">
 <img src="https://img.shields.io/badge/linkedin-blue?logo=linkedin"/>
 </a>
-<a href="https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g">
-<img src="https://img.shields.io/badge/slack-purple?logo=slack"/>
+<a href="http://hf.co/join/discord">
+<img src="https://img.shields.io/badge/Discord-7289DA?&logo=discord&logoColor=white"/>
 </a>
 </p>
 

argilla-server/docker/quickstart/README.md

@@ -36,8 +36,8 @@
 
 
 <p align="center">
-<a  href="https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g">
-<img src="https://img.shields.io/badge/JOIN US ON SLACK-4A154B?style=for-the-badge&logo=slack&logoColor=white" />
+<a  href="http://hf.co/join/discord">
+<img src="https://img.shields.io/badge/JOIN US ON DISCORD-7289DA?style=for-the-badge&logo=discord&logoColor=white" />
 </a>
 <a href="https://linkedin.com/company/argilla-io">
 <img src="https://img.shields.io/badge/LinkedIn-0077B5?style=for-the-badge&logo=linkedin&logoColor=white" />
@@ -46,7 +46,6 @@
 <img src="https://img.shields.io/badge/Twitter-1DA1F2?style=for-the-badge&logo=twitter&logoColor=white" />
 </a>
 </p>
-
 <br>
 
 <h3>

argilla-v1/README.md

@@ -27,8 +27,8 @@
 <a href="https://www.linkedin.com/company/argilla-io">
 <img src="https://img.shields.io/badge/linkedin-blue?logo=linkedin"/>
 </a>
-<a href="https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g">
-<img src="https://img.shields.io/badge/slack-purple?logo=slack"/>
+<a href="http://hf.co/join/discord">
+<img src="https://img.shields.io/badge/Discord-7289DA?&logo=discord&logoColor=white"/>
 </a>
 </p>
 
@@ -61,7 +61,7 @@ We are an open-source community-driven project and we love to hear from you. Her
 
 - [Community Meetup](https://lu.ma/embed-checkout/evt-IQtRiSuXZCIW6FB): listen in or present during one of our bi-weekly events.
 
-- [Slack](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g): get direct support from the community.
+- [Discord](http://hf.co/join/discord"): get direct support from the community in #argilla-general and #argilla-help.
 
 - [Roadmap](https://github.com/orgs/argilla-io/projects/10/views/1): plans change but we love to discuss those with our community so feel encouraged to participate.
 

argilla/README.md

@@ -27,8 +27,8 @@
 <a href="https://www.linkedin.com/company/argilla-io">
 <img src="https://img.shields.io/badge/linkedin-blue?logo=linkedin"/>
 </a>
-<a href="https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g">
-<img src="https://img.shields.io/badge/slack-purple?logo=slack"/>
+<a href="http://hf.co/join/discord">
+<img src="https://img.shields.io/badge/Discord-7289DA?&logo=discord&logoColor=white"/>
 </a>
 </p>
 
@@ -58,7 +58,7 @@ We are an open-source community-driven project and we love to hear from you. Her
 
 - [Community Meetup](https://lu.ma/embed-checkout/evt-IQtRiSuXZCIW6FB): listen in or present during one of our bi-weekly events.
 
-- [Slack](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g): get direct support from the community.
+- [Discord](http://hf.co/join/discord): get direct support from the community in #argilla-general and #argilla-help.
 
 - [Roadmap](https://github.com/orgs/argilla-io/projects/10/views/1): plans change but we love to discuss those with our community so feel encouraged to participate.
 

argilla/docs/community/contributor.md

@@ -9,32 +9,22 @@ Thank you for investing your time in contributing to the project! Any contributi
 ??? Question "New to contributing in general?"
     If you're a new contributor, read the [README](https://github.com/argilla-io/argilla/blob/develop/README.md) to get an overview of the project. In addition, here are some resources to help you get started with open-source contributions:
 
-    * **Slack**: You are welcome to join the [Argilla Slack community](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g), where you can keep in touch with other users, contributors and the Argilla team. In the following [section](#first-contact-in-slack), you can find more information on how to get started in Slack.
+    * **Discord**: You are welcome to join the [Argilla Discord community](http://hf.co/join/discord), where you can keep in touch with other users, contributors and the Argilla team. In the following [section](#first-contact-in-discord), you can find more information on how to get started in Discord.
     * **Git**: This is a very useful tool to keep track of the changes in your files. Using the command-line interface (CLI), you can make your contributions easily. For that, you need to have it [installed and updated](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) on your computer.
     * **GitHub**: It is a platform and cloud-based service that uses git and allows developers to collaborate on projects. To contribute to Argilla, you'll need to create an account. Check the [Contributor Workflow with Git and Github](#contributor-workflow-with-git-and-github) for more info.
     * **Developer Documentation**: To collaborate, you'll need to set up an efficient environment. Check the [developer documentation](../getting_started/installation.md) to know how to do it.
     * **Schedule a meeting with our developer advocate**: If you have more questions, do not hesitate to contact our developer advocate and [schedule a meeting](https://calendly.com/david-berenstein-huggingface/30min).
 
-## First Contact in Slack
+## First Contact in Discord
 
-Slack is a very useful tool for more casual conversations and to answer day-to-day questions. Click [here](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g) to join our Slack community effortlessly.
+Discord is a handy tool for more casual conversations and to answer day-to-day questions. As part of Hugging Face, we have set up some Argilla channels on the server. Click [here](http://hf.co/join/discord) to join the Hugging Face Discord community effortlessly.
 
-The following screens will be displayed, choose how you wish to join and enter the code sent to you via email.
+When part of the Hugging Face Discord, you can select "Channels & roles" and select "Argilla" along with any of the other groups that are interesting to you. "Argilla" will cover anything about argilla and distilabel. You can join the following channels:
 
-![argilla-slack](../assets/images/community/contributing/argilla-slack.png)
+* **#argilla-general**: 📣 Stay up-to-date and general discussions.
+* **#argilla-help**: 🙋‍♀️ Need assistance? We're always here to help. Select the appropriate label (argilla or distilabel) for your issue and post it.
 
-Once you have joined the community, you'll be added to some channels by default, but below we show you all the community channels you can join:
-
-* **00-announcements**: 📣 Stay up-to-date on official Argilla
-* **01-introductions**:  👋 Say hi! to the community Fun facts are appreciated.
-* **02-support-and-questions**: 🙋‍♀️ Need help with Argilla or NLP? We are always here.
-* **03-discoveries-and-news**: 📚 Looking for resources and news related to everything NLP?
-* **04-contributors**: 🏗️ A channel for contributions and contributors.
-* **05-beta-testing**: 🚧 For access to the latest features and help us with testing the newest features.
-* **06-general**: 🐒 This channel is for... well, everything else.
-* **07-distilabel**: ⚗️ For all of you questions about our Distilabel project.
-
-So now there is only one thing left to do, introduce yourself and talk to the community. You'll be always welcome! 🤗👋
+So now there is only one thing left to do: introduce yourself and talk to the community. You'll always be welcome! 🤗👋
 
 
 ## Contributor Workflow with Git and GitHub
@@ -113,6 +103,7 @@ git checkout [branch-name]
 ### Use CHANGELOG.md
 
 If you are working on a new feature, it is a good practice to make note of it for others to keep up with the changes. For that, we utilize the `CHANGELOG.md` file in the root directory. This file is used to list changes made in each version of the project and there are headers that we use to denote each type of change.
+
 - **Added:** for new features.
 - **Changed:** for changes in existing functionality.
 - **Deprecated:** for soon-to-be removed features.
@@ -171,19 +162,11 @@ First, click on `compare across forks` and select the right repositories and bra
 
 ![compare-across-forks](../assets/images/community/contributing/compare-across-forks.PNG)
 
-Then, fill in the pull request template. In the title, add the feat, bug or docs prefix depending on the type of modification. A general template will be shown, please click on `Preview` and choose the corresponding pull request template. In addition, on the right side, you can select a reviewer (for instance, if you discussed the issue with a member of the Argilla team) and assign the pull request to yourself.
-
-It is highly advisable to add labels to PR as well. You can do this again by the labels section right to the screen. For instance, if you are addressing a bug, add the `bug` label or if the PR is related to the documentation, add the `documentation` label. This way, PRs can be easily filtered.
-
-Additionally, you should add a prefix to the PR name as we did with the branch above. If you are working on a new feature, you can name your PR as `feat: TITLE`. If your PR consists of a solution for a bug, you can name your PR as `bug: TITLE` And, if your work is for improving the documentation, you can name your PR as `docs: TITLE`.
-
-Finally, click on `Create pull request`.
-
-![pr](../assets/images/community/contributing/pull-request.PNG)
+Then, fill in the pull request template. You should add a prefix to the PR name as we did with the branch above. If you are working on a new feature, you can name your PR as `feat: TITLE`. If your PR consists of a solution for a bug, you can name your PR as `bug: TITLE` And, if your work is for improving the documentation, you can name your PR as `docs: TITLE`.
 
-Below, we chose the feature template. Now, fill in it carefully and follow the guidelines. Remember to link the original issue. Finally, enable the checkbox to allow maintainer edits so the branch can be updated for a merge and click on `Create pull request`.
+In addition, on the right side, you can select a reviewer (for instance, if you discussed the issue with a member of the Argilla team) and assign the pull request to yourself. It is highly advisable to add labels to PR as well. You can do this again by the labels section right to the screen. For instance, if you are addressing a bug, add the `bug` label or if the PR is related to the documentation, add the `documentation` label. This way, PRs can be easily filtered.
 
-![pr-feature-template](../assets/images/community/contributing/pull-request-feature.PNG)
+Finally, fill in the template carefully and follow the guidelines. Remember to link the original issue and enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Then, click on `Create pull request`.
 
 
 ### Review your pull request
@@ -209,7 +192,7 @@ Additionally, we will include your changes in the next release based on our [dev
 
 Here are some helpful resources for your reference.
 
-* [Configuring Slack](https://slack.com/help/articles/218080037-Getting-started-for-new-Slack-users), a guide to learn how to configure Slack.
+* [Configuring Discord](https://support.discord.com/hc/en-us/categories/115000217151), a guide to learn how to get started with Discord.
 * [Pro Git](https://git-scm.com/book/en/v2), a book to learn Git.
 * [Git in VSCode](https://code.visualstudio.com/docs/sourcecontrol/overview), a guide to learn how to easily use Git in VSCode.
 * [GitHub Skills](https://skills.github.com/), an interactive course to learn GitHub.

argilla/docs/community/index.md

@@ -9,14 +9,14 @@ We are an open-source community-driven project not only focused on building a gr
 
 <div class="grid cards" markdown>
 
--   __Slack__
+-   __Discord__
 
     ---
 
-    In our Slack you can get direct support from the community.
+    In our Discord channels (#argilla-general and #argilla-help), you can get direct support from the community.
 
 
-    [:octicons-arrow-right-24: Slack ↗](https://join.slack.com/t/rubrixworkspace/shared_invite/zt-whigkyjn-a3IUJLD7gDbTZ0rKlvcJ5g)
+    [:octicons-arrow-right-24: Discord ↗](http://hf.co/join/discord)
 
 -   __Community Meetup__
 

argilla/docs/how_to_guides/dataset.md

@@ -432,7 +432,7 @@ retrieved_dataset = client.datasets(name="my_dataset", workspace=workspace)
 
 ## Check dataset existence
 
-You can check if a dataset exists by calling the `exists` method on the `Dataset` class. This method returns a boolean value.
+You can check if a retrieved dataset exists by calling the `exists` method on the `Dataset` class. This method returns a boolean value.
 
 ```python
 import argilla as rg

argilla/docs/how_to_guides/record.md

@@ -82,7 +82,7 @@ You can add records to a dataset in two different ways: either by using a dictio
 
     If your data structure does not correspond to your Argilla dataset names, you can use a `mapping` to indicate which keys in the source data correspond to the dataset fields.
 
-    We illustrate this python dictionaries that represent your data, but we would not advise you to to define dictionaries. Instead use the `Record` object for instatiating records.
+    We illustrate this python dictionaries that represent your data, but we would not advise you to define dictionaries. Instead use the `Record` object for instantiating records.
 
     ```python
     import argilla as rg
@@ -119,16 +119,14 @@ You can add records to a dataset in two different ways: either by using a dictio
     ```
 
     1. The data structure's keys must match the fields or questions in the Argilla dataset. In this case, there are fields named `question` and `answer`.
-    2. The data structure has keys `query` and `response` and the Argilla dataset has `question` and `answer`. You can use the `mapping` parameter to map the keys in the data structure to the fields in the Argilla dataset.
+    2. The data structure has keys `query` and `response` and the Argilla dataset has fields `question` and `answer`. You can use the `mapping` parameter to map the keys in the data structure to the fields in the Argilla dataset.
 
 
 === "From a Hugging Face dataset"
 
     You can also add records to a dataset using a Hugging Face dataset. This is useful when you want to use a dataset from the Hugging Face Hub and add it to your Argilla dataset.
 
-    You can add the dataset where the column names correspond to the names of fields, questions, metadata or vectors in the Argilla dataset.
-
-    If the dataset's schema does not correspond to your Argilla dataset names, you can use a `mapping` to indicate which columns in the dataset correspond to the Argilla dataset fields.
+    You can add the dataset where the column names correspond to the names of fields, metadata or vectors in the Argilla dataset.
 
     ```python
     from uuid import uuid4
@@ -148,13 +146,13 @@ You can add records to a dataset in two different ways: either by using a dictio
 
     2. In this example, the Hugging Face dataset matches the Argilla dataset schema. If that is not the case, you could use the `.map` of the `datasets` library to prepare the data before adding it to the Argilla dataset.
 
-    Here we use the `mapping` parameter to specify the relationship between the Hugging Face dataset and the Argilla dataset.
+    If the Hugging Face dataset's schema does not correspond to your Argilla dataset field names, you can use a `mapping` to specify the relationship. You should indicate as key the column name of the Hugging Face dataset and, as value, the field name of the Argilla dataset.
 
     ```python
-    dataset.records.log(records=hf_dataset, mapping={"txt": "text", "y": "label"}) # (1)
+    dataset.records.log(records=hf_dataset, mapping={"text": "review", "label": "sentiment"}) # (1)
     ```
 
-    1. In this case, the `txt` key in the Hugging Face dataset corresponds to the `text` field in the Argilla dataset, and the `y` key in the Hugging Face dataset corresponds to the `label` field in the Argilla dataset.
+    1. In this case, the `text` key in the Hugging Face dataset would correspond to the `review` field in the Argilla dataset, and the `label` key in the Hugging Face dataset would correspond to the `sentiment` field in the Argilla dataset.
 
 
 ### Metadata