That is a really good opportunity. We also have http://meta.wikimedia.org/wiki/Wikisource_roadmap, that we set up at Wikimania 2012. Few of those thought are now in the Wikisource Grant proposal, too: http://meta.wikimedia.org/wiki/Grants:IEG/Elaborate_Wikisource_strategic_vision
I would say that a proper metadata handling system is maybe the first priority, but maybe we can accomplish that via Lua templates on WS and metadata stored in Wikidata. Another thing would be working with OKFN tools for seeking and integration (TEXTUS, for example). http://textusproject.org/ Moreover, Djvu support/handling was an interest also of the WMF: http://meta.wikimedia.org/wiki/Wikisource_roadmap#Djvu Well, there's a lot of stuff we can do :-) Aubrey On Sat, Mar 23, 2013 at 3:02 AM, billinghurst <[email protected]>wrote: > It was suggested to me that the Wikisources should be paying attention to > the opportunity available through WMF's participation in Google Summer of > Code. > > I have started a discussion at > > https://wikisource.org/wiki/Wikisource:Scriptorium#Wikisources_asked_for_ideas_re:_Google_Summer_of_Code > > Regards, Billinghurst > > -------- Original Message -------- > Subject: [Wikitech-l] Missing project ideas for GSOC > Date: Wed, 20 Mar 2013 16:43:23 -0700 > From: Quim Gil <[email protected]> > Reply-To: Wikimedia developers <[email protected]> > Organization: Wikimedia Foundation > To: Wikimedia developers <[email protected]> > > 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: > > https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects > > 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 > * Extension:OEmbedProvider > * 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 > InstantCommons > * 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! > > -- > Quim Gil > Technical Contributor Coordinator @ Wikimedia Foundation > http://www.mediawiki.org/wiki/User:Qgil > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > _______________________________________________ > Wikisource-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikisource-l >
_______________________________________________ Wikisource-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikisource-l
