Hi, I foward this mail to design, since it seems relevant here.
As far as I know, currently there is no other way to create (world)maps
than taking some existing blank one, and put the color on regions of
interest. Maybe it would be intersting to have such a tool online, but
more important, to ease contributors ability to make interactive maps,
which enable readers to see how a phenomenon evolved/is evolving through
time.
What do you think ?
Le 2013-05-24 20:26, phoebe ayers a écrit :
> On Fri, May 24, 2013 at 1:55 AM, Mathieu Stumpf <
> psychoslave(a)culture-libre.org> wrote:
>
>> Le 2013-05-23 19:03, phoebe ayers a écrit :
>>
>> Perhaps of interest to many Wikimedians: the Endangered Languages
>> project
>>> recently launched a new layout, making it easier to find and submit
>>> information on languages that are in the "catalog of endangered
>>> languages"
>>> that they are building. Worth a look.
>>>
>>> http://www.**endangeredlanguages.com/<http://www.endangeredlanguages.com/>
>>>
>>> -- phoebe
>>>
>>
>> Thank you for the link.
>>
>> It seems to be the result of a realy huge work! Do you know if their
>> solution to create interactive map is free software? I would love to
>> have
>> such a tool within wikimedia. To my mind, it would be really useful
>> for
>> geographic and historical articles. Having a tool that would enable
>> to
>> "watch events propagation through time and localisation on a map"
>> would be
>> awesome, and it seems to me that their software is almost all that.
>>
>
> Hi Mathieu,
>
> I don't know anything about this project beyond what's on the site --
> I
> just ran across it. From what I can tell the user-submitted language
> data
> is CC-by but unfortunately they seem to be using Google Maps for the
> map
> interface.
>
> -- phoebe
--
Association Culture-Libre
http://www.culture-libre.org/
Hello,
It was nice to meet you all, this hackathon was really a great event
for me, enriching, passioning and enjoyable. I hope that it was also the
case for all others.
So, in one of the design workshop, we worked on the "Knowledge
requirement", that is some time articles treat non-obvious subjects and
go with assumptions on user knowledge. That can lead the user to a
frustrating situation where she think that she will never be able to
understand the topic. As far as I know, the writing guideline is that
every article should be suffisant, so probably that kind of article
would need to be improved. On the other hand, some community member
aren't find with the idea to "expand the whole subject from the ground"
in every article, and the most knowledgeable on a topic are not
necessarily those with the best pedagogic skills.
So our concern here is to bring a solution to user who want to know,
but don't necessarily have the basic knowledge expected to understand
it. The "let's make the article perfect for everyone" being out of
reach, the proposal to avoid user frustration is to inform him that the
article have knowledge requirements that she can acquire with some
pedagogical materials (preferably on wikversity/wikibook/wikisource).
I already had a mokcup of a possible solution I thought by myself, but
within this workshop, we were able to come with something probably far
more relevant : simpler, less invading, while at least as much
informative. The idea is to use a something similar to
Template:Disambiguation, and to list all the "dependencies" in a section
at the bottom of the article or in a subpage.
Moreover I think that this template may rise a warning message when
this sections/subpages doesn't exist, like with the ref and references
markup, so that if one place the template in an article, if would be
inclined to create the corresponding sections/subpages.
Now what is needed is to design/pick the text (which should short of
course) and the picture/icon to illustrate it. I already made some
research on commons to find a releavant icon, but maybe someone could
come with a better proposition, or even an original icon which fit the
topic. You can find a preliminary report on[1], but it's in french. I
will translate it later this week on meta, but this mail tell most of
what is written there, and I guess you don't need to know french to tell
your opinion on icons I selected from Commons as candidate for this
template.
[1]
https://fr.wikipedia.org/wiki/Utilisateur:Psychoslave/pr%C3%A9requis
--
Association Culture-Libre
http://www.culture-libre.org/
We currently have a goal to push our nearby feature to stable next week.
Your feedback on the current page would thus be greatly appreciated:
https://en.m.wikipedia.org/wiki/Special:Nearby
In particular please focus on these outstanding concerns remembering
this is a first pass and we should focus on the most essential things:
1) Copy text - in particular is it clear that certain pages need
photos and how to do that?
2) Refreshing the list of nearby results - is the icon choice correct
and how is the user experience?
3) Is the preview useful? (the preview is mobile only and activated
when you click on an article) - does the experience break without it?
(to get an idea of how it might work without try the desktop version
at https://en.wikipedia.org/wiki/Special:Nearby or click "Read this
article in full" before reading the preview and click back button to
get back to the nearby view
4) Any styling tweaks you'd recommend (especially with respect to the
article preview)?
Thanks for your feedback - all much appreciated!
Matthew Roth, 23/05/2013 17:31:
> So, what's the future of CC on Flickr?
> http://www.flickr.com/__creativecommons/
> <http://www.flickr.com/creativecommons/> shows only 260M CC images:
> there were already 220M in 2011 if I read news correctly; only 60M
> are free. 75 % of the times I ask a user to put an image under
> cc-by-sa they choose -nc-nd because "it was the first option" (and
> some of course "what, isn't Wikipedia non-commercial?!).
> Is this the price to pay to Instagram, Tumblr and Facebook?
>
>
> There are already lots of problems with Facebook (and various other
> social networks) and free licenses. See this analysis here:
> http://meta.wikimedia.org/wiki/Legal_and_Community_Advocacy/CC-BY-SA_on_Fac…
Yes but there's a difference between that and forcing good sources of
free knowledge like Flickr to drop this aspect, which Facebook never
had. :) (If this is what's happening.)
Ah, of course they also removed the option to have unlimited uploads:
only current pro users can keep it, for the others there are only
expensive storage plans.
Nemo
I made this today:
http://unicorn.wmflabs.org/staticheader/
It could use some work (I hard-set the searchbox width on movement, and it should probably flow to fill all available space).
But it gives an idea of what the experience would be like.
---
Brandon Harris, Senior Designer, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
Currently we have very different upload detail and add-category screens
between Android and iOS versions of the Wikimedia Commons uploader app.
I've put descriptions and quick comparative videos on mediawiki.org:
https://www.mediawiki.org/wiki/Apps/Commons/Categories
Impressions and ideas welcome!
(Y'all can try the Android version with categorization from Google Play --
the iOS version in the App Store doesn't yet have categories but you can
try the older version to get a feel for the layout and the first data entry
screen. For those on the beta group, there'll be a push via TestFlight
later today.)
-- brion
Thanks Jared. What are you thoughts on pre vs post category addition ?
--tomasz
On Mon, May 13, 2013 at 8:31 AM, Jared Zimmerman
<jzimmerman(a)wikimedia.org> wrote:
> The variable height is nice for the panoramic images especially. It would
> certainly require us to come up with something different in the detail
> views.
>
> …will give it some more thought.
>
> Sent from my iPhone
>
> On May 12, 2013, at 2:18 PM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
>
> Here's a quickie alternate mockup of the gallery & detail screens:
> https://brionv.com/misc/commons-mockup/
> Source at https://github.com/brion/commons-mockup
>
> Mockup uses actual items from this month's Picture of the Day feed.
>
> This explores the more 'mosaic'-style model to the gallery view where items
> aren't cropped and have variable height. I like this for a single column,
> but I'm not satisfied with how it could work sensible in multi-column.
>
> Clicking/tapping on individual images transitions to a detail screen, with
> the image stretched, cropped and darkened in the background as we currently
> do on Android's title/description screen. We can imagine a fancier
> transition, such as animating the image from its place in the gallery view
> as it zooms in to the full screen (oooh!) but I didn't mock up the
> transition yet. ;)
>
> Detail screen contents are based on one of Jared's mockups, using a more
> compact category view. The items on the detail screen load asynchronously,
> so be warned they jump around a bit. We'd want to make such things much
> smoother "for real" of course... we'd also probably use this screen to
> provide sharing controls, etc.
>
> If the categories, description etc are large, we can easily go beyond a
> screenfull, and have to scroll this screen. Should the background image stay
> still during scrolling or should it move a little, parallax-y? (ooooh more
> visual effects)
>
> Do we want to use the detail screen as the data-entry screen on new uploads
> as well, or keep them distinct?
>
> Do we need a separate 'view image' screen that can handle pan/zoom?
>
> How will we scale this up on tablets?
>
> Thoughts, ideas?
>
> -- brion
>
>
>
>
> On Fri, May 10, 2013 at 10:50 AM, Tomasz Finc <tfinc(a)wikimedia.org> wrote:
>>
>> Thanks Brion.
>>
>> Vibha & Jared, it would be great to get you guys to weigh in on this.
>> --tomasz
>>
>>
>> On Thu, May 9, 2013 at 5:02 PM, Brion Vibber <bvibber(a)wikimedia.org>
>> wrote:
>> > Currently we have very different upload detail and add-category screens
>> > between Android and iOS versions of the Wikimedia Commons uploader app.
>> >
>> > I've put descriptions and quick comparative videos on mediawiki.org:
>> > https://www.mediawiki.org/wiki/Apps/Commons/Categories
>> >
>> > Impressions and ideas welcome!
>> >
>> >
>> > (Y'all can try the Android version with categorization from Google Play
>> > --
>> > the iOS version in the App Store doesn't yet have categories but you can
>> > try
>> > the older version to get a feel for the layout and the first data entry
>> > screen. For those on the beta group, there'll be a push via TestFlight
>> > later
>> > today.)
>> >
>> > -- brion
>> >
>> > _______________________________________________
>> > Design mailing list
>> > Design(a)lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/design
>> >
>>
>> _______________________________________________
>> Design mailing list
>> Design(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/design
>
>
Jared was showing me an iOS app that has a cool-looking (but IMO a little
disorienting) tablet view with the mosaic model... I'll record a screencast
so y'all android folks can see what it looks like. ;) Not sure I like it
but it's a good thing to compare against.
-- brion
On Mon, May 13, 2013 at 8:42 AM, Yuvi Panda <yuvipanda(a)wikimedia.org> wrote:
> I'll note that if we start doing variable heights we need a solution for
> multiple items in the same row of differing heights - for tablets and
> phones in landscape mode. When we last looked around for 'MosaicView'
> widgets there weren't any good ones, so we might have to build our own if
> we go that way. Not sure about the situation on iOS though.
>
Reminder for folks interested in testing beta versions of the Commons app
for iOS: you must register on TestFlight.app or you'll only have access to
the App Store builds which are way behind what we're working on!
Register for the beta team at http://tflig.ht/Zl9Ef7 -- then don't forget
to go to http://testflightapp.com/ on your iPhone/iPod/iPad and register
the device! Without this step we won't be able to include you.
Note that Android betas don't require registration; we'll also be updating
in the Google Play store more often than in the Apple App Store.
-- brion
I have thrown together an interactive prototype of Flow. It's fairly functional and I intend to make it even more so.
You can play with it here: http://elohim.gaijin.com/flow/
Nothing is saved to disk. You can reply to topics or even add new ones but on refresh everything reverts to state.
Right now, the "you" you are logged into is "Jorm" but I'll be adding functionality to handle that.
In the sidebar are a couple links to various "board examples":
* Fully Chaos (everything is generated randomly.)
* Jimmy Wales
* Maggie Dennis (Moonriddengirl)
* Me
* A single topic (this is what you get to if you get an echo notification)
Speaking of, if you click the echo badge, and then click on the unread notification, you'll get the experience of the user getting a reply and going to the single conversation view.
You can also click the "Feed" link and you'll be brought to your feed. The "feed" view is different from the "Board" view. The feed is private - it's all the conversations that you my be interested in or are subscribed to (have a solid star). You also see activity from the boards of *people* you're subscribed to as well, but it floats away fairly quickly if you don't subscribe to it.
Known bugs:
* The "New Topic" dialog doesn't close when you click the "X" button. No idea why; it worked the other day and now it doesn't.
* Some of the conversations are threaded weird. This is an artifact of the JSON.
* The tab highlights are a bit goofy.
Upcoming:
* The search functionality will work
* You'll be able to add and edit tags
* Stuff like archive/split/whatever
* Edit your own post, etc.
Please share your thoughts.
---
Brandon Harris, Senior Designer, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate