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 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/62717742-8a30-f298-a7c5-f7888649987c%40riseup.net. For more options, visit https://groups.google.com/d/optout.
