(Added tips under "Getting Started" section) |
|||
| (18 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | = Software Bounty: A/V tools for Rhea = | + | = Software Bounty: A/V tools for [[About Rhea|Rhea]] = |
| + | [[Rhea_Bounties|Software Bounty]] | ||
| + | Status: OPEN | ||
| − | + | Click [[Rhea_Bounties|here]] to view all software bounties. | |
| + | ---- | ||
| + | The goal of this [[Rhea Bounties|bounty]] is to enable Rhea users to easily upload and view video and/or audio files. You must be a Purdue student in order to participate. You may choose to work either on the audio portion of the bounty, the video portion of the bounty, or both together. You will be responsible for integrating your software to the current Rhea code. | ||
| − | + | As soon as we receive a functional piece of code, we will announce that there remain 10 days to the competition: anybody who wishes to compete must hand in their code before 10 days have passed in order to be considered for the bounty. The author(s) of the best software that satisfies the requirements will receive the money. Note that we strongly prefer open source solutions... | |
| − | + | ||
| − | Video: $ | + | If none of the software competing is satisfactory, we will reopen the call for bounty until the money is claimed. |
| + | |||
| + | We thank the Motorola Foundation for their financial support for this competition. | ||
| + | |||
| + | Questions? Write them below or talk to Andrew Haddad haddada@purdue--[[User:Haddada|Haddada]] 17:54, 9 April 2010 (UTC) | ||
| + | |||
| + | == $ Amount: == | ||
| + | <pre>Audio: $350 (Audio Only) | ||
| + | Video: $650 (Includes Audio as Part of Video Format) | ||
------------ | ------------ | ||
| − | A/V: $ | + | A/V: $1000 (Independent Audio and Video</pre> |
| + | == Use Cases == | ||
| + | |||
| + | The software developed must satisfy the following use cases: | ||
| + | |||
| + | *uploadingFromFile | ||
| + | *capturingFromComputer | ||
| + | *uploadFromURL | ||
| + | *postingToAPage | ||
| + | *watchingAVideo | ||
| + | *listeningToAudio | ||
| + | *publicizingMedia | ||
| + | *controllingMedia (play, pause, FF, RW) | ||
| + | *deletingMedia | ||
| + | *watermarkingMedia | ||
| + | *downloadingMedia | ||
| + | *compressingMedia (on upload) | ||
| + | *splittingMedia (on upload) | ||
| + | |||
== Bounty Requirements/Acceptance Criteria*<br> == | == Bounty Requirements/Acceptance Criteria*<br> == | ||
| Line 14: | Line 43: | ||
#Software must meet the Usability Rules as proposed by Constantine & Lockwood in their text ''Software For Use'' - see below | #Software must meet the Usability Rules as proposed by Constantine & Lockwood in their text ''Software For Use'' - see below | ||
#It is highly suggested that developers follow User-Interface Design Principles as proposed by ''Software For Use'' - see below | #It is highly suggested that developers follow User-Interface Design Principles as proposed by ''Software For Use'' - see below | ||
| + | #Follow the [[Usability Rules|Usability Rules]] | ||
| − | == | + | == Getting Started == |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | Email Andrew Haddad haddada@purdue to obtain Rhea's SVN repository. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | It looks like '''''Flow Player''''' is a great open source javascript player to use... Rhea would only need to add parser hooks to "install" the javascript player on any page with the correct tags. For example, after a user uploads purduepete.mp4, they could edit a page with: <flowplayer>/path/to/purduepete.mp4</flowplayer>. Also, it supposedly supports plugins (for editing, converting, etc), and best of all, audio playback. | |
| + | Quick Start: [http://flowplayer.org/demos/installation/index.html here!] | ||
| + | Audio Demo: [http://flowplayer.org/plugins/streaming/audio.html here.] --[[User:Mreeder|Mreeder]] 02:15, 29 December 2010 (UTC) | ||
| − | |||
| − | + | == Questions == | |
| − | + | *Write a question here | |
| − | + | **answer will be written here | |
| − | + | *write another question here | |
| + | **answer will be written here. | ||
| − | + | ---- | |
| − | [ | + | [[Rhea Bounties|Back to Rhea Bounty Page]] |
Latest revision as of 22:15, 28 December 2010
Contents
Software Bounty: A/V tools for Rhea
Software Bounty Status: OPEN
Click here to view all software bounties.
The goal of this bounty is to enable Rhea users to easily upload and view video and/or audio files. You must be a Purdue student in order to participate. You may choose to work either on the audio portion of the bounty, the video portion of the bounty, or both together. You will be responsible for integrating your software to the current Rhea code.
As soon as we receive a functional piece of code, we will announce that there remain 10 days to the competition: anybody who wishes to compete must hand in their code before 10 days have passed in order to be considered for the bounty. The author(s) of the best software that satisfies the requirements will receive the money. Note that we strongly prefer open source solutions...
If none of the software competing is satisfactory, we will reopen the call for bounty until the money is claimed.
We thank the Motorola Foundation for their financial support for this competition.
Questions? Write them below or talk to Andrew Haddad haddada@purdue--Haddada 17:54, 9 April 2010 (UTC)
$ Amount:
Audio: $350 (Audio Only) Video: $650 (Includes Audio as Part of Video Format) ------------ A/V: $1000 (Independent Audio and Video
Use Cases
The software developed must satisfy the following use cases:
- uploadingFromFile
- capturingFromComputer
- uploadFromURL
- postingToAPage
- watchingAVideo
- listeningToAudio
- publicizingMedia
- controllingMedia (play, pause, FF, RW)
- deletingMedia
- watermarkingMedia
- downloadingMedia
- compressingMedia (on upload)
- splittingMedia (on upload)
Bounty Requirements/Acceptance Criteria*
- Software must complete all of the proposed use-cases as specified.
- Software must meet the Usability Rules as proposed by Constantine & Lockwood in their text Software For Use - see below
- It is highly suggested that developers follow User-Interface Design Principles as proposed by Software For Use - see below
- Follow the Usability Rules
Getting Started
Email Andrew Haddad haddada@purdue to obtain Rhea's SVN repository.
It looks like Flow Player is a great open source javascript player to use... Rhea would only need to add parser hooks to "install" the javascript player on any page with the correct tags. For example, after a user uploads purduepete.mp4, they could edit a page with: <flowplayer>/path/to/purduepete.mp4</flowplayer>. Also, it supposedly supports plugins (for editing, converting, etc), and best of all, audio playback. Quick Start: here! Audio Demo: here. --Mreeder 02:15, 29 December 2010 (UTC)
Questions
- Write a question here
- answer will be written here
- write another question here
- answer will be written here.
