Topic on Talk:Outreach programs/Possible projects

I promise this is the last thread I open with a list of GSOC 2013 candidates. I will keep it updated, notifying about the projects that make it to Summer_of_Code_2013#Project_ideas and the ones that get discarded.

• Improve the mediawiki-bugzilla extension to a deployable level: needs Bug Squad buy-in and at least one mentor. Discussing with Mozilla.
• Multilingual, usable and effective captchas: project scope needs clarification. Too much / too vague for a GSOC project?
• Mentorship_programs/Possible_projects#MediaWiki LocalisationUpdate for all: does it have MediaWiki core maintainers buy-in?
• Mentorship_programs/Possible_projects#Multilingual SemanticMediaWiki: does it have SMW maintainers buy-in?

Proposed:

• Improve Extension:CSS.
• Wikidata Entity Suggester.
• Prototyping inline comments.
• Add support for x3d 3D files to MediaWiki as part of New media types supported in Commons
• Tools for migration to structured page translation.
• Create plugins for jQuery.IME for Firefox and Chrome.

Discarded:

• Extension pages management: nice idea but with unknown origin/promoter, requires significant planning and buy-in from mediawiki.org.
• System documentation integrated in source code: too complex for GSOC - see bug 46526.
• Work on outstanding Parsoid bugs and/or add features: the Parsoid team has big release in July and they are very busy. Not the best time for a student to land.
• Work on RefToolbar: we want to promote work on VisualEditor instead. The first release this Summer has basic cite support, and more can be added later on.
• Phase out the Vector extension; merge the good parts into core: not considered a good GSOC task in the current status of the project. (discuss)
• Browser Test Automation: considered not a good fit for GSOC.
• Improve accessibility of MediaWiki and MediaWiki extensions: not suggested anymore.
• Gadgets: no project.
• Write useful Lua modules: no project.
• Build an interwiki notifications framework and implement it for InstantCommons: nobody answered.

This post was posted by Qgil-WMF, but signed as Qgil.

For the x3d one. Well it wouldn't be my first choice for a project to mentor, however if I was not mentoring something else and there was a student really interested in it I could probably mentor that. On a similar note make a kml validator/media handler would also possibly make a good media-handler-extension gsoc project (and maybe a little better scoped than the x3d one)

Wouldn't KML support be bug 26059? High priority, assigned to nobody, 30 comments 16 followers and stalled... Do we really want a student to jump there? If you want to test the waters in the report please do. I'd rather put my time pushing current project candidates to become actual GSOC ideas. An equivalent to "feature freeze", I guess.

This post was posted by Qgil-WMF, but signed as Qgil.

Yeah that is the bug. I would just reccomend it be considered before x3d since from a technical prespective its almost the same project, but about half the work (and also probably has more people who care about it)

