Grants talk:IdeaLab/Maintenance tags follow-up
Interesting but...[edit]
This needs to be opt in and/or, might be focused in a different way: for example, I think assuming that editors who tag, are not working on the backlog and/or only tagging articles by new editors, doesn't think through how this behaviour happens. A big part of the reason I tag, is because while working on one backlog, principally article assessment, I tag on other backlog items that I don't have the focus to work on in the moment. I also, systematically work through other types of the backlog (like BamBots listing, or back in the day, I did category intersections areound orphaned articles), and find that trying to meet all of the needs on an article at once, is often to much for my limited volunteer time. I do support the idea of "backlog review", where articles that receive a major revision and have broad maintenance tags, get thrown into a queue for brief article revision check. I would definitely think this is something that @Harej: might be interested in with WikiProjectX. Sadads (talk) 19:55, 1 March 2016 (UTC)
- As is often the case, the original exposition of an idea need substantial tweaking. I have briefly thought about the opt in issue, but as is obvious, didn’t mention it in my initial exposition. One way to achieve opt-in is quite easy — rather than modifying the existing maintenance tags, create a new set of maintenance tags which do create the reminder, then allow editors to use the old tags if there is good reason they do not want to deal with the reminders. I am open to that is a possibility but if we go that route I’d also like to devise some mechanism for follow-up. Can we create a cat (or is there one already) that keeps track of these tags? Can we create a task force or convince an existing task force such as the Guild of Copy editors to monitor this cat?--Sphilbrick (talk) 20:21, 1 March 2016 (UTC)
- I tweaked my goal statement to reflect the possibility that this might be an an opt-in approach.--Sphilbrick (talk) 20:27, 1 March 2016 (UTC)
- If this were more like a by-WikiProject maintenance queue that says "x article with x maintenance tag, just saw x major revisions: check out the diff". My ideal user story would be being able to run through the list with popups, and selectively say: yes that one needs to be removed, and that one, etc. This might be something that we could get the Bambot operator to do, @Bamyers99:, especially if he is already creating the maintenance lists. Sadads (talk) 14:59, 3 March 2016 (UTC)
- A systematic way of revisiting articles with maintenance tags is something I'm interested in, particularly as someone who copyedits articles for fun. I see "this article is lousy, clean it up (May 2008)" and then I see an article that's not all that bad. I look for the original revision that warranted that tag, and I compare to the present day, and then just decide to remove the tag if I think the article is sufficiently improved. The problem is that improvements are made so incrementally no one can actually tell that the article has gotten better. I don't know that creating a new batch of templates is the solution. What would be useful is finding the articles with the oldest outstanding tags, show the revisions side by side, and ask "mission accomplished? yes or no." And then the tag is removed if so. This could be a nice tool, and something that could be deployed on a WikiProject-by-WikiProject basis. harej (talk) 08:29, 31 March 2016 (UTC)
- If this were more like a by-WikiProject maintenance queue that says "x article with x maintenance tag, just saw x major revisions: check out the diff". My ideal user story would be being able to run through the list with popups, and selectively say: yes that one needs to be removed, and that one, etc. This might be something that we could get the Bambot operator to do, @Bamyers99:, especially if he is already creating the maintenance lists. Sadads (talk) 14:59, 3 March 2016 (UTC)
April 12 Proposal Deadline: Is your project ready for funding?[edit]
The deadline for Individual Engagement Grant (IEG) submissions this round is April 12th, 2016. If you’ve developed your idea into a project that would benefit from funding, consider applying!
To apply, you must (1) create a draft request using the “Expand into an Individual Engagement Grant” button on your idea page, (2) complete the proposal entirely, filling in all empty fields, and (3) change the status from "draft" to "proposed." As soon as you’re ready, you should begin to invite any communities affected by your project to provide feedback on your proposal talk page.
If you have any questions about IEG or would like support in developing your proposal, we're hosting a few proposal help sessions this month in Google Hangouts:
- April 5th, 16:00 - 17:00 UTC
- April 8th 1:00 - 2:00 UTC
- April 12th 16:00 - 17:00 UTC
I'm also happy to set up an individual session. With thanks, I JethroBT (WMF) 00:38, 2 April 2016 (UTC)
WMF Blog[edit]
Hi Sphilbrick, I wanted to just drop by to let you know that I highlighted your idea here in a recent post on the Wikimedia Foundation blog. I hope it brings some more feedback and participation on how to improve maintenance tag systems in our projects. Thanks, I JethroBT (WMF) (talk) 22:47, 13 April 2016 (UTC)
- Thanks for the heads up I appreciate it, and hope we make some progress.--Sphilbrick (talk) 12:57, 14 April 2016 (UTC)