= Project Name Packaging & Support for OpenMAX =<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
<!-- == 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.
== Project Leader(s) ==
*[http://zenit.senecac.on.ca/wiki/index.php/User:Rlawrence5 Ryan Lawrence Aqualie (rlawrence5) ]<br *[http:/>Andrei Martinenco amartinenco <!-- Name(s) of primary people working /zenit.senecac.on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within ca/wiki and to blog sites/index. -->php/User:Amartinenco Andrei Martinenco]
== Project Contributor(s) ==
<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
NOTE: only ==Project LeaderPlan=====Key Contacts===* Peter Robinson (sIRC @ Freenode #fedora-arm)* Nicolas Chauvet (kwizart) should add names here===Andrei Martinenco=======gst-openmax====* 0.1 Have the testing environment ready. Have openmax packaged. Have RPM package signed and put it into local repository folder. Information sent for documentation.* 0.2 Project submitted for review.* 0. You should not add your own name to 3 Work out the Contributor listbugs. Information sent for documentation.===Ryan Lawrence=======libomxil-bellagio====* 0. 1 Resolve omxregister-bellagio error and omx-mad library released.* 0.2 Reincorpoate omx->mad library into upstream RPM.* 0.3 RPM submitted to upstream developer.
== Project Details Communication ===== Mailing List ===* https://lists.sourceforge.net/lists/listinfo/gstreamer-openmax
<!=== Links/Bugs/Tracking ===* gst-openmax (Fedora Package Review) https://bugzilla.redhat.com/show_bug.cgi?id=879881* libomxil- Provides more depth than the Project Descriptionbellagio (Revised Patch) https://bugzilla. This is the place for technical discussions, project specs, or other detailsredhat. If this gets very long, you might consider breaking this part into multiple pages and linking to themcom/show_bug. cgi?id=882743* libomxil-->bellagio (dynamicloader error) https://bugzilla.redhat.com/show_bug.cgi?id=885402
== Project Plan =Participants ===* [http://zenit.senecac.on.ca/wiki/index.php/User:Rlawrence5 Ryan Lawrence]* [http://zenit.senecac.on.ca/wiki/index.php/User:Amartinenco Andrei Martinenco]
Tracking mechanism (bugzilla, trac, github, === Source Code Control ===* http://sourceforge.net/projects/omxil '''OpenMax IL'''* http://cgit.freedesktop.)org/gstreamer/gstreamer '''GStreamer'''* http://cgit.freedesktop.org/gstreamer/gst-openmax '''OpenMax Plugin'''
Key contacts=== Blogs ===* [http://omxil.sourceforge.net OpenMax]<!-- Add links to any mentors or key participants in the community* [http://gstreamer.freedesktop. -->org GStreamer]
Goals for each release and plans for reaching those goals== Project News ===== 0.1 Release =======Ryan Lawrence====* Unused Doc:http://zenit.senecac.on.ca/wiki/index.php/How_To_Packaging_and_support_for_OpenMAX<!* Documentation: http://zenit.senecac.on.ca/wiki/index.php/RPM_Packaging_and_support_for_OpenMAX* libomxil-bellagio bug report: https://bugzilla.redhat.com/show_bug.cgi?id=882743* libomxil- Notebellagio patch: https: each contributor is expected to have unique goals//bugzilla. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' workredhat. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own projectcom/attachment. cgi?id=656322* libomxil-bellagio omx->mad library: http://www.mediafire.com/download.php?lcb2ilzm4qha2le
====AndreiMartinenco====* RPM 0.1 Build the test environment, package the omxil package: https://docs.* 0.2 Sign the RPM package and put it into local repository foldergoogle.com/file/d/0B0THh1GbRWnAUkV6dnQ1VVZESVE/edit* 0.3 Attempt to publish the rpm. Work out the bugsSpec File: https://docs. Send information to Ryan for documentationgoogle.com/file/d/0B0THh1GbRWnAanc2aWFseFY5RkE/edit
=== 0.2 Release =======Ryan Lawrence====* 0Documentation: http://zenit.senecac.1 Test the omxil package with koji on arm7.ca/wiki/index.php?title=HOWTO:_Setup_GST-OpenMAX_on_Fedora_17&oldid=91781* README(GST-OpenMAX): http://www.mediafire.com/download.php?psrl06edgc91xf5* Package Request(GST-OpenMAX): https://bugzilla.redhat.com/show_bug.cgi?id=879881* libomxil-bellagio-0.2 Point to the local repository and test the package with yum9.3 (RPM): http://www.mediafire.com/download.php?hs04bdflb034nnn* libomxil-bellagio-devel-0.9.3 Do final tests and notify Andrei about the bugs(RPM): http://www.mediafire. Once the bugs are finished create a project documentationcom/download.php?r546d169g61zo3d
== Communication ==Andrei Martinenco====
=== Mailing Lists ===Out of date:<!-- Add any appropriate mailing lists to which you are subscribed (e* RPM 0.g2: https://docs., see httpgoogle.com/file/d/0B0THh1GbRWnAcTJEbjF5N2d3Nms/edit* Devel RPM: https://listsdocs.fedoraprojectgoogle.org -->com/file/d/0B0THh1GbRWnAak1oSzBuNmlyWFU/edit* Spec File: https://docs.google.com/file/d/0B0THh1GbRWnATncxRy1WMXNiQnM/edit
=== Upsteam Wiki and Web ===Latest release:<!-- Links to upstream wiki* SRC RPM: https://docs.google.com/web pages -->open?id=0B0THh1GbRWnAV3RJN3hKbEJLTDQ
=== Links/Bugs/Tracking 0.3 Release ===<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> === Source Code Control =Ryan Lawrence====<!* Documentation: http://zenit.senecac.on.ca/wiki/index.php/HOWTO:_Setup_GST-OpenMAX_on_Fedora_17* Repository RPM: http://matrix.senecac.on.ca/~rlawrence5/repo/rlawrence-repo- Add a link to source code URLs, including git0.1-1.fc17.x86_64.rpm* SRPM: http://matrix.senecac.on.ca/mercurial~rlawrence5/svnrepo/cvs repositories libomxil-bellagio->0.9.3-7.fc17.src.rpm * RPM: http://omxilmatrix.sourceforgesenecac.neton.ca/~rlawrence5/repo/libomxil-bellagio-0.9.3-7.fc17.x86_64.rpm === Blogs ===<!* RPM-devel: http://matrix.senecac.on.ca/~rlawrence5/repo/libomxil- Links to the blogs of people involved, both inside and outside Seneca bellagio-devel-> ==== Seneca Particpants ==== ==== Non0.9.3-Seneca Participants ====7.fc17.x86_64.rpm<!* RPM-test: http://matrix.senecac.on.ca/~rlawrence5/repo/libomxil- Links to the blogs of any nonbellagio-Seneca participants in this project test-0.9.3->7.fc17.x86_64.rpm* RPM-mad: http://www.mediafire.com/download.php?1j65gyyp9wdlywx==== Planets ====<!* RPM-debuginfo: http://matrix.senecac.on.ca/~rlawrence5/repo/libomxil-bellagio- Links to any planets related to this project debuginfo-0.9.3-> == Project News ==7.fc17.x86_64.rpm
<!====Andrei Martinenco====* Release package: http://matrix.senecac.on.ca/~amartinenco/PACKAGES/f17/noarch/gstopenmax-release- This is where a permanent record of your releases and updates will go0. In these you should discuss the status or your work, your interactions with other members of the community (e10.g1-1., Seneca and Mozilla), problems you have encountered, etcfc17. -->noarch.rpm]
