Below it old project plan:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into #multiple pages and linking to them. -->##Oct 6, 2012. Group Meeting.<br /><br />#We discussed about which hardware and interface we are going to contribute. And the final decision is we are gonna use Pandaboard device. I will work on the GPIO interface, and Luis will work on the I2C #interface. One of our member drop the course, so, that is all for now.##we did some research on the library and drivers, here is the google doc link for sharing the information within group member: https://docs.google.com/document/d/1TJQb7bEK91TNs3f2jqkOiQU3_ro8Z7BhKEbdtaCOoxc/edit
#Oct 6, 2012. Group Meeting.<br /><br />We discussed about which hardware and interface we are going to contribute. And the final decision is we are gonna use the Beaglebone/Beagleboard Pandaboard device for . I will work on the GPIO interfacesinterface, and Luis will work on the I2C interface. One of our member drop the course, so, that is all for now.<br /><br />
#we did some research on the library and drivers, here is the google doc link for sharing the information within group member: https://docs.google.com/document/d/1TJQb7bEK91TNs3f2jqkOiQU3_ro8Z7BhKEbdtaCOoxc/edit We are going to use the Beaglebone/Beagleboard device for the GPIO interfaces.<br /><br /> Luis Fuentes : Package appropriate libraries for Beagleboard GPIO <br />#Jiecheng Qiu : Package appropriate libraries for Beaglebone GPIO <br />
<br /><br />
#Oct 15, 2012 Update Project Home Page.<br /><br />
#Today we update the Project Detail, Project Plan, and Blogs.#We will continue do some research on library, and try to package it soon. And we will ask for loan some hardware.
#Tracking mechanism (bugzilla, trac, github, ...):
#Key contacts:
<!-- Add links to any mentors or key participants in the community. -->
#Goals for each release and plans for reaching those goals:
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. 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 project. -->
<br /><br />
#0.1 release an initial version of our package <br /><br />#0.2 release a final version and get it into the Fedora package review process <br /><br />#0.3 the package has gone through the final release process and is available in Fedora <br /><br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
== Communication ==
