First of all, I have to say sorry for the vacancy of AGCs.
I'm confident in the style of AtCoder problems, but I have to admit that I was too strict; when I found a problem that was interesting but had a tiny flaw, I didn't try to use it in AGCs. In fact, I received several messages that some ARC problems are good enough for AGCs. If people who are stronger than me say that, what is my severe threshold for? Therefore, I'll be looser in selecting problems. It isn't such a big change that ARC becomes AGC. However, with the new policy, I could have made a few more AGCs in the first half of this year.
Now let's get down to the main subject: Call for Tasks. There were a few non-Japanese AGC writers, but the procedure of contest proposals was obscured. I want to make it public here. Please follow the following steps:
FAQ:
Q. What kind of problems are welcome/unwanted.
A. I'd love to have ad-hoc problems. I don't like implementation-heavy or knowledge-oriented problems. Data structures are OK as long as implementation<<<thinking.
Q. How much rejection rate should I expect?
A. It highly depends on how your "taste" is similar to mine. For some, I don't often reject proposals, while for others I keep complaining. Please check past AGC problems to see where you stand on.
Q. Why not allow ARC submissions?
A. Currently I check ARC/AGC proposals alone, so I'll be too busy to check additional ARC submissions.
Q. What happens when a problem gets rejected?
A. You are free to use it elsewhere. You may also write an ARC if you want.
Q. What's the fee?
A. 400000 JPY (subtracted by the tax) for one AGC. We can also pay for testers.
Hope to see your submissions and more AGCs!
Полный текст и комментарии »