Difference between revisions of "Packaging WeatherMan"

From CDOT Wiki
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Packaging Weatherman ==
+
= Packaging WeatherMan =
 
 
<!--
 
 
 
 
 
 
 
 
 
 
 
#### EDIT A COPY OF THIS PAGE, NOT THE ORIGINAL SAMPLE PROJECT PAGE! ####
 
 
 
 
 
 
 
 
 
 
 
-->
 
 
 
= Project Title =
 
 
<!-- 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 ==
 +
weatherman displays weather information from weatherbug.com on the command line. It is written entirely in bash and will run on most UNIX/Linux systems.
  
 
<!-- 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 ==
 
== Project Leader ==
 
+
[[User:pphan|Phuoc Phan]]  [http://pphanopensource.blogspot.ca/ (pphan)]
 
<!-- Name(s) of primary person working on the project.
 
<!-- Name(s) of primary person working on the project.
  
Line 37: Line 22:
  
 
== Project Details ==
 
== Project Details ==
 +
weatherman displays weather information from weatherbug.com on the command line. It is written entirely in bash and will run on most UNIX/Linux systems.
 +
 +
The latest version of weatherman was released on January 12, 2013 with the following changes:
 +
 +
Using metric units with extended forecasts works once again
 +
Better column alignment when metric units are specified
 +
Fixed a rare case where extended forecasts would be displayed incorrectly
 +
No longer display units with empty values
 +
Removed the program name and project URL from the output
  
 
<!-- 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 44: Line 38:
 
=== Tracking ===
 
=== Tracking ===
 
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
 
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
 
+
Ill use bugzilla to track my packaging review.
 
=== Key contacts ===
 
=== Key contacts ===
 
<!-- Add links to any mentors or key participants in the community. -->
 
<!-- Add links to any mentors or key participants in the community. -->
 
+
None
 
=== Goals by Release ===
 
=== Goals by Release ===
  
Line 53: Line 47:
 
<!-- 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. -->
 
<!-- 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
 
* 0.1
 +
Get package in review
 
* 0.2
 
* 0.2
 +
Hopefully review process is finish
 
* 0.3
 
* 0.3
 +
Release into Fedora
  
 
== Communication ==
 
== Communication ==
Line 66: Line 63:
 
=== Links/Bugs/Tracking ===
 
=== Links/Bugs/Tracking ===
 
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
 
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->
 
+
Source: http://darkhorse.nu/weatherman/
 
=== Source Code Control ===
 
=== Source Code Control ===
 
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
 
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->
Line 72: Line 69:
 
=== 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://pphanopensource.blogspot.ca/ Phuoc's Blog]
 
=== Non-Seneca Participants ===
 
=== Non-Seneca Participants ===
 
<!-- Links to the blogs of any non-Seneca participants in this project -->
 
<!-- Links to the blogs of any non-Seneca participants in this project -->
Line 78: Line 75:
 
=== Planets ===
 
=== Planets ===
 
<!-- Links to any planets related to this project -->
 
<!-- Links to any planets related to this project -->
 
+
[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet]
 
== Project News ==
 
== Project News ==
  
 
<!-- 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. -->
 +
'''Nov 30th 2013'''
 +
• Weatherman packaged. Will send to Koji for further testing.
 +
 +
• Started packaging new package. Pianobar need packages that is not in Fedora.

Latest revision as of 17:18, 30 November 2013

Packaging WeatherMan

Project Description

weatherman displays weather information from weatherbug.com on the command line. It is written entirely in bash and will run on most UNIX/Linux systems.


Project Leader

Phuoc Phan (pphan)

Project Contributor(s)

Project Details

weatherman displays weather information from weatherbug.com on the command line. It is written entirely in bash and will run on most UNIX/Linux systems.

The latest version of weatherman was released on January 12, 2013 with the following changes:

Using metric units with extended forecasts works once again Better column alignment when metric units are specified Fixed a rare case where extended forecasts would be displayed incorrectly No longer display units with empty values Removed the program name and project URL from the output


Project Plan

Tracking

Ill use bugzilla to track my packaging review.

Key contacts

None

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1

Get package in review

  • 0.2

Hopefully review process is finish

  • 0.3

Release into Fedora

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source: http://darkhorse.nu/weatherman/

Source Code Control

Blogs

Phuoc's Blog

Non-Seneca Participants

Planets

Planet

Project News

Nov 30th 2013 • Weatherman packaged. Will send to Koji for further testing.

• Started packaging new package. Pianobar need packages that is not in Fedora.