I'm not sure whether it'd be helpful for this project, but https://github.com/akrennmair/speech-to-server looks interesting. Somebody ported lame (the mp3 encoder) to JavaScript. The demo I linked to records in the browser and streams it to a server over websocket.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerromeo@gmail.com
On Sun, Mar 17, 2013 at 9:47 AM, Sumana Harihareswara <sumanah@wikimedia.org
wrote:
On 03/13/2013 12:15 AM, Antoine Musso wrote:
Le 13/03/13 04:07, K. Peachey wrote:
That wouldn't be a bad project for GSoC as it isn't too large so it
means
we could actually see some results, And if it was too small, The student could probably do a couple of smaller projects (it being one) then
focus on
one after the other.
The smaller big project: get its code deployed on the cluster and enabled for all wikis!
Quick reminder:
If you think something would be a good project for a student, put it on https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects . I suggest we scope these proposals at about 6 weeks of coding work to ensure we dedicate enough time (out of the 3-month GSoC period) to bugfixing and code review. Past proposals often allotted either no time or about 2 weeks for merging with trunk, pre-deploy code review, and integration. That's not enough.
Basically, if you think a project might take about 2 weeks for you to code, go ahead and put it on that list. Students run into lots of problems, and your 2-week project is someone else's whole summer.
-- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l