add screenshots of old FMN

Signed-off-by: Ryan Lerch <rlerch@redhat.com>
This commit is contained in:
Ryan Lercho 2022-05-09 17:22:41 +10:00
parent 9b8520367c
commit 2b596656cc
6 changed files with 50 additions and 4 deletions

View file

@ -356,6 +356,52 @@ Because the configuration of the default setup has changed over the
years, users that logged in earlier have older default filter setups, years, users that logged in earlier have older default filter setups,
making it harder to figure out who is using defaults. making it harder to figure out who is using defaults.
Current UI
^^^^^^^^^^
Login page
''''''''''
::
apps.fedoraproject.org/notifications/
.. image:: oldscreenshots/login.png
About page
''''''''''
::
apps.fedoraproject.org/notifications/about
.. image:: oldscreenshots/about.png
Profile page
''''''''''''
::
apps.fedoraproject.org/notifications/<fedora_username>.id.fedoraproject.org/
.. image:: oldscreenshots/profile.png
Filter list per context
'''''''''''''''''''''''
::
https://apps.fedoraproject.org/notifications/<fedora_username>.id.fedoraproject.org/irc/
https://apps.fedoraproject.org/notifications/<fedora_username>.id.fedoraproject.org/email/
.. image:: oldscreenshots/filterlist.png
Create / Edit Filter page
'''''''''''''''''''''''''
::
https://apps.fedoraproject.org/notifications/<fedora_username>.id.fedoraproject.org/irc/<filter_id>/
https://apps.fedoraproject.org/notifications/<fedora_username>.id.fedoraproject.org/email/<filter_id>/
.. image:: oldscreenshots/createfilter.png
Skillsets Skillsets
--------- ---------
@ -378,14 +424,14 @@ Possible Timeline
----------------- -----------------
In 1 month In 1 month
^^^^^^^^^^ ~~~~~~~~~~
* Email notifying community about work started on new FMN service has gone out * Email notifying community about work started on new FMN service has gone out
* The development team has been onboarded * The development team has been onboarded
* The backlog has epic level tickets created * The backlog has epic level tickets created
* Testing criteria is loosely defined for performance, ie what is the min/max acceptable time for receiving a notification * Testing criteria is loosely defined for performance, ie what is the min/max acceptable time for receiving a notification
In 3 months In 3 months
^^^^^^^^^^^ ~~~~~~~~~~~
* An update is sent to the lists on work underway * An update is sent to the lists on work underway
* Infra leads have been invited to a review of the work to date * Infra leads have been invited to a review of the work to date
@ -393,13 +439,13 @@ In 3 months
* There is testing criteria/benchmarking agreed to * There is testing criteria/benchmarking agreed to
In 6 months In 6 months
^^^^^^^^^^^ ~~~~~~~~~~~
* The service is deployed in staging *or* its in production but it is not enabled for everyone yet * The service is deployed in staging *or* its in production but it is not enabled for everyone yet
* Testers are invited to onboard into the new service and help test performance * Testers are invited to onboard into the new service and help test performance
* An outage period for cutover to the new service has been identified and planned if needed * An outage period for cutover to the new service has been identified and planned if needed
In 9 months In 9 months
^^^^^^^^^^^ ~~~~~~~~~~~
* Hotfixes are applied * Hotfixes are applied

Binary file not shown.

After

Width:  |  Height:  |  Size: 308 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 81 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 114 KiB