Alain Vigne wrote:
> 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
On Sun, Nov 18, 2018, 18:15 Alain Vigne 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
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
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
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,
