Friends,
I'm helping review a tool <https://www.mediawiki.org/wiki/Extension:Ids>
that I understand Wikimedia Taiwan is eager to use, which uses a parser
hook to render ideographic description characters
<https://en.wikipedia.org/wiki/Ideographic_Description_Characters_(Unicode_b…>
into PNG glyphs in order to display historic or rare characters which
aren't covered by Unicode. It's very cool.
The challenges are first that it's based on a Tomcat backend
<https://github.com/Wikimedia-TW/han3_ji7_tsoo1_kian3_WM/blob/master/src/ids…>,
which I'm not sure is precedented in our current ecosystem, and second that
the code uses Chinese variable and function names, which should
unfortunately be Anglicized by convention, AIUI. Finally, there might be
security issues around the rendered text itself, if it were misused to mask
content.
I'm mostly asking this list for help with the question of using Tomcat in
production.
Thanks,
Adam
Hello everybody,
The Technical Collaboration team is very happy to introduce you to Srishti
Sethi <https://meta.wikimedia.org/wiki/User:SSethi_(WMF)>, our new
Developer Advocate. Srishti will lead our efforts to engage volunteer
developers in Wikimedia software projects and to grow the Wikimedia
technical community. In her first assignments, she will help promote
Community Wishlist projects, the Wikimedia Developer Summit, and
Wikimedia’s participation in Google Code-in. Srishti just relocated from
Boston to San Francisco, and she will work at the Wikimedia Foundation
office.
Srishti originally hails from Rajasthan, India. She recently finished her
Masters in Media Arts and Sciences from the MIT Media Lab, where she was
exploring how online platforms for learning could be made more peer-led,
engaging, participatory and accessible to diverse populations. At the Media
Lab, Srishti contributed to the design, development, and research of
Unhangout (http://unhangout.media.mit.edu), a platform for running
large-scale un-conference style events online.
Before joining MIT, she was working as a software developer with a startup
organization in India. As an undergrad, she was involved with the open
source community GNOME and its educational project GCompris.
In her spare time, Srishti likes to play ping-pong, do long bike trips,
take photographs and make masala chai for friends. :)
Please join us in welcoming Srishti!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi Shoichi,
On Mon, Oct 17, 2016 at 5:25 AM, 魔法設計師 <shoichi.chou(a)gmail.com> wrote:
> 1. Acutally speaking it can be launched as a self-server by lightweight
> Jetty (the server is Jetty embedded) it will be launched as a nomal java
> application. Why I use Tomcat now but not launched by "java -jar XXXX.jar"
> ,is because on tools.wmflabs.org , as I remembered,
>
> I had took the way :
> "webservice generic start /data/project/toolname/code/myserver.bash "
>
> Then, the port binding always faiedl,because the command "port" seemed
> always take away parameters belongs to
> the java ap owns.
>
> I couldn't resolve it,so I changed to Tomcat.
>
Great point--we can serve this using whatever Java web container is most
practical! Question for wikitech-l: Which would that be? It looks like
we're already running Jetty for Gerrit, is that the best choice for a new
service?
> 2.About Chinese variable and function names in the server code, after
> forking from the upstream , I think it can be translated to English (
> Actually speaking,I have get some works done.)
>
I'd be happy to help with some of that, maybe we can coordinate the work at
some point. Forking just for the sake of translation sounds problematic,
though. Maybe I'm wrong about this being a review requirement--or maybe
the upstream author would be open to switching to English variable names?
Sorry again about the anglocentrism...
3. There are another way : deploying it to an independent server. For
> example
>
> a. use the upstream server like this
> <http://%E6%BC%A2%E5%AD%97.%E6%84%8F%E5%82%B3.%E5%8F%B0%E7%81%A3/%E2%BF%B1%E2%BF%B0%E7%81%AB%E7%81%AB%E2%BF%B0%E7%81%AB%E7%81%AB.png?%E5%AD%97%E9%AB%94=%E5%AE%8B%E9%AB%94>
> b.use a server maintained by we, Taiwan Chapter, providing service for
> C.J.K.V wiki_____ and etc.
>
I don't think we have the option of using a 3rd-party server, nor relying
on a WMF Labs service for production use. We want to have the same uptime
and security guarantees as for the wiki itself. The production
configuration will probably need to look like a dedicated node or cluster
for serving the IDS requests, and we would cache its PNG or SVG responses.
Someone here might be able to correct me, though?
Thanks again for integrating this tool for us!
-Adam
Hi all,
At this week's ArchCom Office hour, we'd like to help the WMF Legal
team ensure our software development practices don't accidentally
cause us to enable all sorts of creepy surveillance because a naive
developer adds it. The challenge, of course, is when the royal "we"
accidentally add something, and then we deploy it (because that's a
pretty routine thing these days). Sometimes, no amount of begging "NO
WAIT, WE DIDN'T *MEAN* TO DO THAT" (no matter how sincere) can undo
the damage done. Wikimedia seems to have a pretty good reputation in
the grand scheme of things, but maintaining that reputation is going
to take a lot of vigilance.
Zhou Zhou filed an RFC about this:
<https://phabricator.wikimedia.org/T145472>
<https://www.mediawiki.org/wiki/Requests_for_comment/Survey_Cookies/Local_St…>
...which seems like a good topic for our Wednesday meeting[1]. Zhou
is hoping to figure out how to build the alerts necessary to
understand when some new form of tracking is created. I'm guessing
there's lots of automated and semi-automated monitoring that we could
create to make keeping track of new cookie uses easier; let's talk
about what's realistic, what WMF needs to invest in directly, and how
our wider community of developers can chip in.
Our meeting is at its usual time (Wednesday 21 UTC, 14 PDT, 23 CEST)
and place (#wikimedia-office).
Rob
p.s. Obligatory reminder about ArchComStatus page[2]
[1]: <https://phabricator.wikimedia.org/E316>
[2]: <https://www.mediawiki.org/wiki/ArchComStatus>
Hi everyone,
The WMF Community Tech team is starting to wrap up our work on this year's
Community Wishlist projects, as we prepare for the new Community Wishlist
Survey starting in November.
We've got a new Status report to share, with an update on the work that's
been done this year on the Community Wishlist:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_repor…
Here's a quick overview for the top 10 --
COMPLETED WORK on 5 wishes:
* Wish #1: Migrate dead external links to archives, with volunteer dev
Cyberpower678 -- currently on English Wikipedia, other languages coming
* Wish #2: Improved diff comparisons, by WMF developer MaxSem, live on all
wikis
* Wish #5: Numerical sorting in categories, currently on English, Swedish
and Macedonian Wikipedias, more languages coming soon
* Wish #7: Pageview stats tool, live on all wikis
* Wish #9: Improve the plagiarism detection bot, with volunteer dev Eran --
currently on English Wikipedia, other languages coming
CURRENTLY WORKING on 1 wish:
* Wish #4: Cross-wiki watchlist, currently in progress
OTHER TEAMS ARE WORKING on 2 wishes:
* Wish #3: Central repository for gadgets, templates and Lua modules,
foundational work is underway by Legoktm
* Wish #6: Allow categories in Commons in all languages, related work is
underway by the Wikidata team
DECLINED 2 wishes:
* Wish #8: Global cross-wiki talk page
* Wish #10: Add a user watchlist
There's lots of information on the top 10, plus the work being done by
WMDE's Technical Wishes team and the Technical Collaboration team, on the
Status report page:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_repor…
And we hope that everyone will come and participate in the 2nd annual
Community Wishlist Survey, starting November 7th!
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey
See you soon,
-- Danny
DannyH (WMF)
Senior Product Manager
WMF Community Tech Team
Dear all,
I am working on a simple idea that would simplify how update.php can be
used for wiki families. Please consider commenting on
https://phabricator.wikimedia.org/T147817
Thanks,
Huji
Hi could could any postgres developer please help with task https://phabricator.wikimedia.org/T147599 please. Postgres is currently broken in mw 1.28 and needs fixing please.