Come join us in building the Neuros Embedded Hardware Module. Let's make this the best open-source, video-focused, Internet enabled media center platform available!

Through the generous support of Texas Instruments, the provider of the module's underlying DaVinci DM6446 processor, we are able to offer to our developers several bounties to build functionality into the product. This site is the central repository of information to enable you to learn more about the program.  You do not need the hardware to apply.  Bounty winners will be loaned or given hardware to complete their bounties.

Bounties will be added over time, so check back regularly.

What is a bounty?

Think of a "bounty" as a contract without all the legal wrangling of a contract.  Our goal is to assign a bounty to a competent, responsive community developer who will write quality code and help build a quality product.

What is the bounty process?

Follow these four easy steps.

1. Find a proposal for the bounty that you like. You can find the list of bounties here. Ask the questions you need to by posting to the Neuros Mailing List, or by logging onto IRC, channel #neuros, server irc.freenode.net.
2. Submit a proposal for the bounty. What are you going to do? How are you going to do it? What background do you have with this subject? We will assign the bounties to the developers with the proposal that most directly addresses the problem.
3. Once you have been awarded the "right to bounty", do the work!
4. Submit your completed work by the deadline. With functioning, well-documented code, you will be paid the bounty.

What are the bounties?

You can see all open bounties here.

What are the rules?

This is pretty straightforward. Feel free to ask if you have questions.

• If you complete the work you agreed to do, based on Neuros and/or TI judges, you will get paid.
• The work must 1.) work, 2.) be structured reasonably well, and 3.) be well documented.
• You must submit a short, end-user-friendly description of what you have done. This will be posted on open.neurostechnology.com for the world to see.
• Based on internal developments throughout the bounty period, your direction could be subject to change. After all, it doesn't help anyone to build something that may have already been built.
• All code will be licensed under GPL v2.
• The judgment of the bounty committee is final. They might decide that a bounty payment should not be issued, or split, or something else entirely. Who is in the bounty committee? This is TBD, but it will likely be a combination of TI employees, Neuros employees, and Community members.

I don't want to have to pay for hardware, but want to apply.  What should I do?

Apply! 
Competent, responsive developers will be loaned or given the hardware
to complete the project should they be assigned the bounty.