Comments

The following is an automatically-generated compilation of all talk pages for the Signpost issue dated 2013-01-07. For general Signpost discussion, see Wikipedia talk:Signpost.

Featured content: Featured content in review (624 bytes · 💬)

I wonder if there'd be any interest in reviving Featured sounds? Adam Cuerden ^(talk) 12:51, 9 January 2013 (UTC)

Perhaps. I'd help, but I've got a tin ear and no quality sound equipment (one may have influenced the other). — Crisco 1492 (talk) 12:58, 9 January 2013 (UTC)

News and notes: 2012—the big year (2,364 bytes · 💬)

Jclemens was not new to the committee in 2012, having been elected in 2011. --Alexandr Dmitri (talk) 12:40, 9 January 2013 (UTC)
- Ah, you are correct; fixed now. Ed ^{[talk] [majestic titan]} 12:47, 9 January 2013 (UTC)
In other news, Jimmy Wales apparently doesn't know the name of the new travel project. =) Powers ^T 21:21, 9 January 2013 (UTC)
I've given up on RfA reform. If you look at the very first version of the RfA page you will see that the process is basically unchanged from 2003, despite the squillions of words and hours devoted to its reform. Short of the Esperanza solution, RfA reform is not going to happen, so we really need to work with what we've got. --Surturz (talk) 23:19, 9 January 2013 (UTC)
Where is Ed Poor when you need him? Kaldari (talk) 20:10, 10 January 2013 (UTC)
Deleting RfA might not be the worst idea ever. ;-) Ed ^{[talk] [majestic titan]} 20:56, 10 January 2013 (UTC)
Neither MonmouthpediA nor GibraltarpediA usually are, or should be, seen as GLAM (Galleries, libraries archives and museums, remember) activities, though they expanded techniques developed in earlier GLAM activities, but applied them to everything in a particular location. "Wikitowns" is sometimes used for them. This should be rephrased. Johnbod (talk) 13:07, 12 January 2013 (UTC)
I wonder how this report failed to mention the June launch of IPv6, which was quite a news-maker.--Jasper Deng (talk) 03:51, 14 January 2013 (UTC)

Op-ed: Meta, where innovative ideas die (18,543 bytes · 💬)

Blame the watchlist and set up a Diaspora pod for Wikimedians, please

Thanks for the analysis which I think is mostly correct. I think the solution to the Meta dilemma lies in the fact that it's just another wiki. You need to visit Meta in order to learn what's going on there. There is no common watchlist for all Wikimedia projects. This is why most Wikipedians visiting the watchlist on their home wiki only do not realise proceedings on Meta. Also, you have to follow recent changes because new pages are constantly being created on Meta. So a watchlist doesn't really help you with that. Neither does sending out pointers to Meta on mailinglists because only a few Wikipedians have subscribed to them.

I think the solution nowadays lies in a combination of a social network and Meta. It is good to have a public working wiki for co-operating, but for communicating within a group outside your home wiki it would be best to set up a Diaspora pod for Wikimedians. Would be much better than using the commercial networks for that because we can do it ourselves.--Aschmidt (talk) 13:18, 9 January 2013 (UTC)

I'd be interested in a Wikimedian Diaspora pod. I stopped using Diaspora months ago because it was a dead end socially, but if we can get a critical mass of Wikimedians who want to try it out together, there's potential for making something useful. Social networking within the broad Wikimedia community is still an unmet need, which we do (poorly) to some extent through Facebook and such, but which suffers from the fuzzy boundaries between our identities as Wikimedians and our social lives outside the projects. Do I post this bit of insider baseball, even though most of my friends would have no idea what I'm talking about? In a dedicated Wikimedian social network, the answer would be yes.--ragesoss (talk) 15:29, 9 January 2013 (UTC)

Does anyone actually use Diaspora? Someone told me recently that even the authors of Diaspora don't use Diaspora anymore. Any project that is failing to eat their own dogfood seems doomed to utter failure. —Tom Morris (talk) 23:45, 9 January 2013 (UTC)

Which site are you talking about? Google turns up nothing about it. OhanaUnited^{Talk page} 04:29, 10 January 2013 (UTC)

Diaspora (software); https://www.joindiaspora.com --MZMcBride (talk) 07:27, 10 January 2013 (UTC)

