Discussion:
How to get a list of C-only packages to review ?
Alain Vigne
2018-11-18 14:16:47 UTC
Permalink
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 ?
Best regards
--
Alain V.
Rex Dieter
2018-11-18 15:12:13 UTC
Permalink
Post by Alain Vigne
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 -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
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/li
Alain Vigne
2018-11-18 16:23:48 UTC
Permalink
Agree, once the .spec file is opened, it is obvious.

But the list such as :
https://fedoraproject.org/PackageReviewStatus/NEW.html
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:
https://bugzilla.redhat.com/show_bug.cgi?id=1636668
?

I think I am looking for a kind of "TODO" task list I can contribute on.

BR,Alain
Post by Alain Vigne
Post by Alain Vigne
As a new packager, I understand peer-reviewing packages is very
important,
Post by Alain Vigne
but it takes me (a lot of) time, and I do not have the necessary skills
to
Post by Alain Vigne
review any kind of packages (Go, Python, Rust, Java, Javascript, Ruby,
...
Post by Alain Vigne
you name it)
That is why I can offer to review packages of C libs, apps, or GNOME
apps,
Post by Alain Vigne
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
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
--
Alain V.
Fabio Valentini
2018-11-18 17:42:20 UTC
Permalink
Post by Alain Vigne
Agree, once the .spec file is opened, it is obvious.
https://fedoraproject.org/PackageReviewStatus/NEW.html
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 ?
https://bugzilla.redhat.com/show_bug.cgi?id=1636668
?
If someone agrees to review a package, they usually assign the bug to
themselves - which also removes it from the "NEW" package reviews list you
linked above. So, assigning it to yourself after submitting the request
only hides the bug from this list, and possible reviewers.
Post by Alain Vigne
I think I am looking for a kind of "TODO" task list I can contribute on.
The link for Package Reviews in "NEW" status is exactly what you are
looking for - It's just that not all reviewers and submitters are strictly
following the procedure, making the list less useful than it might be.

Fabio
Post by Alain Vigne
BR,Alain
Post by Alain Vigne
Post by Alain Vigne
As a new packager, I understand peer-reviewing packages is very
important,
Post by Alain Vigne
but it takes me (a lot of) time, and I do not have the necessary skills
to
Post by Alain Vigne
review any kind of packages (Go, Python, Rust, Java, Javascript, Ruby,
...
Post by Alain Vigne
you name it)
That is why I can offer to review packages of C libs, apps, or GNOME
apps,
Post by Alain Vigne
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
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
--
Alain V.
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Rex Dieter
2018-11-19 04:19:48 UTC
Permalink
Post by Alain Vigne
Agree, once the .spec file is opened, it is obvious.
https://fedoraproject.org/PackageReviewStatus/NEW.html
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 !)
Every (good) review should give a direct link to the .spec

-- Rex

_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
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

Loading...