diff --git a/README.md b/README.md index eddfdedf46d3bbb24ae0ed67c84605010f7527f7..fbc407550b5ed44300b540147499d318e5fec15e 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,3 @@ # Licencia Feminista de Pares - F2F - - -## Getting started - -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://0xacab.org/labekka/f2f.git -git branch -M no-masters -git push -uf origin no-masters -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](https://0xacab.org/labekka/f2f/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +Disponible en [https://labekka.red/licencia-f2f](https://labekka.red/licencia-f2f). diff --git a/licencia-f2f-es.md b/licencia-f2f-es.md new file mode 100644 index 0000000000000000000000000000000000000000..f85d42bbf9c3afd2a4586f6adac67de5de179138 --- /dev/null +++ b/licencia-f2f-es.md @@ -0,0 +1,50 @@ +# Licencia de producción de pares feministas + +Con la Licencia de producción de pares feministas (F2F) son libres de compartir la obra (copiarla, distribuirla, ejecutarla, o comunicarla públicamente) y de hacer obras derivada bajo las siguientes condiciones: +Atribución + +## Atribución + +Debes reconocer los créditos de la obra de la manera especificada por la o las autoras o las licenciantes (pero no de una manera que sugiera que tiene su apoyo o que apoyan el uso que hace de su obra). +Compartir bajo la misma licencia + +## Compartir igual + +Si modifican o transforman esta obra, o producen una obra derivada, sólo pueden distribuir la obra generada bajo una licencia idéntica a ésta. +Feminista no capitalista + +## Feminista no capitalista + +La explotación comercial de esta obra sólo está permitida a cooperativas, organizaciones y colectivos sin fines de lucro, y organizaciones de trabajadoras autogestionadas, que se identifiquen y organicen bajo principios feministas. Todo excedente o plusvalía obtenidos por el ejercicio de los derechos concedidos por esta licencia sobre la obra debe ser reinvertidos en la lucha contra el patriarcado y el capitalismo. +Entendiendo que… +- Alguna de estas condiciones pueden no aplicarse si se obtiene el permiso de la o las titulares de los derechos de autor. +- Cuando la obra o alguno de sus elementos se halle en el dominio público según la ley vigente aplicable, esta situación no quedará afectada por la licencia. +- Los derechos siguientes no quedan afectados por la licencia de ninguna manera: + - Los derechos derivados de usos legítimos u otras limitaciones reconocidas por ley no se ven afectados por lo anterior; + - Los derechos morales de la o las autoras; + - Derechos que pueden ostentar otras personas sobre la propia obra o su uso, como por ejemplo derechos de imagen o de privacidad. + - Al reutilizar o distribuir la obra, tienen que dejar muy en claro los términos de la licencia de esta obra. La mejor forma de hacerlo es enlazar a esta página. + +## Preguntas frecuentes + +**¿Qué se entiende por ‘principios feministas’?** +Eso lo decide cada persona, colectiva u organización. Cómo mínimo tiene que tener una aspiración de lucha contra el cisheteropatriarcado. + +**¿Qué es el cisheteropatriarcado?** +Es el sistema de organización social que tiene al hombre cisheterosexual como centro y medida de todo; estableciendo relaciones de poder desiguales y sometimiento con el resto de seres humanos y la naturaleza. + +##Algunas obras publicadas con esta licencia +- Fanzine: Cómo montar una servidora feminista con una conexión casera. Ver ↗ +- Fanzine: Ciberfeminismo radiofónico. Miguitas para la producción de podcasts feministas libres. Ver ↗ + +## Imágenes para tu obra + +Copia de aquí las imágenes para añadir esta licencia a tu obra. + +- [Para web ↗](https://labekka.red/media/f2f-web.png) +- [Para imprimir ↗](https://labekka.red/media/f2f-imprimir.png) +- [Vectores (SVG) ↗](https://labekka.red/media/f2f-vectores.svg) + +## Créditos + +Esta licencia fue creada a partir de la [Licencia de Producción de Pares](https://endefensadelsl.org/ppl_deed_es.html). diff --git a/license-f2f-en.md b/license-f2f-en.md new file mode 100644 index 0000000000000000000000000000000000000000..4a120804b7e44df4bb7f0b6fe59502ee15f2cc7a --- /dev/null +++ b/license-f2f-en.md @@ -0,0 +1,60 @@ +# Feminist Peer Production Licence + +Under the Feminist Peer Production License (F2F) **you are free to share the work** (copy, distribute, perform, or publicly communicate it) and **to make derivative works** under the following conditions: + +## Attribution + +You must **credit the work in the manner specified by the author(s) or licensor(s)** (but not in a way that suggests that they endorse or support your use of their work). + +## Sharing under the same licence + +If you modify or transform this work, or produce a derivative work, **you may only distribute the generated work under a licence identical to this one.** + +## Non-capitalist feminism + +Commercial exploitation of this work is only permitted to cooperatives, non-profit organisations and collectives, and self-managed workers' organisations, **which identify and organise themselves under feminist principles**. Any surplus or surplus value obtained from the exercise of the rights granted by this licence on the work must be reinvested in the struggle against patriarchy and capitalism. + +## Understanding that... + +- Some of these conditions may not apply if permission is obtained from the copyright holder(s) +- Where the work or any element of the work is in the public domain under applicable law, this is not affected by the license. +- The following rights are not affected by the license in any way: + - Rights arising from legitimate uses or other limitations recognised by law are not affected by the above; + - The moral rights of the author(s); + - Rights that others may have in the work itself or its use, such as image or privacy rights. + - When reusing or distributing the work, you need to make very clear the terms of the license for this work. The best way to do this is to link to this page + - When reusing or distributing the work, you need to make very clear the terms of the license for this work. The best way to do this is to link to this page. + + +--- + +### Frequently Asked Questions + +**What is meant by 'feminist principles'?** + +That is up to each individual, collective or organisation to decide. At the very least it has to have an aspiration to fight against cisheteropatriarchy. + +**What is cisheteropatriarchy?** + +It is the system of social organisation that has the cisheterosexual men as the centre and measure of everything; establishing unequal power relations and oppression with the rest of human beings and nature. + +### Some works published under this licence + +- Fanzine: How to set up a feminist server with a home connection. [Link](https://labekka.red/servidoras-feministas) +- Fanzine: Ciberfeminismo radiofónico. Little crumbs for the production of free feminist podcasts. [Link](https://radioslibres.net/ciberfem) + +### Images for your work + +Copy from here the images to add this license to your work. + +- [For web](https://labekka.red/media/f2f-web.png) +- [For print](https://labekka.red/media/f2f-imprimir.png) +- [Vectors (SVG)](https://labekka.red/media/f2f-vectores.svg) + +### Credits + +This license was created from [the Peer Production Licence.](https://endefensadelsl.org/ppl_deed_es.html) + +la_bekka - hackfeminist space + +hacklabfeminista[at]riseup.net