Hi everyone,
As an applicant of FOSS-OPW Round 7, I took a deep and profound interest in
one of the featured projects "Uploadwizard:OSM map embedding" . If chosen
or allowed I am planning to focus on this particular project.
****Project Synopsis***
"This project is about enhancing the image upload process for Wikimedia
Commons.
Commons has millions of images and Wikipedia editors need to be able to
find quickly the right ones for their articles, so it is important to store
various metadata with the image which will help navigation - topic of the
image, when it was made and so on. This metadata is usually stored in a
complex template language that is specific to MediaWiki, and the sight of
which usually makes people to flee in terror.
Since we cannot expect image authors to learn to write something like that,
Commons has a tool called UploadWizard which creates all the code for you,
after you fill out a bunch of forms. The main goal of the OSM map embedding
project would be to provide map interface & the integration with external
databases to the UploadWizard. (OSM stands for OpenStreetMap - a free map
application which is similar to Google Maps but not encumbered by
restrictive copyright.)
The secondary goal is to integrate with some databases of locations and use
that in various ways. One way would be checking if there are locations with
requested images nearby (that is, someone put out a note that Commons needs
good images about a certain place and doesn't currently have any), and warn
the uploader about them. Another involves image competitions where people
can participate with pictures taken at some predefined locations;
UploadWizard could get a list of these locations and use it to help the
participant in selecting where he took the photo."
- Mentor,Gergő Tisza
Expecting valuable comments and suggestions to improve the project from
vibrant MediaWiki community. :)
+ wikitech
On Tue, Oct 29, 2013 at 8:54 AM, Siebrand Mazeland (WMF) <
smazeland(a)wikimedia.org> wrote:
> Also see https://gerrit.wikimedia.org/r/#/c/23424/
>
> In my opinion, external link icons add a lot of visual noise and not that
> much relevant information.
>
>
> On Mon, Oct 28, 2013 at 11:22 PM, Jon Robson <jrobson(a)wikimedia.org>wrote:
>
>> Changed subject to reflect this change in topic. Also cc'ing design
>> mailing list.
>>
>> In terms of external links to me I don't care about whether I'm leaving
>> the site or not. If I clicked on something and it wasn't what I expected
>> that's a badly labeled link. A link saying there is more information on the
>> [white house official website] and a link to the word [house] should be
>> enough information to tell which I'd external and which isn't.
>>
>> I actually think the only place an icon next to a link really makes sense
>> is for downloads. Clicking something that downloads a PDF when I thought it
>> was a web page is a little confusing (on mobile at least).
>>
>> That said if all the external links are in the external links /
>> references section wouldn't encouraging that organisation of links be
>> better....?
>>
>> Also I agree with Juliusz that we shouldn't force behaviour of where
>> links open. It should be up to the user if they want the same tab or new
>> one and it should be configurable within the browser preferences.
>> On 24 Oct 2013 16:07, "Juliusz Gonera" <jgonera(a)wikimedia.org> wrote:
>>
>>> No, we should definitely not warn people, that's just weird ;) It's
>>> not like something bad is about to happen.
>>> I'm also not saying that users have the expectation that links point to
>>> local URLs, I'm only saying that it might be a useful piece of information
>>> to some.
>>>
>>>
>>> On 10/24/2013 02:48 PM, Jared Zimmerman wrote:
>>>
>>> Its definitely a less heavy handed way of doing the thing many
>>> (annoying) sites do when they warn you that you're leaving their site. I
>>> just wonder is the signal to noise it worth it. I don't know that modern
>>> web users have any expectations that link within a site always point to
>>> local site urls.
>>>
>>> *
>>> *
>>> *
>>> *
>>> *Jared Zimmerman * \\ Director of User Experience \\ Wikimedia
>>> Foundation
>>> M : +1 415 609 4043 | : @JaredZimmerman<https://twitter.com/JaredZimmerman>
>>>
>>>
>>>
>>>
>> _______________________________________________
>> Design mailing list
>> Design(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/design
>>
>>
>
>
> --
> Siebrand Mazeland
> Product Manager Language Engineering
> Wikimedia Foundation
>
> M: +31 6 50 69 1239
> Skype: siebrand
>
> Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
>
> _______________________________________________
> Design mailing list
> Design(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/design
>
>
--
Jon Robson
http://jonrobson.me.uk
@rakugojon
On Mon, Oct 7, 2013 at 9:01 AM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
> As an experiment, I've built Xiph's ogg, vorbis, and theora C libraries
> cross-compiled to JavaScript
>
[snip]
> Performance on iOS devices isn't great, but is better with lower
> resolution files :)
>
I've also started on an experimental native iOS library for .ogg/.oga/.ogv
playback, again cross-compiling the existing Xiph ogg, vorbis, and theora
reference libraries as the actual decoder:
<https://github.com/brion/OgvKit>
It's still a proof of concept, currently without color conversion, sane
drawing code, audio, playback controls, etc, but the demo successfully
plays a small 3-second sample video I pulled from Commons: <
https://commons.wikimedia.org/wiki/File:Peacock_Mating_Call.ogg>
Note that doing custom video decoding like this will still be a lot less
efficient and user-friendly than using native, hardware-accelerated
.mp4/H.264/AAC playback, but would be *much* faster for iPhones and iPads
than the JavaScript version... and a hell of a lot better as a fallback
position than "no audio/video for you".
(Unfortunately you can't download an installable build yet due to Apple's
restrictions on third-party app installation. If anybody's interested in
testing, I'll continue to do some experimenting on this on the weekends and
could make builds available via TestFlight. Let me know!)
-- brion
Here's your deploy highlights for next week:
Full schedule for the next two weeks here:
https://wikitech.wikimedia.org/wiki/Deployments#Next_2_weeks
== Monday ==
* MediaWiki 1.23wmf2 will be deployed to remaining test wikis
(mediawiki.org, loginwiki, and test.wikidata.org)
** If the above goes smoothly, 1.23wmf2 will be deployed to all
non-Wikipedia wikis
** This is due to an intial problematic deploy on Thursday Oct 31st of
1.22wmf2.
* Updates to CentralNotice (see above linked page for details)
== Tuesday ==
* CirrusSearch enabled on: se.wikimedia.org, ast.wikipedia.org,
gu.wikipedia.org, el.wikipedia.org, and fr.wikisource.orghttps://www.mediawiki.org/wiki/Search#Timeline
== Thursday ==
* MediaWiki 1.23wmf2 to all Wikipedias
* MediaWiki 1.23wmf3 to all testwikis
** MassMessage update on test wikis (minus mediawiki.org)
** BetaFeatures with CommonsMetadata and MultimediaViewer to Commons and
MetaWiki
As always, let me know if you have any questions!
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Wikimedia is one of the ten organizations selected to participate in
Google Code-in 2013! This means that on November 18 we will start having
hundreds of 13-17 year old students looking at Wikimedia tech tasks to
be completed.
The announcement:
http://google-opensource.blogspot.com/2013/11/mentoring-organizations-for-g…
Our GCI page:
https://www.mediawiki.org/wiki/Google_Code-In
If you are involved in FOSS Outreach Program for Women in any way you
can stop reading here. Otherwise, please stay with us. This program is a
very good opportunity to find fresh young helpers willing to complete
that little task that has been sitting in your ToDo list for too long.
WE NEED STRUCTURE
Andre Klapper and me are the Wikimedia org admins and we will take a lot
of dirty and boring work so the rest of you don't have to. However, we
won't be able to make it without meta-mentors.
META-MENTORS are seasoned contributors that have a good knowledge of the
relevant technologies, features and people involved in a specific area.
They are also mentors of some tasks in their areas, but their role
includes looking for more mentors that bring more tasks, and coordinate
with them. GCI organizations get an average of 150-200 tasks completed
during the program. You see the need for a distributed structure that
scales.
GCI has five areas:
* Code (proposing MatmaRex, helped by ?)
* Documentation/Training (guillom, helped by ?)
* Outreach/Research (?, helped by Quim - or the other way around)
* Quality Assurance (proposing Željko, helped by Andre)
* User Interface (Pau and Jorm)
Please, help substituting question marks with names.
WE NEED MENTORS BRINGING TASKS
The deal is simple: join GCI as mentor and bring your little tasks (that
would take you 2-3 hours to complete). You need to describe the tasks
for a newcomer, linking to the resources needed to complete them. You
also need to be ready to answer the questions of the students assigning
your tasks to them.
We will have more specific instructions for mentors before the beginning
of the program.
WE NEED PEOPLE PROPOSING TASKS
Even if you can't mentor a specific task we still want to know about it.
All we need is a bug report with
gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
added to its Whiteboard field to make it easy to track them. Please CC
the related meta-mentors, Andre and me.
Questions? Please ask and you will help us improving our documentation.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Dear all,
I am happy to announce that a Memento time travel extension for MediaWiki is now available for testing and feedback. The extension can be downloaded via [1] and requires MediaWiki version 1.21.1+. A demonstration wiki equipped with the Memento extension is available [2].
The extension is fully compliant with the Memento specification [3] that will soon be released as an RFC. This new extension is the result of a significant re-engineering effort guided by feedback received from Wikipedia experts to a previous version [4]. The effort is generously funded by the Andrew W. Mellon Foundation and is a collaboration between Old Dominion University and the Los Alamos National Laboratory.
The Memento protocol extends HTTP with content negotiation in the datetime dimension. The document [5] is helpful to get an insight in the added value that support for the protocol can bring to MediaWiki platforms. The 1-minute screencam [6] and the 10-minute screencam [7] illustrate Memento at work in the Web at large. The latter pays significant attention to temporal navigation in Wikipedia, and hence illustrates that the Memento Team considers time travel in MediaWiki platforms a major use case of the protocol.
The Memento protocol is not yet natively supported by browsers but a fully functional extension for Chrome is available [8]. The Memento Team hopes that adoption by MediaWiki platforms, in addition to the existing adoption by major web archives [9] and support by the International Internet Preservation Consortium [10], may lead browser manufacturers to consider implementation.
The Memento team is eager to get feedback to the extension in order to guide its further development to a state where it fully meet the needs of the MediaWiki community. A separate mail will list some issues that came up during the development process to which explicit feedback is solicited. But feedback beyond those issues is very welcome and hopefully some experienced extension developers will find the time to scrutinize the code base and help us to improve it.
Very much looking forward to your feedback.
Herbert Van de Sompel on behalf of the Memento Team
http://public.lanl.gov/herbertv/
[1] http://www.mediawiki.org/wiki/Extension:Memento
[2] http://ws-dl-05.cs.odu.edu/demo-302-recommended-relations/
[3] http://www.mementoweb.org/guide/rfc/ID/
[4] https://bugzilla.wikimedia.org/show_bug.cgi?id=34778
[5] http://www.mementoweb.org/wikipedia/
[6] http://www.youtube.com/watch?v=0_70lQPOOIg
[7] http://www.youtube.com/watch?v=WtZHKeFwjzk
[8] http://bit.ly/memento-for-chrome
[9] http://mementoweb.org/depot/
[10] http://netpreserve.org