Yes. There's a plan to do so. We'd merge wikitech into labsconsole, but we'll likely rename labsconsole to wikitech (and of course add a redirect, so that old links continue to work). We'll also have a wikitech-static mirror, which similar to wikitech now, will be offsite and can be used for reference if the cluster is down. We need to identify which documentation should and should not be migrated over when it occurs, as there is a lot of documentation that is old/inaccurate and should be deleted. We'd love to have some community support for this, if anyone wants to help out.

I'd be happy to help, however wikitech is restricted wiki, so I guess I can't really help there, anyway I think it would be best if current wikitech was kept for historical purposes, and in case we forgot to move something you could find it in, wikitech-historical.wikimedia.org or similar url

Ok, if there is any stuff that can be done on wikitech like categorization of pages etc I could help with that, but otherwise I have no idea how I could be useful on that wiki, I have barely any knowledge of production. What exactly did you mean by community support

Rob Moen has been working on a simple JS tool that facilitates the tagging process. Basically, instead of manually tagging the pages with a different template for each action (archive, delete, keep), there's a simple box that shows up at the top of the page, and you can tag the page with a few clicks. The goal of this tool is to allow people with expertise and/or authority to quickly tag the content. Once the content has been tagged, other people can deal with the actual move. So far the possible actions are: * archive * delete * keep and (optionally) expand and/or update The actions use radio buttons, and the options checkboxes. This list is just a start; if you see other or better qualifiers, we can change them. Do you think this would be useful, or do you prefer to stick to manual templating/categorizing?

Also, the gadgets extension isn't currently installed on wikitech.wm.o. I'm not sure it's worth going through the trouble of installing it (would it even be compatible with the 1.17 MediaWiki that's running it?). Perhaps it would be simpler to just add the code snippet to [[MediaWiki:Vector.js]] for the duration of the cleanup?

I'm not sure if it makes sense to have the Labs/OpenStack/Nova management interface on this same "new wikitech" wiki though. This means that all the community projects running inside labs will/might use this same wiki to document their internal structure - which can (and should be) a lot of projects that are not Wikimedia engineering projects. Documentation for labs as being a Wikimedia project makes sense, but the actual projects inside and management maybe don't fit well inside the new wikitech. I like that of the labsconsole.

On Jun 7, 2012, at 10:49 AM, Ryan Lane wrote: No, that's not what I meant. Contributions (from whomever) to for example the production cluster puppets (through gerrit), that may have an RFC on wikitechwiki ahead of time sounds awesome. Stuff can be proposed by whomever, and then implemented by whomever. Then tested in labs and merged/pushed to production. I was refering to projects that will not be foundation engineering projects, or at least do not intend to be that. *cut 2 paragraphs* ...when trying to come up with examples, it turns out that those examples   (Tool-Labs: early extension development, bot hosting, slow-query tools, ..) probably wouldn't put their documentation on either wikitech or labsconsole, so nevermind. -- Krinkle _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

There is a difference between wikimedia projects which are somehow related to wikimedia projects, and foundation projects which are funded by foundation. But this difference is only about people and money, so why should we have a different wiki for that On Thu, Jun 7, 2012 at 5:19 PM, Petr Bena <benapetr(a)gmail.com> wrote: > I don't understand why? Wikitech is a perfect place for bots > documentation as well, especially when it comes to large bots operated > by many people, these needs to have documentation so that they can be > overtaken by someone else in case the original person who launched > bot, doesn't have a time to maintain it. > > Why should it be for foundation only projects? > > On Thu, Jun 7, 2012 at 5:08 PM, Krinkle <krinklemail(a)gmail.com> wrote: >> On Jun 7, 2012, at 10:49 AM, Ryan Lane wrote: >> >>>> I'm not sure if it makes sense to have the Labs/OpenStack/Nova management >>>> interface on this same "new wikitech" wiki though. This means that all the >>>> community projects running inside labs will/might use this same wiki to document >>>> their internal structure - which can (and should be) a lot of projects that are >>>> not Wikimedia engineering projects. >>>> >>>> Documentation for labs as being a Wikimedia project makes sense, but the actual >>>> projects inside and management maybe don't fit well inside the new wikitech. I >>>> like that of the labsconsole. >>>> >>> >>> Do you mean they aren't *staff* engineering projects? Labs is meant to >>> be a stepping stone. For most projects, the idea is that people will >>> implement something in Labs and it'll get moved into production. The >>> documentation for that project will then be the documentation for Labs >>> and production. >>> >>> One of the biggest reasons I wanted to merge the wikis is because I >>> feel that volunteer operations engineers should be documenting their >>> infrastructure changes in the same place as staff operations >>> engineers. >>> >>> - Ryan >> >> No, that's not what I meant. >> >> Contributions (from whomever) to for example the production cluster puppets (through gerrit), that may have an RFC on wikitechwiki ahead of time sounds awesome. Stuff can be proposed by whomever, and then implemented by whomever. Then tested in labs and merged/pushed to production. >> >> I was refering to projects that will not be foundation engineering projects, or at least do not intend to be that. >> >> *cut 2 paragraphs* >> >> ...when trying to come up with examples, it turns out that those examples   (Tool-Labs: early extension development, bot hosting, slow-query tools, ..) probably wouldn't put their documentation on either wikitech or labsconsole, so nevermind. >> >> -- Krinkle >> >> >> _______________________________________________ >> Wikitech-l mailing list >> Wikitech-l(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

I agree with Petr, I see no reason to put them on different wikis. Namespaces are cheap.

From his post: "... but that would address many of the reasons that people

I don't think we need namespaces. I definitely don't think we need multiple wikis, though. The best part about a wiki is that if we figure out we did it wrong, we can change it. - Ryan _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l