Changes

Jump to: navigation, search

SBR600 Potential Projects

1,359 bytes added, 11:41, 25 September 2013
Infrastructure Projects
Expected results: A configuration package that, when installed, will correctly set up Avahi for local discovery on the Pi
 
== Create a Fedpkg-compatible Package Repository for Pidora ==
 
Fedpkg is a tool used to manage Fedora packages using GIT (and http). We'd like to be able to use it for Pidora-specific (non-Fedora) packages as well. To set up Fedpkg, a package database (pkgdb), GIT repository, http repository, and Fedpg configuration will be required. Completion of the various components of this project should result in a usable, RPM-installable Fedpkg configuration for Pidora packages.
 
Skills required: system administration, testing, packaging
 
Maximum number of participants: 3
 
Expected result: A working Fedpkg repository, plus configuration files package up in an RPM
== Upstream the Pidora RPM Changes ==
There are a number of Pi-specific software packages that could/should be included in Pidora. Select one, package it, and get it into Fedora (preferred) or directly into Pidora.
{{Admon/tip|Finding Your Own Package|You can find any Pi-specific software and propose packaging it for your project. Note that it must be (a) broadly-useful Pi-specific software, or (b) a substantial software package that would be generally useful in Fedora and specifically on the Pi, in order to be approved as a project.}} Some possible packages ideas to get you started:
* Adafruit WebIDE
* Adafruit libraries/tools/etc(select a specific piece of software)
* OMXplayer
* Vidcore library compatibility package (symlink farm in /opt/vc so that source code expecting to find the VC libraries there will work successfully)
* Quick2wire python library
There are a number of See the [http://trac.proximity.on.ca/projects/rpfr/report/1 Pidora Bug Tracker] for ideas for other package requests packages that people want included in the Pidora bug tracking system.
Skills required: packaging
Expected result: A working, Pidora-compatible package that has gone through package review
 
== Clean Up the Pidora Kickstart File ==
 
The Pidora images are composed using a kickstart-based process. The kickstart file could be cleaned up for better readability and smallest-functional package selection.
 
Recent (but not necessarily latest) kickstart: http://scotland.proximity.on.ca/raspberrypi/test-releases/rpfr18v6/latest/pidora-18.ks
 
Skills required: packaging, composing
 
Maximum number of participants: 1
 
Expeccted result: A clean kickstart file for Pidora 19
= Infrastructure Projects =
Expected result: A spam-resistant bug tracking system
 
== Create a Fedpkg-compatible Package Repository for Pidora ==
 
Fedpkg is a tool used to manage Fedora packages using GIT (and http). We'd like to be able to use it for Pidora-specific (non-Fedora) packages as well. To set up Fedpkg, a package database (pkgdb), GIT repository, http repository, and Fedpg configuration will be required. Completion of the various components of this project should result in a usable, RPM-installable Fedpkg configuration for Pidora packages.
 
Skills required: system administration, testing, packaging
 
Maximum number of participants: 3
 
Expected result: A working Fedpkg repository, plus configuration files packaged up in an RPM
 
== Mirrorlist CGI Script ==
 
Yum uses a mirrorlist retrieved from a server to determine which mirrors to use for downloading packages. This mirrorlist can be generated by a script (e.g., to randomize or to optimize mirror selection), but at the present time a static file is just passed through to the yum client.
 
Skills required: scripting, testing
 
Maximum number of participants: 1
 
Expected result: An updated mirrorlist script

Navigation menu