till date i have done many FE package reviews and first time i am going to
review a package for fedora core. 
Kindly tell me if i need any thing to change/set here.

Taking this package for official review.

mockbuild failed.
You need to create a patch to Makefile.am
and replace following line
                mkfontdir -e /usr/X11R6/lib/X11/fonts/encodings; \
with
                mkfontdir -e /usr/share/X11/fonts/encodings; \

submit new package after adding patch.

No response from submitter so leaving this review as it looks dead to me.

And another two months with no response; it's definitely dead.

How does me not responding makes Fedora not need Thai fonts?!?!?!

For your information, at the time I submitted this, there was also the issue of
Red Hat legal needing to check copyright/ownership of the fonts.  Not sure what
it should go through these days.

Again, just because original reporter doesn't finish the work, doesn't mean it's
not worth a bug.  STOP CLUTTERING BUGZILLA AND PEOPLE'S INBOX.

Nobody said that your lack of response implies anything about the need for Thai
fonts.  Frankly, all it says is that you haven't bothered to respond to review
commentary, which is puzzling since you sure responded to the closing of the
ticket quickly enough.

So, do you actually want to respond to the comments?  If not, the review ticket
gets closed so that someone else who will actually bother to respond can submit
the package.  Those are the rules.  Comical all-caps replies and anger
misdirected at me, one of the people tasked with keeping the review queue
cleaned up and closing out stalled reviews, isn't going to help the issue.

Either answer the comments or close this ticket.  It's that simple.  I'll clear
the DEADREVIEW blocker, but if there's no response in the future I'll just be
back here to close out this ticket again.

Well, it's been another month with no commentary; setting NEEDINFO.  I'll close
in a week if there's no further response.

Closing as promised.

Behdad, maybe someone in the i18n team can take up this package for you?

Jens, anyone should feel free to finish this.  I still think that it's not
productive to close bugs for the sake of doing that.

It's not productive to have a "review" ticket open when the submitter won't even
bother to respond to review commentary.  And now for some reason someone has
come along and renamed this as a merge review when we have no existing
fonts-thai package which was merged.

I really don't understand the point of putting this package out here and then
not even having the common courtesy to respond when a volunteer comes along and
provides review commentary.

So, fine, leave this ticket open and just sitting here.  Perhaps this final
message will discourage any other reviewiers from wasting their time: If you try
to review, you'll be ignored and if you follow policy and close this bug because
the submitter is ignoring comments, you'll get flamed and the ticket will be
reopened.

Hi Jason,

Sorry for reopening the ticket again.  I don't want to get into any flame-wars
but this package is important to for the i18n team, so we give it a higher
priority than Behdad.  I just feel more comfortable leaving it open
so that it does not fall-off our radar but I also understand your wish to get
it off the review list in a timely manner.  Anyway I think the i18n team should
be able to get this moving again.  But if it is better to start a new ticket,
we can do it that way too. :)

Yes, better to start a new ticket submitted by the person who will be driving
the submission.  I'm sure we can get it reviewed relatively quickly.

bureaucracy.

I'm reassigning this to fontconfig, so you are not bothered by an open bug for a
real issue.  If you cannot respect the fact that I don't have the free time to
follow up with this, I don't think you should be responsible for a bugzilla
product.  Get a lesson on what issue tracking means.

Review Requests are always filed against "Package Review" component.
Just checked Bug Activity and bugzilla comments and found that Jason is right. I
mistakenly renamed bug to "Merge Review" rather to make it as "Review Request". 
Its almost another more than one month spent on open review(which should be
closed and reopened again after license issue got solved).

 Anyway whenever fonts-thai package finish its packaging it have to go thru'
package review and package reviews must be reported against "Package Review"
component only.

(In reply to comment #14)
> bureaucracy.
> 
> I'm reassigning this to fontconfig, so you are not bothered by an open bug for a
> real issue.  If you cannot respect the fact that I don't have the free time to
> follow up with this, I don't think you should be responsible for a bugzilla
> product.  Get a lesson on what issue tracking means.

Good to ask FESCO and prove that their procedure of handling stalled reviews is
WRONG. If we stop people following accepted policies then no one will try to
look at bugs and thus nothing got progressed in bugzilla.

I think the package should be rename to be closer to the upstream name;
maybe thaifonts-scalable would be good?

I submitted thaifonts-scalable, cleaned up from Behdad's packaging, under bug
431829.

Hope that is ok, otherwise we can also continue the review here.
Just felt it was easier to start with a fresh ticket with a new submitter. :)

Thanks for the good start with packaging these fonts.

Finally we should have decent Thai fonts in F9. :)

*** This bug has been marked as a duplicate of 431829 ***