Difference between revisions of "Packaging and support for OpenMAX"

From CDOT Wiki
Jump to: navigation, search
(Source Code Control)
(Communication)
Line 50: Line 50:
 
== Communication ==
 
== Communication ==
  
=== Mailing Lists ===
 
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
 
  
 
=== Upsteam Wiki and Web ===
 
=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->
+
 
  
 
=== Links/Bugs/Tracking ===
 
=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
+
 
  
 
=== Source Code Control ===
 
=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
+
 
  
  
Line 69: Line 67:
  
 
=== Blogs ===
 
=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
 
 
==== Seneca Particpants ====
 
 
==== Non-Seneca Participants ====
 
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
 
==== Planets ====
 
<!-- Links to any planets related to this project -->
 
  
 
== Project News ==
 
== Project News ==
  
 
<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->
 
<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->

Revision as of 11:45, 7 November 2012

Project Name

Project Description

OpenMax is a means of supporting media well on a lot of ARM platforms. It should be packaged and present in Fedora.
The OpenMAX IL API strives to give media components portability across an array of platforms using the C-language. In the OpenMAX IL, components represent individual blocks of functionality. Components can be sources, sinks, codecs, filters, splitters, mixers, or any other data operator.

Project Leader(s)

Ryan Lawrence Aqualie (rlawrence5)
Andrei Martinenco amartinenco


Project Contributor(s)

Project Details

Project Plan

Tracking mechanism (bugzilla, trac, github, ...):

Key contacts:

Goals for each release and plans for reaching those goals:

Andrei

  • 0.1 Have the testing environment ready. Have omxil packaged. Have RPM package signed and put it into local repository folder. Information sent for documentation.
  • 0.2 Project submitted for review.
  • 0.3 Work out the bugs. Information sent for documentation.

Ryan

  • 0.1 Package tested. Documentation in progress.
  • 0.2 Project reviewed for submission.
  • 0.3 Final tests are done. Project documentation ready.

Communication

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

http://omxil.sourceforge.net OpenMax IL
http://gstreamer.freedesktop.org GStreamer
http://cgit.freedesktop.org/gstreamer/gst-openmax OpenMax Plugin
https://github.com/robclark/gst-ducati Ducati Plugin

Blogs

Project News