In answer to Tom Morris, Diaspora's founders stopped developing it to do some more traditional start-up-y stuff. But they actually had gotten it to (in my opinion) a quite nice, usable place: a federated, open-source social network that duplicates most of the key features of Facebook (with an interface that's a little more like Google+). It never reached anywhere near critical mass in terms of active users (at least, within a few degrees of separation of people I'm interested in) but for a use case like this--connecting a well-defined community that is not already strongly networked on Facebook--I think it's got a lot of potential.--ragesoss (talk) 02:07, 11 January 2013 (UTC)

You say "mandarin" twice in three sentences. Just sayin'. — Francophonie&Androphilie^{(Je vous invite à me parler)} 19:23, 9 January 2013 (UTC)

Great piece, well done. And yes, a Wikimedia-wide unified watchlist would go a long way to fixing this and related problems. Given the money WMF has knocking about, it's sad they can't make this happen :(. Additionally or alternatively, a merge with Commons would also make sense - one big umbrella wiki for cross-wiki stuff, with different sections for different purposes. Rd232 ^talk 22:26, 9 January 2013 (UTC)

Although it won't yet offer cross-wiki support in its upcoming first release, Echo might eventually bring us closer to the long-awaited global watchlist (which, from what I hear, is not an easy technical problem at all). Regards, Tbayer (WMF) (talk) 23:24, 9 January 2013 (UTC)

A global watchlist would be wonderful. As for the Diaspora idea, please don't ask me to create an account on another social networking site. If you want to send me to yet another web site, it's just not going to happen, even if I have good intentions to participate. To a large extent that just moves the problem of not cecking Meta to another website. I have enough pages to check, and I'm sure I'm not the only Wikimedian who feels that way. LadyofShalott 22:19, 14 January 2013 (UTC)

Authorship

Who actually wrote this? I haven't had time to fully digest the piece, but it doesn't sound like Sj's writing to me. The page history is unfortunately useless.

These complaints have come up previously (cf. WP:IGNOREMETA). --MZMcBride (talk) 16:00, 9 January 2013 (UTC)

Collapsed resolved issue: appears to have been a misunderstanding.

~~I would assume that the words "By Jan eissfeldt" at the top of the article give you the authorship. --Guy Macon (talk) 16:38, 9 January 2013 (UTC)~~

Don't be a jackass. --MZMcBride (talk) 17:14, 9 January 2013 (UTC)

~~Meta Wiki: Where the admins are thin-skinned and cannot take a bit of good-natured ribbing. --Guy Macon (talk) 21:05, 9 January 2013 (UTC)~~

Guy: ha! mzm: good eye, corrected. I was sent a draft of this for comments (off wiki, pity). These aren't my opinions or views- I believe I was asked as a representative of an opposing school of thought; I suggested ways that some of the criticism might be worded more constructively. I also offered to coauthor a future series on meta and related issues which would cover related topics and highlight different large or longterm projects there. But this piece was not coauthored: I had no input into its thesis, reasoning, or title, and do not support them. I do recognize that they are not unique to ~~Jan~~ this essay, and need to be addressed, as others have expressed them before. (cf. Rd232's comments below and on Meta)

I think the work of the Meta community is essential and useful and considerate, and has become richer in the past year. And I think it has been a safe space for creative and unusual thought and essays, since its founding. I am sometimes surprised that others do not see it so. It has preserved some of the original wiki nature that we should all revisit regularly. Perhaps I should write a counterpoint op-ed and send it to Jan for comment :)

PS. Happy 2013 to all - I wrote this from my mobile phone... Thanks to any devs who have made the process a mite easier and apols for any typos. – SJ + 23:25, 9 January 2013 (UTC)

Apologies if I came off as rude. In hindsight, it was quite obviously a legitimate question (thank you for the correction, Sj!) and your reply to it didn't indicate sarcasm, so I thought you were rudely pointing me to the byline. I don't think Meta-Wiki admins have particularly thin skin and I always enjoy a good ribbing. :-) --MZMcBride (talk) 07:25, 10 January 2013 (UTC)

Yes, I'm truly sorry but think we established which mails caused the confusion on this point pre-christmas. I took on board your argumentative point made below, regards --Jan eissfeldt (talk) 08:35, 10 January 2013 (UTC)

Thanks for the essay and update. These are all topics worth addressing; as Meta becomes more actively used, they pend with more force. And this is a fine starting point for further discussion <ribs MZM and Jan, one with each elbow> – SJ + 16:52, 10 January 2013 (UTC)

"A (meta-)wiki community is somewhat dysfunctional; film at 11."

Given the existence of m:Help:Unified login (oh look, a link to Meta-Wiki!), I think some of these problems are overblown. I'm biased, of course, being an admin at Meta-Wiki, but I don't see a clear statement of a problem (which innovative ideas exactly are being stifled?) or a clear list of proposed solutions here, which I think is really unfortunate (the piece seems to end with the suggestion to keep using Meta-Wiki, after trying to establish that Meta-Wiki is horribly broken).

