Hello,
A quick reminder that the Language Engineering IRC office hour is happening
later today at 1700 UTC on #wikimedia-office. Besides project updates, we
have 30 mins open for discussions about the internationalization and
localization projects in Google Summer of Code (GSoC) and Outreach Program
for Women (OPW). Please see below for event details, agenda and local time.
Thanks
Runa
Event Details:
==========
# Date: March 12, 2014 (Wednesday)
# Time: 1700-1800 UTC, 1000-1100 PDT (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140312T1700)
# IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
======
1. Ongoing Projects - Content Translation tool
2. GSoC and OPW - open house for Language Engineering projects
3. Q & A
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Fri, Mar 7, 2014 at 10:09 PM
Subject: Language Engineering IRC Office Hour on March 12, 2014 (Wednesday)
at 1700 UTC
To: MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>,
Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikimedia Mailing
List <wikimedia-l(a)lists.wikimedia.org>,
wikitech-ambassadors(a)lists.wikimedia.org
[x-posted]
Hello,
The Wikimedia Language Engineering team will be hosting the monthly IRC
office hour on March 12, 2014 (Wednesday) at 1700 UTC/ 1000 PDT on
#wikimedia-office.
In this edition, we will be talking about our ongoing projects, like the
Content Translation tool[1]. Also, we would like to extend this invitation
specially to the students who are looking forward to participate in Google
Summer of Code (GSoC) 2014 and Outreach Program for Women (OPW) - Round 8,
for the Language Engineering projects[2] under Wikimedia. We will be happy
to answer your questions about our work and projects. Please see below for
the event details and check for local time at your location.
Questions can also be sent to me before the event. See you all at the IRC
office hour!
Thanks
Runa
[1] https://www.mediawiki.org/wiki/Content_translation
[2]
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Intern…
Event Details:
==========
# Date: March 12, 2014
# Time: 1700-1800 UTC, 1000-1100 PDT (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140312T1700)
# IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
======
1. Ongoing Projects - Content Translation tool
2. GSoC and OPW - open house for Language Engineering projects
3. Q & A
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hi,
I am Dinu Kumarasiri an undergraduate at Department of Computer Science and
Engineering, University of Moratuwa. I am Interested in Wikidata Outreach
project for the FOSS outreach Program for Women.
Following is the link to the proposal of my outreach campaign.
https://docs.google.com/document/d/1Vkj8d9q8WiVe2GZ2wkcIwVOLdDr3KaGjxa0V3mI…
I hope to do this campaign in two categories ; improving documentation and
social media campaign. A detailed plan of the outreach campaign can be
found in the given link.
Media wiki page for the project proposal is given below:
https://www.mediawiki.org/wiki/Project_Eclipse_:_Wikidata_Outreach_Project
I hope to hear some feedback on this and any improvements i can make.
Thanks in advance!!
--
Dinu Kumarasiri*,*
*Undergraduate,*
*Department of Computer Science and Engineering,*
*University of Moratuwa*
--
Dinu Kumarasiri*,*
*Undergraduate,*
*Department of Computer Science and Engineering,*
*University of Moratuwa*
After a lot of analysis, discussions and preparations, today we announce
that WAP/WML support has been removed from MobileFrontend. Our sites
were running HTML only for a couple weeks now, so since we received no
complaints, we pulled the trigger. Final deprectation might take a
couple more weeks, but we're already beyond the point of no return.
I would like to thak everyone who participated in this effort!
This wasn't an easy decision, however the share of WAP has fallen
tremendously and we can find better use for engineering resources we
would have needed to maintain WAP support functional.
--
Best regards,
Max Semenik ([[User:MaxSem]])
On 8 mrt. 2014, at 21:48, Russell Nelson <russnelson(a)gmail.com> wrote:
> On Fri, Mar 7, 2014 at 7:36 PM, Derk-Jan Hartman <d.j.hartman+wmf_ml(a)gmail.com> wrote:
>
> This is thinking way too simple. Would it be nice to be able to do this ? Sure, but we already have dynamic maps. WikiMiniAtlas, the german OSM map. Those even have area highlights these days. Can they be better ? sure, is that something difficult, is it really needed ? No not really x2. Wikipedians are much more focused on making static maps usually.
>
> Refutation: http://en.wikipedia.org/wiki/Interurban_and_streetcar_railways_in_Syracuse,…
> That map is utter crap, completely unusable for any kind of mobile usage, even if it were georeferenced.
>
>
> Is it possible / useful to generate thematic renderings of OSM tiles? Sure, and they look really good, for example here: http://www.itoworld.com/map/15
>
> My feeling is that Wikipedia has desperately needed a map generator, whether static or dynamic, for at least five years now. Yet something always comes between Wikipedia and OSM for some reason. I think it's because people keep saying that that's too easy! We need to do something better, something more complicated, something that's a real challenge. Well, if it's so simple, why doesn't every page with coordinates have a map?? Obviously, it's NOT that simple.
I see I failed to make my point. Its indeed NOT simple. We keep thinking that it's simple: 'build some technology and people will come' but models like that have proven to fail quite often (especially on en.wp). You need to find the user stories, find the building blocks and see where you get the most return for your money/effort. If you want something to succeed, you need a very concerted effort that leads to integration and acceptance. Not just one thing: Let's build the map. You need a line of careful steps with goals and metrics, reflection and evaluation. One of those steps might be to "build the map", but it's definitely not the only one.
DJ
Yesterday we were so busy with the beginning of GSoC and FOSS OPW
round 8 that I didn't have time to post about the end of OPW round 7:
https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_7
Quite silently, the six teams participating in this round have set a
new benchmark for future mentoring programs. All of them have
delivered functional features that are as published / merged /
deployed as it is advisable in a complex community project like ours.
All of them had slight changes of plans, require more testing and
fine-tuning... but this is the usual situation of any free software
project four months after its inception.
Check the results:
Anu's upload wizard with OSM support
http://uploadwizard-osm.wmflabs.org/wiki/Special:UploadWizard
Diwanshi's Wikipedia API courses in Codecademy
http://www.codecademy.com/courses/web-beginner-en-vj9nh/0/1http://www.codecademy.com/courses/web-beginner-en-yd3lp/0/1
Brena's prototype of mediawiki.org's redesigned homepage
https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview
Be's clean up of Parsoid's round-trip testing UI is merged
https://gerrit.wikimedia.org/r/#/q/owner:bebirchall%2540gmail.com,n,z
Maria's clean up of Parsoid's tracing/debugging/logging is merged
https://gerrit.wikimedia.org/r/#/q/owner:maria.pacana%2540gmail.com,n,z
Niharika's compact language links is part of this week's deploymeent
train as Beta feature
https://www.mediawiki.org/wiki/Universal_Language_Selector/Design/Interlang…
Not coincidentally, these interns have also excelled in regular
reporting, combining in most cases weekly reports with sporadic blog
posts. Check the table at the OPW wiki page.
Of course a fair part of the merit goes to the mentors, most of them
first-timers. We still must wrap up the projects and recollect the new
lessons learned.
One area where we still want to improve is in the continuity of these
contributors, now as regular volunteers. For this, the role of the
mentors and other experienced contributors is key. Please approach the
not-interns-anymore, and propose them new tasks or new areas to
contribute to. In addition to this, Sumana has been discussed with
each of them possible opportunities within Wikimedia.
CONGRATULATIONS TO THESE SIX TEAMS! Thank you for the work you have
done, and we hope to see you around, jumping on new tasks.
As always, ideas and criticism are welcome. How can we do better in
the next round of mentoring programs, starting now?
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi,
I am a 4th year student of the Department of Computer Science and
Engineering at Indian Institute of Technology( IIT), Kharagpur, India.
I am good at programming in PHP, MySQL, JavaScript, jQuery, HTML, CSS,
Java, C, C++ and Python. I have done all the important courses including
Machine Learning, Artificial Intelligence, Algorithms, Information
Retrieval, Natural language processing, Advanced Graph theory.
I am very enthusiast to work with Wikimedia in GSOC 2014. I have an idea
which I believe can help improve Wikipedia content:
I want to implement a ranking system of the editors(especially 3rd party
editors) of the Wikipedia through which viewers can differentiate between
the content of the page. This ranking system will
increase the content reliability. We can implement :
1. An extension which take all the editors information--
a. How many times editor has edited this particular page,
b. The number of pages he edited and editor's reputation( i.e number and
type of badge)
We can get this information from the "view history tab and then user info
from the user page" and generate a reliability score by using (i.e Data
clustering <https://en.wikipedia.org/wiki/Cluster_analysis>) for every
line/paragraph of the content for all Wikipedia page. After installing this
extension, user right click on any line to see the reliability score, all
editor info and history in concise form.
2. Make the different color of the line/paragraph if the content of the
line/paragraph is very new and its reliability score is less.
Please let me if I should go with this idea. If not, guide me how to start
working on different idea.
Thanks and Regards
Devender (Linkedin
Profile<http://in.linkedin.com/pub/devender-bindal/27/70b/133/>
)
4th Year Student
Dual Degree(B.Tech+M.Tech)
Computer Science and Engineering
IIT Kharagpur
Phone +91-8967224480
Alternate Email *devender(a)cse.iitkgp.ernet.in
<devender(a)cse.iitkgp.ernet.in>*
I'm very pleased to announce that Chase Pettet is joining the Wikimedia Foundation as Operations Engineer. Chase comes to us from DeviantArt, where he was responsible for their general server management infrastructure, monitoring and networking, as well as supporting the development team(s). Within Wikimedia Operations he will have similar responsibilities, working on Operations infrastructure projects and supporting other Engineering teams with their Operations needs. Chase will be working remotely from his home in Missouri. He started with us yesterday.
Please join me in welcoming Chase!
—
Mark Bergsma <mark(a)wikimedia.org>
Lead Operations Architect
Director of Technical Operations
Wikimedia Foundation
Hi,
Starting today, candidates of Google Summer of Code and FOSS Outreach
for Women can submit their proposals officially. See
https://www.mediawiki.org/wiki/Summer_of_Code_2014https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8
We are hosting an IRC meeting to answer the questions of candidates and
mentors tomorrow Tuesday, March 11, at 15:00 UTC (New Delhi 20:30,
Amsterdam 16:00, San Francisco 8:00 AM).
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140311T08&p1=224…
As Wikimedia did in previous rounds, we are extending the rules of these
projects with a requirement on transparency. All candidates must draft
their proposals in mediawiki.org pages, and they must list themselves in
the tables of candidates at the pages linked above.
This allows the whole community to watch and get involved in discussions
at the related wiki pages, Bugzilla reports, and this list. Please keep
an eye to new submissions. Whoever you are, your feedback is welcome.
Candidates must submit their proposals directly to GSoC and OPW as well,
but thanks to our application template this shouldn't imply more work
that copy & paste:
https://www.mediawiki.org/wiki/Mentorship_programs/Application_template
This time we also have many new mentors. Please get familiar with the
timeline of the programs. Your most important task now is to assess your
candidates, based on their proposal but also on practical assignments
like fixing real bugs related to their projects.
By April 7 we will communicate to Google how many slots we want, based
on the projects proposed that we believe that can succeed. This year the
definition of success will be based on measurable outcome: new feature
functional, merged, and deployed in Wikimedia Labs at least.
Candidates and mentors willing to pass the cut must work with this goal
in mind. Cmpared with last year, we will focus more on the quality of
the projects, not worrying about the quantity of projects we get.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil