Page MenuHomePhabricator

Allow moving to draftspace and tagging accordingly (keywords: draft, draftify, draftification)
Open, Needs TriagePublicFeature

Description

Many times the best route for handling a new, underdeveloped article is to put it in draftspace (so the editor can continue building if they want, but the article doesn't linger without proper sourcing in mainspace). I think this would be a smart addition to Page Curation and it would certainly help my own work. I think it would need to be a simple macro for the following:

  1. moved to draftspace (ideally without a redirect)
  2. tag article for AfC
  3. comment out or remove categories and maintenance templates
  4. updated wikiproject status on talk page

Event Timeline

czar raised the priority of this task from to Needs Triage.
czar updated the task description. (Show Details)
czar added a project: PageTriage.
czar subscribed.
Restricted Application added subscribers: StudiesWorld, Aklapper. · View Herald Transcript
Aklapper renamed this task from Feature request: move to draftspace and tag accordingly to Allow moving to draftspace and tagging accordingly.Jan 22 2016, 11:23 AM
Aklapper set Security to None.

For anyone watching this task, I am currently using a script for this function: User:Evad37/MoveToDraft

User:Evad37/MoveToDraft was written because of the WMF delay in writing it. It does everything the original request made since by https://en.wikipedia.org/wiki/User:Czar on en.Wiki in 2015. It's since been requested by the community many, many times.
Can it now finally be added to the Curation Toolbar - primarily to restrict its use to the New Page Reviewer group to avoid its overuse/abuse by unqualified editors. Thanks.

No coment? Just being ignored?

@Kudpung: Regarding expectations, there is no need for others to add comments when there are no questions. Others are not obliged to comment on every task.
No need either to ask rhetoric questions like in T124396#4201888 when you already know the answer. The etiquette explains which types of comments are useful.
If someone (you or someone else) is interested in seeing progress in a task, providing patches is the most helpful way, or asking specific questions if something is technically unclear.

I'd be happy just forking the code from User:Evad37/MoveToDraft and adding a button to the Page Curation tools for it. Please DO NOT make the default message hardcoded somehow (there is another Phab ticket asking to make other messages non-hardcoded (https://phabricator.wikimedia.org/T204464).

@Kudpung: Regarding expectations, there is no need for others to add comments when there are no questions. Others are not obliged to comment on every task.

There is an expectation that the developers will bother to spend a few ounce of resources into issues of urgent-need that has been solicited by the community.(Do not point me to the SantaClaus wishlist!)
Otherwise, you need to send the message out to the community in unequivocal terms that:--We, developers are free to work on any issue of our liking and at a pace of our choosing.The community shall be grateful, if some developer chooses to chime in at a ticket.
In other words, do not have any expectations from us, except as to SantaClaus wish-list.

No need either to ask rhetoric questions like in T124396#4201888 when you already know the answer.

Is English your first language? The comment by @Kudpung solely intended to emphasize the lackadaisical state of affairs from your side, wherein practically none of the improvement requests for NPP, spanning over years, has been taken care of.

[offtopic]

There is an expectation that the developers will bother to spend a few ounce of resources into issues of urgent-need that has been solicited by the community.(Do not fucking point me to the SantaClaus wishlist!)

@WingedBladesofGodric: Your strong language is uncalled for and not welcome. This has been pointed out before. As it seems like you do not plan to follow our community's etiquette for Wikimedia Phabricator I've disabled your Wikimedia Phabricator account for the time being.

Are you serious? @WingedBladesofGodric is one of the few people who has been willing to actually help us out over at New Page Patrol with the list of tasks that have languished for years (some of which are apparently very simple to accomplish). We are all very sick of being pointed in the direction of the Wishlist even for fixing bugs which have existed in the software for years (like the one that makes using it for AfD impossible on second AfDs).

User:Evad37/MoveToDraft was written because of the WMF delay in writing it. It does everything the original request made since by https://en.wikipedia.org/wiki/User:Czar on en.Wiki in 2015. It's since been requested by the community many, many times.
Can it now finally be added to the Curation Toolbar - primarily to restrict its use to the New Page Reviewer group to avoid its overuse/abuse by unqualified editors. Thanks.

@Aklapper could the NPP community please have an update on the status of this request. It appears to have been a year and a half with no action. Thank you.

@Kudpung: Not sure why you're asking me specifically. For the task status, see "Open" in the upper left corner: You or anyone else is free to work on this task. For general understanding and information, see https://www.mediawiki.org/wiki/Bug_management/Development_prioritization - thanks!

Hi @Kudpung -- thanks for checking in on this. I'm tagging @ifried, who is the product manager working with the Community Tech team right now on the NPP requests from the wishlist. She'll be able to tell us whether/where this idea does or does not fit in with the current plans.

Hi @Kudpung -- @ifried and I talked about this task, and it looks like it's not one of the NPP priority tasks that are included in the large amount of work being done by the Community Tech team via the wishlist. When Community Tech is finished working on those NPP tasks, they'll need to move on to other wishlist items, and the responsibility for maintaining Page Curation tools will come back to the Growth team (the team I'm on). The Growth team will be able to address breaking bugs to make sure that patrollers can continue to do their work, but we'll not be able to commit to extending Page Curation to include features like the idea on this task (about moving to draft namespace). I totally understand why that idea is useful, but the Growth team is going to be using all our bandwidth in the coming year to pursue our priority of increasing the retention of new editors in mid-size Wikipedias. So for new features like this one (for the future that we can foresee), it could be approached in future wishlists or through volunteer developers. Let me know if you have any questions!

Novem_Linguae renamed this task from Allow moving to draftspace and tagging accordingly to Allow moving to draftspace and tagging accordingly (keywords: draft, draftify, draftification).Sep 27 2022, 3:47 AM
Novem_Linguae moved this task from Backlog to Soon on the PageTriage board.

https://en.wikipedia.org/wiki/User:Evad37/MoveToDraft is currently how most people draftify. To add this feature to PageTriage, if @Evad37 is OK with it, we would probably want to incorporate a lot of their code.

Per the doctrine that PageTriage should be a one stop shop for new page reviewing and not require the installation of any additional scripts, @MB_phab suggests that we incorporate this feature into PageTriage.

Originally created seven years ago I am surprised that this task was not addressed at that time. As I wrote above in 2018:

User:Evad37/MoveToDraft was written because of the WMF delay in writing it. It does everything the original request made since by https://en.wikipedia.org/wiki/User:Czar on en.Wiki in 2015. It's since been requested by the community many, many times. Can it now finally be added to the Curation Toolbar - primarily to restrict its use to the New Page Reviewer group to avoid its overuse/abuse by unqualified editors. Thanks.

It should be noted once again that the maintenance of PageTriage is a Foundation responsibility and on their own admission it is beyond the bandwidth of Community Tech and the Growth teams. Suggestions in other places that the Foundation lacks funds or HR are neither accurate nor acceptable and some response at this time would be much appreciated.

@MMiller_WMF What can we do to help expedite this request? This is a tool we really need. I have been asked to provide a list of what we have repeatedly requested (wished for) that has not yet been completed. This request appears to be high on the list we will be providing to Ms Denckelmann who is going to look into why the tasks are not being fulfilled. Anything you can do to help will be greatly appreciated.

A recent discussion at the village pump about draftification has made it clear that user talk messages should be carefully crafted, friendly, and specific. Here is one mockup that @Kudpung did:

Page Curation move to draft.png (765×911 px, 363 KB)

Here are some custom messages that patroller @Onel5969 created.

https://en.wikipedia.org/wiki/User:Onel5969/Draftify_templates

The important feature of the Kudpung mockup is that rather than attempting to explain the issues in detail and with a mass of alphabet soup, the message invites the creator to visit a very warmly presented page that is absolutely neither bitey nor accusatory, but which provides all the answers in a friendly way: at Help:Unreviewed new page and without presenting the creator with walls of text.

Because all the reviewer needs to do is check a box, the reviewer does not need to customise a default message. The six selectables cover all the main issues. It is intended, if technically possible, that the message to the creator contains only the checked criterion and not the entire list with one or some of them checked.

@Atsme -- I just wanted to let you know that I just now saw your ping here in Phabricator from a few days ago, because I'm browsing through the list of NPP tasks to refamiliarize myself. But as an FYI, these days I'm much more reachable on wiki than in Phabricator because my current role is less in the weeds of specific tickets. Anyway, I see you're signed up for next week's meeting, so I'm looking forward to talking there!

Thank you!! I have always found you a pleasure to work with and look forward to next week.

Novem_Linguae changed the subtype of this task from "Task" to "Feature Request".Dec 11 2022, 9:24 AM

https://en.wikipedia.org/wiki/User:MPGuy2824/MoveToDraft incorporates the above mockup, is written in JavaScript, and has an active maintainer.

Best way forward with this ticket is probably to copy paste the MoveToDraft code into PageTriage and adapt it so it works, basically "moving" the user script into PageTriage. Or if the exact code is too difficult to adapt, then the front end specifications and logic should be matched.

This feature request keeps with our philosophy that PageTriage software should be a one stop shop for enwiki new page patrollers.