4 ms·
Wikipedia doesn’t want to host journalism. It wants to host editorial content. This is an important distinction for technical reasons of editorial process: the
by derefr 8y ago
Wikipedia doesn’t want to host journalism. It wants to host editorial content. This is an important distinction for technical reasons of editorial process: the content on Wikipedia should always be able to be recreated from the article’s sources. If the article is the canonical place where the assertion can be found, then editors have to tip-toe around editing that piece of content much more carefully, being careful to preserve it as an artifact—which makes some of Wikipedia’s regular editorial approaches (e.g. deleting “niche” articles) untenable.
The proper way to contribute primary-source knowledge to Wikipedia is to create a secondary source (like an article on a third-party website) containing quotes of your primary-source statements. Then edit Wikipedia and cite that third-party source.
If you think this won’t work: how do you think the Wikipedia articles for companies get updated to reflect news about them? Almost always, the company’s PR team writes an article, puts it on the PR news-wire, and then goes and edits the relevant Wiki article to reflect the new information, citing the PR news-wire article.
The key reason this is allowed is that anyone could have made those same edits (and probably would have—the PR team isn’t changing the outcome, just expediting it.) The edits aren’t accepted by an argument to authority of the editor, but by an argument to consensus-acceptance of the secondary source as reflective of reality.
By analogy: it’s untenable to put code (e.g. a usage example) in a Git commit message. The commit messages are on a layer above the code; they refer to the code, but they can’t refer to themselves. Nobody can edit the code in somebody else’s commit message to fix it if it’s wrong. It’s much better to have the code committed as code (or docs, tests, etc.) in the repo, because then you can fix it, change it, talk about it, whatever.
The code is the primary source; the commits are the secondary sources, citing the primary sources; and the commit messages are an editorial reflection of the secondary sources. (This is especially true in LKML-style commits where submitters squash their commits into patches, dropping their messages; and then maintainers—essentially editors—write the final commit message.)
If you want to make a new commit message in the commit log, it has to serve as a description of a new commit, which in turn has to package a change in the code. If you want to make a new paragraph in a Wikipedia post, it has to serve as a description of a citation, which has to package new primary-source information. But solving both problems is easy: your write the code/third-party article, and then commit/cite it.
- reaperducer 8y agothe content on Wikipedia should always be able to be recreated from the article’s sources If Wikipedia only wants content from published sources, then it's going to miss the 99% of history that's not reported on a newspaper web site.
- derefr 8y agoNobody said anything about "published" sources. Anything that is not Wikipedia (or another purely-editorial tertiary source like a rival Encyclopedia, or a survey-level textbook) qualifies as a secondary source. Assertions about history before the Internet—before writing, even—can be cited just like anything else. The "99% of history" that we currently know about, we know about because some historian or paleontologist or anthropologist dredged up primary-source data, put it together, made sense of it, and wrote down their findings in a journal paper (i.e. a secondary source.) Wikipedia, like all encyclopedias, cites those secondary sources. You have primary-source knowledge of your own? Write a blog post about it. Just like a historian writing a journal paper, that blog post is now a secondary source that quotes your primary-source knowledge (ETA: or maybe the blog post is even a primary source itself, depending on how fresh your knowledge was and how unbiased your reporting of it was.) Wikipedia can now cite your blog post. Wikipedia cites plenty of blog posts. Alternatively, if you're doing journalism—going out and talking to primary sources—then the Wikimedia group of sites has a place that will host any secondary-source artifact you create from that: Wikinews. You can write a Wikinews article, and then cite it on Wikipedia. Wikipedia cites plenty of Wikinews articles. Let me make another analogy: if you compare the Wikimedia foundation as a whole to, say, a newspaper publisher; then Wikipedia is specifically the editorials section of that newspaper. Journalism is most of a newspaper; but the one place it doesn't belong, is in the editorials section of the newspaper. Journalism belongs in the "news" part of the paper. Wikipedia editors know that people can wear many hats, and there's nothing wrong with being both an editor and a journalist. The whole distinction they're making, is that Wikipedia doesn't want people editing articles with their primary-source hats on, or with their journalist hats on. Wikipedia wants people editing articles purely with their editor hats on. If you're a primary source, or a journalist, you do that stuff outside of Wikipedia proper. Then you turn around, take off those hats, put on your editor hat, and edit Wikipedia to refer to what primary-source-you or journalist-you just created. (Or, if you're not an editor by nature but just want your content cited, then you should just be a primary source and/or journalist—someone who writes stuff down somewhere it can be cited—and leave editing Wikipedia to people who like editing. Maybe make friends with some Wikipedia editors, and send them links to your new stuff when you produce it. If it's worth including, they'll cite it and write about it! This is literally exactly the same as having a relationship with the editors of a newspaper/magazine/regular encyclopedia. Just because you/anyone can be a Wikipedia editor, doesn't mean that you have to; and it doesn't mean that being a (Wikipedia) editor is not a specialized job that is some people's comparative advantage, while your comparative advantage might lie elsewhere—like in being a personal historian.) I want to call out a specific example of blog posts being cited as secondary sources, to make this clear. Microsoft's Raymond Chen is a blogger (https://devblogs.microsoft.com/oldnewthing/ https://devblogs.microsoft.com/oldnewthing/). He writes a lot about the path-dependencies in Microsoft products that have led to them being the way they are today. Wikipedia cites these posts all the time. Even though he's writing about things he did himself. You are allowed to be a primary-source man-on-the-spot recollecting history; and the secondary-source historian "interviewing" the primary source; and even the tertiary-source editor citing the secondary-source blog-post "interview" artifact. (I don't think Chen bothers to edit Wikipedia to cite his posts, but there's no reason he couldn't.)