Hey folks :)
Wikimedia Germany has been working with a team of students over the
past months. They have among other things developed a pubsubhubbub
extension. The idea is that we allow 3rd parties to easily subscribe
to changes made on Wikidata or any other wiki. Wikidata's changes get
send to a hub which then notifies all subscribers who are interested
in the change.
We'd like to get this extension deployed for Wikidata and possibly
later other Wikimedia projects. For this they need some more eyes to
review them. RobLa suggested I send an email to wikitech-l about it.
The review bugs for this are
https://bugzilla.wikimedia.org/show_bug.cgi?id=67117 and
https://bugzilla.wikimedia.org/show_bug.cgi?id=67118
Thanks for your help getting this ready for deployment.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi folks,
We're hosting a conversation about standardization and continued
development of front-end libraries in MW core on 6/25, 5:30 PM UTC,
#wikimedia-office.
This is driven by a recognized need for teams at WMF to work more
effectively on user-facing features and reduce duplication of efforts
and inconsistencies across extensions. We're willing to take a bit of
a hit on the short term velocity of feature development to build a
more robust, consistent and developer-friendly platform.
Timo Tijhof, Trevor Parscal and Roan Kattouw have proposed a
systematic effort to improve MW core's front-end libraries, building
on existing efforts (see
https://www.mediawiki.org/wiki/UX_standardization for a messy but
reasonably comprehensive overview of some of the inconsistencies and
wheel duplication we need to solve).
This will be done in partnership with other interested front-end
engineers across the org and the community.
We'll try to come up with a clear scope of work, such as:
- having Mobile and VisualEditor depend on the same front-end
libraries in MW core and use them effectively
- eliminating dependencies on jQuery UI from all WMF-deployed code, to
be replaced with a MediaWiki-native look and feel
- creating a proper living style guide and UX standardization pipeline
in partnership with the WMF UX team.
This conversation is just a first step to ensure this effort has
visibility from the start, and major architectural changes will go
through the usual public conversations.
Thanks,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Hello!
O think that is the right for you:
https://m.mediawiki.org/wiki/Manual:ImportImages.php
Simply upload the images via FTP for example to the server and run the script like explainend on Manual page.
Kind regards
Florian
Gesendet mit meinem HTC
----- Reply message -----
Von: "Yury Katkov" <katkov.juriy(a)gmail.com>
An: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org>
Betreff: [Wikitech-l] tool for quickly uploading 10000 images with description
Datum: Mo., Juli 7, 2014 16:36
Hi everyone!
Does anyone knows about the tool that can help to upload a lot of files and
create the page for every file with a given description? I'd say that it
should be a maintenance script since for some reason the API upload works
pretty slow. I saw UploadLocal Extension but it's too manual and it doesn't
work well when the amount of files to upload is very large.
Cheers,
-----
Yury Katkov
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello,
MediaWiki has JavaScript code conventions which is enforced on core and
some extensions by running jshint in Jenkins:
http://www.mediawiki.org/wiki/CC/JS
Unfortunately lot of extensions do not match that expectation yet and it
would be rather nice to bring them on par.
We have a tracking bug listing some repositories which are not passing
jshint yet:
https://bugzilla.wikimedia.org/show_bug.cgi?id=60619
It would be rather nice to have all extensions fixed :-]
--
Antoine "hashar" Musso
Hi, in my settings for the Wikimedia email lists I have activated the
option to receive copies of emails that I send to the lists. I received
these emails in the past but no longer receive them. I checked my settings
and the lists still say that I should receive copies of emails that I send
to the lists. Does anyone have ideas about how to fix this?
Thanks,
Pine
Until two days ago, I was able to modify the background color of a Wikipedia
page with a style sheet containing the following:
body {
background-color: rgb(68, 68, 68) !important;
color: rgb(204, 204, 204) !important;
}
The line for color still works, but the line for background-color does not.
Does anyone know what changed and what I have to do now to change the
background color?
If this is not the right mailing list for this question, could someone
direct me to the right one?
Thanks.
---
Jeffrey Barish
Hi folks,
The Wikidata dev team has been working on simple query functionality
for Wikibase over the past months. It's now in a state where we would
like to get it reviewed and deployed. RobLa suggested I email
wikitech-l to get some more eyes on it. Once deployed users will be
able to search for single property-value pairs and get a list of
results - via the API and a special page. Example: Give me all items
that have a statement "producer: J.J. Abrams".
The bug reports for performance and security review are at:
* https://bugzilla.wikimedia.org/show_bug.cgi?id=67533
* https://bugzilla.wikimedia.org/show_bug.cgi?id=67534
* https://bugzilla.wikimedia.org/show_bug.cgi?id=67535
* https://bugzilla.wikimedia.org/show_bug.cgi?id=67536
Thanks for your help getting this ready for deployment.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
== The problem ==
MediaWiki has a huge UI standardisation problem. We use different
libraries, different css styles and class names, some of which do the
same thing.
Recently the teams working on Flow and MobileFrontend noticed they
were doing various things in a similar fashion. We were both using
client side templates, we had various bits of JavaScript that were
similar, and many styles that we could potentially be sharing.
== The motivation ==
The Flow team has recently decided to use Handlebars [1] templating
language and the mobile team has been heavily using Hogan [2]
templating language for over a year now. Both of us are actively
involved in the templating RFC [3] however neither of us want to be
blocked by that RFC. Despite these different templating language
choices and the knowledge that we will one day need to standardise on
just one templating language, we both had a need to pass templates
from the server to the client via ResourceLoader. Mobile has been
doing this for a year, and rather than another big project like Flow
reinventing the wheel, we decided it was time to share code.
We attempted to put the code straight into core, but Krinkle quite
rightly pointed out that a templating RL language solution without a
templating language packaged with it would be confusing and not useful
to the majority of developers outside the Flow/mobile bubble. So
instead, Mantle [4] was born.
== Mantle ==
The purpose of Mantle is to wrap additional infrastructure code that
core is missing, and iterate on that code quickly to get it to a state
where it is as generic as possible.
As a result of Flow and mobile's collaboration the template code from
mobile supports multiple languages which is great for 3rd party users
who might want to write code using a different template language) and
it now has eyes from both the mobile and Flow teams on it, so it
should become stronger now it has 2 use cases. We're hoping to add
support for Knockoff which Gabriel has been working on in the near
future to experiment with that.
We are waiting on a standard template language before upstreaming this
code to core and going through another round of review amongst our
developer peers.
Currently Flow depends on Mantle, and there is a patch in gerrit to
move MobileFrontend to using it [5]
== The future ==
Mantle is only a short term measure. The hope is that all the code
that goes here will eventually go into core. We hold the code here to
exactly the same high standards that we hold core to, we are just able
to more freely experiment and iterate. I hope Mantle doesn't exist in
a year and instead we have a healthy frontend architecture that Mantle
has helped grow.
In the meantime however mobile and Flow will use it to at least
standardise on a few things between our codebases with the goal to
make Flow as mobile friendly as possible. We don't want to ship two
bits of code, one from MobileFrontend and one from Flow, to a mobile
Flow page that do exactly the same thing.
I also hope overtime it could be used to share other aspects of
missing frontend code architecture across extensions. For example, it
could potentially be used to rapidly develop new components for
MediaWiki UI [6] that are not quite stable enough to be placed in
core and made available to all.
If you're interested in sharing and collaborating on frontend code
with Flow and mobile feel, or client side templates in general free to
grab me off list and on irc (@jdlrobson). We don't do enough of this
:-)
Jon
[1] http://handlebarsjs.com/
[2] http://twitter.github.io/hogan.js/
[3] https://www.mediawiki.org/wiki/Requests_for_comment/HTML_templating_library
[4] https://www.mediawiki.org/wiki/Extension:Mantle
[5] https://gerrit.wikimedia.org/r/129335
[6] https://git.wikimedia.org/tree/mediawiki%2Fcore.git/49f86a90520e6618c1e3044…