Checkpoint Review Notification

[SathyaJayabal]

To track discussions
https://topcoder.slack.com/archives/CG2J9RH70/p1584083663037900

For Design:

1. Event- Checkpoint screening starts
   Message- "Checkpoint screening phase is now open. You may now begin screening checkpoint submissions."
   Target audience- screeners for that particular design challenge
2. Event- Checkpoint Review starts
   Message- "Checkpoint Review is now open. You may now begin reviewing checkpoint submissions
   Target audience- reviewers for that particular design challenge.

cc @Oanh-and-only-Oanh @sachin-maheshwari @luizrrodrigues

[luizrrodrigues]

@sachin-maheshwari Let me know when this one is ready in backend.

[sachin-maheshwari]

@Oanh-and-only-Oanh @luizrrodrigues @SathyaJayabal #1, here "target audience" is not clear to me, please explain with example. And that is for "Design challenge" only ? what about other challenges ?
As I checked for Live Design Challenge https://www.topcoder.com/challenges/30119422 , corresponding backend api - v4/challenges/30119422/resources is giving only one "Primary Screener" i.e. "leben" . So only "leben" will be notified in this case. correct ?
And #2, above api giving only one "Specification Reviewer" i.e. "fajar.min". correct ?

[SathyaJayabal]

@Dara-K @Oanh-and-only-Oanh , I think checkpoint review phase is only applicable for design contests. Other challenges will not have this notification. Am I correct?

@Dara-K , Do design challenges have a reviewer role or is it done by the copilot (actual review by the client) ?

cc @sachin-maheshwari

[Oanh-and-only-Oanh]

@SathyaJayabal. checkpoint review phrase only applicable for design.

[Dara-K]

@SathyaJayabal Yes, the reviewer is the copilot for design challenges who acts in the name of the customer.

[SathyaJayabal]

@sachin-maheshwari , to summarise

When checkpoint screening starts, "Checkpoint screening phase is now open. You may now begin screening checkpoint submissions." to Primary Screener

When checkpoint review starts, ""Checkpoint Review is now open. You may now begin reviewing checkpoint submissions." to the Copilot.

cc @Oanh-and-only-Oanh @Dara-K

[SathyaJayabal]

cc @luizrrodrigues

[SathyaJayabal]

verified on test env

[SathyaJayabal]

@Oanh-and-only-Oanh @Dara-K @sachin-maheshwari @sushilshinde
On testing in beta, it became clear that the checkpoint screening is done by the "Checkpoint Screener" role and not "Primary Screener" as perviously mentioned.

We need to update the code to reflect this. The Checkpoint Screener must get the Checkpoint Screening Start notification.

[SathyaJayabal]

@Oanh-and-only-Oanh @sachin-maheshwari @sushilshinde
Checkpoint screening start notification was not received.
On looking into it, the event for checkpoint screening start was not published by OR.
Other events like checkpoint screening end, checkpoint review start etc were published. I have contacted support to help with resetting the contest phases so that we can try testing again.

The checkpoint review start notification was received by the copilot.

[SathyaJayabal]

@Oanh-and-only-Oanh @sachin-maheshwari @sushilshinde , checkpoint screening notification was also received when testing today

[SathyaJayabal]

@Oanh-and-only-Oanh @Dara-K @sachin-maheshwari @sushilshinde
On testing in beta, it became clear that the checkpoint screening is done by the "Checkpoint Screener" role and not "Primary Screener" as perviously mentioned.

We need to update the code to reflect this. The Checkpoint Screener must get the Checkpoint Screening Start notification.

This issue will be tracked in #4146

[SathyaJayabal]

verified on beta (develop branch)

[SathyaJayabal]

Verified on prod.