Changes

Jump to: navigation, search

General HW enablement

1,401 bytes added, 23:44, 8 December 2012
Project News
*<u>'''Nikhil Sharma:'''</u><br />
**Learn a little about Nikhil here: [http://zenit.senecac.on.ca/wiki/index.php/User:Nikhil_Shrey_Sharma About Nikhil]
**Check out my Nikhil's blog here: [http://wwwi0x777.elite-mafiawordpress.net/blog com Nikhil's Blog]<br /><br />
*<u>'''Hugo Pombo:'''</u><br />
**Learn a little about Hugo here: [http://zenit.senecac.on.ca/wiki/index.php/User:hapombo About Hugo] <br />
**Check out my Hugo's blog here: [http://hapombo.blogspot.ca/ Hugo's Blog]<br /><br />
<!-- Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki and to blog sites. -->
 
== Project Contributor(s) ==
 
Here are some Trim-Slice Projects in motion: [http://www.trimslice.com/wiki/index.php/Trim-Slice_Projects Trim-Slice Projects]<br /><br />
== Project Details ==
*<u>Expected outcome: </u> The identified features will be supported on the identified board(s) within Fedora.
*<u>Skills required: </u> packaging, kernel/module building, testing
*<u>Maximum number of students: </u> One per hardware feature to be supported
*<u>Resources: </u> Chris Tyler (ctyler), Peter Robinson (pbrobinson)<br /><br />
<!-- 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. -->
== Project Plan ==
Tracking mechanism (bugzillaHere are our goals for each release and plans for reaching those goals:<br /><br /><!-- 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, tracone student may work on packaging a piece of software and another may work on documentation, githubor 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.-->(Discontinued)* <u>0.1 - '''Design:'''</u> Designing a rough version of our package within a fedora platform.):<br /><br />
Key contacts:Chris Tyler (ctylerRevised)* <u>0.2 - '''Draft Edition:'''</u> Test Bluetooth/WiFi on the Trim Slice, Peter Robinson create a draft version of a Test Plan along with a draft version of a Script (pbrobinsonto automate the process).<br /><br />
Goals for each release and plans for reaching those goals:* <!-u>0.3 - Note: each contributor is expected to have unique goals. These goals may be ''related'Final Edition:' 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 </u> Create a piece final version of software our Test Plan 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 finalize our Scripts for optimal efficiency. Resulting with the same bug or depend on end user acquiring success when using Bluetooth/WiFi technology with the other students' work in order to be able to complete their own projectTrim-Slice Pro. --<br /><br />* 0.1* 0.2* 0.3
<u>'''IMPORTANT:'''</u><br />
I Hugo Pombo and Nikhil Sharma will be implementing each section of our project plan <u>individually</u>.<br /><br />
Here is the declared ownership of hardware we are aspiring to enable:<br />
*<u>Hugo Pombo:</u> Enabling Bluetooth on the Trim-Slice board.<br /><br />
*<u>Nikhil Sharma:</u> Enabling WiFi on the Trim-Slice board.<br /><br />
<u>'''Notes:'''</u><br />
#Take advantage of tracking mechanisms such as: bugzilla, trac, github, etc.
#Using our key contacts: '''Chris Tyler (ctyler), Peter Robinson (pbrobinson).'''<br /><br />
== Communication ==
=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
=== Upsteam Wiki We are currently attempting to find a new and Web ===<!appropriate mailing list of which to subscribe to. However there does not seem to be a specific mailing list that revolves around Trim-- Links Slice projects. We will attempt to find a more generic mailing list that can be of some assistance to upstream wikithis project. Once found, we will let you know and update this section.<br /><br /web pages -->
=== Links/Bugs<u>As of now, we are currently subscribed to these mailing lists:</Tracking ===u><!*secondary-request@lists.fedoraproject.org*devel- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) request@lists.fedoraproject.org*announce-request@lists.fedoraproject.org*arm-request@lists.fedoraproject.org<br /><br />
=== Source Code Control ===<!-- Add Here is a link to source code URLs, including gitthe mailing lists: [https://lists.fedoraproject.org/mailman/mercuriallistinfo Mailing Lists]<br /svn><br /cvs repositories --=== Blogs ===<!-- Links Add any appropriate mailing lists to the blogs of people involvedwhich you are subscribed (e.g., both inside and outside Seneca see http://lists.fedoraproject.org -->
==== Seneca Particpants ====
 ==== Non-Seneca Participants ====<!-- Links to So far, we are the blogs of any non-only known Seneca participants in with regards to this project --> ==== Planets ====<!-- Links to any planets related to . Please, periodically check this project -->page for updates.
== Project News ==
Please see our blogs for our final deliverable files. Thank You.
<!-- This is where a permanent record of your releases and updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->
1
edit

Navigation menu