- 1 Pre-Launch Questions
- 1.1 Group Name
- 1.2 Public Email
- 1.3 Describe Your Group
- 1.4 What do you hope to gain by participating in this challenge?
- 1.5 Do you participate in IRC?
- 1.6 Where are you located, and what hours do you tend to work?
- 1.7 What is your project?
- 2 Authors
- 3 Features
- 4 Pictures & Videos
- 5 Usage Instructions
- 6 Source Code
- 7 Schematics
What do you want to be called.
where can you be reached for questions? This is your main point of contact.
Describe Your Group
Describe your group. What are the interests and skills of your group members. Give a small bio here to help people get to know you.
What do you hope to gain by participating in this challenge?
This can be anything like enhancing your programing skills, gaining reputation in the open source community, rounding out your resume. You can list multiple reasons.
Do you participate in IRC?
If so what channels? What is your IRC nick?
irc.freeenode.net #beagle johndoe
Where are you located, and what hours do you tend to work?
This is so people know when you are likely to be available
What is your project?
The title of the wiki article will be the title of your project.
Short 10-20 sentence description that tells readers:
- What are you making?
- For whom are you making it, and why do they need it?
- What technologies (programming languages, etc.) will you be using?
- In general, feel free to add as much content as you think is valuable. Consider this template as the bare minimum.
Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline given. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant. Provide references such as professors who know your work if you like.
What license(s) does your project use?
For code written for this project, we will use GPLv2. When the project is based on an existing open source package, the license of that package will be used.
Existing code is primarily GPLv2 and all kernel code should be so. Some developers use other FOSS licenses, such as MIT, LGPL, etc. There are some TI codecs available for use on the platform that are provided under publicly-available binary-only licenses as well as other binary firmware builds distributed as part of the Linux kernel, but these are discouraged from being used as part of any student project.
Generally you should avoid using the GPLv3 license if possible.
- John Doe (firstname.lastname@example.org) - email can be omitted if you have concerns with privacy.
- Fred Flintstone (Fred@gmail.com)
- TJ Max (email@example.com)
- Feature 1
- Feature 2
- Feature 3
Pictures & Videos
Video your design working and upload to YouTube with link here:
Videos can be embedded directly into the wiki using the EmbedVideoPlus extension. For documentation on this extension, please see http://www.mediawiki.org/wiki/Extension:EmbedVideoPlus
Include any instructions that a user will need if they try to reproduce your project. This might include instructions on installing some piece of software, compiling something, or hardware assembly.
- Please upload all source and project files. Source code and be uploaded directly to the wiki, but larger projects may benefit from being posted externally on sites like sourceforge.net or github.com.
- Please upload your schematics in CAD preferably or PDF
- Ex. http://processors.wiki.ti.com/index.php/File:DM355_LEOPARD_BOARD.pdf