Evalai: Add the functionality to disable the Challenge

[deshraj]

Objective

A challenge host should be able to delete the challenge using the UI. At the backend, set the flag is_disabled whenever a challenge host submits a request to delete the challenge.

[rishabhja]

Can i contribute to this?

[RishabhJain2018]

@rishabhja yes sure. Go ahead.

[rishabhja]

Can you assign the issue to me?

[taranjeet]

@deshraj: I would prefer that you call this issue as "Add functionality to disable a Challenge" since at the backend you are disabling the challenge. It does not make sense to introduce an inconsistency in actions at backend and frontend.

[rishabhja]

Where is the disable button to be shown?

[deshraj]

The disable button should be shown right below the challenge description in a card where if the challenge host clicks on that button then a dialog box opens that asks the challenge host to enter the challenge name and then press submit in that dialog box. Does that sound good @rishabhja ?

[rishabhja]

Why do i need to ask for the challenge name if he is pressing the disable button on a specific challenge?

[deshraj]

We are doing this to make sure that the challenge host is not pressing the button by mistake.

[rishabhja]

A confirmation dialog maybe better

[deshraj]

We have thought about both the approaches earlier and we wanted to go with this approach similar to what Github follows. :)

[rishabhja]

okay, sure. I am assuming this disable button is not shown on the all challenges screen?

[deshraj]

Cool. @rishabhja please let us know if you have other doubts about this.

[rishabhja]

Disabling the challenge doesnt hide it. Is it expected?

[rishabhja]

Can you give me access to push?

[RishabhJain2018]

@rishabhja yes, disabling a challenge must hide it from the list of all challenges.
Moreover, please create a pull request with the changes that you have done.

[rishabhja]

I am not able to push my branch. So, how will i create a PR?

[RishabhJain2018]

For creating a PR, please fork the repository then you can push your local branch to your origin and then create a PR from there. Please ask if something is not clear. Please refer here for more details https://help.github.com/articles/creating-a-pull-request-from-a-fork/

[RishabhJain2018]

@rishabhja Any update on this ?

[anuj-rathore]

@RishabhJain2018 If nobody is working on this, can I work on this?

[aka-jain]

Sure @anuj-rathore please go ahead. Assigning this to you.

[guyandtheworld]

@anuj-rathore Are you working on this?

[aka-jain]

I think @anuj-rathore is inactive. You can work on this @isht3

[anuj-rathore]

I am up for this...

On 08-Jan-2018 12:29 PM, "Akash Jain" [e-mail] wrote:

I think @anuj-rathore https://github.com/anuj-rathore is inactive. You
can work on this @isht3 https://github.com/isht3

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Cloud-CV/EvalAI/issues/1080#issuecomment-355894409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMIQ0M7rgh6cpUabER5IFD6YuP5C3CIBks5tIby5gaJpZM4OQ9KU
.

[aka-jain]

@isht3 you have started working on this?

[guyandtheworld]

@aka-jain Nope!

[deshraj]

Wow, lot of comments. I think the final conclusion is that @anuj-rathore you can start working on this. :) Feel free to ask questions if you have any.

[anuj-rathore]

I am really sorry, as I am quite busy these days! It would be really good if you could assign this to someone else @deshraj @aka-jain

[codervivek]

Can I claim this assignment?

[deshraj]

Sure @codervivek. :)