[MIR] gnome-clocks

[Sebastien Bacher]

[Availability]
The package gnome-clocks is already in Ubuntu universe.
The package gnome-clocks build for the architectures it is designed to work on.
It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x
Link to package https://launchpad.net/ubuntu/+source/gnome-clocks

[Rationale]
- The package gnome-clocks is required in Ubuntu main as a desktop application and to allow integration of extra timezones to the shell calendar interface
- There is no other/better way to solve this that is already in main or
  should go universe->main instead of this.

- It would be great and useful to community/processes to have the
  package gnome-clocks in Ubuntu main, but there is no definitive deadline.

[Security]
- No CVEs/security issues in this software in the past

- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024).
- Package does not expose any external endpoints
- Packages does not contain extensions to security-sensitive software

[Quality assurance - function/usage]
- The package works well right after install

[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and have a limited number of minor issues reported
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/gnome-clocks/+bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gnome-clocks
  - Upstream's bug tracker, https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues
- The package does not deal with exotic hardware we cannot support

[Quality assurance - testing]
- The package runs limited tests at build time, it's a desktop application and integration in the desktop which isn't easy to test and upstream isn't providing those.
Build log https://launchpadlibrarian.net/678368727/buildlog_ubuntu-mantic-amd64.gnome-clocks_44.0-2_BUILDING.txt.gz
We are writing a manual testplan in addition that will be published on https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeClocks

- The package does not run an autopkgtest because it's a graphical GTK application and we currently don't really have a way to do test those currently in the autopkgest infrastructure.

[Quality assurance - packaging]
- debian/watch is present and works

- debian/control defines a correct Maintainer

- The package only has minor lintian warnings

# lintian --pedantic gnome-clocks_44.0-2_amd64.changes
W: gnome-clocks: no-manual-page [usr/bin/gnome-clocks]
W: gnome-clocks source: no-nmu-in-changelog [debian/changelog:1]
W: gnome-clocks source: source-nmu-has-incorrect-version-number 44.0-2 [debian/changelog:1]

- Lintian overrides are not present

- This package does not rely on obsolete or about to be demoted packages.
- This package has no python2 or GTK2 dependencies

- The package will be installed by default, but does not ask debconf questions

TODO-A: - Packaging and build is easy, link to debian/rules https://salsa.debian.org/gnome-team/gnome-clocks/-/blob/debian/master/debian/rules

[UI standards]
- Application is end-user facing, Translation is present, via standard gettext

- End-user applications that ships a standard conformant desktop file

[Dependencies]
- No further depends or recommends dependencies that are not yet in main

[Standards compliance]
- This package correctly follows FHS and Debian Policy

[Maintenance/Owner]
- Owning Team will be desktop-packages
- Team is already subscribed to the package

- This does not use static builds

- This does not use vendored code

- This package is not rust based

- The package has been built in the archive more recently than the last
  test rebuild

[Background information]
The Package description explains the package well
Upstream Name is gnome-clocks
Link to upstream project https://gitlab.gnome.org/GNOME/gnome-clocks