Rosetta Code:Village Pump/Old draft tasks: Difference between revisions
Rosetta Code:Village Pump/Old draft tasks (view source)
Revision as of 16:21, 18 May 2011
, 13 years agoMight work
(mentors) |
(Might work) |
||
Line 30:
:: Yes. And this wouldn't prevent that. The best tasks on the site have tended to be those which someone sat through and was available as they evolved. However, not everybody has the skills to take a task idea and put it into enough human words to be clear and task-like. (I personally know people who've chosen not to create tasks not because they wouldn't like to, but because they don't think they're allowed, but because they don't believe they can put their idea clearly into task form) Not everybody has the skills to actually know about what it is they'd like to see written as a task. (Such as when I asked for [[Levenshtein distance]], or, really, half the things I've put on [[Rosetta Code:Village Pump/Suggest a programming task]]; these are things I'd like to understand, but don't) A custodial system would let someone take an abandoned task suggestion, boil it down to find the interesting bits and build tasks out of those. If there was anything useful in the original idea, it isn't lost, but refined by someone with an interest in it. --[[User:Short Circuit|Michael Mol]] 14:07, 12 May 2011 (UTC)
::: 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)
| |||