Difference between revisions of "Automatic ExclusiveArch Addition/Removal"
| 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 purpose of this project is to write a script that will automatically loop through a given list of packages and automatically download them. It will then change a line specified by the user. | |
<!-- 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 17: | Line 17: | ||
== Project Details == | == Project Details == | ||
| − | + | Script will be written in Python.Input can include a csv file or command line arguements. | |
| + | There will be a config file. | ||
<!-- 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 23: | Line 24: | ||
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: | ||
| Line 31: | Line 33: | ||
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 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 == | == Communication == | ||
| Line 50: | Line 53: | ||
=== Blogs === | === Blogs === | ||
| − | <!-- Links to the blogs of people involved, both inside and outside Seneca --> | + | [[tuori.tk Matt's Blog]]<!-- Links to the blogs of people involved, both inside and outside Seneca --> |
==== Seneca Particpants ==== | ==== Seneca Particpants ==== | ||
| Line 63: | Line 66: | ||
<!-- 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. --> | <!-- 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. --> | ||
| + | ]'''] | ||
Revision as of 07:21, 3 February 2011
[[= Automatic ExclusiveArch Addition/Removal =
Contents
Project Description
The purpose of this project is to write a script that will automatically loop through a given list of packages and automatically download them. It will then change a line specified by the user.
Project Leader(s)
Matthew Tuori
Project Contributor(s)
Project Details
Script will be written in Python.Input can include a csv file or command line arguements. There will be a config file.
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
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
Blogs
Seneca Particpants
Non-Seneca Participants
Planets
Project News
]]
