Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🌐 New Crowdin translations #155

Merged
merged 41 commits into from
Sep 23, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
41 commits
Select commit Hold shift + click to select a range
a133d4a
New translations en.json (Portuguese)
aaronleopold Sep 8, 2023
88253be
:memo: Update README and CONTRIBUTING
aaronleopold Sep 8, 2023
22563b5
:bug: fix autoclosing drawer (#157)
aaronleopold Sep 10, 2023
5589803
:sparkles: basic PDF support (#158)
aaronleopold Sep 19, 2023
ce250ef
:bug: Fix entrypoint.sh adduser and addgroup commands (#160)
aaronleopold Sep 20, 2023
eefa6cb
New translations en.json (German)
aaronleopold Sep 21, 2023
aeca5f7
New translations en.json (German)
aaronleopold Sep 21, 2023
1fbba0f
New translations en.json (Dutch)
aaronleopold Sep 21, 2023
7048270
🎨 support regenerate thumbnails from UI and improve mobile friendline…
aaronleopold Sep 22, 2023
7ce0cc0
New translations en.json (Romanian)
aaronleopold Sep 22, 2023
3be3d46
New translations en.json (French)
aaronleopold Sep 22, 2023
9e7b982
New translations en.json (Spanish)
aaronleopold Sep 22, 2023
cc098ad
New translations en.json (Afrikaans)
aaronleopold Sep 22, 2023
0532d91
New translations en.json (Arabic)
aaronleopold Sep 22, 2023
d53a226
New translations en.json (Catalan)
aaronleopold Sep 22, 2023
7cc6616
New translations en.json (Czech)
aaronleopold Sep 22, 2023
f4fcd60
New translations en.json (Danish)
aaronleopold Sep 22, 2023
6c3cdb6
New translations en.json (German)
aaronleopold Sep 22, 2023
4450224
New translations en.json (Greek)
aaronleopold Sep 22, 2023
1517cc1
New translations en.json (Finnish)
aaronleopold Sep 22, 2023
88cf2fb
New translations en.json (Hebrew)
aaronleopold Sep 22, 2023
fcb9317
New translations en.json (Hungarian)
aaronleopold Sep 22, 2023
8dee718
New translations en.json (Italian)
aaronleopold Sep 22, 2023
006cb9b
New translations en.json (Japanese)
aaronleopold Sep 22, 2023
40abc56
New translations en.json (Korean)
aaronleopold Sep 22, 2023
b966fed
New translations en.json (Dutch)
aaronleopold Sep 22, 2023
b8bfd94
New translations en.json (Norwegian)
aaronleopold Sep 22, 2023
c5a8c2f
New translations en.json (Polish)
aaronleopold Sep 22, 2023
914cc22
New translations en.json (Russian)
aaronleopold Sep 22, 2023
e41adf1
New translations en.json (Serbian (Cyrillic))
aaronleopold Sep 22, 2023
4185d9a
New translations en.json (Swedish)
aaronleopold Sep 22, 2023
5fd6d5f
New translations en.json (Turkish)
aaronleopold Sep 22, 2023
1e859d4
New translations en.json (Ukrainian)
aaronleopold Sep 22, 2023
611a402
New translations en.json (Chinese Simplified)
aaronleopold Sep 22, 2023
cbb9ff1
New translations en.json (English)
aaronleopold Sep 22, 2023
43d68d1
New translations en.json (Vietnamese)
aaronleopold Sep 22, 2023
1a055a8
New translations en.json (Portuguese, Brazilian)
aaronleopold Sep 22, 2023
90755de
New translations en.json (Portuguese)
aaronleopold Sep 22, 2023
bfafdc6
New translations en.json (French)
aaronleopold Sep 23, 2023
6858696
Merge remote-tracking branch 'origin/l10n_develop' into al/develop-l1…
aaronleopold Sep 23, 2023
9b455e6
make all available languages selectable
aaronleopold Sep 23, 2023
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 20 additions & 22 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
# Contributing

You can contribute by opening new issues or PRs. Do not make random PRs without talking with me first - to ensure nobody's time and effort is wasted, please follow the guidelines below.
To ensure nobody's time and effort is wasted, please be sure to follow the guidelines below.

## Guidelines

1. Check to see if an issue already exists relevant to your feature/topic
2. Create an issue (if an issue does not already exist) and express interest in working it (see the [issues](#issues) section below)
3. Create a fork of the repository.
4. Create a new feature branch **off of the `develop` branch** - _not_ `main`.
5. Add appropiate documentation, tests, etc, if necessary.
6. Ensure you have your code formatters properly configured (both Prettier and Rustfmt).
7. Once you've completed your changes, create a PR from your feature branch into `develop` - _not_ `main`.
8. Be sure to update your feature branch with any new changes **before** making the PR.
9. Follow the PR naming format to help ensure the changelog generator properly picks up your additions:
3. Create a new feature branch **off of the `develop` branch** - _not_ `main`. All PRs should be made against `develop`.
4. Add appropiate documentation, tests, etc, if necessary.
5. Ensure you have your code formatters properly configured (both Prettier and Rustfmt).
6. Once you've completed your changes, create your PR!
7. Follow the PR naming format to help ensure the changelog generator properly picks up your additions:

> :information_source: Honestly, don't stress about this part right now. I don't even have a changelog generator!! This kind of structure will only matter once releases are more regular and providing changelogs are more important. For now, just make sure your PR name and body is descriptive and concise :heart:

```
<type>: <description>
Expand Down Expand Up @@ -45,28 +45,26 @@ You can contribute by opening new issues or PRs. Do not make random PRs without
docs: update CONTRIBUTING.md to include PR naming format
```

10. Stick around and make sure your PR passes all checks and gets merged!
8. Stick around and make sure your PR passes all checks and gets merged!

## Issues

I don't have any strict guidelines for issues, but do please try and be as descriptive as possible. There are a few templates to help you out, but in general:

- If you're interested in working on an issue, please leave a comment so that I know you're interested.
- If you're opening an issue to request a feature, please try and explain why you think it would be a good addition to the project. If applicable, include example use cases.
- If you're opening an issue to report a bug, try to fill in the template as best you can. If you can, please include a minimal reproduction of the bug (video, code, etc).
- If you're not sure if an issue is relevant appropriate, e.g. if you have more of a question to ask, feel free to pop in the [Discord server](https://discord.gg/63Ybb7J3as) and ask!
I use GitHub issues to track bugs, feature requests, and other tasks. No rigid structure is enforced, but please try and follow these guidelines:

**Please don't ghost an issue you've been assigned** - if you're no longer interested in working on it, that is totally okay! Just leave a comment on the issue so that I know you're no longer interested and I can reassign it to someone else. I will never be offended if you no longer want to work on an issue - I'm just trying to make sure that nobody's time and effort is wasted.
- Please try and be as descriptive as possible when opening an issue.
- There are a few templates available to help guide you, but if you're not sure which one to use just use the "Blank Issue" template.
- If you're opening an issue to request a feature, please try and explain why you think it would be a good addition to the project. If applicable, include example use cases.
- If you're opening an issue to report a bug, please try and include a minimal reproduction of the bug (video, code, logs, etc).
- If you're not sure if an issue is relevant or appropriate, e.g. if you have more of a question to ask, feel free to pop in the [Discord](https://discord.gg/63Ybb7J3as) and ask!
- **Please don't ghost an issue you've been assigned** - if you're no longer interested in working on it, that is totally okay! Just leave a comment on the issue so that I know you're no longer interested and I can reassign it to someone else. I will never be offended if you no longer want to work on an issue - I'm just trying to make sure that nobody's time and effort is wasted.

## A note on merging

I will not merge your PR until:
PRs will be merged once the following criteria are met:

- It aligns with the [guidelines](#guidelines) outlined above
- In most cases, any issues outside of a malformed PR name, I will not fix for you. If you're unsure how to fix it, ask for help. Stale PRs will be closed after 10 days.
- All checks pass
- At least one maintainer has reviewed your PR
- All CI checks pass
- At least one _maintainer_ has reviewed your PR

All PRs to `develop` will be squashed. All PRs to `main` will be merge commits. This is to ensure that the commit history is clean and easy to follow, and to ensure that the changelog generator works properly.

Thanks for considering to contribute! :heart:
Thanks for considering contributing to Stump! :heart:
Loading