What happens next#

You have sent a report or a suggestion. This page is what happens to it, so that the silence afterwards is a known length and not a mystery.

An admin reads it#

Reports from a posting and suggestions made in place land in the same list. One queue, worked through by an admin.

They see the current wording beside what you suggested, so they are comparing two things and not reading a description of a problem.

Four ways it can end#

• Fixed. The wording was changed.
• Being worked on. It has been read and accepted, and the change is not done yet.
• Left as it is. They decided the current wording is right, or that yours changes the meaning.
• Waiting to be read, which is where every one of them starts.

Every one is answered#

An admin has to write a note when they close a report, including when they turn it down.

That is a rule the site enforces and not a courtesy somebody remembers. You took the trouble to tell us, and closing it silently teaches you not to bother next time.

The note appears beside your report on your account settings page, under Translation problems you reported.

Nobody is named#

You see the decision and the note. You do not see which member of staff made it.

The status and the note are the answer, and an applicant account has no relationship with an individual staff account.

Content is changed there and then#

A posting, a team name or a tag name lives in the database. An admin who agrees with you can apply the change directly, and it is live once they do.

Interface wording waits for a deploy#

Every label, button and message on the site lives in the code, in two dictionary files. That is what keeps the site fast and lets it work offline.

So a suggestion about interface wording is a change a developer makes and a release carries. The admin view says so plainly, so that nobody accepts one and wonders why nothing changed.

There is no interface string editor, and there will not be one. Moving the dictionaries into the database to avoid the wait would cost the offline copy and a request on every page.

No dates#

Nothing here promises a timeframe:

Sent. Somebody will read it. We will not promise you a date, but it lands in the same queue as everything else.

A date invented to sound reassuring is a date somebody has to explain later.

If it has been a long time#

Ask in the GFTV Telegram group, or wherever you normally reach the team. Pointing at a specific report is fine, and it is more useful than a general question about the queue.