Translated using Weblate (Spanish)

Currently translated at 94.2% (1138 of 1208 strings)

Co-authored-by: Kimberly <kimisaes@gmail.com>
Translate-URL: http://translate.akkoma.dev/projects/foundkey/foundkey/es/
Translation: Foundkey/foundkey

.woodpecker/build.yml

@@ -8,15 +8,15 @@ clone:
 pipeline:
   install:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn install
   build:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn build

.woodpecker/lint-backend.yml

@@ -8,15 +8,15 @@ clone:
 pipeline:
   install:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn install
   lint:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn workspace backend run lint

.woodpecker/lint-client.yml

@@ -8,15 +8,15 @@ clone:
 pipeline:
   install:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn install
   lint:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn workspace client run lint

.woodpecker/lint-foundkey-js.yml

@@ -8,15 +8,15 @@ clone:
 pipeline:
   install:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn install
   lint:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn workspace foundkey-js run lint

.woodpecker/lint-sw.yml

@@ -8,15 +8,15 @@ clone:
 pipeline:
   install:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn install
   lint:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn workspace sw run lint

.woodpecker/test.yml

@@ -5,11 +5,14 @@ clone:
       depth: 1 # CI does not need commit history
       recursive: true
 
+depends_on:
+  - build
+
 pipeline:
   build:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn install
@@ -18,15 +21,15 @@ pipeline:
       - yarn build
   mocha:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: node:18.6.0
     commands:
       - yarn mocha
   e2e:
     when:
-      event:
-        - pull_request
+      branch: main
+      event: push
     image: cypress/included:10.3.0
     commands:
       - npm run start:test &

.yarnrc.yml

@@ -8,4 +8,4 @@ plugins:
   - path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs
     spec: "@yarnpkg/plugin-workspace-tools"
 
-yarnPath: .yarn/releases/yarn-3.3.0.cjs
+yarnPath: .yarn/releases/yarn-3.4.1.cjs

CHANGELOG.md

@@ -86,8 +86,6 @@ This release contains 6 breaking changes, including changes to the configuration
 
 ### Removed:
 - **BREAKING** server: remove Twitter, Github and Discord integrations
-ff31b8b06 server: remove bios and cli
-a673647fb server: remove avatarColor and bannerColor properties
 - **BREAKING** server: remove `api/admin/delete-account`, 
   You should use the API endpoint `admin/accounts/delete` instead.
   It has the same parameter and the same behaviour.
@@ -108,6 +106,8 @@ a673647fb server: remove avatarColor and bannerColor properties
   - `/api/i/gallery/likes`
   - `/api/i/gallery/posts`
   - `/api/users/gallery/posts`
+- server: remove bios and cli
+- server: remove avatarColor and bannerColor properties
 - server: remove application level websocket ping
   This pinging mechanism was unused in `foundkey-js`, and we expect other usage to be low.
   You can use the pinging mechanism built into the websocket protocol if you wish.

CODE_OF_CONDUCT.md

@@ -1,46 +1,134 @@
+
 # Contributor Covenant Code of Conduct
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment include:
+Examples of behavior that contributes to a positive environment for our
+community include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
 
-Examples of unacceptable behavior by participants include:
+Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
-## Our Responsibilities
+## Enforcement Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at syuilotan@yahoo.co.jp. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement via email at
+johann<EFBFBD>qwertqwefsday.eu and/or toast<73>bunkerlabs.net .
+All complaints will be reviewed and investigated promptly and fairly.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+