Page MenuHomePhabricator

Allow moving to draftspace and tagging accordingly
Open, Needs TriagePublic

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 created this task.Jan 22 2016, 8:07 AM
czar raised the priority of this task from to Needs Triage.
czar updated the task description. (Show Details)
czar added a project: PageCuration.
czar added a subscriber: czar.
Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptJan 22 2016, 8:07 AM
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.
czar added a comment.Jun 13 2017, 3:59 PM

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

Kudpung added a subscriber: Kudpung.EditedJul 22 2017, 12:44 AM

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?

8 months and no comments?

@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).

Restricted Application added a project: Growth-Team. · View Herald TranscriptOct 19 2018, 6:59 AM

@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!