Is Meta-Wiki perfect? Absolutely not. But I don't quite see how it's stifling innovative ideas. The Wikimedia Foundation and the Wikimedia community have limited (finite) resources. The Wikimedia Foundation, for its part, has begun putting in place systems such as the m:Funds Dissemination Committee in an effort to better support worthwhile ideas that further Wikimedia's wmf:mission. I'm (still) surprised to see Sj's name attached to this piece when he's been an active member of the Board, overseeing a number of positive developments (including the m:Sister Projects Committee and the m:FDC) that run counter to many of the arguments made in this piece.

I've personally strongly advocated for the Wikimedia Foundation to use a public and global space (Meta-Wiki) for its work. I don't see how trying to frame that as a Bad Thing is reasonable, fair, or healthy. --MZMcBride (talk) 17:32, 9 January 2013 (UTC)

I might get your point wrong but I hardly feel represented fairly by your take of the piece. It states very clearly that Meta is indispensable ("the only place"), why it is indispensable ("need for multilingual communities to engage much more freely on a common website" etc.), why no other potential contender can provide the same services under review ("none of these channels provides anything like a space for cross-community dialogues"), and why more people should care: otherwise you may encounter one day a popular edit-counter is no longer working (the German Toolserver debate example). The Sister Projects Committee (which is linked) provides the list (here) you are looking for and the text sets out what the problem is, i.e. a meaningful feedback mechanism - the very committee - to deal with new project ideas that don't come along with a million dollar funding (Wikidata) or already established structures (Wikivoyage) is not yet operational.

