Difference between revisions of "Automatic ExclusiveArch Addition/Removal"
(Created page with ' = Project Name = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == <!-- Description should be no longer than a …') |
|||
| Line 1: | Line 1: | ||
| − | + | = Automatic ExclusiveArch Addition/Removal = | |
| − | |||
| − | = | ||
<!-- Replace "Project Name" with the actual name of the project in the line above. --> | <!-- Replace "Project Name" with the actual name of the project in the line above. --> | ||
== Project Description == | == Project Description == | ||
| − | + | The aim of this project is to write a script that will loop through a given list of packages and automatically download the packages. It will then change the Arch lines that the user indicated he or she wanted changed. | |
<!-- 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]. --> | <!-- 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(s) == | == Project Leader(s) == | ||
| − | + | Matthew Tuori | |
<!-- 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. --> | <!-- 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. --> | ||
| Line 19: | Line 17: | ||
== Project Details == | == Project Details == | ||
| − | + | Script will be written in Python. | |
| + | Line added/removed will be set in config file. | ||
| + | Can include switch to pull package names from a CSV file or to just take command line arguement. | ||
<!-- 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. --> | <!-- 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. --> | ||
| Line 25: | Line 25: | ||
Tracking mechanism (bugzilla, trac, github, ...): | Tracking mechanism (bugzilla, trac, github, ...): | ||
| + | To be determined - Still have to look at the available options to determine the solution that is best for this project. | ||
Key contacts: | Key contacts: | ||
| + | [[ctyler]] | ||
| + | [[PaulW]] | ||
<!-- Add links to any mentors or key participants in the community. --> | <!-- Add links to any mentors or key participants in the community. --> | ||
Goals for each release and plans for reaching those goals: | 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. --> | <!-- 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. --> | ||
| − | * 0.1 | + | * 0.1 Have a rough working script (May not include automatic download of packages) |
| − | * 0.2 | + | * 0.2 Add extra features, get automatic download of packages working, debug |
| − | * 0.3 | + | * 0.3 Write documentation, polish off program |
== Communication == | == Communication == | ||
| Line 39: | Line 42: | ||
=== Mailing Lists === | === Mailing Lists === | ||
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | <!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | ||
| + | users@lists.fedoraproject.org | ||
=== Upsteam Wiki and Web === | === Upsteam Wiki and Web === | ||
| Line 51: | Line 55: | ||
=== Blogs === | === Blogs === | ||
<!-- Links to the blogs of people involved, both inside and outside Seneca --> | <!-- Links to the blogs of people involved, both inside and outside Seneca --> | ||
| − | + | [http://www.tuori.tk Matt's blog] | |
==== Seneca Particpants ==== | ==== Seneca Particpants ==== | ||
Revision as of 07:15, 3 February 2011
Contents
Automatic ExclusiveArch Addition/Removal
Project Description
The aim of this project is to write a script that will loop through a given list of packages and automatically download the packages. It will then change the Arch lines that the user indicated he or she wanted changed.
Project Leader(s)
Matthew Tuori
Project Contributor(s)
Project Details
Script will be written in Python. Line added/removed will be set in config file. Can include switch to pull package names from a CSV file or to just take command line arguement.
Project Plan
Tracking mechanism (bugzilla, trac, github, ...): To be determined - Still have to look at the available options to determine the solution that is best for this project.
Goals for each release and plans for reaching those goals:
- 0.1 Have a rough working script (May not include automatic download of packages)
- 0.2 Add extra features, get automatic download of packages working, debug
- 0.3 Write documentation, polish off program
Communication
Mailing Lists
users@lists.fedoraproject.org
