Difference between revisions of "Package Raspberry Pi Logos"
(→Mailing Lists) |
(→Mailing Lists) |
||
Line 52: | Line 52: | ||
* Fedora Mailing Lists | * Fedora Mailing Lists | ||
** [https://admin.fedoraproject.org/mailman/listinfo/arm arm] - For discussion of the ARM secondary architecture | ** [https://admin.fedoraproject.org/mailman/listinfo/arm arm] - For discussion of the ARM secondary architecture | ||
+ | ** [https://lists.fedoraproject.org/mailman/listinfo/announce announce] - | ||
=== Upsteam Wiki and Web === | === Upsteam Wiki and Web === |
Revision as of 13:02, 11 March 2012
Contents
Package Raspberry Pi Logos
Project Description
Fedora usually contains three packages that cannot be redistributed with derived (remixed) versions:
fedora-logos fedora-release fedora-release-notes
Dummy versions of these packages are available, substituting generic- for fedora- (i.e., generic-logos, generic-release, and generic-release-notes).
The fedora-release package has been replaced by the raspberrypi-fedora-remix-release package.
This project involves creating a replacement for the other two packages:
raspberrypi-logos -- This package will contain replacements for the Fedora logos, including the Raspberry Pi logo (and possibly the Fedora secondary mark) where appropriate. It would probably also be a good idea to produce a raspberrypi-backgrounds package with Raspberry Pi-branded wallpaper.
Project Leader(s)
Kavishankar Srivamathevan
Project Contributor(s)
Christopher Choo
Project Details
The basic idea behind this part of the project is to change all of the existing Fedora logos to the Fedora Remix logos with a little bit of Raspberry Pi fusion. It will consist of custom logos and backgrounds that will be used in our Raspberry Pi Fedora Remix.
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
Goals for each release and plans for reaching those goals:
- 0.1 Research what logos need to be changed, how the logos will be integrated, rough sketches of logos and background ideas and release alpha package.
- 0.2 Take the 0.1 release and make any changes or correction that need to be done and test it and release the beta package.
- 0.3 Final final package release.
Communication
Mailing Lists
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
Blogs
Seneca Particpants
Kavishankar Srivamathevan, Christopher Choo