Wikinews:Water cooler/technical

Refresh

Archive, post

---

Archives July 2009 August 2009 September 2009 October 2009 November 2009 December 2009 January 2010 February 2010 March 2010 April 2010 May 2010 June 2010 July 2010 August 2010 September 2010 October 2010 November 2010 December 2010 January 2011 February 2011 March 2011 April 2011 May 2011 June 2011 July 2011 August 2011 September 2011 October 2011 December 2011

Required: Userspacing gadget

Looking at use of Wikinews for education projects, such as the UoW ones, there is obviously a need to quickly and easily move articles to userspace. Deletion as stale/abandoned means that examples of not-up-to-scratch work are being lost, and the educational value from failing with them.

I would like to see a gadget developed to deal with this — possibly also being included as a button from within the {{abandoned}} and {{stale}} templates. The required functionality is, I believe, covered by the below:

1. Retrieve the article's edit history, this is to be parsed for possible target userspace to put the article in.
2. As-default, offer the most frequent contributor prior to the first addition of the review template. (Identified with edit summary: Please review this article. (moved using js via button)).
3. Then, ignore edits by the same editor leading to a failed review (Identified with edit summary: Not ready when reviewed: article needs improvement(s). Add article flag. (Using easy peer review)) back to the next differing editor. With the remaining revisions, offer contributors in order of how many contributions.
4. Lastly, offer option to open edit history in new Window/Tab next to a box to manually specify the user whose space the article should be moved to.
5. When "Userspace article" is clicked, article is moved with a redirect left behind.
6. Once article is in userspace:
   1. 'Deactivate' {{date}} templates (insert the tl| to avoid category inclusion)
   2. 'Deactivate' any infobox template (method as-per date template, but assume any template within the 1st 3-4 lines is an infobox).
   3. 'Deactivate' categories by prefixing the Category: with a colon (":").

Saving failed articles in this way will allow a great deal more to be learned from submissions which don't end up published. And, with a single automated edit, the most troublesome work of userspacing an article is automated. --Brian McNeil / ^talk 16:39, 12 January 2012 (UTC)

We'd likely want ability to manually specify a userspace by a parameter to the template, which when present would settle the question of whether to move to userspace and obviate the elaborate automatic search for a choice of destination. Conceivably, we might want to limit the move-to-userspace option to articles marked in some way (either the parameter, or otherwise).

When an article's problems include (non-blatant, hence non-speedy-able) copyvio, moving to user space on a permanent basis may be the wrong approach (though the article talk page may be less problematic).

Though {{tl}} disables thoroughly, it may also obscure what the template was supposed to look like; a parameter (perhaps nocat=1 ?) might be better if supported. --Pi zero (talk) 17:31, 12 January 2012 (UTC)

Notification of review

This would likely be an added function of EZPR (terrifying thought). When a review is submitted, the gadget would automatically identify users who have done nontrivial work on the article, and would put a notice on each of their user talk pages.

• This function should probably be optional, so a reviewer can choose not to do it.
• We'd need to hammer out the automated criteria for who to inform. (To get fancy, should the reviewer be able to adjust the criteria, or even remove and add users to the list to be informed?)
• The notice would go in a section titled "[[Name of article]]".

If there is already a section on the user talk page with that name, the notice should probably be put in that already-existing section.

• Here's a likely form for the notice:

* This article, [to which you have contributed/which you created], has been [published/found not ready on review]. See: [[Name of article#anchor|review comments]], {{plainlinks|{{fullurl:Name of article|action=history}}|history of edits during review}}. <small>—review via easyPeerReview by ~~~~</small>

where the anchor sends the link directly to the particular review section for that review.

--Pi zero (talk) 18:00, 4 February 2012 (UTC)

• What about also a nice Congratulations! or Job well done! when a review is successfully completed? -- Cirt (talk) 19:15, 4 February 2012 (UTC)

These little extra messages should probably be manual customizations, or at least manually customizable. This also highlights that we don't want review notifications going to users whose contributions to the article were vandalism. —The preceding unsigned comment was added by Pi zero (talk • contribs)

• Just a thought, maybe the tool could give a list of all users who contributed, and then allow a check off list to only notify the users manually selected by the reviewer. Cocoaguy^talk_contribs‽ 19:56, 10 February 2012 (UTC)
• Support If we can do it, let's do it! —Tom Morris (talk) 22:23, 4 February 2012 (UTC)
• Support If technically possible. Cocoaguy^talk_contribs‽ 04:33, 8 February 2012 (UTC)
• Support provided we can add the customizable options as specified, above. -- Cirt (talk) 04:55, 8 February 2012 (UTC)
• Support Sounds like a really good idea. --Cspurrier (talk) 04:08, 11 February 2012 (UTC)