[Bug 594064] Review Request: id3mtag - Command line mass ID3 tagging utility for audio files

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=594064

--- Comment #13 from Michael Schwendt <mschwendt at gmail.com> 2010-11-23 04:43:38 EST ---
So, instead of posting a short comment to acknowledge things a reviewer seems
to have found, you either stay away for a long time or you prefer to argue.

Some things to consider:

* You don't need to publish a new src.rpm/spec for every single issue reported
by a reviewer. You are free to collect the found issues, depending on whether
the src.rpm builds at all, of course.

* However, you are expected to communicate with the reviewers and either
confirm the found problems or explain why you do something differently (and
possibly in violation of the guidelines).

Many reviewers expect you to offer something you consider "final" before they
would allocate the time to work with you on your package or your sponsorship.

* In the same way, reviewers are not expected to be perfect at finding _all_
issues with a single look at the package. The more issues there are, the more
time it takes to spot [or understand] non-obvious things which don't break the
build but which are against the guidelines nevertheless. It's normal that
reviewers find some issues, which are not covered by the packaging guidelines,
but which are bad or fragile. The guidelines aren't complete and never will be.

[...]

Further comments to your replies:

> I just opened a new one because of this comment.

As I understand it, Mamoru suggested closing this old ticket because it's the
cleanest way for _somebody_ to take over a stalled package review ticket (other
than reassigning it and keeping old cruft). The old one has been without a sign
of life from you for over four months. And once closed, somebody else with
interest in packaging the same software would simply open a new review ticket
anyway and not search in the pile of DEADREVIEW tickets.

> If you look at those 2 bug reports with the whole timeline of comments
> and edits, I think there were 4 or 5 different reviewers,

A single one only. He even promised a complete review, albeit pointed out that
he could not be your sponsor. No response from you at all. No response -> no
review -> no progress.

Then, in this new ticket, you didn't follow the documentation for new
packagers,

  https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
  https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

so you didn't even appear on the NEEDSPONSOR list, and again you didn't
respond.

> The report bounced too much and at the end I lost tracking.

I fail to understand that. Two comments on the package. No response.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.