1
edit
Changes
Created page with '= Package the Mirrorlist CGI Script Library = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == This project will…'
= Package the Mirrorlist CGI Script Library =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
This project will create a script that will optimize the performance of all yum updates and package installation.
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
== Project Leader ==
[[User:Matthew Kam-Man Wong|Matthew Kam-Man Wong]]
<!-- Name(s) of primary person working on the project.
If there is more than one person working on related projects, they must have separate project pages, and the project title and description should identify who is doing what. For example:
Include links to personal pages within wiki and to blog sites. -->
== Project Contributor(s) ==
* TBA
<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. -->
== Project Details ==
CGI
<!-- 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 ===
* Bugzilla or Trac will be used for review management.
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
<!-- === Key contacts ===
* TBA
-->
<!-- Add links to any mentors or key participants in the community. -->
=== Goals by Release ===
Goals for each release and plans for reaching those goals:
<!-- Note: Each student must 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. -->
* 0.1 - Initial packaging. Package sent for review in Fedora (if this is useful on devices beyond the Pi) or Pidora (if useful only on the Pi)
* 0.2 - Review issues addressed, package through the review process.
* 0.3 - Package in Fedora or Pidora.
== Communication ==
=== Mailing Lists ===
* Google group:
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
=== Upsteam Wiki and Web ===
*
<!-- Links to upstream wiki/web pages -->
=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
=== Source Code Control ===
* Upstream source code: https://github.com/quick2wire/quick2wire-python-api
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
=== Blogs ===
*
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
<!--
=== Non-Seneca Participants ===
-->
<!-- Links to the blogs of any non-Seneca participants in this project -->
<!--
=== Planets ===
-->
<!-- Links to any planets related to this project -->
== Project News ==
* 2013-10-07: Project started!
<!-- 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. -->
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
This project will create a script that will optimize the performance of all yum updates and package installation.
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
== Project Leader ==
[[User:Matthew Kam-Man Wong|Matthew Kam-Man Wong]]
<!-- Name(s) of primary person working on the project.
If there is more than one person working on related projects, they must have separate project pages, and the project title and description should identify who is doing what. For example:
Include links to personal pages within wiki and to blog sites. -->
== Project Contributor(s) ==
* TBA
<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. -->
== Project Details ==
CGI
<!-- 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 ===
* Bugzilla or Trac will be used for review management.
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
<!-- === Key contacts ===
* TBA
-->
<!-- Add links to any mentors or key participants in the community. -->
=== Goals by Release ===
Goals for each release and plans for reaching those goals:
<!-- Note: Each student must 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. -->
* 0.1 - Initial packaging. Package sent for review in Fedora (if this is useful on devices beyond the Pi) or Pidora (if useful only on the Pi)
* 0.2 - Review issues addressed, package through the review process.
* 0.3 - Package in Fedora or Pidora.
== Communication ==
=== Mailing Lists ===
* Google group:
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->
=== Upsteam Wiki and Web ===
*
<!-- Links to upstream wiki/web pages -->
=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
=== Source Code Control ===
* Upstream source code: https://github.com/quick2wire/quick2wire-python-api
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
=== Blogs ===
*
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
<!--
=== Non-Seneca Participants ===
-->
<!-- Links to the blogs of any non-Seneca participants in this project -->
<!--
=== Planets ===
-->
<!-- Links to any planets related to this project -->
== Project News ==
* 2013-10-07: Project started!
<!-- 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. -->
