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

Publish Development Roadmap #258

Open
tangomanni opened this issue Nov 6, 2020 · 13 comments
Open

Publish Development Roadmap #258

tangomanni opened this issue Nov 6, 2020 · 13 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA transparency calls for a more transparency regarding development

Comments

@tangomanni
Copy link

tangomanni commented Nov 6, 2020

Hallo,
ich finde es sehr gut dass man hier auf Github Anforderungen zur CWA stellen bzw. Fragen zur CWA stellen kann und diese auch zeitnah beantwortet werden. Großes Kompliment !
Mir ist allerdings unklar wie die Weiterentwicklung der CWA prozesstechnisch abläuft ?

  • Wer entscheidet über die Umsetzung von Issues ? Gibt es ein Entscheidungs-Board ?
  • Wie sieht die Versionsplanung aus ? Wann kommt die nächste Version ?
    Diese Information finde ich nicht bzw. vermisse ich.

Internal Tracking ID: EXPOSUREAPP-3643

@tangomanni tangomanni added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 6, 2020
@achisto
Copy link

achisto commented Nov 6, 2020

English below
Ich möchte dem zustimmen: eine Roadmap der geplanten Entwicklungen fände ich sehr hilfreich. Ich kann mir auch vorstellen, dass hierdurch viele Requests nicht ständig neu gestellt würden, wenn bereits klar ist, dass eine Änderung geplant ist. Die Diskussion könnte sich dann auch mehr auf das WIE der Integration beschränken und würde sich nicht größtenteils darum drehen, ob ein Feature sinnvoll ist.

I strongly support this request: having a roadmap with features currently in development would be really helpful. In my opinion knowing a feature is already on the timeline could also prevent people from issuing the same requests over and over again and therefore focus the discussion on HOW to integrate a feature instead of IF it is possible to integrate.

@heinezen heinezen changed the title CWA Development Process Roadmap Nov 8, 2020
@heinezen heinezen changed the title Roadmap Publish Roadmap Nov 8, 2020
@heinezen heinezen changed the title Publish Roadmap Publish Development Roadmap Nov 8, 2020
@heinezen
Copy link
Member

heinezen commented Nov 8, 2020

Hey @achisto and @tangomanni ,

I have merged your requests regarding a roadmap/version planning into an internal Jira ticket (EXPOSUREAPP-3643). This will now be discussed by the devs and the RKI. I have also changed te issue title accordingly.

We have a general statement regarding "Wer entscheidet über die Umsetzung von Issues ? Gibt es ein Entscheidungs-Board ?" in the README:

Issues will be scanned regularly by members of the CWA Github organization and discussed with the product management and the RKI. If an issues is selected to be implemented in a future release of the Corona-Warn-App, it will be moved to the CWA Backlog Repository.

Regards,
CH


Corona-Warn-App Open Source Team

@heinezen heinezen added the mirrored-to-jira This item is also tracked internally in JIRA label Nov 8, 2020
@ndegendogo
Copy link

If an issues is selected to be implemented in a future release of the Corona-Warn-App, it will be moved to the CWA Backlog Repository.

@heinezen is the CWA backlog repo really still alife? I have the impression that it contains rather tickets from May, but seems not being maintained consistently?

@heinezen
Copy link
Member

heinezen commented Nov 8, 2020

@ndegendogo The cwa-backlog is only meant for confirmed future features and is supposed to be used for communication while a feature is implemented. It is still alive and used, though there are not many recent things to discuss.

The older issues you see are probably from a time before cwa-wishlist was created.


Corona-Warn-App Open Source Team

@ndegendogo
Copy link

@heinezen thanks for clarification. Still, I did not see it in use for the features we got in last releases, like 1.5. But I will be happy if this changes in future and we get more transparency on your roadmap planning.

@heinezen
Copy link
Member

heinezen commented Nov 8, 2020

@ndegendogo I was under the impression that details and UI mockups about 1.5 features were shared there before the release. I will try to address this next week, so that the repo gets used as intended for future releases.


Corona-Warn-App Open Source Team

@ndegendogo
Copy link

Thanks @heinezen

@MikeMcC399
Copy link
Contributor

I read a related post from @christianbrb in https://github.com/corona-warn-app/cwa-backlog/issues/2#issuecomment-727907859 who referred to Spiegel article "Spahn will Corona-Warn-App nachbessern" from today Nov 16, 2020.

As far as the wishlist here in the github repository is concerned and the related app roadmap it would be good if RKI could say here directly (and not just through articles we can read about from the press) which issues they are interested in developing or discussing for the CWA. Also it would be helpful to know which issues definitely will not be considered, so that discussions can be focused on the ones with the most promise of implementation.

@alanrick
Copy link

@ndegendogo I was under the impression that details and UI mockups about 1.5 features were shared there before the release. I will try to address this next week, so that the repo gets used as intended for future releases.

@heinezen Thanks for considering this. I notice the label Planned For Development hasn’t been assigned to any items in the wish-list so far. I’m sure you can understand that after 5 months of community feedback that’s a bit disappointing.

@dsarkar
Copy link
Member

dsarkar commented Jan 1, 2021

Happy New Year! Added this issue to Internal Tracking ID: EXPOSUREAPP-3643

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Mar 3, 2021

Are you able to share the high level feature highlights for the future versions already under development?

In the Android app repository there are three is one open relevant branches:

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Mar 26, 2021

The RKI site - Infektionsketten digital unterbrechen mit der Corona-Warn-App has been updated to include the following text:

"In einem der nächsten Releases soll die Corona-Warn-App um die Möglichkeit einer Event-Registrierung per QR-Code erweitert werden. Auch mit dieser Funktionalität bleibt der dezentrale Ansatz der App gewahrt. Es werden keine persönlichen Daten erfasst."

Stand: 26.03.2021

I have seen related draft documentation published to event_registration.md.

Edit: See release 2.0 https://www.coronawarn.app/en/blog/2021-04-21-corona-warn-app-version-2-0/

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Jun 30, 2021

RKI has started to use the Twitter channel https://twitter.com/coronawarnapp (@coronawarnapp) to pass on information about future functionality and release dates planned for the Corona-Warn-App.

https://twitter.com/coronawarnapp/status/1410175946792083463?s=20 says:

"5/x
Wann kommen die Familienzertifikate?

In der nächsten Version 2.5 (Mitte Juli) wird es möglich sein, auch die Impfzertifikate von Familienmitgliedern in der App abzulegen. Im Moment geht das schon in der #CovPass-App."

"6/x
Wann kann man das Genesenen-Zertifikat integrieren?

Die Integration von Genesenen-Zertifikaten wird mit dem nächsten Release (2.5, Mitte Juli) möglich sein. Die Herausgabe der Genesenen-Zertifikate wird analog dem Prozess der Impfzertifikate für bereits Geimpfte erfolgen."

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA transparency calls for a more transparency regarding development
Projects
None yet
Development

No branches or pull requests

9 participants