<div dir="ltr">One issue: Many of us have our hand-rolled "libraries" (that is, scripts with often-used functions) shared between tools. If I understand correctly, each tool will live in its own space, separate of all other tools. I would not be a problem to just give every tool a copy of the library, but I can see code diverging over time between copies. Will there be a way to share code between tools, or should we use git for that?<div>
<br></div><div style>Cheers,</div><div style>Magnus</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 5:52 PM, Marc A. Pelletier <span dir="ltr"><<a href="mailto:marc@uberbox.org" target="_blank">marc@uberbox.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><futurama>Good news, everyone!</futurama><br>
<br>
As many of you know, I officially started my duties today as the WMF Operations Engineer attached to the Tool Labs. I intend to make a point of informing all of you of recent news, what I'm working on, and where I'm headed at regular intervals (probably weekly).<br>
<br>
First, a bit of news: I have had confirmation this weekend that the DB replication made available to Tool Labs users will, in fact, allow the creation of databases alongside the project ones. This means that one of the use cases that seemed the most troublesome in the transition (joins between the WMF databases and tool-specific ones) will be fully supported.<br>
<br>
We are making good strides in documenting the *impressive* inventory of tools that run on toolserver and their requirements (thanks, Silke!). The list-in-progress can be found at [1]. If you see missing or incorrect information, please feel free to adjust it -- the more precisely we know the requirements, the faster we can see about meeting them.<br>
<br>
I've started documenting my preleminary design for the shiny new Tool Labs infrastructure at [2]. This is a living document, and will see a great deal of revision before it's over (and will serve as the seed for the documentation). I will shortly create a new Labs project where that architecture is deployed in preproduction so we can shake out the kinks. The existing projects, "bots" and "webtools" will be left active for the forseeable future until (a) the new architecture has proven itself and (b) every user has sucessfuly moved their tools to it.<br>
<br>
I'm planning on having the new project be fully operational for new tools by the time the Amsterdam Hackathon takes place at the end of May at the very least.<br>
<br>
For the next week, I'll be mostly in information-gathering mode, as well as refining the design and requirements of the Tool Labs. Feel free to poke me for information (or /with/ information) by email or on IRC (where I am user 'Coren' and idle on #wikimedia-labs and #wikimedia-toolserve at the very least)<br>
<br>
-- Marc A. Pelletier<br>
<br>
[1] <a href="http://www.mediawiki.org/wiki/Toolserver/List_of_Tools" target="_blank">http://www.mediawiki.org/wiki/<u></u>Toolserver/List_of_Tools</a><br>
[2] <a href="http://www.mediawiki.org/wiki/Wikimedia_Labs/Tool_Labs/Design" target="_blank">http://www.mediawiki.org/wiki/<u></u>Wikimedia_Labs/Tool_Labs/<u></u>Design</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Labs-l mailing list<br>
<a href="mailto:Labs-l@lists.wikimedia.org" target="_blank">Labs-l@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/labs-l" target="_blank">https://lists.wikimedia.org/<u></u>mailman/listinfo/labs-l</a><br>
</blockquote></div><br></div>