Hello Codeforces!
At the end of August, I (and my friend) proposed Div 2 contest and don't get the review for now. In general, it's okay. We understand that this not maybe so fast and 3+ month delay it's normal, but it's not really clear when it will happen.
I tried to ask MikeMirzayanov and after that KAN. And they gave us some information about the situation with proposals queue. (Thanks to them indeed. Cool when the organisers respond in person)
I think it would be cool If contest authors have the possibility to view approximate position in the proposals queue and to estimate the approximate time of receipt their review. And today I want to ask the Codeforces community about the need to introduce such a feature, and the Codeforces organisers about the possibility of implementing something similar.
And I certainly want to thank Codeforces for the opportunity to participate in the preparation of the round (as an author or a tester) and all coordinators for their hard work!
It would definitely be nice to have something like this. I've thought about submitting proposals a few times and have problems thought of (and some even prepared already on Polygon), but I've heard that the waiting time for the queue is a year long which is pretty discouraging.
So, I waited for the review of my first round (div2 too) for about 3 weeks. Proposals queue can be different. Sometimes it takes more time than usual.
My friends and I have proposed a round earlier than you (in May). We got a coordinator in August, he hasn't answered yet. It seems that sometimes coordinators don't follow the order by date of proposal.
Wow. it's a surprise for me. I thought this doesn't happen. Have you tried to ping your coordinator?
I have a great suspicion that some proposals get "ghosted" if they have too many not-so-great problems.
But should we expect a response sooner or later or should we give up?
And if you have good problems, you will have a good round that is valuable. While waiting, you can prepare some problems which you are sure or just improve your round (maybe you will find mistakes in solutions or just replace your problems)