X3D support for mediawiki can be simplified by using the open source x3dom.js (http://www.x3dom.org/) - after that it's mostly about whitelisting the X3D tag set.

What about having a catch-all entry at the GSOC page for unsupported file types in Commons/MediaWiki? We could explicitly point to KML, x3d (anything else highlighted?) and link to the full list at Commons.

This post was posted by Qgil-WMF, but signed as Qgil.

Discarded: Extension pages management: nice idea but with unknown origin/promoter, requires significant planning and buy-in from mediawiki.org.

This post was posted by Qgil-WMF, but signed as Qgil.

Discarded: System documentation integrated in source code: too complex for GSOC - see bug 46526.

This post was posted by Qgil-WMF, but signed as Qgil.

I'm available to mentor the E:CSS, E:UploadWizard, the XML sitemaps extension, automatic category redirects, and/or E:OEmbed*. Which one I do I'll leave up to somebody who has a better idea of which projects WMF would prefer. Depending on the time commitment involved, I may be able to mentor more than one project.

If you could mentor Category redirects then bawolff would be available for another one. This is all relative since we might end up with other combinations as soon as interesting project proposals from students show up, but it would be a good combination to start with.

This post was posted by Qgil-WMF, but signed as Qgil.

Sounds good to me.

Discarded: Work on outstanding Parsoid bugs and/or add features: the Parsoid team has big release in July and they are very busy. Not the best time for a student to land.

This post was posted by Qgil-WMF, but signed as Qgil.

Discarded: Work on RefToolbar: we want to promote work on VisualEditor instead. The first release this Summer has basic cite support, and more can be added later on.

This post was posted by Qgil-WMF, but signed as Qgil.

Proposed: Improve Extension:CSS.

This post was posted by Qgil-WMF, but signed as Qgil.

Proposed: Wikidata Entity Suggester.

This post was posted by Qgil-WMF, but signed as Qgil.

Browser Test Automation: needs at least one project idea.

I am not sure what would be a good project idea. For now we have this: "The goal would be to create decent test coverage for a feature or an extension. ... Good example would be Extension:MobileFrontend extension." Is that good enough?

This post was posted by ZFilipin (WMF), but signed as Zeljko.filipin(WMF).

As said in wikitech-l: 12 weeks of a student to get good coverage of MobileFrontend automated testing? Maybe, but... One thing is the amount of work. Another thing is that it feels like quite volatile / WIP work. I'm open to be convinced, though.

We need to solve this today. Let's chat / talk.

This post was posted by Qgil-WMF, but signed as Qgil.

Discarded: Browser Test Automation: considered not a good fit for GSOC.

This post was posted by Qgil-WMF, but signed as Qgil.

Proposed: Prototyping inline comments.

This post was posted by Qgil-WMF, but signed as Qgil.

Proposed: Add support for x3d 3D files to MediaWiki as part of New_media_types_supported_in_Commons

This post was posted by Qgil-WMF, but signed as Qgil.

Proposed:

• Tools for migration to structured page translation.
• Create plugins for jQuery.IME for Firefox and Chrome.

Discarded:

• Improve accessibility of MediaWiki and MediaWiki extensions: not suggested anymore.
• Gadgets: no project.
• Write useful Lua modules: no project.
• Build an interwiki notifications framework and implement it for InstantCommons: nobody answered.

This post was posted by Qgil-WMF, but signed as Qgil.

Suggestion, "Implement SASS or LESS support in ResourceLoader". It includes implementing bugzilla:46546 (languages like SASS or LESS in debug mode), and then one or both of bugzilla:46545 (SASS) and bugzilla:40964 (LESS).

This post was posted by Mattflaschen, but signed as Superm401.

Good! Assuming that the maintainers are ok with this. Please write a more explanatory description under Raw projects. Thank you!

This post was posted by Qgil-WMF, but signed as Qgil.

I've added details at Mentorship_programs/Possible_projects#SASS.2FLESS. Let me know if more information would be helpful (some additional info is at the linked bugs). I also linked there from the SASS and LESS bugs.

This post was posted by Mattflaschen, but signed as Superm401.

I could also probably mentor this project as well if needed.

Hello, I hope I am not writing in the wrong place. I am a student(4h year in Department of Informatics, University of Athens) interested in Gsoc and would like to apply for a project in wikimedia. On this page: http://www.mediawiki.org/wiki/Summer_of_Code_2013 (Incremental data dumps -> https://bugzilla.wikimedia.org/show_bug.cgi?id=28956 and especially this post: http://www.mediawiki.org/wiki/User:ArielGlenn/Dumps_new_format_%28deltas,_changesets%29 ) I have found an interesting subject that I have some experience with. Is this still open, because on this page I don't see it anywhere? My experience on this issue come from my involvement recently in the Sigmod 2013 Programming Contest, where we faced many similar issues. The competition was in C++ but the theoretical background is similar and XML-Python will definitely not be the problem I imagine. If this project is not available any more, it would be really helpful to point me towards something else available and similar. I have strong skills in C,C++,Python,Java,Web Languages(JS,CSS,PHP,HTML) and the ability and time to learn anything else needed.

Hello Sibetheros! The best place to ask is indeed bug 28956. You can also contact Ariel directly (who coincidentally or not happens to be a fluent Greek speaker) via IRC or email.

This post was posted by Qgil-WMF, but signed as Qgil.