-----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-----
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.
Hi,
The cronie line at krinkle(a)submit.toolserver.org for KrinkleBot[1]:
3,18,33,48 * * * * python $HOME/externals/pywikipedia/fileprotectionsync_live.py > $HOME/bots/py_fileprotectionsync_live.log 2>&1
.. has not run for over 27 hours.
I just ran it manually once[1], which made 4 edits.
Are there known problems with it?
-- Krinkle
[1] https://commons.wikimedia.org/wiki/Special:Contributions/KrinkleBot
Hi again,
to take up a topic that was touched on at Wikimania and now discussed on
labs-l: Is it allowed to migrate tools that use Google Maps?
tl;dr: Hard to tell right now. Please provide examples! Ask about your
tools, give details!
Here is why:
Marc-Andre Pelletier and Luis Villa explained the following: The tool would
have to respect both the Labs Terms of Use and the Google Maps Terms of
Use. This can mean users have to read and acknowledge a disclaimer before a
tool can point to Google Maps.
Without concrete examples this is hard to analyse. How exactly would this
be used? If you want your tool to be looked at as an example please come to
labs-l and present it.
Kolossos also strongly recommended to look at open source tools like
OpenLayers or Leaflet as alternatives to Google Maps. Most things can be
solved with open stuff nowadays.
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.
Dear tool maintainers!
This is about the Terms of Use in Wikimedia Labs [1] and the projects that
are invited to live in Labs/Tool Labs. If your tools are not explicitly
related to Wikipedia-Wikimedia-Mediawiki projects, please answer this
e-mail.
The upcoming new version of the Terms of Use will add Openstreetmap to the
(obvious) Wikipedia-Wikimedia-Mediawiki projects. I was asked if there are
other free projects supported by your tools. I need your help to answer
this question!
If the Terms of Use tend to exclude your project because of the limitation
to specific free projects, please let me know what your tool does.
Thanks and cheers,
Silke
[1] https://wikitech.wikimedia.org/wiki/Wikitech:Labs_Terms_of_use
<https://wikitech.wikimedia.org/wiki/Wikitech:Labs_Terms_of_use>
--
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.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all!
Pywikibot finished GIT migration. Now a question has anybody ever
tryed to clone and use the e.g. the pywikibot/compat repo on the TS?
If I do, I get and .git folder of about 200MB which nearly fills my
home quota. (this is the plain clone - nothing done to/with it yet!!)
Yes I could do 'git gc' I could also switch to using SVN from github
(but needs to handle all externals manually)...
So... what was acutally the reason for switching to GIT? Despite the
fact that I have to enter about 1 million different commands now (in
SVN I needed 5 ... maybe 10 - 1 command per action, in GIT I need
about 5-10 command PER action) I am dealing 75% of my time with GIT
issues (that SVN did not have)...
In fact I am not able to to USE or further develop the GIT repo since
the migration - and I am SERIOUSLY thinking about setting up an own
copy on sf.net again and work there... (then we would also have the
bug-tracker back in the same place) At the moment I see just 2 drawbacks:
1.) not hosted by mediawiki (really a drawback?)
2.) no review (this is the one and only advantage of git till now, and
in fact it's git-review which causes issues too)
The list of advantages on the other side, is that long that I will not
even start making one, think of it yourself and please give me some
feedback!
At least I do not see if there will ever be a point in time when GIT
will start to work as well as SVN did in the past. I do also not see
why I have to enter 5 commands just to make a simple commit. And that
will never change...
Thanks for your thoughts and Greetings
DrTrigon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIGBzQACgkQAXWvBxzBrDC40gCeNt8b7KoBLV9BDNDojjM01Upp
ZsEAoIQIJ7W1FGMNysOE7LIp4qi25pyW
=mvrX
-----END PGP SIGNATURE-----
Thanks, I listed into labs-l and I logged into #wikimedia-labs , I hope I
will get help.... presently I found blocking issues bot in compat and in
core, I'll ask there.
Everyway, I keep my Toolserver account alive :-)
Alex
2013/8/11 Silke Meyer <silke.meyer(a)wikimedia.de>
> Hi Alex,
>
> cool that you are having a go for Tool Labs. I really recommend the
> #wikimedia-labs channel. People help each other a lot. I consider it
> newby-friendly. Also on labs-l, I asked a lot of things myself and always
> got helpful replies.
>
> Cheers, Silke
>
>
>
Hello all,
the WMF had some problems with one for their servers (db45).
Unfortunately that’s the server we replicate s5 and wikidata of. Nosy
fixed s5 already, but for wikidata it looks not that good – AFAIS a
re-import is needed.
For that reason I will stop the s5-replication
WEDNESDAY, 20:00 UTC
to create a dump and use Thursday to import wikidata everywhere again.
You can follow the process at [1].
Sincerely,
DaB.
[1] https://jira.toolserver.org/browse/MNT-1336
Hi,
I would like to use the script xmlreader.py of Pywikipedia, but I have not all the informations to use it correctly. Maybe you could help me because it seems this script is used on the Toolserver.
I suppose this script is the equivalent with XML of replace.py without replace but just using the search option. Does anyone know what the parameter to define the text to search on the XML dump files? If there an other important parameter except this and the parameter 'filename' (example: the 'regex' parameter of replace.py could be maybe used here to search with a regexp)?
If I'm wrong on my explanations, please tell me.
Thanks by advance,