Would there be interest in integrating the work on authorship computation?
This would not be an extension; it would be ... server-side development
that could fit well with a Summer of Code?
On Wed, Mar 20, 2013 at 4:43 PM, Quim Gil <qgil(a)wikimedia.org> wrote:
It's time to start defining what we want our
Google Summer of Code to be
all about. Let's look at the ideas we are proposing to potential students:
Many of the ideas listed there are too generic ("Write an extension"),
improvements of existing features ("Improve Extension:CSS") or
work-in-progress tasks ("Fix Parsoid bugs"). Many others are not directly
related with development, and therefore not suitable either for GSOC.
After this filtering, we seem to be left with:
* Article evolution playback tool idea
* An easy way to share wiki content on social media services
* Write an extension to support XML Sitemaps without using command line
* Add support for x3d 3D files to MediaWiki
* Allow smoother and easier Wikimedia Commons pictures discovery
* Build an interwiki notifications framework and implement it for
* Automatic category redirects
(If you think your project should also be considered here please speak up!)
Most of these projects seem to be extension (and PHP?) centric. Can we
have more diversity? Maybe gadgets and templates are too simple for a GSOC
project? What about the mobile front? Do we have skin development projects
that could make it here? Anything in the DevOps area? Anything the
MediaWiki core maintainers would like to see happening?
It would be also nice to have more candidates benefiting specific
Wikimedia projects. Beyond Wikipedia, we have several proposals related to
Commons. Wikidata seems to be joining soon. What else? Could this be a
chance to help Wiktionary, Wikibooks or any other project with specific
needs craving for tech attention?
Also to the many students that have already showed their interest: feel
free pushing your project ideas now!
Technical Contributor Coordinator @ Wikimedia Foundation
Wikitech-l mailing list