These resources may give ideas to people who create project proposals or
any of several kinds of reports.
http://www.datavizcatalogue.com/index.htmlhttp://survey.timeviz.net/
Have fun exploring,
Pine
P.S. In the multimedia domain, I'd like to have the ability to add
interactive visualizations to Wikipedia and its sister projects. For
example, imagine how engaging it would be to have interactive phylogenetic
trees that allow the user to zoom in and out and see images of species.
Everyone,
It's my pleasure to welcome Joe Matazzoni to the Editing department as the
new product manager for the Collaboration team from today. Joe will help
the team develop aligned with the needs of our editors, prioritizing and
shaping the improvements we're making to notifications, watchlists, change
tracking, discussions and more. He replaces Danny Horn, who is now helping
the Community Tech team.
Joe has had a long career in digital publishing and media, particularly in
public broadcasting, first at NPR, where he helped rebuild the Web site and
then founded the Arts & Life section, and more recently at KQED, where he
created an Emmy-winning arts video team. Joe has a master’s degree in
interactive telecommunications from NYU and a background in UX design. He
was the director of UX at the Wall Street Journal, where he helped lead a
complete site and CMS redesign and relaunch.
After many years in New York and DC, Joe is delighted to be back in his
native Bay Area. He's a big reader, enjoys biking and swimming and likes to
dabble in the kitchen. He will be based in the office, which he plans to
commute to via the ferry from Marin, where he lives with his wife and
11-year-old son. Joe will be on IRC and of course on-wiki as [[User:JMatazzoni
(WMF) <https://meta.wikimedia.org/wiki/User:JMatazzoni_(WMF)>]].
Welcome, Joe!
Yours,
--
James D. Forrester
Lead Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
oHi everybody,
I don't really know if this list is the right place to start the
discussion, but I'll force my luck.
We have a usecase in Wikidata for property proposals where we use templates
to internationalize Property Proposals
https://www.wikidata.org/wiki/Wikidata:Property_proposal/
Wikidata is a central place for community, like commons, and it's important
for this place to make this place friendly for non english-speaker. Amongst
other problems it's a blocker for some Wikipedians, or it does not help at
least, to contribute or discuss in a different language than their home
language.
Discussions in Wikidata can lead to important or technical decisions, so
this is more important than say, in commons to handle correctly languages.
If we sum-up the stuffs we have to di this, we mainly have and use:
* The translate extension
* Ad-hoc template
The translate extension works, but it needs some administration to be
functional and this is not really adapted because to heavy for frenquently
updated pages like property proposals. It also requires interventions in
the initial page like wikitext annotations, and this unfortunately can be a
community problem - The translation of
https://www.wikidata.org/wiki/Wikidata_talk:WikiProject_Taxonomy for
example does not exists because, apparently, one of the main contributors
thinks it complicates the editions of the project page and reverted the
attempts to prepare the page for translation.
Ad-hoc templates like https://www.wikidata.org/wiki/Template:TranslateThis
are used to translate the property proposals atm. The actual problem that
pushed me to write this mail is related to this :
* each property proposal as its own section in the page
* it's convenient for discussions to point to a section in a link by using
the section name
But ... the titles are translated using translate this, which make the
title section not stable and can then break the links, make the histories
unreadable ... so there is (I think) an anchor added by the template. But
this make the history unreadable.
To address this problem Yair Rand proposed an ad-how hacky gadget to have a
cleaner history :
https://www.wikidata.org/wiki/Wikidata_talk:Tools#Gadget_proposal:_User:Yai…
The subsequent discussion lead me there : Maybe Flow could be of some help
: its section ids are stable, but ... again we can't use template in Flow
titles.
So my question would be : I understood the Flow team switched to a more
"Workflow oriented" orientation. Where can we contact you/them to discuss
the needs like this one ? Can we be sure translations problematics will be
took into account in this Flow follos-up ?
Cheers, Tom
FYI
We are headed into the season of vacations and high risk fundraising, as
such, the WMF is (I am) putting in place "deployment freezes" for a few
weeks over the next seven. See full details below and on the Deployments
page on wikitech.
Greg
----- Forwarded message from Greg Grossmeier <greg(a)wikimedia.org> -----
> Date: Wed, 25 Nov 2015 08:19:26 -0800
> From: Greg Grossmeier <greg(a)wikimedia.org>
> To: Development and Operations engineers <engineering(a)lists.wikimedia.org>, Operations Engineers <ops(a)lists.wikimedia.org>
> Cc: Katie Horn <khorn(a)wikimedia.org>, Megan Hernandez <mhernandez(a)wikimedia.org>
> Subject: Deploy freeze(s) in effect for the next 7 weeks (ish, read for more details)
>
> A reminder of the upcoming deployment freezes. All details, of course,
> can always be found on the Deployments[0] page on wikitech; it is the
> canonical location for all deployment freeze (and exception)
> information.
>
>
> FTR: "High Priority" means security and data loss, really. There may be
> other exceptions but they need pre-approval from at least myself and
> sometimes Katie.
>
>
> * Week of Nov 23rd: No normal deploys - high prioity SWATs only
> (pre-approval from Greg needed) (Why: Thanksgiving)
>
> * Week of Nov 30th: No normal deploys - high prioity SWATs only
> (pre-approval from Greg and/or Katie needed) (Why: First of Dec
> Fundraising)
>
> * Week of Dec 7th: Normal deploy week
>
> * Week of Dec 14th: Normal deploy week
>
> * Week of Dec 21st: No normal deploys - high prioity SWATs only (and
> only on Monday and Tuesday) (pre-approval from Greg and/or Katie needed)
> (Why: End of year Fundraising)
>
> * Week of Dec 28th: No normal deploys - high prioity SWATs only
> (pre-approval from Greg and/or Katie needed) (Why: End of year
> Fundraising)
>
> * Week of Jan 4th: No normal deploys - high prioity SWATs only
> (pre-approval from Greg needed) (Why: DevSummit16 and WMF All Hands)
>
> * Week of Jan 11th: Resume normal deploy schedule
>
>
> Thanks and enjoy the break from breakages (hopefully!),
>
> Greg
>
> [0] https://wikitech.wikimedia.org/wiki/Deployments
>
> --
> | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
> | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
----- End forwarded message -----
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hello,
A reminder that the online office hour hosted by the Wikimedia Language
Engineering team is scheduled for later today at 1300 UTC. You can join the
hangout or watch the session from:
https://plus.google.com/u/0/events/cprj7uhtiercilrilp2gfpca8dg
Please note, due to the limitation of Google Hangouts there are few seats
available. So do let us know before hand if you would like to participate
on the hangout. We will also be on the IRC channel #wikimedia-office to
take questions. Please see below for the event details, local time and
original announcement.
Thanks
Runa
== Details ==
# Event: Wikimedia Language Engineering office hour session
# When: November 25th, 2015 (Wednesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151125T1300)
# Where: https://plus.google.com/u/0/events/cprj7uhtiercilrilp2gfpca8dg and
on IRC #wikimedia-office (Freenode)
# Agenda: Content Translation updates and Q & A
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Thu, Nov 19, 2015 at 5:50 PM
Subject: Language Engineering office hour and online meeting on 25 November
2015 (Wednesday) at 1300 UTC
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Wikimedia
developers <wikitech-l(a)lists.wikimedia.org>, MediaWiki internationalisation
<mediawiki-i18n(a)lists.wikimedia.org>, "Wikimedia & GLAM collaboration
[Public]" <glam(a)lists.wikimedia.org>
[x-posted announcement]
Hello,
The next office hour of the Wikimedia Language Engineering team is
scheduled for next Wednesday, November 25th 2015 at 13:00 UTC. Similar to
our recent office hours, this is also going to be an online discussion over
Hangout/Youtube with a simultaneous IRC conversation. Due to the limitation
of Google Hangouts, only a limited number of slots are available. Hence, do
please let us know (on the event page) if you would like to participate on
the Hangout. The IRC channel #wikimedia-office and the Q&A channel for the
youtube broadcast will be open for interactions during the session.
Our last online round-table session was held in September 2015. You can
watch the recording here: https://www.youtube.com/watch?v=nW5l7fNeMQg
Please read below for the event details and do let us know if you have any
questions.
Thank you
Runa
== Details ==
# Event: Wikimedia Language Engineering office hour session
# When: November 25th, 2015 (Wednesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151125T1300)
# Where: https://plus.google.com/u/0/events/cprj7uhtiercilrilp2gfpca8dg and
on IRC #wikimedia-office (Freenode)
# Agenda: Content Translation updates and Q & A
--
Language Engineering Manager
Outreach and QA Coordinator
Wikimedia Foundation
--
Language Engineering Manager
Outreach and QA Coordinator
Wikimedia Foundation
Hi folks,
One idea that achieved consensus here at WMF, but was never discussed
publicly (that I'm aware of) is the idea that meetings should use the
Google Calendar speedy meeting option.[1]
Since we didn't have a public discussion of this, it's technically not
the standard for RFC review meetings. However, this led to the
natural question "why not?"
So....why not? Is there any opposition to us ending RFC meetings 5-10
minutes early?
Rob
[1] http://getsolid.io/blog/enabling-speedy-meetings-google-calendar/