On Thu, May 15, 2014 at 7:35 PM, Dan Andreescu wrote:
> I like Visual:, any +1s? +2s?
>
I give it a +0.5 :) I also like "Render" but its meaning has become too
attached to 3d graphics...
Anyhow if we have a "Visual" and a "VisualData" namespace, they could be
associated to each other:
https://www
Hoi,
For your information there are several things Wikidata can already do.
- When for instance a district is associated with a "shape", multiple
shapes could be known and dated by Wikidata.
- It could know of the existence of maps and when a map is defined in a
way that allows for que
Thanks Sumana! That works :-)
Best,
Alolita
Alolita Sharma
आलोलिता शर्मा
Director of Engineering
Internationalization & Localization
Wikimedia Foundation
On Thu, May 15, 2014 at 7:22 PM, Sumana Harihareswara wrote:
> On 05/15/2014 01:00 AM, Alolita Sharma wrote:
> > That's 230am in India. Wis
On Thu, 2014-05-15 at 21:34 +, Jeremy Baron wrote:
> On Thu, May 15, 2014 at 9:20 PM, Quim Gil wrote:
> > There are good reasons to plan for Wikimedia SUL only (consistency with the
> > rest of Wikimedia projects), and there are good reasons to plan for other
> > providers as well (the easiest
There is some privacy question around it?
2014-05-15 20:42 GMT-03:00 C. Scott Ananian :
> Ideally you would be able to link your (say) github and WMF account.
> So that if I (as an outsider) start a bug report/patch/etc using my
> existing github account, and then eventually get a WMF account (s
Ideally you would be able to link your (say) github and WMF account.
So that if I (as an outsider) start a bug report/patch/etc using my
existing github account, and then eventually get a WMF account (so
that I can do labs-related things?) I can manage my bugs/patches
regardless of which account's
On Thu, May 15, 2014 at 2:20 PM, Quim Gil wrote:
> However, Phabricator can support authentication using 3rd party providers
> like GitHub, Google, etc. You can get an idea at
> https://secure.phabricator.com/auth/start/
>
I think since this is already built and would require no extra work, we
s
On Thu, 2014-05-15 at 14:20 -0700, Quim Gil wrote:
> This is a casual request for comments about the use of 3rd party
> authentication providers for our future Wikimedia Phabricator instance.
>
> Wikimedia Phabricator is expected to replace Bugzilla, Gerrit and many
> other tools, each of them hav
On Thu, May 15, 2014 at 8:06 AM, Jon Robson wrote:
> Visual: ?
The mild conflict VisualEditor: conflict aside, that seems reasonable.
View: might also work if it's not used for something else. Either way,
it's going to be a bit tricky to translate.
It might be good to design it with Commons in
On Thu, May 15, 2014 at 2:20 PM, Quim Gil wrote:
> There are good reasons to plan for Wikimedia SUL only (consistency with the
> rest of Wikimedia projects), and there are good reasons to plan for other
> providers as well (the easiest path for most first-time contributors).
>
> What do you think
Folks, this looks really fantastic, way to go!!
I'd really love to contribute to this, as time allows, BTW.
* Data (one or more sets of data, can be geojson, topojson, tsv, csv,
layers from OSM [3], OHM [4], etc.)
* Datasets in WikiData using an alternative data model
I'm especially interest
DataDisplay:
On May 15, 2014, at 22:59 , Dan Andreescu wrote:
> By the way, the Vega work is deployed to this wiki:
>
> http://analytics-wiki.wmflabs.org/mediawiki/Main_Page#Visualization
>
> Jon/DJ/Aude, if you want I can add a more generic proxy name for that wiki
> and put your stuff on th
i like the idea of having one wikimedia login for all wikimedia wikis, tools,
labs, gerrit, mail lists, etc. and keeping other logins such as google, yahoo,
or github in their own domain.
On May 15, 2014, at 23:20 , Quim Gil wrote:
> This is a casual request for comments about the use of 3rd
On Thu, May 15, 2014 at 9:20 PM, Quim Gil wrote:
> There are good reasons to plan for Wikimedia SUL only (consistency with the
> rest of Wikimedia projects), and there are good reasons to plan for other
> providers as well (the easiest path for most first-time contributors).
If there's a problem
On Thu, May 15, 2014 at 5:20 PM, Quim Gil wrote:
> This is a casual request for comments about the use of 3rd party
> authentication providers for our future Wikimedia Phabricator instance.
>
> Wikimedia Phabricator is expected to replace Bugzilla, Gerrit and many
> other tools, each of them havi
This is a casual request for comments about the use of 3rd party
authentication providers for our future Wikimedia Phabricator instance.
Wikimedia Phabricator is expected to replace Bugzilla, Gerrit and many
other tools, each of them having their own registration and user account.
The plan is to o
By the way, the Vega work is deployed to this wiki:
http://analytics-wiki.wmflabs.org/mediawiki/Main_Page#Visualization
Jon/DJ/Aude, if you want I can add a more generic proxy name for that wiki
and put your stuff on there too? It's in the analytics project in labs but
I'm happy to give anyone r
On Thu, May 15, 2014 at 6:43 PM, Quim Gil wrote:
> On Sun, May 11, 2014 at 2:00 AM, Rachel Farrand
> wrote:
>> Join Nik Everett on May 15 at 19:00 UTC for his talk on Elasticsearch:
>> What it is? Why we chose it? How does it work? What is left to do before we
>> cut over to it completely?
>>
>>
This session is starting in 15 minutes.
On Sun, May 11, 2014 at 2:00 AM, Rachel Farrand wrote:
> Join Nik Everett on May 15 at 19:00 UTC for his talk on Elasticsearch:
> What it is? Why we chose it? How does it work? What is left to do before we
> cut over to it completely?
>
> https://www.mediaw
I like Visual:, any +1s? +2s?
The only downside might be a slight conflict with VisualEditor
On Thu, May 15, 2014 at 11:20 AM, dan-nl wrote:
> PictureIt:
> Envision:
> Imagine:
>
> On May 15, 2014, at 17:06 , Jon Robson wrote:
>
> > Visual: ?
> > On 14 May 2014 10:44, "Derk-Jan Hartman"
> > w
On 05/15/2014 01:00 AM, Alolita Sharma wrote:
> That's 230am in India. Wish these meetings were held a bit earlier (9am PDT
> :-)
>
> Best,
> Alolita
>
> Alolita Sharma
> आलोलिता शर्मा
> Director of Engineering
> Internationalization & Localization
> Wikimedia Foundation
Thanks, Alolita. I'll ho
Bryan's made some updates to the docs! Here's what Bryan just said to me
(forwarded with permission):
> I put the core of my narrative on wikitech [0] along with the diagram.
> The page I put that on could use a little more attention to ensure
> that references to pmtpa are gone. It might be good
PictureIt:
Envision:
Imagine:
On May 15, 2014, at 17:06 , Jon Robson wrote:
> Visual: ?
> On 14 May 2014 10:44, "Derk-Jan Hartman"
> wrote:
>
>> PS, i'm building an instance that is running this extension.
>>
>> On Wed, May 14, 2014 at 12:34 AM, Jon Robson
>> wrote:
>>> During the Zurich hac
Visual: ?
On 14 May 2014 10:44, "Derk-Jan Hartman"
wrote:
> PS, i'm building an instance that is running this extension.
>
> On Wed, May 14, 2014 at 12:34 AM, Jon Robson
> wrote:
> > During the Zurich hackathon, DJ Hartman, Aude and I knocked up a
> > generic maps prototype extension [1]. We ha
On Thu, May 15, 2014 at 1:42 PM, Cristian Consonni
wrote:
> Thanks for the pointer, "How can I put this open data on Wikidata is a
> question that I have been asked many times", this page was needed.
>
Thanks for your comment!
On Thu, May 15, 2014 at 3:59 PM, Samuel Klein wrote:
> Thanks Mic
Am 14.05.2014 16:04, schrieb Gabriel Wicke:
> On 05/14/2014 03:22 PM, Daniel Kinzler wrote:
>> My patch doesn't change the handling of ... by the parser. As
>> before, the parser will pass HTML code in ... through only if
>> wgRawHtml is enabled, and will mangle/sanitize it otherwise.
>
>
> Oh, I
On 05/14/2014 05:38 PM, Terry Chay wrote:
> Hello everyone,
>
> It's a testament to either how awesome our people are… or just how notorious
> I am for not announcing things promptly that I noticed this sitting in my
> Google Docs the other day with the note from the VisualEditor Team: "terry,
Thanks Micru! I think we should start by including datasets on
wikisource, with descriptions about them (storing the files on commons
where possible). And adding more data formats to the formats
accepted on commons.
Other tools can follow later.
On Thu, May 15, 2014 at 5:25 AM, David Cuenca w
>
> 2014-05-14 19:43 GMT+03:00 Dan Andreescu :
> > For the short term, I think further exploration of the Map namespace is
> > great, but I think generic visualization work could go into the
> > Visualization namespace. My suggestion for a name for this namespace may
> > seem a bit obscure. It's
yup we will move it.as long as Git repositories are easier for me to setup
on GitHub I will always start projects there... ;)
On 15 May 2014 10:59, "Niklas Laxström" wrote:
> 2014-05-14 1:34 GMT+03:00 Jon Robson :
> > During the Zurich hackathon, DJ Hartman, Aude and I knocked up a
> > generic m
2014-05-15 11:25 GMT+02:00 David Cuenca :
> During the Zürich Hackathon I met several people that looked for solutions
> about how to integrate external open datasets into our projects (mainly
> Wikipedia, Wikidata). Since Wikidata is not the right tool to manage them
> (reasons explained in the RF
Hi,
During the Zürich Hackathon I met several people that looked for solutions
about how to integrate external open datasets into our projects (mainly
Wikipedia, Wikidata). Since Wikidata is not the right tool to manage them
(reasons explained in the RFC as discussed during the Wikidata session),
2014-05-14 1:34 GMT+03:00 Jon Robson :
> During the Zurich hackathon, DJ Hartman, Aude and I knocked up a
> generic maps prototype extension [1]. We have noticed that many maps
> like extensions keep popping up and believed it was time we
> standardised on one that all these extensions could use so
On 05/14/2014 12:43 PM, Dan Andreescu wrote:
* File namespace serving raw data from Commons (where people are familiar
with take down notices and have the infrastructure to deal with that)
We shouldn't let copyright considerations dictate which WMF project
hosts the data. https://wikimediafou
On 14 May 2014 23:38, Terry Chay wrote:
> Hello all,
>
> It is with great pleasure that I’m announcing that Alex Monk[0] has joined
> the Wikimedia Foundation as a contractor in Features Engineering.
>
Welcome, Alex; great to be able to say so formally!
J.
--
James D. Forrester
Product Man
35 matches
Mail list logo