Hi.
Do we have plans for the Toolserver wiki (<https://wiki.toolserver.org/>)?
There's some very good content in/on the wiki that would be nice to move
to either wikitech.wikimedia.org or mediawiki.org, I think.
Has this been discussed anywhere? Does anyone have any thoughts about this?
MZMcBride
Hi all!
When it comes to the question of migrating tools to Tool Labs, some of you
might notice that you don't have the amount of time needed for maintenance
that you had earlier. WMDE offered to help you with the actual migration
but we can't maintain abandoned tools in the long run. For migration
support, contact me!
Note that in Tool Labs *every* tool is a multi-maintainer project! This
shall make it easier for you to bring others in. On the toolserver you can
add a ticket in Jira to request for your project to become an MMP, so
others can join you before migration and help with it.
Best, Silke
--
Silke Meyer
Internes IT-Management und Projektmanagement Toolserver
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
I'm about to head off for three months for a sabbatical, so I wanted to
let you know of a few more underappreciated resources.
https://lists.wikimedia.org/mailman/listinfo/wikitech-announce is a very
low-traffic list with announcements of office hours, meetups, bug days,
and so on. And https://meta.wikimedia.org/wiki/Tech/News is a weekly
summary of changes in the world of Wikimedia tech.
http://vmartinezdelacruz.com/in-a-nutshell-how-openstack-works/ is an
introduction to how OpenStack works. Wikimedia Labs is built in
OpenStack; this will help you if you've ever wondered "WTF is Nova?"
And there's a sample Python application
http://tools.wmflabs.org/flask-stub/ "for those who want some yeast to
start their own project." More information:
https://wikitech.wikimedia.org/wiki/Flask-stub Thanks, User:Little green
rosetta.
I'm unsubscribing from the toolserver-l list and labs-l for my
sabbatical now -- more info at
http://www.harihareswara.net/sumana/2013/08/28/1 . If you need to talk
about Wikimedia technical community stuff before January, please consult
Quim Gil, qgil at wikimedia dot org. Silke and Coren will be able to
answer your questions and keep momentum going on Tool Labs, as they
already are already. :-) Thanks! Looking forward to coming back in January.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Erwin85 is looking for people to maintain his very popular tools [1] (as he
wrote on [2]). They are currently running on the toolserver. If you are
looking for a project to help with, please have a look at the tools.
If you are interested in helping to maintain one or a few of them, here are
your next steps:
* Contact Erwin85. ;)
* Ask in Jira [3] to have the tool you want to work on transformed into a
multi-maintainer project and have yourself added to it.
* Migrate them to Tool Labs. (WMDE can help here, if you want. Contact me!)
* Take over responsibility for long term maintenance of one or several of
the tools.
Cheers, Silke
[1] https://toolserver.org/~erwin85/
[2] https://meta.wikimedia.org/wiki/User_talk:Erwin#Tool_Labs
[3] https://jira.toolserver.org
--
Silke Meyer
Internes IT-Management und Projektmanagement Toolserver
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/Help
If you know anyone who's been confused by Labs documentation in the
past, the revamped Tool Labs guide is pretty helpful. Thanks to Ryan
Kaldari for recently adding instructions for configuring MySQLWorkbench
(an alternative to phpMyAdmin).
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello DaB!
Could you please give me a short update - the end of 2013 is
approaching, what is the current state for TS resp. Labs?
Thanks and Greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIGCboACgkQAXWvBxzBrDAKPwCgjsEcGfRtbKaw/eDwTxNhUFfo
XgwAoLzV6J+TCdJZ3lvwvkqsMWihQmr+
=1dN+
-----END PGP SIGNATURE-----
On Wed, Sep 11, 2013 at 9:50 PM, Leslie Carr <lcarr(a)wikimedia.org> wrote:
>
>
>
>
> On Wed, Sep 11, 2013 at 1:19 AM, Federico Leva (Nemo) <nemowiki(a)gmail.com>wrote:
>
>> Just spotted this (
>> http://lists.wikimedia.org/pipermail/toolserver-l/2013-August/006260.html):
>>
>> ----
>>
>> > > I'm more than happy to recommend a number of cloud services and am
>> > > more than willing to give advice on how to configure and run tools
>> > > and bots from those services. It's even possible to reuse the work
>> > > we're doing in the tools project, or in the Wikimedia infrastructure
>> > > via our puppet repository since our infrastructure is Open Source.
>> >
>> > Very nice idea – how I get the mysql-replication-stream? I got several
>> > offers of donation if the Toolserver would continue; the only problem is
>> > the replication-data. But because the data is open-source, it shouldn’t
>> > be a problem than, should it?
>> >
>> >
>>
>> Assuming you found a non-profit, host your infrastructure somewhere that
>> doesn't cause legal issues and every person that has access to the data
>> stream signs an NDA it's likely doable.
>>
>> ----
>>
>> Can WMF please confirm that this is the case and it wasn't a boutade? If
>> yes, could you indicate a single point of contact interested parties can
>> negotiate such an arrangement with?
>> (See also the first unanswered question by Sj at <
>> https://meta.wikimedia.org/wiki/Talk:Future_of_Toolserver#September_2012
>> >.)
>>
>> Generically, legal(a)wikimedia.org would be the point of contact for
> anything like that.
>
>
I think there is some historical context here I'm missing, so I'm looking
into it, but can't promise an answer particularly quickly.
Luis
--
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810
NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
Hello all,
next
FRIDAY, 13. September 19:00-22:00 UTC
I will update our Linux-hosts with all non-critical updates that
happened since the last maintenance-window. This will include the
userland-hosts and the database-servers. Several downtimes may occur
during that window.
After the update I will prepare the upgrade from Debian Squeeeze
(oldstable) to Debian Wheezy (stable). The upgrade will surely break
some stuff, because several important packages will switch to a new
major release (for example perl from 5.10 to 5.14, php from 5.3 to 5.4).
I will send a further mail after Friday with details. The upgrade is
planed to happen 1 or 2 weeks later.
Sincerely,
DaB.
Hi all!
Today WMFs bug wrangler Andre Klapper visited our office and gave a Q&A
session about Bugzilla. Together with Daniel Kinzler, we discussed the
question if it's possible to migrate your tickets from Jira to Bugzilla.
(For all tools, that would be about 1100 open tickets at the moment, open,
reopened, in progress.)
The last status of the discussion (according to [1]):
* Tool maintainers can request their own bugzilla "component".
* There doesn't seem to be a tool to migrate, so someone would have to
write and test it.
* Does it make sense to migrate tickets related to the toolserver
environment, not to the tool itself? (Tim: Yes, because of the historical
value)
Andre gave me these hints for an investigation:
(Don't laugh, maybe you know all this already.)
* Jira has a REST API, Bugzilla doesn't.
* Bugzilla has a json rpc (example:
https://bugzilla.wikimedia.org/jsonrpc.cgi?method=Bugzilla.extensions)
* It's not likely that all fields can be transferred, it might be a good
idea to concentrate on the tool name and the status.
* To import tickets, Andre would take a list of all users that want their
tickets in Bugzilla but don't have an account. He could then create the
list of account IDs that the tickets are associated with.
Existing similar things the could help to find out more are below.
Now, I would like to know if there is anyone among you who would like to
investigate this further or has experience reports to pass along.
Best, Silke
Links:
[1]
https://www.mediawiki.org/wiki/Wikimedia_Labs/Toolserver_features_needed_in…
Migrating report (2011):
http://www.bdunagan.com/2011/11/07/migrating-jira-to-bugzilla/
Pywikipediabot (Sourceforge -> Bugzilla)
https://www.mediawiki.org/wiki/Manual:Pywikipediabot/Migrating_to_bugzilla
Mingle -> Bugzilla: https://github.com/awjrichards/bingle
--
Silke Meyer
Internes IT-Management und Projektmanagement Toolserver
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.