#774 Clarify default functionality requirements for apps implementing multiple roles
Opened 13 days ago by kparal. Modified 12 days ago

In this blocker proposal it was claimed that nautilus doesn't need to withstand a basic functionality test for archive management, because it's primarily a file manager and not an archive manager (even though it's the primary and only archive manager in Fedora Workstation default install).

It would be good to clarify the criterion and define requirements when an app serves multiple roles (and perhaps even when there's no app for a particular role). Perhaps the criterion could also be rewritten to be focused on roles (browsing the web) instead of apps (web browser), to make it even clearer.


oh, hmm, I actually completely forgot while considering that proposal that we kinda count nautilus as being an 'archive manager'.

honestly I'd still probably vote -1 on the basis that I'd say in release media it's much more important to be able to decompress archives than compress them, but it's a good point to consider.

in release media it's much more important to be able to decompress archives than compress them

Until you want to upload crash logs :-D

Login to comment on this ticket.

Metadata