GSOC 2014: Difference between revisions
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
== Client-side audio rendering == |
== Client-side audio rendering == |
||
This one's a low-maybe on priorities, compared to others. |
This one's a low-maybe on priorities, compared to others. The goal is to make it themable. |
||
Switch the audio spectrogram rendering to be done on the user's end. During processing, the relevant data should be extracted and stored as metadata, but should be presented to the user. |
Switch the audio spectrogram rendering to be done on the user's end. During processing, the relevant data should be extracted and stored as metadata, but should be presented to the user. |
||
| Line 34: | Line 34: | ||
Switch to or write a new feed library that is capable of handling enclosures and port MediaGoblin to it. |
Switch to or write a new feed library that is capable of handling enclosures and port MediaGoblin to it. |
||
== Media embedding and OEmbed support == |
|||
Revision as of 19:35, 19 February 2014
We are hoping to participate in GSOC 2014 under the GNU umbrella.
Possible projects
Gstreamer audio/video code cleanup
Investigate and fix the issues with thumbnailing in the video processing pipeline. Investigate the rest of the gstreamer code, clean up and document.
Show progress on gstreamer pipeline.
Processing panel improvements
Could be combined with the above.
Better indication of the status of media processing. This includes better representation of current processing progress, as well as representation of possible errors.
Client-side audio rendering
This one's a low-maybe on priorities, compared to others. The goal is to make it themable.
Switch the audio spectrogram rendering to be done on the user's end. During processing, the relevant data should be extracted and stored as metadata, but should be presented to the user.
(Could possibly be combined with the above two; student should talk to paroneayea on IRC before doing so and also get some sense of the existing processing code)
Port migrations to Alembic
Currently we use sqlalchemy-migrate, but it's fairly outdated and unmaintained
Port the migration infrastructure to using Alembic instead.
This includes making sure that sqlite can be continued to be used with MediaGoblin's migrations (which may require working on some upstream contributions... this is unclear at the time of writing).
Podcasting support / new feed library?
Switch to or write a new feed library that is capable of handling enclosures and port MediaGoblin to it.