1,885
edits
Changes
→Infrastructure Projects
* Resources - An initial list of computer and information resources to get started on the project.
* Expected result - A rough indication of what is expected at the conclusion of the project.
You will have an opportunity to investigate, expand upon, and fine-tune this information as you prepare your initial project plan. For example, you may come up with a more detail list of expected results (deliverables), resources, and contacts during your planning.
Maximum number of participants: 1
Expected result: An updated, working raspberrypi-config package
== Kernel Configuration Files ==
Maximum number of participants: 1
Expected result: An improved kernel configuration in the raspberrypi-kernel package
== Profile and Improve RPM and YUM performance on the Pi ==
Maximum number of participants: 1
Expected result: Either a report proving that RPM/YUM are as fast as can be expected on the Pi, or changes to affected packages to improve performance
== Internationalization Support in Firstboot for Pidora 19 ==
Maximum number of participants: 1
Expected result: A version of firstboot and the firstboot modules that are fully internationalized
== New Firstboot for Pidora 20 ==
Maximum number of participants: 1
Expected result: A version of the Fedora 19 or Fedora 20 firstboot that works on the Pi and has full support for the Pidora options (such as rootfs resizing)
== Compiler Flags on Pidora ==
Maximum number of participants: 1
Expected result: Modified RPM macros that include the optimal flags for Pidora
== Avahi Configuration for Pidora ==
Maximum number of participants: 1
== Upstream the Pidora RPM Changes ==
Maximum number of participants: 1
Expected results: Pidora RPM changes will be upstreamed
== Wayland ==
Maximum number of participants: 2
Expected results: The Wayland snapshot in Fedora 20 will be usable on the Pi (Ideal: fully packaged; Acceptable: Instructions on how to set it up)
== Automate Pidora Kernel and Firmware Building ==
Maximum number of participants: 1
Expected results: Raspberry Pi kernel and firmware updates will be included in a package in a testing repository through an automated (cron'd) process
== Change raspberrypi-vc Package to Build from Source ==
Maximum number of participants: 1
Expected result: A new version of the raspberrypi-vc package that build from source, is compatible with the current Pidora package, and can be easily updated/maintained
== Write an Updated Boot Screen ==
Maximum number of participants: 1
Expected result: A visually appealing boot screen, packaged as a drop-in replacement for the current boot screen
== Update rootfs-resize ==
Maximum number of participants: 1
Expected result: An updated rootfs-resize package
== Packaging Pi-compatible Software ==
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
Skills required: packaging
Maximum number of participants: 1 per package (identify the package!)
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 =
Maximum number of participants: 1
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
