Mikolaj Izdebski

We need to make sure that auth works in both Fedora and non-Fedora environments.

> Because at that point (you may toggle it back after a year) the resolution state is not known until an attempt to resolve the package is made (on next...

This is very closely related to #46 - the same materialized view could be re-used for storing average build times.

You can achieve this by setting "manual priority" to negative value (which is documented at https://fedoraproject.org/wiki/Koschei#Priorities). Eventually accumulated dynamic priority (which depends on several factors, including time and number of...

Currently you can set package priority only in web UI, one-by-one. Would CLI tool be useful? > Actually it is not just about BR ... but also every package which...

More generic feature would be allowing bulk-editing of any set of packages - not only manual priority, but also arch override and "skip resolution" flag. Via web or REST API...

Should be doable. Some thoughts: - It should be enough to keep logs for one or two builds per package - latest build, and latest successful build (which is possibly...

Automated log analysis may be wanted by some users. (CC @ignatenkobrain)

Maybe build logs could be stored in [ResultsDB](https://fedoraproject.org/wiki/ResultsDB)?