Last modified: 2014-07-10 11:30:33 UTC
The Indonesian Wikipedia community requested to install Page Curation (PageTriage) http://id.wikipedia.org/w/index.php?title=Wikipedia:Warung_Kopi_(Teknis)&oldid=6196477#Special:NewPagesFeed
Unfortunately, I don't think PageTriage is quite ready for deployment outside en.wiki. The main problem is that we had to add some customized features to support all the different deletion processes on en.wiki, and most of these won't work the same for other wikis. The majority of this functionality is configurable, but a small amount of it isn't. We need to make it completely configurable, but before we can do that we have to understand how the different deletion processes work on other wikis. For example, on en.wiki we have PROD, XFD, and CSD, which are all completely different processes. What are the deletion processes on id.wiki? Are any of them analogous to the processes on en.wiki?
@Ryan Kaldari So on the other hand, you want to us to adjusting the conditions of deletion processes on id.wiki, to match with the processes conditions on en.wiki ? Can you provide guidance for that? Or maybe a help page for the prosess translating Page Curation to the other wiki ? Thanks in advance
(In reply to comment #2) > @Ryan Kaldari > So on the other hand, you want to us to adjusting the conditions of deletion > processes on id.wiki, to match with the processes conditions on en.wiki ? > Can you provide guidance for that? Or maybe a help page for the prosess > translating Page Curation to the other wiki ? > Thanks in advance No, he would like you to describe your current deletion workflows, so we can make the extension configuration aware of your ways to delete pages.
There are other options as well: * We can deploy PageTriage with the deletion wizard part disabled * We can deploy PageTriage with the Curation Toolbar diabled. In this case, when you review an individual article, it will just have a simple 'Mark as reviewed' link at the bottom (similar to page patrolling).
Note: PageTriage seems to not be ready yet, see bug 42322 comment 1 bug 38512 comment 5 but there is ongoing work, see bug 38512 comment 8.
