New subject: Please read: Fixing Incubator

27 Jul 2018


      OWTB makes some good points.
*   There needs to be a consultation with the Incubator admins, and then there needs to be at least one general community discussion. Concerning Incubator admins, three are here (MF-Warburg, Robin and me). Three others are at least reasonably active on Incubator (including OWTB, who is very active), another is responsive to specific requests, and two others haven't made an edit or had a logged event in over a year. Do we want that consultation to be on-wiki (public)? Or should we invite any/all of them to have temporary rights to this list, and discuss it semi-privately here first.
  *   I don't know if the community discussion should be on Incubator (and advertised at Meta [and Beta]), on Meta (and advertised on Incubator [and Beta]), or if there should be two. And when do we start it? Thoughts?
As far as substantive issues go, there are really two separate issues (or constituencies) that partially overlap that are being conflated here.
*   I am strongly in favor of moving the strongest, most active test projects into incubation subdomains. I think that's a great idea. Giving those projects more complete functionality, especially access to WD, and getting rid of Incubator peculiarities like prefixes, is all certainly worthwhile for them. None of the downsides I'm going to point out below really apply to them. So if we can manage an admin interface that continues to let us help them manage spam, bots, etc., and if there are no more than about 20 of them, I think this would be fantastic.
The other issue (which OWTB doesn't mention) is the creation of brand new test projects. The idea is to make it easier for new test wikis, to give them all of the associated functionality that full projects have, and that without all of Incubator's peculiarities. And in principle, that's a great idea. Still, I think there are also a lot of potential problems with this.
*   How do we decide what constitutes a serious enough request to press the button? For "subsequent projects in existing languages", it would be easy enough to require some activity history in the existing wiki(s). But for new languages, how do you do that? Yes, deciding the language is "eligible" is a necessary condition. But sufficient?
     *   Even now, there continue to be LTA's coming and creating new requests that are effectively spurious. They're valid on their face—language is eligible—but requesters don't speak the language, and no community exists. (It happens less now that I am patrolling there, but it still happens.) For now, at minimum we wait until there are people around who create some content before saying, "eligible". That at least demonstrates that a couple of people are present and actually creating content that appears to be in the right language.
     *   I am extremely worried that this will turn into the "bad old days", where just about anyone could create a project, and many fell into disuse (and/or were never serious). Do we want "The Wild West" again?
     *   Yet the idea of making things easier for outright newbies is a very worthwhile one.
I think many of these things have to be discussed, by us and by the Incubator admins, and then by the community, before pulling the trigger for anything except moving the largest, most active wikis. (Even that should also be discussed, of course, but that is likely to be more straightforward.)
In the meanwhile, I think there are three things that we can do right now to see if we can alleviate some of the current editing issues on Incubator right now:
1.  Turn on the "Add Prefix" gadget by default. It doesn't make all the prefix-related problems go away, but it simplifies them quite a lot. Just about everyone except sysops (and similar people who do a lot of maintenance) ought to have this on. [I can open a discussion on Incubator about this today, and trigger it in seven days unless there are objections.]
  2.  Use the authority of LangCom to set a priority to get some kind of access to Wikidata turned on right away. I think a lot of what is holding that up is the challenge of multiple iw links from Incubator. So let's simply not allow/demand/require that for now. Most of the capability currently exists somewhere within the WMF world to allow Incubator's pages (a) to call information from Wikidata into things like infoboxes, and even (b) to produce an iw list to appear on our pages. Much of that capability includes the possibility of calling information from Qxxx even when the page you're editing is associated with Qyyy; all you have to do is add "|q=xxx" as a parameter. So we simply require such a parameter. Access to WD would help a lot.
  3.  Less important, but useful: Finish fixing some of the problems with Incubator extension (like the default info pages and especially their links to Wikipedia projects).
We can see how much some of these things help while we start practicing on the less controversial, bigger test projects. And then we can decide where to go.
Steven
Sent from Outlookhttp://aka.ms/weboutlook

Re: [Langcom] Please read: Fixing Incubator