Difference between revisions of "Packaging and support for OpenMAX"
Amartinenco (talk | contribs) (→Project Description) |
Amartinenco (talk | contribs) (→Project Description) |
||
| Line 6: | Line 6: | ||
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. --> | <!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. --> | ||
| − | 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. | + | 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) == | == Project Leader(s) == | ||
Revision as of 11:20, 15 October 2012
Contents
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:
- 0.1
- 0.2
- 0.3
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
http://omxil.sourceforge.net/
