Rosetta Code:Village Pump/Old draft tasks: Difference between revisions
Rosetta Code:Village Pump/Old draft tasks (view source)
Revision as of 22:04, 11 May 2011
, 13 years agoMore thoughts.
(Cull some ?) |
(More thoughts.) |
||
Line 16:
:By adopting the above, would we then have a sizeable problem of tasks with one good implementation and a good task description but no further activity for some time? Not sure :-)<br> --[[User:Paddy3118|Paddy3118]] 21:51, 11 May 2011 (UTC)
:: I strongly dislike the "must provide an implementation" requirement for something to be a draft task, as it prevents people from trying to build tasks that they don't know enough to implement. That's somewhere in the vicinity of 90% of the things I've tried to get created. I believe the reason the Suggest a Programming task page is a place where ideas go to die, and I hate that page with a passion. I'd rather see large numbers of directionless draft (or sub-draft, whatever) tasks free to be claimed, clarified and directed by anyone with the motivation, then have that festering page sit there. The key problem is that entries on that page don't get revisited by the people who create them, and it's unlikely they will. There needs to be some degree of freedom to take such an idea and mold it into something more suitable, but there's no sense of such freedom or drive in the task page as it exists. There's also no real way to purge items off of that page even if they do get implemented. (This may be a point where I strongly disagree with RC regulars, and if that's the case, then all I ask is that some system of evolving half-baked ideas from people who don't know enough to build them themselves is built) --[[User:Short Circuit|Michael Mol]] 22:04, 11 May 2011 (UTC)
| |||