Rosetta Code:Village Pump/Old draft tasks: Difference between revisions

::: Perhaps it would be of use to identify people who might help shepherd a task through draft. If someone wants to create something but are less comfortable with the wordsmithing and definition, then identify mentors. A task mentor wanted page or something. That would give them someone to bounce ideas off and get the wrinkles out of before things get too loose. --[[User:Dgamey|Dgamey]] 03:47, 18 May 2011 (UTC)

:::: Might work. We'd want to clear out the existing 'suggest a task' page, and create a template for placing new ideas there. The template would need arguments for a short summary, long summary (including offsite references), and who's taken on the shepherd role. The template can even force-sign the submitter's username, to aid communication. It would probably link to a page titled after the short summary. where discussion can take place before a draft task page is created. --[[User:Short Circuit|Michael Mol]] 16:21, 18 May 2011 (UTC)

:Do we want to, in effect, move some of the list of suggested tasks into abandoned task pages with just as much information in them? --[[User:Paddy3118|Paddy3118]] 05:14, 12 May 2011 (UTC)

:: Actually, that's more or less what I'd like to see, with the caveat that we can identify when tasks are abandoned and have free license (in a social sense) to reformulate them into something more useful and/or interesting. The 'custodian' idea was intended as way of explicitly identifying who had that license, and as a way of clarifying whether or not a task is truly abandoned. (If a task transfers custodianship, then we can ask the new custodian. If the new custodian doesn't ceases to take interest in the task, then the custodianship can transfer again) --[[User:Short Circuit|Michael Mol]] 14:07, 12 May 2011 (UTC)