Last modified: 2013-01-09 01:35:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T34211, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 32211 - Contest extension lacks a way to unselect a challenge
Contest extension lacks a way to unselect a challenge
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Contest (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-04 22:50 UTC by MZMcBride
Modified: 2013-01-09 01:35 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2011-11-04 22:50:08 UTC
The Contest extension doesn't seem to offer a way for participants to say "no thanks" to the whole idea. This wouldn't generally be problematic except that people are being spammed via e-mail about the coding challenge with no way to opt-out.

There should be a way to disengage via the Contest UI, surely.
Comment 1 Jeroen De Dauw 2011-11-04 23:46:04 UTC
I asked Greg about this while creating the extension; he said there was no need for such functionality.
Comment 2 MZMcBride 2011-11-04 23:48:14 UTC
(In reply to comment #1)
> I asked Greg about this while creating the extension; he said there was no need
> for such functionality.

Greg is wrong.
Comment 3 Erik Moeller 2011-11-05 00:01:46 UTC
For the purposes of this challenge, we've manually removed people who've requested to be removed.

Going forward, if we do use the extension in its current form again, I do think that a removal feature would make sense (as part of the "my contests" page, and as a link we can add in email).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links