3.10 dev

.github/CONTRIBUTING.md

@@ -0,0 +1,95 @@
+# Contributing to joomlagerman/joomla
+(german language files for Joomla! 3.9 and up)
+
+:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
+
+Our [Code of conduct](../CODE_OF_CONDUCT.md). Please read carefully.
+
+Getting started with [git and github](https://guides.github.com/activities/hello-world/). If you don't have git on your machine, [install it]( https://help.github.com/articles/set-up-git/).
+#### *If you're not comfortable with command line, [here are tutorials using GUI tools.]( #tutorials-using-other-tools )*
+
+## Working with this repository
+
+### Fork this repository
+
+Fork this repository by clicking on the fork button on the top of this page.
+This will create a copy of this repository in your account.
+
+### Clone the repository
+
+Now clone the forked repository to your machine. Go to your GitHub account, open the forked repository, click on the clone button and then click the *copy to clipboard* icon.
+
+Open a terminal and run the following git command:
+
+```
+git clone "url you just copied"
+```
+where "url you just copied" (without the quote marks) is the url to this repository (your fork of this project). See the previous steps to obtain the url.
+
+For example:
+```
+git clone https://github.com/this-is-you/joomla.git
+```
+where `this-is-you` is your GitHub username. Here you're copying the contents of the joomla repository on GitHub to your computer.
+
+### Create or take an issue
+
+Go to [Issues](https://github.com/joomlagerman/joomla/issues) and create a new issue or take one open issue to write an PR.  
+Normally no PR without a previous issue. We have the *issue-first principle*.
+
+### Create a branch
+
+Change to the repository directory on your computer (if you are not already there):
+
+```
+cd joomla
+```
+Now create a branch using the `git checkout` command:
+```
+git checkout -b <add-your-new-branch-name>
+```
+
+For example:
+```
+git checkout -b <issue-number>
+```
+(The name of the branch does not need to have a issue-number as branch name, but it's a easy thing to reference th issue here.)
+
+### Make necessary changes and commit those changes
+
+Now open all files in a text editor or in a IDE e.g. PhpStorm and change it. Now, save the file.
+
+If you go to the project directory and execute the command `git status`, you'll see there are changes.
+
+
+Add those changes to the branch you just created using the `git add` command:
+
+```
+git add .
+```
+
+Now commit those changes using the `git commit` command:
+```
+git commit -m "e.g. fix #<issue-number>"
+```
+replacing `<issue-number>` with the issue-number.
+
+### Push changes to GitHub
+
+Push your changes using the command `git push`:
+```
+git push origin <add-your-branch-name>
+```
+replacing `<add-your-branch-name>` with the name of the branch you created earlier.
+
+### Submit your changes for review
+
+If you go to your repository on GitHub, you'll see a  `Compare & pull request` button. Click on that button.
+
+Now submit the pull request.
+
+We will always try to edit or merge issues and PRs as soon as possible. You will get a notification email once the changes have been merged.
+
+### Where to go from here?
+
+Congrats!  You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor!

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: tecpromotion

.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md

@@ -0,0 +1,25 @@
+---
+name: basic issue template
+about: Use this template for issues.
+assignees: tecpromotion, zero-24, heelc29
+---
+
+### Was soll verbessert / korrigiert werden
+
+
+
+### Wo wird der Sprachstring angezeigt (Frontend/Backend)
+
+
+
+### Was wäre eine bessere Übersetzung / Bezeichnung
+
+
+
+### Joomla Version & Version der deutschen Sprachdatei
+
+
+
+### Zusätzlichen Informationen
+
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -4,22 +4,6 @@ Pull Request für Issue # .
 
 
 
-### Wie kann der Fehler nachgestellt werden
-
-
-
-### Das erwartete Ergebnis
-
-
-
-### Das aktuelle Ergebnis
-
-
-
-### System Information
-
-
-
-### Zusätzlichen Informationen
+### Wo wird der Sprachstring angezeigt / Wie kann getestet werden
 
 

.gitignore

@@ -0,0 +1,19 @@
+# IDE & System Related Files #
+.buildpath
+.project
+.settings
+.DS_Store
+.idea
+.vscode
+
+# OSX #
+._*
+.Spotlight-V100
+.Trashes
+
+# Windows #
+Thumbs.db
+Desktop.ini
+
+# Build files
+build/tmp/

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+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
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/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
+
+## Our 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.
+
+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.
+
+## 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.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at team@jgerman.de. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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.
+
+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.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq