Publish Release 1.26.0

Automerge Pull-Request for Release 1.26.0

.editorconfig

@@ -1,7 +1,16 @@
-[*.{kt, kts, java, xml, gradle, md}]
+[*.{kt,kts,java,xml,gradle,md}]
+
+# General rules
 disabled_rules = import-ordering, filename
 wildcard_import_limit = 999
+
+# Kotlin rules
 ij_kotlin_name_count_to_use_star_import = 999
 ij_kotlin_name_count_to_use_star_import_for_members = 999
 ij_java_class_count_to_use_import_on_demand = 999
-max_line_length = 120
+
+# Line rules
+max_line_length = 160
+end_of_line = lf
+insert_final_newline = true
+ij_any_method_annotation_wrap = split_into_lines

.gitattributes

@@ -0,0 +1,2 @@
+# app/features/src/debug/**/*.png filter=lfs diff=lfs merge=lfs -text
+**/snapshots/**/*.png filter=lfs diff=lfs merge=lfs -text

.gitignore

@@ -10,7 +10,14 @@
 .cxx
 repo
 /artifacts
-
+ci/.idea
+ci/env
+app/android/r8
+.kotlin/
+signing.properties
+erp-release-keystore-huawei.jks
+erp-release-keystore-play.jks
+requirements-report.html
 Jenkinsfile
 Nightly.Jenkinsfile
 Archive.Jenkinsfile
@@ -21,14 +28,27 @@ DependencyReport.Jenkinsfile
 EspressoTest.Jenkinsfile
 Release.Jenkinsfile
 Multibranch.Jenkinsfile
-ci
 ci-overrides.properties
 nexus-init.gradle.kts
-documentation-internal
-android/src/androidTest
 technical_requirements_report.html
-keystore
 CODEOWNERS
 local.cliactions.yaml
+**/virtual_smartcards.json
+2021_s.csv
+2024_s.csv
+mapping.txt
+.aiexclude
+sonar-project.properties
+.snyk
+keystore
 jenkinsfiles
+desktop
+smartcard-wrapper
+common/src/desktopMain
+app/test-actions
+documentation-internal
+app/android/src/androidTest
+ci
+requirements
+gutachter
 

CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+## 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.
+
+### 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
+* Calls for violence, vilification and advertising
+* 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 [email protected]. 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,62 @@
+# Welcome to the gematik contributing guide
+
+Thank you for investing your time in contributing to our projects!
+
+Read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectable. 
+
+In this guide you will get an overview how you can contribute to our projects by opening an issue, creating, reviewing and merging a pull request.
+
+Use the table of contents icon on the top left corner of this document to get to a specific section of this guide quickly.
+
+## Reporting a security vulnerability
+
+Please do not report vulnerabilities and security incidents as GitHub issues. Please contact us by sending an E-Mail to TODO or report them using the contact form at https://fachportal.gematik.de/kontaktformular.
+
+## New contributor guide
+
+To get an overview of the project, read the [README](./README.md).
+
+## Getting started
+
+### Issues
+
+#### Create a new issue
+
+If you spot a problem or have a feature request, search if an issue already exists.
+If a related issue doesn't exist, you can open a new issue.
+
+#### Solve an issue
+
+Scan through our existing issues to find one that interests you. If you find an issue to work on, you are welcome to open a PR with a fix.
+
+### Coding Style
+
+gematik projects follow the kotlin style guide conventions, see [kotlin style guide android](https://developer.android.com/kotlin/style-guide) or [kotlin lang style guide](https://kotlinlang.org/docs/coding-conventions.html). Please follow them when working on your contributions.
+
+### Code Coverage, Sonars, OWASP, Code format, etc.
+
+- CodeFormat & Style: Please check your code with Ktlint and Detekt. commands: "./gradlew ktlintformat" & "./gradlew detekt"
+- Code Coverage: If you add UseCases or ViewModels please add corresponding UnitTests as well. 
+- Code Coverage: If you add or change UI make sure these changes are covered by screenshotstests "./gradlew verifyPaparazziDebug".
+
+
+### Commit your update
+
+Commit the changes once you are happy with them.
+
+### Pull Request Process
+
+- When you're finished with the changes, create a pull request, also known as a PR.
+- Fill the pull request template so that we can review your PR. This template helps reviewers to understand your changes as well as the purpose of your pull request.
+- Don't forget to [link the PR to the issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one.
+- Once you submit your PR, a project team member will review your proposal. We may ask questions or request additional information.
+- We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)
+  or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
+- As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).
+- If your pull request is approved by our developers, we may merge it into the project.
+
+### Your PR is merged!
+
+Congratulations: The gematik team thanks you.
+
+Once your PR is merged, your contributions will be publicly visible on the [gematik github page](https://github.com/gematik/).

LICENSE.md

@@ -1,14 +1,14 @@
+# License
 Copyright (c) 2024 gematik GmbH
-
 Licensed under the EUPL, Version 1.2 or – as soon they will be approved by
 the European Commission - subsequent versions of the EUPL (the Licence);
 You may not use this work except in compliance with the Licence.
 You may obtain a copy of the Licence at:
 
-    https://joinup.ec.europa.eu/software/page/eupl
+https://joinup.ec.europa.eu/software/page/eupl
 
 Unless required by applicable law or agreed to in writing, software
 distributed under the Licence is distributed on an "AS IS" basis,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the Licence for the specific language governing permissions and
-limitations under the Licence.
+limitations under the Licence.