https://bugzilla.redhat.com/show_bug.cgi?id=1503175
--- Comment #19 from Miro Hrončok <mhroncok(a)redhat.com> ---
(In reply to Aivar Annamaa from comment #17)
Thanks for the review! I'll fix the issues soon.
About doing my own review -- am I supposed to just show my ability to review
or should I be really helpful?
I need the first, however the second is more important. Preferably you do both.
I looked through the Python review requests which don't have a
reviewer
assigned yet. In all cases either somebody is already actively commenting
the request or the submitter is really inactive (no responses for long time).
Is it of any use if I provide a second review for a request which already
has a review or where someone has already promised to give a review?
That would satisfy my request but would only generate unnecessary noise and
would not be helpful to others, so probably don't do it.
I found an interesting package without review (python-asttokens,
https://bugzilla.redhat.com/show_bug.cgi?id=1510188), but looks like it's
already (close to be?) included in the Fedora repo. Does it make sense if I
write a review for it?
Actually the review there happened:
https://bugzilla.redhat.com/show_bug.cgi?id=1510188#c1 it was just
extraordinary sloppy (please don't do that kind of reviews once you are
sponsored.)
So we seem to have a problem that there is nothing to review :)
Here are the options I see:
* skim trough other review requests, not just python related
* ask on python-devel mailing list if someone is not working on a package
* wait until something shows up
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component