I'm Manoj. I contribute mainly on Hindi wiki. Regarding software issues I
had one suggestion since the very beginning ( i joined actively in Aug-13).
In India, internet connectivity is very poor in semi urban and rural areas
which has long kept 70% of Indian population away from Internet. Starting
from last 2-3 years this is changing very rapidly thanks to smartphone
revolution. Presently we have millions (soon it may be billion) of
smartphones, primarily Android, in hands of rural young indians. So need of
the hour is to work more on android app which is mostly designed for
viewing rather than editing. In this direction software team still has
miles to go. And I can bet this is the future of wiki, especially in India.
If this issue is not handled NOW, it may be late to attract new generation.
We must also try to convince phone manufacturers and marketers to bundle
Wiki english and Indian languages wiki to be available as pre-installed
apps on their phones. For them it will be an additional selling point.
On Feb 12, 2015 3:27 AM, "Asaf Bartov" <abartov(a)wikimedia.org> wrote:
This is a significant shift in Engineering processes
at the Wikimedia
Foundation. I want to make sure it reaches people not subscribed to
Wikimedia-l or wikitech-l.
---------- Forwarded message ----------
From: Damon Sicore <dsicore(a)wikimedia.org>
Date: Wed, Feb 11, 2015 at 12:31 PM
Subject: [Wikimedia-l] Engineering Community
To: "wikimedia-l(a)lists.wikimedia.org" <wikimedia-l(a)lists.wikimedia.org>
We are changing our engineering processes to improve how we engage with
you -- our valued contributors and editors -- around software development.
We are beginning with the collaborative buildout and deployment of
VisualEditor. We are moving community engagement processes and product
decisions into earlier stages of development, and making them iterative. In
a perfect world this process would start prior to feature development, but
in this case VisualEditor is already in-flight, so your participation now
is critical. With your participation, we can work together to ensure this
new process works.
In this new process, we commit to:
• Collectively identify success criteria for each target audience, from
new editors (simple feature set) to expert editors (complex feature set).
• Ensure success criteria represents the quantified and qualified goals.
The feature will only be shipped when the success criteria is met.
• Enable the feature for only portions of specific audiences that would
best benefit (a process known as “incremental roll-out”) at a time.
• Triage and prioritize all bugs and feature requests on a weekly basis to
ensure they are addressed in a timely fashion. Publicly post responses,
assessment, and target implementations. This will replace the RFP process
and ensure we are tracking on all requested features efficiently.
How you can engage:
• Report bugs or enhancement requests in Phabricator:
• Join any of the weekly triage meetings to nominate a release blocker.
Please see the instructions at:
• Participate in development. You can find the team on IRC in the
#mediawiki-visualeditor channel on irc.freenode.net
We are excited to get this long-standing feature to the level of quality
and success we all want and need. It is a collective effort. You are not
only a stakeholder, but an active contributor in this work. We want to all
to be proud of the outcome. Please participate now.
All my best,
VP of Engineering
Wikimedia-l mailing list, guidelines at:
Wikimedia Foundation <http://www.wikimediafoundation.org>
Imagine a world in which every single human being can freely share in the
sum of all knowledge. Help us make it a reality!
Wikimediaindia-l mailing list
To unsubscribe from the list / change mailing preferences visit