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
Hi! I think you may want to contact the mentors directly (there is several
listed) and ask them for a more detailed spec on the project.
Siko runs the IEG program [1] and I have forwarded your message to the
Committee as well to see anyone who wants to volunteer and help you during your
work
I wish to edit the documentation of Wikidata help pages. For that need to
learn some advanced editing options like creating anchors for topics in a
page. Where can I find a possible help ???
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Thu, Mar 6, 2014 at 7:29 AM, Sumana Harihareswara
suma...@wikimedia.orgwrote:
* automate more of the systems that help developers test new code to find
bugs early (Test Infrastructure
Engineer
I haven't read this topic carefully but I suggest we make a sprint for
pywikibot issues (e.g. very important bugs or a bug triage to take
care of 200 left uncategorized/unknown importance bug)
I have another idea that someone have a presentation about how we can
help pywikibot I don't know if
2014-03-06 13:43 GMT+02:00 Amir Ladsgroup ladsgr...@gmail.com:
I have another idea that someone have a presentation about how we can
help pywikibot I don't know if others like this idea too
Amir, I won't be in Zurich, but I would love to see (and use) such a
presentation.
Thanks,
Strainu
I'll be there if I can get the visa in time and I love to have a
presentation about it but I'm not sure others will like the idea or
not
Best
On 3/6/14, Strainu strain...@gmail.com wrote:
2014-03-06 13:43 GMT+02:00 Amir Ladsgroup ladsgr...@gmail.com:
I have another idea that someone have a
On Sun, Feb 23, 2014 at 6:43 AM, Brion Vibber bvib...@wikimedia.org wrote:
Just an update on this weekend project, see the current demo in your
browser[1] or watch a video of Theora video playing on an iPhone 5s![2]
[1] https://brionv.com/misc/ogv.js/demo/
[2]
Hi,
On Thu, 2014-03-06 at 09:24 +, Anjali Sharma wrote:
I wish to edit the documentation of Wikidata help pages. For that need to
learn some advanced editing options like creating anchors for topics in a
page. Where can I find a possible help ???
https://www.mediawiki.org/wiki/Help:Links
Hello,
I have added a job in Jenkins which runs the Mediawiki core PHPUnit test
suite using the Facebook HipHop virtual machine.
The job is now being run along other testing jobs. It is slightly
slower (4 min 30s) than the other jobs so that would delay the reporting
back to Gerrit by roughly a
On 03/06/2014 05:26 AM, Andre Klapper wrote:
Hi,
On Thu, 2014-03-06 at 09:24 +, Anjali Sharma wrote:
I wish to edit the documentation of Wikidata help pages. For that need to
learn some advanced editing options like creating anchors for topics in a
page. Where can I find a possible help
On 03/06/2014 04:04 AM, Amir Ladsgroup wrote:
I'll be there if I can get the visa in time and I love to have a
presentation about it but I'm not sure others will like the idea or
not
The process for anybody in this situation is simple;
# Create a new topic at
On Thu, Mar 6, 2014 at 8:12 AM, Antoine Musso hashar+...@free.fr wrote:
The job is now being run along other testing jobs. It is slightly
slower (4 min 30s) than the other jobs so that would delay the reporting
I back to Gerrit by roughly a minute. I have made the job to timeout
after 8
I made this topic:
https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Topics#How_to_help_pywikibot
I'll send a note in pywikipedia-l and discuss about how and who want
to present at the Hackathon.
Best
On 3/6/14, Quim Gil q...@wikimedia.org wrote:
On 03/06/2014 04:04 AM, Amir Ladsgroup
On 6 mrt. 2014, at 14:26, Brion Vibber bvib...@wikimedia.org wrote:
Spent some time tonight on audio/video sync; it's now working both with
native Web Audio API and with the Flash audio shim.
Check out a video with someone talking, and marvel at the synchronization!
Ryan, *thank you* very much for the research, and for contacting the
Liberation Sans maintainers with specific bugs.
On 03/05/2014 02:00 PM, Ryan Kaldari wrote:
What do people think of the following stack:
Arimo, Liberation Sans, Helvetica Neue, Helvetica, Arial, sans-serif;
After so much
Hi everybody,
I cannot believe I have to say something about this, but I guess it's no
surprise.
Wikipedia has a notorious policy against edit warring, where users are
encouraged to discuss changes and achieve consensus before blindly
reverting. This applies even more so to Gerrit, since changes
On Thu, Mar 6, 2014 at 8:29 PM, Tyler Romeo tylerro...@gmail.com wrote:
1) not everybody is subscribed to mobile-l, so you cannot expect the
original reviewers to see or know about it
2) this is an issue with MobileFrontend, not MediaWiki core
3) code being merged does not automatically cause
Hello,First of all sorry for inappropriate way of presenting the content
,nbsp;Asnbsp;advisednbsp;by community members
I present my ideas regardingnbsp;Multilingual, usable and effective
captchasnbsp;at my proposal page for GSOC-2014 given here
On 6 March 2014 20:21, Quim Gil q...@wikimedia.org wrote:
Ryan, *thank you* very much for the research, and for contacting the
Liberation Sans maintainers with specific bugs.
Seconded! Arguing is one thing - bothering to go out and finding out
what people actually think is quite another.
In over two years at WMF I have never been involved in a discussion like
this, but here goes:
In this case, I think it was entirely appropriate to revert immediately and
pick up the pieces later. The source of the code is immaterial, if Tim
Starling or Brion Vibber had merged this we would have
On Thu, Mar 6, 2014 at 4:15 PM, Steven Walling steven.wall...@gmail.comwrote:
If your patch causes a serious UX regression like this, it's going to get
reverted. The core patch involved was being deployed to Wikimedia sites /
impacting MobileFrontEnd users today. If we had more time in the
Special:Code automatically generated a list of followup revisions for each
revision (based on linking/mentioning). It would be nice to have that in
Gerrit.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Another note in case you missed it earlier. If your'e looking in general to
test the Wikipedia app reboot, at the moment the Android APK can be
downloaded from
https://releases.wikimedia.org/mobile/android/apps-android-wikipedia-sprint25.apkand
bugs can be filed via Bugzilla. The iOS build is
On Thu, Mar 6, 2014 at 2:08 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 4:15 PM, Steven Walling steven.wall...@gmail.com
wrote:
If your patch causes a serious UX regression like this, it's going to get
reverted. The core patch involved was being deployed to Wikimedia
Hi Devender, I'm not a developer but I hope my feedback as editor is useful.
On 03/06/2014 12:02 AM, Devender wrote:
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.
Communication in the wikiverse is hard.
To clarify, this is _not_ an issue with MobileFrontend. The same
problem effects users without JavaScript. There was a fundamental
problem with this patch that sadly didn't get caught during code
review. It broke the workflow of mobile on an important page
On Thu, Mar 6, 2014 at 2:08 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 4:15 PM, Steven Walling steven.wall...@gmail.com
wrote:
If your patch causes a serious UX regression like this, it's going to get
reverted. The core patch involved was being deployed to Wikimedia
From: David Gerard dger...@gmail.com
Date: Thu, Mar 6, 2014 at 9:44 PM
Subject: Re: [Wikitech-l] Should MediaWiki CSS prefer non-free fonts?
To: Wikimedia developers wikitech-l@lists.wikimedia.org
(Veering off topic: So what does WMF use for a usability lab, anyway?)
...not sure what Kaldari
To take a couple of steps back...
This happened because testing isn't robust enough?
That should be discussed and followed up on.
On Thu, Mar 6, 2014 at 3:34 PM, Brion Vibber bvib...@wikimedia.org wrote:
On Thu, Mar 6, 2014 at 2:08 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar
On Thu, Mar 6, 2014 at 6:34 PM, Brion Vibber bvib...@wikimedia.org wrote:
Is there anything specific in the communications involved that you found
was problematic, other than a failure to include a backlink in the initial
revert?
I think this entire thing was a big failure in basic software
On Thu, Mar 6, 2014 at 3:54 PM, Tyler Romeo tylerro...@gmail.com wrote:
I think this entire thing was a big failure in basic software development
and systems administration. If MobileFrontend is so tightly coupled with
the desktop login form, that is a problem with MobileFrontend. In addition,
On Thu, Mar 6, 2014 at 3:54 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 6:34 PM, Brion Vibber bvib...@wikimedia.org
wrote:
Is there anything specific in the communications involved that you found
was problematic, other than a failure to include a backlink in the
Hi Tyler,
I understand you're frustrated here. As Jon says: communication in the
wikiverse is hard. Also, running a top 10 website is also hard.
Others have covered many of the other points, but I wanted to make sure I
addressed one of the points that hasn't been covered yet:
On Thu, Mar 6,
On 6 March 2014 23:47, Steven Walling steven.wall...@gmail.com wrote:
more automated remote testing and is $35/test (this is really cheap since
the going US rate for an in-person test is something like a $50 Amazon gift
card).
off-topic on off-topic: Offer swag instead. Wikipedia branded
On Thu, Mar 6, 2014 at 4:05 PM, Brion Vibber bvib...@wikimedia.org wrote:
On Thu, Mar 6, 2014 at 3:54 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 6:34 PM, Brion Vibber bvib...@wikimedia.org
wrote:
Is there anything specific in the communications involved that you
On Thu, Mar 6, 2014 at 4:54 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 6:34 PM, Brion Vibber bvib...@wikimedia.org
wrote:
Is there anything specific in the communications involved that you found
was problematic, other than a failure to include a backlink in the
I just wanted to add that in the past, as many people know, we tried a few
different kinds of testing and even hired a usability testing firm to help
us. We conducted research in a lab here in SF and also did some remote
testing, compensating participants with gift cards.
We learned that lab
On 7 March 2014 00:17, Trevor Parscal tpars...@wikimedia.org wrote:
I believe, from lots of first-hand experience and some research on the
subject, that anytime you can get at least 5 users in front of a product
and run them through well written tasks you are going to reveal about 80%
of the
On Thu, Mar 6, 2014 at 4:08 PM, Erik Bernhardson ebernhard...@wikimedia.org
wrote:
Does core have any policies related to merging? The core features team
has adopted a methodology(although slightly different) that we learned of
from the VE team. Essentially +2 for 24 hours before a
It seems that commenters here believe that the patch made it impossible to
create an account if JavaScript was disabled, or via MobileFrontend – this is
obviously not true, it just required an additional confirmation (which was by
design and +1'd by five people). Please stop spreading this
quote name=George Herbert date=2014-03-06 time=15:53:50 -0800
To take a couple of steps back...
This happened because testing isn't robust enough?
That should be discussed and followed up on.
Ish.
The suite of automatic tests caught this bug, actually. It's how the
mobile team found out
So I'm confused on the timeline here.
Did the commit get merged before the testsuite found the breakage, or did
the commit get merged despite the testsuite failing?
Either way sounds like When to merge a changeset needs reviewed.
On Thu, Mar 6, 2014 at 6:38 PM, Greg Grossmeier
On Thu, Mar 6, 2014 at 5:49 PM, OQ overlo...@gmail.com wrote:
So I'm confused on the timeline here.
Did the commit get merged before the testsuite found the breakage, or did
the commit get merged despite the testsuite failing?
The commit was merged late Wednesday. The automated tests that
So the testsuite only runs on merged code and not pending-merge? That
sounds like a large oversight.
On Thu, Mar 6, 2014 at 6:55 PM, Chris McMahon cmcma...@wikimedia.orgwrote:
On Thu, Mar 6, 2014 at 5:49 PM, OQ overlo...@gmail.com wrote:
So I'm confused on the timeline here.
Did the
On 03/06/2014 12:21 PM, Quim Gil wrote:
On 03/05/2014 02:00 PM, Ryan Kaldari wrote:
What do people think of the following stack:
Arimo, Liberation Sans, Helvetica Neue, Helvetica, Arial, sans-serif;
it would be useful to have a table showing
which fonts are rendered by the most popular
quote name=Chris McMahon date=2014-03-06 time=17:55:48 -0700
On Thu, Mar 6, 2014 at 5:49 PM, OQ overlo...@gmail.com wrote:
So I'm confused on the timeline here.
Did the commit get merged before the testsuite found the breakage, or did
the commit get merged despite the testsuite failing?
For the record this the test that alerted us to this issue was the following:
https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/392/testReport/junit/(root)/Create%20failure%20messages/Create_account_password_mismatch_message/
2 problems here - tests run
On Thu, Mar 6, 2014 at 6:07 PM, OQ overlo...@gmail.com wrote:
So the testsuite only runs on merged code and not pending-merge? That
sounds like a large oversight.
Picture in your mind every branch pending merge for every extension in
gerrit. Imagine how many of those branches are eventually
I wonder in future if it might be practical useful for test failures like
this to automatically revert changes that made them or at least submit
patches to revert them that way it's clear how and when things should
be reverted.
On 6 Mar 2014 18:09, Chris McMahon cmcma...@wikimedia.org wrote:
On Thu, Mar 6, 2014 at 9:21 PM, Jon Robson jdlrob...@gmail.com wrote:
I wonder in future if it might be practical useful for test failures like
this to automatically revert changes that made them or at least submit
patches to revert them that way it's clear how and when things should
be
Hi all,
the multimedia team [1] had a chat about some architectural issues with
MultimediaViewer [2] today, and Robla has pointed out that we should
publish such discussions on wikitech-l to make sure we do no reinvent to
many wheels, so here goes. Comments pointing out all the obvious solutions
Tyler wrote:
1. Fix the extension quickly
2. Revert the change
3. Undeploy the extension until its fixed to be compatible with core
So to summarize, #3 is obviously not an option. For #2, are we supposed to
block core development, and let this bug persist indefinitely, because of a
Hi, Devander. Have you looked at WikiTrust[0]? It does roughly what you
describe (though I don't think the live demo works anymore).
[0] https://en.wikipedia.org/wiki/Wikipedia:WikiTrust
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Thu, Mar 6, 2014 at 10:13 PM, George Herbert george.herb...@gmail.comwrote:
Based on the timing description here, it seems more like Either rush 1 or
rush 2.
This is also not true. Something does not have to be reverted in Gerrit in
order for it to be undeployed from production. If there
On 07/03/14 09:07, Chris McMahon wrote:
In over two years at WMF I have never been involved in a discussion
like this, but here goes:
In this case, I think it was entirely appropriate to revert
immediately and pick up the pieces later. The source of the code
is immaterial, if Tim Starling
On 07/03/14 11:38, Greg Grossmeier wrote:
The suite of automatic tests caught this bug, actually. It's how the
mobile team found out about it as they got to work this morning. So the
testing is quite robust.
As I understand it, there was no bug, it was just a controversial
design change.
On 07/03/14 03:58, Tim Starling wrote:
I would never have merged it, because it had a -1 from Steven Walling,
apparently speaking on behalf of others on design-l. I think changes
should be made by consensus.
The changeset was the result of the discussion on the Design list. The
reason Steven
On Thu, Mar 6, 2014 at 7:08 PM, Erik Bernhardson ebernhard...@wikimedia.org
wrote:
Does core have any policies related to merging? The core features team
has adopted a methodology(although slightly different) that we learned of
from the VE team. Essentially +2 for 24 hours before a
Tim Starling wrote:
I would never have merged it, because it had a -1 from Steven Walling,
apparently speaking on behalf of others on design-l. I think changes
should be made by consensus.
The change also had five +1s, as noted in this thread. I find it
interesting that, to you, consensus now
Hey,
This is Nitika from India. I am comfortable with c/c++ , Php,
Javascript,HTML and MySql. In the projects listed on
https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8
I am very interested in the project Book Management in
Wikibooks/WikiSource (mentor :
61 matches
Mail list logo
