From the 101 people that has registered to the Wikimedia Hackathon in
Zürich, 24 are requesting travel and/or accommodation sponsorship (a few
of them apparently by mistake)
https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Scholarships
The deadline for scholarship application is March 16th. Our goal is to
notify applicants by March 17th. Don't miss the deadline!
Five organizations are contributing sponsorship funds and, to be honest,
I still don't know exactly how these five entities will match the budget
available with a common list of accepted participants. Still, it is good
to see more Wikimedia organizations stepping in to support independent
developers, and I have no doubt that we will sort out the process in the
next days.
In order to help sharing common standards between organizations and also
between events, I have started a draft with principles and guidelines at
https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach/Travel_s…
Your help is welcome, regardless of how selfish or altruistic your
motivations are. A good idea is always a good idea, especially when it
comes as an edit to a wiki page.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Dear all,
not sure if this discussion already happens somewhere else, I couldn't
find it on MediaWiki.org or by googling.
The issue at hand is: EU privacy policy 95/46/EG[1] allows usage of
cookies only if
* the user has been informed beforehand in detail
* the user has accepted the cookie
* this acceptance was given freely, without doubt and through by action
(This is the summary by the Article 29 Working Party issued in a Working
Document 02/2013[2] on October 2nd, 2013.)
An example how this is being implemented can be seen on sourceforge.org
or here:
* http://ec.europa.eu/justice/cookies/index_en.htm
I checked MediaWiki:
* anonymous users don't get a cookie, unless the site owner added
something (eg. Google Analytics, Piwik or content served by another site
using cookies)
-> this is fine
* as soon as I click the "Login" button on the wiki, a cookie is being set
-> here we need to work, we need to ask first
So I see two possibilities:
1) catch the click on the "Login" link to show a banner first to ask for
the users consent, on acceptance forward the user to the login page
2) modify the login process to set the cookie after the actual login and
put an additional text on the login page like "by logging in I accept
the usage of cookies by this website"
-> as the login is an action which implies the consent, if we inform
properly on the login form already
Any thoughts about this?
This issue also concerns all our Wikimedia websites, basically every
MediaWiki out there where people may log into.
The Austrian Communication Law (§ 96 Abs. 3 TKG) defines a penalty of
37.000 EUR.
/Manuel
[1]
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31995L0046:en:h…
[2]
http://ec.europa.eu/justice/data-protection/article-29/documentation/opinio…
--
Wikimedia CH - Verein zur Förderung Freien Wissens
Lausanne, +41 (21) 34066-22 - www.wikimedia.ch
Hello, Everyone,
Follows is a link to my project proposal for the Summer 2014 FOSS Outreach
Program for Women. I would like to create a Hacker's Map to make it easier
for new contributors/hackers to get started on Wikidata and then to use the
Map as part of an outreach campaign. Feedback is more than welcome!
https://www.mediawiki.org/wiki/User:JaimeLyn
--
:) JaimeLyn
"I have made this letter longer than usual because I lack the time to make
it shorter."
-- Blaise Pascal
Hi all,
If you haven't followed the teampractices@ list, here's an update on
the Project management tools review that was started a couple months
ago. We're still in the pre-RFC preparatory work, but if you're
interested in this topic, we'd gladly welcome your help :) We're also
happy to answer your questions.
---------- Forwarded message ----------
From: Guillaume Paumier <gpaumier(a)wikimedia.org>
Date: Tue, Mar 4, 2014 at 9:35 AM
Subject: Project management tools review: Help shorten the list of candidates
To: A mailing list to discuss team practices in Wikimedia
organizations <teampractices(a)lists.wikimedia.org>
Hi all,
Thanks again for providing so much input during the consultation
period ( https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review
). It's been extremely useful to understand your respective needs and
workflows.
We've summarized all this input into consolidated requirements. The
goal was to group similar needs to make it easier to identify the
features we need across teams and individuals:
https://www.mediawiki.org/wiki/Project_management_tools/Review/Requirements
Some requirements are conflicting with each other and will require
further discussion later, but overall we're pretty much in agreement
regarding what we want (even if that's a five-legged unicorn).
We've been diligent in including everything that was provided during
the consultation. Nonetheless, please take a look at the list of
requirements if you have a moment, to make sure we haven't missed
anything important.
We've also assembled a list of options, i.e. the possible outcomes of
this review process. The options go from keeping the status quo to
changing a single tool, to consolidating most tools into one. It's
still very much a draft and nothing's final. If we've missed anything
in that table, please be bold and edit it:
https://www.mediawiki.org/wiki/Project_management_tools/Review/Options
We've tried to keep the list inclusive, but now we'd like to shorten
the list of options, so that the upcoming RFC can focus on the options
that actually have a shot.
If you're interested in helping with this, please take a look at the
list of options and discuss them on the talk page:
https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review/Options…
Basically, we want to move items from the "Options under
consideration" section to the "Unlikely options" one. Ideally, we
should keep no more than 2 or 3 candidates, to make the RFC easier.
If you think an option is unavoidable (e.g. "We absolutely must
discuss replacing Trello by Pivotal Tracker"), then say so on the talk
page in the relevant section. Conversely, if you think there's no way
we're using iceScrum, leave a comment on the talk page. We'll assess
consensus collaboratively and hopefully get rid of unlikely options.
This is a collaborative process: we need your help so others don't
make decisions on your behalf. Please take a few minutes to review the
options and give your opinion. It's Notavote; think of it as a sane
version of RfD ("you must be new around here?").
Let us know if you have any questions and we'll do our best to answer :)
Andre and Guillaume
--
Guillaume Paumier
Technical Communications Manager — Wikimedia Foundation
Hi all,
I'm trying to create a fix for the above mentioned bug. But I have some
doubts about the description. It says to change the date format "dd mm" to
"dd-mm". So the only change needed is to add a hyphen if there is a date
and then a month? (Other than the decimal point change).
I have already fixed the bug according to what I have understood (which is
mentioned above). Please explain me how to push it to the github (I found
the instructions in [1]. Relevant project name and the needed branch name
is what I want. Or is there any other way to submit the patch?)
[1]https://gerrit.wikimedia.org/r/Documentation/user-upload.html
--
Maduranga Siriwardena
Undergraduate
University of Moratuwa, Faculty of Engineering
Department of Computer Science and Engineering
Trying again with changed subject. I would really appreciate someone
reviewing the changes below. And I would appreciate it even more if this
could be done soonish. Deadline for student applications for gsoc is in a
week and if these patches need additional work then it's going to get tight.
Cheers,
Stephan
Sent from my mobile
---------- Forwarded message ----------
From: "Stephan Gambke" <s7eph4n(a)gmail.com>
Date: Mar 11, 2014 12:18 AM
Subject: Re: [Wikitech-l] GSoC Proposal : Simultaneous Modification of
Multiple Pages with Semantic Forms
To: <wikitech-l(a)lists.wikimedia.org>, "
Semediawiki-user(a)lists.sourceforge.net" <
Semediawiki-user(a)lists.sourceforge.net>
Cc:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
@wikitech-l:
Could a core developer with a database background please have a look
at Pawan's patches:
* https://gerrit.wikimedia.org/r/#/c/110503/
* https://gerrit.wikimedia.org/r/#/c/110949/
I tried reviewing them, but I really don't know much about the MW
database structure.
@Semediawiki-user:
Including the SMW user list as this project concerns SMW/SF. Please
feel free to comment on the proposal as suggested by Pawan.
Cheers,
Stephan
On 2014-03-09 18:22, Pawan wrote:
> Hi, I am Pawan Kumar D. I am a final year Computer Sciene student
> from IIT Roorkee, India.
>
> More info on me can be found my user
> page<https://www.mediawiki.org/wiki/User:Pawanseerwani_1> .
>
> I intend to work on a GSoC project under this organization. I have
> made a proposal for the following project : Simultaneous
> Modification of Multiple Pages with Semantic
> Forms<
https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014#Simultaneous_Modi…
>
>
>
Do go through the project .
> I would be happy to answer any queries or suggestion on the project
> here but I would appreciate if it could be done at the
> corresponding discussion
> page<
https://www.mediawiki.org/wiki/User_talk:Pawanseerwani_1/GSoC_proposal>
> so that its all at one place and can be easily accessible.
>
> Thanks, Pawan kumar D IIT Roorkee
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTHlYEAAoJENc2Q4BsPGAQ9sYP/1mTd82Av68WftHC+BGgKOqm
X4Y+m+HnnfM3k1gYLWd0GUmc9krXMrUpwS6zB+Mkdx1CN9SKT/x7n/nfC6+4f/91
1S8neEEyphoDdEVbm3PMVPB6ggKXUDhUSTCui50Mxzq57vc726EZo9h17wGxkM4w
8d1HPoQi1txaxoQoJiVkYS42LiEoSiPqRiAMIP39g9UcrRoNHHjOyPQ0M1UtdQL1
vbWb+Csvkl517rTDoVoLuFulSLAaSVHB4QuJhx1oXsAaAKM09rrqqKKQHs72AAZe
g+va92zxzv+zq3pceeUxGKtYN0V5+yCRXXZF8Jrd3NTTMqwhoQWwJKG9m/tyiijE
rR93ZY1GvfPvlCiqC1NjZSIwxlnCOjpiKOt/E1Pc2Po7kojuH0fyNIEEpv+R9gTF
6ZjDYzU0cqMqMWZm55BDEs7DS9tiSaNyJKlgjXkHZEG6ISW6x/OESmThg2FQgFuD
0ZghqrSnG3lDPkXTRTQy117sRYAtmDWu1EYu89/Sd+YcPdtga9+m1GAXAqsIYyvS
OY4+iMGe4WZGrMUnPnhY1LmYOlS5Z3qYUg2IXzriiVWI6VigMR080/7FgLbD6WMX
8BiLs3Br5YqvTPnA8LjzeRY5dIkW0DshI1FDU1U2+ufOO8mm2kv9lp2unftc3QXI
S/s/iFMRHYDxDCAj+dSX
=4rTp
-----END PGP SIGNATURE-----
Please forward this email wisely. Yes, we need your help getting the word
out.
So far, all our GSoC candidates come from only two (neighbor) countries:
India and Sri Lanka. While we are very happy seeing how popular Wikimedia
is among technical students in the Indian subcontinent, we are concerned
about the lack of candidates from anywhere else.
https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014#Candidates
GSoC 2013 had accepted students from 69 countries [1], and we have
participants from eight.[2] We can discuss about the deep causes of this
situation but... Considering that we have less than 9 days before the GSoC
deadline for students (March 21 @ 19:00 UTC) we should focus on finding new
candidates.
There is still time to become a strong GSoC candidate for Wikimedia. Many
project ideas in our GSoC page (linked above) have mentors available and no
candidates yet. Go for them! Also, since our evaluation of candidates is
based on their proposals published in mediawiki.org, Google's deadline is
not a hard stop to keep improving your plans together with your mentors.
April 7 is when we need to decide how many slots we will request, meaning
how many teams (candidates and mentors with a common plan) we believe that
can complete GSoC 2014 successfully. That date is more than three weeks
from now.
Diversity is an important factor for Wikimedia. We are putting a lot of
effort promoting gender diversity in our outreach programs, and we are
seeing good progress. It would be surprising to realize that a global
project like Wikimedia has a serious problem with geographical diversity.
Your ideas and actions to fix this situation are welcome.
[1] https://code.google.com/p/google-summer-of-code/wiki/ProgramStatistics
[2] https://www.mediawiki.org/wiki/Summer_of_Code_2013
PS: in comparison, FOSS OPW is doing a lot better, with five candidates
from four countries
https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8#Cand…
coincidence?
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi Everyone!
I plan to propose a GSOC project through Wikimedia this year, based around
the idea of Parsoid-based online-detection of broken wikitex
t. The original idea of the project is defined here [1], Which is to
develop a tool that will use parsoid to fix broken wikitext found while
parsing wiki pages and then develop a user interface for editors to fix
broken wikitext. But after few discussions on the project with the parsoid
team, We found out that we already have tool [2] which has a decent UI and
which performs same functions. But it lacks the fixup information that
parsoid generates while parsing wiki pages. So through my GSOC project we
plan to integrate this information with the tool.
After having discussions with parsoid devs, I have written an application
draft under my username [3].
I would be really thankful, if I get some feedback.
Links:
[1]-
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Parser…
[2] -
https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Check_Wikipedia
[3] - https://www.mediawiki.org/wiki/User:Hardik95/GSoC_2014_Application
More:
Bug Link - https://bugzilla.wikimedia.org/show_bug.cgi?id=46705
Regards
Hardik Juneja
Wiki Technology,
Greetings. I would like to invite interested participants in the wikitech-l mailing list to support and to participate at the new W3C Collaborative Software Community Group.
http://www.w3.org/community/groups/proposed/#collaboration
The mission of the Collaborative Software Community Group is to provide a forum for experts in collaborative software and groupware for technical discussions, gathering use cases and requirements to align the existing formats, software, platforms, systems and technologies (e.g. wiki technology) with those used by the Open Web Platform. The goal is to ensure that the requirements of collaborative technology and groupware can be answered, when in scope, by the Recommendations published by W3C. This group is chartered to publish documents when doing so can enhance collaborative technology and groupware. The goal is to cooperate with relevant groups and to publish documents to ensure that the requirements of the collaborative software and groupware community are met.
Kind regards,
Adam Sobieski