Agree, once the .spec file is opened, it is obvious.
But the list such as :
doesn't give you easy access to the info: you have to open the BZ, then look for the file (if you are lucky). Worst case is when .spec file needs to be extracted (takes even more time !)
Also, how in BZ, do you state there is no need for reviewer, because review already started ?
For example:
?
I think I am looking for a kind of "TODO" task list I can contribute on.
BR,Alain
On Sun, Nov 18, 2018 at 5:03 PM Rex Dieter <rdieter@xxxxxxxxx> wrote:
Alain Vigne wrote:
> As a new packager, I understand peer-reviewing packages is very important,
> but it takes me (a lot of) time, and I do not have the necessary skills to
> review any kind of packages (Go, Python, Rust, Java, _javascript_, Ruby, ...
> you name it)
>
> That is why I can offer to review packages of C libs, apps, or GNOME apps,
> Vala programs, or ..?, if I can be aware of such review to do.
>
> How do I get such a list ?
Package reviews are not tracked by language, in general, so as far as I
know, there is no such list currently.
That said, it's generally not a large task to determine if something is a C
lib, gnome app, or something that depends on vala, by examining the
package's .spec file for build depdnencies.
-- Rex
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
--
Alain V.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