Said that, you may have been distracted by the first paragraph, which sums up what "many people have argued" before the "the only place"-reply (especially combined with the fact that the piece was originally scheduled for the last edition and therefore the editor-in-chief uploaded it today). I was very keen (Sj wasn't) to deal with the ordinary "get rid of Meta"-tamtam early on to make room to actually look at the new tasks, and the strings and problems attached to them, of the project. I'm sorry, if that didn't work out that way in your case; its not a "horribly broken"-diagnosis but aims at purposefully making people wonder, regards --Jan eissfeldt (talk) 18:49, 9 January 2013 (UTC)

Thank you very much for clarifying. I believe I did misinterpret the piece and I'm concerned that others might as well. If the piece had actually said "Meta-Wiki is indispensable," I think that would have been clearer. :-) The headline of the piece ("Meta, where innovative ideas die") also seems to cast a much grimmer tone than the reply you've written here. --MZMcBride (talk) 20:05, 9 January 2013 (UTC)

I think we all know that Meta is utterly useless. No one uses it and yet, it attempts to make binding decisions for all the other projects. Luckily, they usually don't get passed, but when they do and attempt to become binding, the Wikipedia projects appropriately rebel. This is often because the group that is passing such things is a small group of Meta admins that think they should hold all the power. Silverseren^C 22:22, 9 January 2013 (UTC)
- I did last year propose a model whereby major global policy decisions have to be approved locally by a certain proportion of projects and a certain proportion of all users in order to be approved. Makes more sense than Meta in its current form, anyway. Rd232 ^talk 22:27, 9 January 2013 (UTC)

Thanks for the interesting overview (and from my own perspective as member of the WMF Communications team, for the shout-out for the blog and the Wikimedia Highlights). I'd like to add a few elements to the picture:

Regarding "the need for efficient translation support", I think the article could well have mentioned that Meta-wiki has been maturing a lot as a translation platform over the last two years, with the deployment of the Translate Extension in 2011, and the introduction of the related TranslationNotification extension in mid-2012. The translation interface is still a bit unappealing, but the WMF language team is making progress on this as well. - This doesn't yet solve the problem of true multilingual discussion, but it goes a long way towards informing non-English speaking Wikimedians better (obligatory ad: Please consider signing up for translation notifications if you want to help with that).
(To add to the examples - FDC, grants, etc - for the Foundation's use of Meta as a much more open platform that what a normal nonprofit might employ: ) We have moved our "communications calendar" of planned blog posts from the nonpublic Office wiki (Intranet) to Meta.
Likewise in mid-2012, we moved the drafting process for the blog largely out of our Wordpress installation into the open on Meta, to increase participation and transparency.
In 2011, the WMF Research Committee started the Research Hub in a new dedicated Research: namespace on Meta.
Regarding Meta's Not my wiki problem: As mentioned above, there is hope that Echo could eventually help to improve that; at least with respect to the difficulty of staying updated on relevant new developments there if one does not already visit the wiki frequently for other reasons (see also the Wikimania talk I gave with MZ about "movement broadcasting").

Regards, Tbayer (WMF) (talk) 23:24, 9 January 2013 (UTC)

Hi Tilman. Thank you for these details. It's good that Meta is already tackling some of these issues.

More active use by chapters and the wmf has helped, including public drafting of personal essays or proposals. Working on the blog there has filled a gap left since wikizine stopped drafting its issues. And minutes from any off-wiki event or meetings are posted there as well; though that is not new.

Yes, Echo will help; but its the cross-wiki messaging that is really needed. Also needed: a better-publicized central list of active meta-discussions, and better lightweight techniques for pushing announcements and updates [using the global sitebanner is too much. a similar banner that only pushes to every project's community portal/messageboard would be perfect]. – SJ + 16:31, 10 January 2013 (UTC)

(disclosure:I am the original author of WP:IGNOREMETA and am pretty much hated by the community on that site) I think the title sums it up nicely. There is of course some very important cross-wiki coordination that goes on there, but outside of that it is basically. dead end with a culture that does not seem interested in ever seeing anything through to a conclusion. I also found the system for requesting translation of proposals incomprehensible. When I asked for help understanding it I was insulted by an administrator for daring to ask for help. The steward areas of meta are vital and essential, but its broader community is in serious need of reform in its approach to outsiders, It is supposed to be there to help and serve the other WMF projects, but it rarely if ever accomplishes anything toward that end. Indeed I and many others have found it to be a very closed community that is openly hostile towards outsiders not well versed in its internal politics. I realize that same criticism has been leveled at en.wp and that we have experienced similar problems here, but the small size of the community and the blatant disregard for shocking misbehavior by their own admins there seems to me to intensify the problem. Beeblebrox (talk) 18:49, 10 January 2013 (UTC)

Technology report: Looking ahead to 2013 (9,252 bytes · 💬)

What exactly does "obsoleting almost all inter-language links" mean, please? Peridon (talk) 12:55, 9 January 2013 (UTC)
- I rephrased to "making almost all inter-language links in pages obsolete". 81.175.123.154 (talk) 12:58, 9 January 2013 (UTC)
  - Thanks. I've further tweaked the wording slightly. - Jarry1250 ^{[Deliberation needed]} 13:28, 9 January 2013 (UTC)
    - Still not certain what's going on. Does this mean the sidebar 'other language' links, or links in the text like fr:squidge or both or something else altogether? Does 'making obsolete' mean they're no longer needed, or that they no longer will work? Technology's your business - words are mine... Peridon (talk) 14:43, 9 January 2013 (UTC)
      - We will be able to get "other language" links in the sidebar from Wikidata. (e.g. one copy of the list of links for all the wikipedias, vs. hundreds now) The current interwiki language links (in the sidebar), coming from wikitext will still work but I expect bots to "migrate" them to wikidata and then remove them as they will then be "obsolete" or not needed. If some wants to override an interwiki link coming from Wikidata, that can still be done with regular wikitext on a Wikipedia page, and there is the ability also to suppress them with a magic word or parser function. (see mw:Extension:Wikibase Client#noexternallanglinks) --Aude (talk) 17:54, 9 January 2013 (UTC)
        So what will this mean for someone who on occasion adds interwiki links to articles here and places like the Breton, Marathi and Swedish Wikipedias (to name but three? I'm not sure about what you mean about 'not needed'. How can wikilinks not be needed? Peridon (talk) 19:32, 9 January 2013 (UTC)
        There will still be interwiki links. You can add them in Wikidata, and there will be a widget in Wikipedia for editing them without going to Wikidata. It just means if you add a interwiki link, say to Breton, then other wikipedias can also fetch the links from Wikidata. (vs. bots going around and adding them everywhere). --Aude (talk) 20:21, 9 January 2013 (UTC)
        
        It's the adding links in wikitext is what won't be needed. Add them in Wikidata or with the widget instead. --Aude (talk) 20:22, 9 January 2013 (UTC)
        So it's going to be easier than typing fr:squidge or en:thingy inside square brackets? Peridon (talk) 21:11, 9 January 2013 (UTC)
        Yes, and in a couple months, infoboxes may get a little bit easier too as we'll have a central location for basic facts like population that are probably the same on all Wikipedias. The links help to know which pages are connected and the pages will be able to use data from Wikidata. --Aude (talk) 23:01, 9 January 2013 (UTC)
        This will probably cause a problem for some mathematics pages which have ambiguous interwiki links. For example, see Talk:Aleph number#Interwikis. JRSpriggs (talk) 16:21, 10 January 2013 (UTC)
        If there is not a one-to-one relationship for particular interwiki links, then we can stick to the current system for particular pages. There also are some interwiki links that link to a subsection of another wiki's page, for example. Wikidata doesn't handle that scenario.Either add no connection to Wikidata (no sitelinks from Wikidata to X wikipedia) or use the magic word or parser function to switch the Wikidata stuff off for a page. --Aude (talk) 18:27, 10 January 2013 (UTC)
I don't think I understand what "questions about code duplication could well give existing {{#if:{{{image|{{{image_name|}}}|[[File:{{{image|{{{image_name|}}}|thumb|{{{image_size|250px}}}]]|}}-style code a reprise" means. Can someone clarify? --Waldir ^talk 16:41, 9 January 2013 (UTC)
- I think it means they're trying to get rid of things like that, but aren't too sure about success. The problem with experts explaining things is that they (usually) know what they're talking about, but outsiders don't speaka da lingo and end up more puzzled. Sorry, folks, it's a standard thing in many fields and compulsory in manuals... Peridon (talk) 17:23, 9 January 2013 (UTC)
  - On the meta point, the Technology Report has a varied audience of approximately 1000, including completely non-tech-savvy users, people who are IT but not programming literate, developers, system administrators, Wikipedia insiders with technical expertise, template experts, user script writers... I'm always open to suggestions on how to improve the offering -- this report was relatively rushed, so probably worse than usual -- but unfortunately it is the nature of the beast that some readers will not be able to understand some bits. I do my best to respond to comments, however, and am happy to explain further there :) - Jarry1250 ^{[Deliberation needed]} 18:02, 9 January 2013 (UTC)
- Peridon more or less has it. The project is to make blocks of code like the one provided - which are completely unintelligible to anyone but a template expert - a thing of the past, but questions about code duplication (i.e. the prevention of users having to copy and paste code between wikis) may prevent the project coming to fruition as early as previously hoped. - Jarry1250 ^{[Deliberation needed]} 18:02, 9 January 2013 (UTC)
  - And why would users be prevented from copy-pasting code between wikis? Is Lua going to be deployed only to a few wikis? --Waldir ^talk 20:27, 9 January 2013 (UTC)
    - Well, there are many problems with copied and pasted code, mostly related to the fact that updates to one don't find their way into the other. Thus we have wikis at the moment running versions of gadgets en.wp was running back in 2007. Allowing this to happen again with Lua is undesirable; rather, you want to have a strong system of centralisation (Wikimedia Commons-style) in place, so that changes propagate. - Jarry1250 ^{[Deliberation needed]} 23:18, 9 January 2013 (UTC)
      - Still, how does that bias things towards template-like code rather than Lua code (as the sentence seems to suggest)? Both are equally vulnerable to the unsync problem. --Waldir ^talk 01:06, 10 January 2013 (UTC)
        Oh, they're not, but this is a once in a decade opportunity to drastically increase the amount of template-code centralisation. Many will be prepared for Lua to be held up to ensure that that opportunity isn't missed. - Jarry1250 ^{[Deliberation needed]} 11:28, 10 January 2013 (UTC)
        Ok, I get it (and agree, btw). But I think the original passage should be rewritten, as I could hardly extract anything resembling what you explained in this thread. --Waldir ^talk 20:11, 10 January 2013 (UTC)
From where I stand, things look a lot less monolithic and a lot more vibrant, but I'm not quite sure how to convey it. I suspect that the data produced by our Git and Gerrit workflow, being a mixture of machine-readable data and high-level descriptions (in the form of commit messages and comments), could be used to programmatically generate summaries of ongoing development activity. We get a little bit for free by mirroring our code on GitHub. You can get a lot of useful information out of GitHub's dashboards (extensions, core). Let me know if you have other ideas on how to raise the visibility of smaller projects (or of development work generally). --Ori.livneh (talk) 09:56, 10 January 2013 (UTC)
- Yes. I tend to get a lot more on the smaller projects into my précises of the monthly reports. An annual roundup is bound to be a simplification by comparison. - Jarry1250 ^{[Deliberation needed]} 11:28, 10 January 2013 (UTC)

WikiProject report: Where Are They Now? Episode IV: A New Year (998 bytes · 💬)

I really enjoy these "where are they now"-type pieces; it's nice to know what projects are doing, and continue to do. Thanks for the update. I'd be curious to hear why WP:TREK is considered more "prosperous" than WARS. Der Wohltemperierte Fuchs^(talk) 16:44, 9 January 2013 (UTC)

Just in case anyone wants to see the older "Where are they now" articles, here are links to them: one, two, three. Double sharp (talk) 04:03, 13 January 2013 (UTC)