-
Notifications
You must be signed in to change notification settings - Fork 224
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
FAQ - update 'apk' entry #1070
FAQ - update 'apk' entry #1070
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One grammar correction and some suggestions for using the exact names for English and German used by RKI and Google.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's great to hear that you are planning to mention our project in your FAQ. I have one comment aiming to help avoid confusion among readers.
src/data/faq.json
Outdated
"Furthermore, there is an initiative in the developer community to make the Corona-Warn-App executable independently of Google Play Services via appropriate extensions. Details can be found in the issue <a href='https://github.com/corona-warn-app/cwa-app-android/issues/75' target='_blank' rel='noopener noreferrer'>corona-warn-app/cwa-app-android#75</a>." | ||
"On the one hand, the Robert Koch Institute, which is legally and content-wise responsible for its distribution, is responsible for the delivery of the app. At the moment, the focus is only on delivery via the respective App Stores.", | ||
"The distribution of the existing app on other channels is currently published as a request on <a href='https://github.com/corona-warn-app/cwa-wishlist/issues/57' target='_blank' rel='noopener noreferrer'>corona-warn-app/cwa-wishlist#57</a>. The discussion about alternative distribution platforms such as F-Droid can be found at <a href='https://github.com/corona-warn-app/cwa-app-android/issues/1483' target='_blank' rel='noopener noreferrer'>corona-warn-app/cwa-app-android#1483</a>.", | ||
"The developer community has developed an inofficial fork of the app under the name <i>Corona Contact Tracing Germany</i> to make the Corona-Warn-App executable independently of Google Play Services via appropriate extensions. However, the fork is not maintained by the Robert Koch-Institut and therefore receives <b>no official support</b>. Details about the development can be found in the issue <a href='https://github.com/corona-warn-app/cwa-app-android/issues/75' target='_blank' rel='noopener noreferrer'>corona-warn-app/cwa-app-android#75</a> as well as in the code repository of the fork: <a href='https://codeberg.org/corona-contact-tracing-germany/cwa-android' target='_blank' rel='noopener noreferrer'>Corona Contact Tracing Germany</a>." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In connection with your notes in #971 (comment):
Furthermore, there is an initiative in the developer community to make the Corona-Warn-App executable independently of Google Play Services via appropriate extensions. Details can be found in the issue corona-warn-app/cwa-app-android#75.
If this refers to microG, then the initiative has been successful
The initiative that was mentioned in the FAQ was a different project called CoraLibre, which has been discontinued and, according to themselves, is "not ready for real-world usage".
The issue corona-warn-app/cwa-app-android#75 does not help explain these circumstances, as it is mostly about CoraLibre development but does not indicate that CoraLibre is a different project than CCTG. For this reason and to avoid such confusion, I recommend against linking this issue here (as it doesn't actually provide "[d]etails about the development" of CCTG).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the info. I was not aware that CoraLibre was discontinued. That indeed makes linking the issue seem a bit clunky. corona-warn-app/cwa-app-android#75 contains some discussion about CCTG though (although it starts later in the comments) which is why it's linked here. We have to have continuity to the CWA repo. Any external link that is not related to or affiliated with the CWA, RKI, Breg or another state actor will require rigid approval (as @dsarkar already pointed out). Having existing discussions in our repos (and you being a contributor) help in that regard.
Since corona-warn-app/cwa-app-android#75 is technically obsolete, I would recommend you or someone else redoes the issue with updated information on solutions developed by the community. The issue doesn't even have to be about a specific project. Then, we can close the older issue, continue with fresh information and also have something to link to from other issues or the FAQ.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@heinezen I opened a new issue that intends to list all current and past CWA-compatible community projects: corona-warn-app/cwa-app-android#2837
@heinezen @fynngodau @MikeMcC399 Thanks for all the "cleaning up" in the FAQ. Regarding linking directly to the CCTG project, I have raised this internally. I am afraid, that this issue has to go through some more "instances", before, or if at all, we can do this on the FAQ. Stand by, please. |
3c63846
to
deb9949
Compare
If this PR is not being worked on then I suggest to change the status to draft. The text is out-of-date and nothing has been changed for the last 16 months. If there is no chance of it ever being merged, then it could be closed. |
This PR is heavily out of sync with the |
@Ein-Tim is completely right. This PR is unusable in its current state since it is so far behind the current master branch. To resolve the conflicts you would need to copy out the text changes and edit them in to a fresh copy of the master branch. The current branch heinezen-refaq-apk does not lend itself to rebasing on to the master branch any more. It would be better to open a new issue on the topic and close the old PR. Opening an issue would only make sense if there is a likelihood of there being a decision on the topic of officially recognising the CCTG fork as an unofficial alternative. That does seem questionable however, since the last comment from @dsarkar is more than a year and a half old, where he asked us to "stand-by"! |
Changelog: