I would like to have a small feedback to my style on handling this ticket.

https://github.com/QubesOS/qubes-issues/issues/2198

It was:

- a long ticket with a lot to read
- me being wrong and educated beforehand for an invalid suggestion, yet
the ticket was still containing valid TODO items
- ticket perhaps useful being split...

In my perception such a ticket is hard to work on and exhaustively solve
without overlooking something. Every time it is being worked on, one
would have to re-read all of it to make sure not to forget any important
points.

Therefore I created (hopefully) short, concise, clear, actionable follow
up tickets.

There is probably no perfect way to deal with this and it may be a
matter of preference, however I wanted to try a reality check if my
assumptions are more right than wrong.

Cheers,
Patrick

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I agree with your handling of this ticket, and in general, I'm strongly in
favor of having concise, clear, and actionable tickets.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXm5g5AAoJENtN07w5UDAwlcsP/iIywePzL3Gx60mV3sd8mhYd
rADAbt7I4gsE8OpzWTLudCh/GhsMoN/fDcHMH4HNY4ujMHq6BtJ1VIDIKefBRnvP
1IAr0x7BPTvNaYaA5HNmnDgZTGCLFsxJOS5IbrHqO16kv91ZTYa0+dCir4Uo0EfN
IQzGCyALNCDoeAX3nGOUjfiN/YxV2dWZYet4IxNSUwMT47+XrovbWhlMKiXldGeE
Njp24JCMGhGtLp+ZtcOjRtrxpaecXOuqBguAqcWSMWEcD/sVgXXWmlFKnZ126Axj
DNKyYt81ngcSyzbHZCYnxelMD6ibQ8IkAw/CVlmwku9ZGPxVDb/hvZkRej1CMohH
Ia0Z62ERExSUxuusTd3RUJmZ9e4QkkmCLMSHO5uYpOzZ8LWstQO6uODULxiNRomr
fmpZg5eh21c7ounHAzK5OWLE4rLJrj7nOb8cA9N/tOKjgKBuL7vTEC9oIY2l9dUy
l5N0/M1jIvPBihgcGZA0ooheqUW6vh1wNqV3ism2PFSgNGwZX8KmNsOXgPQZpgy9
MEs85vlVQBgTbRYRb9D5vJdbCicaZAnlfHyK6VeewEVhnCS1fYngHf4zzwp4+Bxy
NsAAaZPPF5jcgrQN1LnepDO9G3TsayqDZwhdbI9vS1Gqu357LjLYAfcgOvusR6B8
sgn+U8xNrhVVHvLvEsic
=/K53
-----END PGP SIGNATURE-----