Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Repository description and README do not mention use for app bugs of iOS and Android #707

Closed
MikeMcC399 opened this issue Sep 14, 2021 · 1 comment
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Sep 14, 2021

Where to find the issue

Describe the issue

The "About" text for this repository is set to:

"Project overview, general documentation, and white papers."

This does not mention the use of the repository for handling bugs which affect both iOS and Android operating systems, as described in ISSUE_TEMPLATE/02_bugs.md

* [ ] Bug affects both Android **and** iOS, for specific issues / questions that apply only to one operating system, please raise them in the respective repositories:
    * [Android repository](https://github.com/corona-warn-app/cwa-app-android)
    * [iOS repository](https://github.com/corona-warn-app/cwa-app-ios)

The README.md file contains no mention either of the use of the repository issue list to track not only documentation issues, but also app issues affecting both iOS and Android.

Suggested change

  • Update the description for this repository which appears under "About" so that it covers "app bugs common to both iOS and Android" (this has to be done by the Open Source Team due to permissions needed).
  • Update the README.md file of this repository with a new section describing how the repository is used to submit and track app bugs which are common to both iOS and Android operating system environments.
  • Update the README files of both iOS and Android repositories with an explicit cross-reference to the documentation repository as a place to report and track issues affecting both iOS and Android apps.
@MikeMcC399 MikeMcC399 added bug Something isn't working documentation Improvements or additions to documentation labels Sep 14, 2021
@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 18, 2022

This issue is open for ca. 6 months now and there was no comment from the Open-Source-Team at all. Please let us know how you plan to proceed with this issue.

@MikeMcC399 MikeMcC399 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants