Wikipedia:Articles for deletion/Geek Code

Geek Code

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Potentially amusing, but doesn't make any real claim to notability. The only references are to blogs and personal web pages and the only implementations are personal projects. Why did you do it (talk) 10:14, 27 February 2010 (UTC)[reply]

Speedy Keep If you don't see the formal notability references in the article - please bother to find and add them, before putting anything you don't understand for the deletion. Funny that I spotted this AfD request not by looking over some afd logs, but because I needed the information on the geek code myself, and the first place I decided to consult was Wikipedia. Honeyman (talk) 15:27, 27 February 2010 (UTC)[reply]
- Now, to the point: the most prominent reference is the own article in the Jargon File, currently maintained by somebody called Eric S. Raymond (his personal homepage may give you some more clues on it). Btw, Jargon File is 26 years older than Wikipedia. Also, a quick lookup on Google hints us about 69 books whose authors are aware about Geek Code and want either to tell about it a word or two, or at least mention their own geek codes in the book. This includes the books from marginal and sociological ones as The New Hacker's Dictionary by the aforementioned Eric Raymond (and in fact being the print version of the Jargon File) or Communities in Cyberspace by Peter Kollock, or Ethnologies by the Folklore Studies Association of Canada (where the Geek Code named "one of the more fascinating folkloric creations to come out of the internet"); but also the books purely technical like The SAGE handbook of online research methods‎, or ENTERPRISE 2.0 IMPLEMENTATION. Honeyman (talk) 15:27, 27 February 2010 (UTC)[reply]
- Uh yes, and the latter book tells us that the geek code is a part of FOAF ontology standard. That should close any other questions. Honeyman (talk) 15:27, 27 February 2010 (UTC)[reply]
  - These are only passing references, not substantial coverage. The Jargon File does not meet Wikipedia's criteria for reliable secondary sources as it is a personal project of Eric Raymond and not subject to formal editorial control. And inclusion in FOAF is similarly unconvincing: as a minor, little known feature of the standard, it too is no more than a passing reference. Why did you do it (talk) 17:31, 27 February 2010 (UTC)[reply]
    - The Jargon File ... is a personal project of Eric Raymond and not subject to formal editorial control. - please reconsider the Eric S. Raymond and Jargon File articles; the Jargon File first appeared in 1975 while Eric Raymond claims that "his involvement with hacker culture began in 1976". The Jargon File is a manuscript of geekdom knowledge that changed several authors and editors (most important one, besides Eric Raymond, is probably Guy Steele), and passed several published editions (note Guy L. Steele, Eric S. Raymond, eds. (1996). The New Hacker's Dictionary (3rd ed.). MIT Press. ISBN 0-262-68092-0.). I doubt it could ever be considered "not a subject to formal editorial control" with such a long history. As for the FOAF, the [FOAF vocabulary specification] clearly shows that it is not "a minor, little known feature" but just the usual vocabulary term like "age", "publications", or "weblog". Honeyman (talk) 22:47, 27 February 2010 (UTC)[reply]

Delete unless someone can come up with substantial coverage in reliable sources. I'm utterly unconvinced by the above. Andrew Lenahan - Starblind 15:36, 27 February 2010 (UTC)[reply]
- Sorry for importunity, but I need to stress again that the geek code is a part of standard in the FOAF Vocabulary Specification, together with such fields as Myers-Briggs classification or the list of other people the person being covered by FOAF data personally knows. Honeyman (talk) 15:50, 27 February 2010 (UTC)[reply]
  - As I noted above, that does not qualify as substantial coverage in a reliable secondary source. Why did you do it (talk) 17:33, 27 February 2010 (UTC)[reply]