Merge branch 'main' into dependabot/npm_and_yarn/fullhuman/postcss-purgecss-5.0.0

Author: harm-devries

content/en/docs/about/ip.md

@@ -21,12 +21,12 @@ We believe the soul of BigCode to be clear and transparent communication strivin
 
 **Machine Learning Models**. Any machine learning model and related features (e.g. checkpoints) resulting from the Project will be licensed under an [Open & Responsible AI License](https://www.licenses.ai/blog/2022/8/18/naming-convention-of-responsible-ai-licenses). Please take a look at the [FAQ for our CodeML OpenRAIL-M v0.1](https://www.bigcode-project.org/docs/pages/model-license-faq). OpenRAILs are licenses designed to permit free and open access, re-use, and downstream distribution of the Model and its derivatives while establishing a set of behavioral-use restrictions for which the model cannot be used, due to ethics-informed concerns and/or the technical limitations of the model as informed by its model card. 
 
-**Datasets**. We value openness and transparency about the training data of LLMs and intend to release datasets whenever we have the rights to do so. We will also provide [data cards](https://arxiv.org/abs/2204.01075) for all datasets we release. We are aware of ongoing discussions around the data governance of LLMs and would like to research better processes for it. See, for example, how we experiment with giving developers the possibility [to have their data removed from The Stack](({{< relref "docs/about/the-stack.md" >}}).  
+**Datasets**. We value openness and transparency about the training data of LLMs and intend to release datasets whenever we have the rights to do so. We will also provide [data cards](https://arxiv.org/abs/2204.01075) for all datasets we release. We are aware of ongoing discussions around the data governance of LLMs and would like to research better processes for it. See, for example, how we experiment with giving developers the possibility [to have their data removed from The Stack]({{< relref "docs/about/the-stack.md" >}}).  
 
 ## Contributions under a different license
 We are flexible and understand that each individual contributor or contributing party might have its own interests besides the collective BigCode effort. In case you do not feel comfortable licensing some of your contributions to the project under the Apache 2.0, please get in touch with us. We will see how to work around and make everyone comfortable. Note that for contributions with a non-permissive license, our general policy is to put them in a separate Github repository living outside the BigCode organisation. 
 
 <!-- ## No CLA or DCO
 Unlike open-source projects such as [PyTorch](https://github.com/pytorch/pytorch/) and [TensorFlow](https://github.com/tensorflow/tensorflow), Big Code does not make use of a [Contributor License Agreement](https://www.apache.org/licenses/contributor-agreements.html) (CLA). We believe the main role of a CLA is to centralize the IP licensing management under a single legal entity. Since Big Code is not a legal entity, we do not use a CLA. This means that if, for example, Big Code wants to change the license of the project, we will need to reach consensus among all contributors. We also opted not to use a [Developer Certificate of Origin](https://developercertificate.org/).     -->
 
-If you have any further questions regarding IP, please reach out at contact@bigcode-project.org. 
+If you have any further questions regarding IP, please reach out at contact@bigcode-project.org.