Zlobober's blog

Codeforces update: contests and problemsetters
By Zlobober, 9 years ago, translation, In English

Hi everybody!

Hope you liked our Revolution of Colors and Titles. Maybe you even have took part in a contest in new status. The last round have set an incredible record: 8000 participants! And I'm glad to tell you that there was no single technical issue during the round time! Consider the 15-minute delay as a part of our evil plan for setting up a new record :)

I'm glad to tell that Codeforces team is able not only to tune colors and formulas, but also to work on new features for you. You may see on contests page that there is a list of authors for each of the rounds! Moreover, in profile of a person there is now an entry called "problemsetting" that allows you to see the list of all contests in whose preparation a person took a part.


Endagorion looks like this.
Let's clarify what do we mean by taking part in preparation. The person is a problemsetter of a contest, if he proposed tasks on this contest or if he was directly involved in preparing those contest tasks. This list normally doesn't include testers and acting coordinator of Codeforces except cases when he actually proposed or prepared some problems.

Unfortunately the paragraph above can't be formally implemented by using all information about rounds we have in our databases. So, all the data was prepared by me almost manually for each of almost 600 rounds we had (including combined rounds and every kind of unusual rounds) on Codeforces, by using information from announcements, editorials, problems autorship in Polygon and some other sources of information (like "Mike, don't you remember, who was an author of Yandex.Algorithm 2011 Finals?"). All this process took two days of my life, when I had to read announcements for all rounds that happened in last five years :) Applauds to Vitaliy kuviman Kudasov who implemented all these features on Codeforces.


(this is how it happened, the image is clickable)

In all data we aggregated, obiously, there are mistakes. If you were accidentally called a problemsetter of unnecessary contest, or if we forgot to mention you as an author, write it down in comments for this post or directly to somebody in Codeforces administration.

And the last piece of news for today. Starting from Codeforces Round #326 I'm no longer a coordinator of Codeforces. I'm transferring this honorable duty to the next person, who is... well, you will eventually know him.

It was a great year when I worked on a super-cool community of a competitive programming and when I met lots of interesting people. See you in the ranking table :)

  • Vote: I like it
  • +673
  • Vote: I do not like it

Comments Comments (17)
| Write comment?
»
9 years ago, # |
  Vote: I like it +4 Vote: I do not like it

It is very good idea with "problemsetting")

→ Reply
»
9 years ago, # |
  Vote: I like it +17 Vote: I do not like it

Hi Zlobober, I am wrongly marked in Codeforces Round #250 (Div. 1). I was not an author of this round.

→ Reply
»
9 years ago, # |
  Vote: I like it +15 Vote: I do not like it

As you are no longer a coordinator, we also hope to see you in the ranking table :)

→ Reply
»
9 years ago, # |
  Vote: I like it +1 Vote: I do not like it

Thanks for your work and good luck in the future.D

→ Reply
»
9 years ago, # |
  Vote: I like it +6 Vote: I do not like it

Great, this is something which I badly desired. This makes searching for problems much easier when you remember an author (in most cases blog entries do the thing but not always).

→ Reply
»
9 years ago, # |
  Vote: I like it 0 Vote: I do not like it

I was very eager to see whether tourist arranged any round or not!!

→ Reply
»
9 years ago, # |
  Vote: I like it 0 Vote: I do not like it

User ainta and xtalclr is also the author of Codeforces Round #233 (Div. 1). (The announcement has been disappeared because of the Black Day of Codeforces..) Could you mention them as authors of that round?

→ Reply
  • »
    »
    9 years ago, # ^ |
      Vote: I like it +3 Vote: I do not like it

    Added them to #233 (Div. 1 and Div. 2) both.

    → Reply
»
9 years ago, # |
← Rev. 2   Vote: I like it +8 Vote: I do not like it
"The last round have set an incredible record: 8000 participants! And I'm glad to tell you that there was no single technical issue during the round time!"

Their was some issues during the start of the round! I could enter into the problem page after TWO minutes of terrible loading! and, maybe there was some other issues too: check this comment

→ Reply
»
9 years ago, # |
  Vote: I like it 0 Vote: I do not like it

Great！But I suggest adding the writers to the upcoming contest.I think it's better.

→ Reply
»
9 years ago, # |
  Vote: I like it +7 Vote: I do not like it

Awww, man we're gonna miss you! GL to you in the future. In the meantime, we should get ready to greet the new coordinator with open arms!

→ Reply
»
9 years ago, # |
  Vote: I like it +27 Vote: I do not like it

Very much appreciated work by you guys kudos :-)

→ Reply
»
9 years ago, # |
  Vote: I like it +32 Vote: I do not like it

And the last piece of news for today. Starting from Codeforces Round # 326 I'm no longer a coordinator of Codeforces.

Thanks for your works.

→ Reply
»
9 years ago, # |
  Vote: I like it +1 Vote: I do not like it

Greate job! Thank you Zlobober!

Btw, why there are some unrated writers?

I know:

→ Reply
  • »
    »
    9 years ago, # ^ |
      Vote: I like it +1 Vote: I do not like it

    Those are duplicating accounts of authors. On first rounds there was no option for problemsetter to register on both div1 and div2 contest, so they had to create multiple accounts, as far as I understand.

    → Reply