Jump to content

User:Mwn3d/Personal policies: Difference between revisions

m
Another one
m (→‎Upgrading tasks from "draft": Clarify that one of these conditions is probably not sufficient)
m (Another one)
Line 7:
 
==Upgrading tasks from "draft"==
This has been called "touchy-feely". I will quote phrases which require ad hoc evaluation (on the talk page preferrablypreferably) to see if the time "feels right" to upgrade a draft task.
 
A task could be upgraded when "most or all of" the following have happened:
*"A couple" of users other than the original task writer have contributed correct examples
*There are "at least 4" different langaugeslanguages implementing the task (since that is when the TOC automatically shows up)
*"Like a week or two" has gone by since all questions on the talk page have been "answered"
*"Like a week otor two" has gone by without any "significant" changes to the task description
 
==Creating categories/templates==
Line 20:
==Lang tags for new languages==
*Every language should have a unique lang tag name even if that language shares keywords with another language. This makes it easier to deal with new languages diverging from other languages as they grow.
*Every language should have a tag even if it is not suppoertedsupported by [[GeSHi]].
*Lang tags should be kept "in the 1-7 character range" depending on other similar language names.
 
==Run times==
These should only be added for comparison of two different methodologies in the same language. Comparing run times between languages could lead to language superiority complexes and plain old flaming. Listing a run time for a single approach to a task has almost no value since hardware and other configurations will vary drastically among readers. The goal of RC is to help people learn, not to write the fastest (or shortest or least memory-intensive) programs.
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.