Last modified: 2008-06-12 18:47:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14428 - Please unlock Wolof Wiktionary, which was locked on error
Please unlock Wolof Wiktionary, which was locked on error
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
  Show dependency treegraph
Reported: 2008-06-06 07:15 UTC by Justin Anthony Knapp
Modified: 2008-06-12 18:47 UTC (History)
3 users (show)

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


Description Justin Anthony Knapp 2008-06-06 07:15:22 UTC

Personally, I am not in favor of closure, but as long as it is to be closed, it should be locked. As best as I can tell, the consensus was reached but the project is still open. Please correct me if this has been resurrected.
Comment 1 JeLuF 2008-06-06 19:30:38 UTC
Comment 2 Johannes Rohr 2008-06-07 21:24:41 UTC
please unlock the Wolof Wiktionary again, the closure decision had been taken two years ago and was later overturned, see bug 11512 

The submitter of this bug has apparantly not understood this history. Meanwhile the Wolof Wikitionary has been very active since it was reopened and has lots of legitimate content, Therefore closing it cannot be justified. 
Comment 3 JeLuF 2008-06-12 18:47:03 UTC
This was unlocked already a few days ago. I forgot to close this ticket.

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