[[Category:SBR600]][[Category:Winter 2012 SBR600]]
{{Draft}}
= Introduction =
This is a list of potential projects related to the [[SBR600]] course that need people.
'''Students''': Please select a project that you're interested in and add an entry to the [[Fall 2011 2013 SBR600 Participants|project table/participants page]].
'''Open Source Community Members''': We welcome your recommendations for potential projects. Please create an account on this Wiki and create a description for your proposed project below. Please list your contact info (just an IRC or FAS2 name is OK) as well as links to any related web pages as Resources for the proposed project. (Questions? Ask [[User:Chris Tyler|Chris Tyler]]).
* 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.
* Initial contacts - Who to initially talk to about this project. These contacts may refer you on to other people with the respective open source communities.
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.
= Raspberry Pi Fedora Remix Projects =
== Package Update the Raspberry Pi firmware raspberrypi-config package ==
The raspberrypi-config package contains the default configuration files for Pidora. These files need to be updated to reflect new options available in the Raspberry Pi ships with some proprietary firmware , as well as options that are not commonly used by and may conflict with common use-cases - for example, the current configuration files cause kernel start-up messages to be reported on the graphics processing unit serial port. This is rarely used, any may cause conflicts with other devices connected to that port (GPU)e. This firmware should be packaged within Fedorag. Expected outcome: a Fedora package containing the Raspberry Pi firmware, LCD displays).
Skills required: packaging
Maximum number of participants: 1
== Generate an RPMExpected result: An updated, working raspberrypi-based Raspberry Pi kernel ==config package
The Fedora project has a standard RPM kernel package. The Fedora ARM project has extended this package to build separate kernels for various ARM system-on-a-chip (SOC) platforms, generating binary RPM packages for kernel-omap, kernel-tegra, kernel-kirkwood, and so forth. This package should be extended to generate a kernel package for the Broadcom SOC used in the Raspberry Pi (either kernel-raspi or kernel-bcm).== Kernel Configuration Files ==
In order The build process for the kernel uses a configuration file to create control which kernel capabilities are built into the kernel itself, which are built as loadable modules, and which are not built. The Pidora kernel configuration file is a standard RPM package combination of the RaspberryPi default configuration file and the Fedora configuration file, Dracut (initramfs) will need . This project involves reviewing the Pidora kernel configuration to be properly supportedoptimize it for the widest possible range of use-cases while ensuring a fairly small kernel image size.
Expected outcomeSkills required: the Fedora kernel package generates a Raspberry Pi kernel binary RPM.configuration/building, packaging
Skills requiredMaximum number of participants: packaging, kernel building1
Maximum number of participantsExpected result: 2 (An improved kernel configuration in the raspberrypi-kernel package, initramfs/dracut setup)
== Package Profile and Improve RPM and YUM performance on the Raspberry Pi libraries ==
The Raspberry RPM/YUM appear to perform slowly on the Pi -- which is appropriate, since the Pi includes has a number slower processor and storage system than most modern PCs -- but the performance can probably be improved. This project involves profileing the RPM/YUM operations to determine which parts of proprietary libraries. These libraries the processing are expected slowest, and then examining how those parts work to be re-licensed under an open source license see if any improvements in the coming months. These libraries should be packaged ready for inclusion in Fedora; until they speed are licensed under an open-source license, only the SRPMs should be releasedpossible.
Note that the libray headers (-devel package) should be released in source form.Skills required: profiling, programming, packaging
Expected outcomeMaximum number of participants: a raspberrypi-firmware (or bcm2835-firmware) package containing the GPU firmware.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 == This project involves taking the Pidora 19 Firstboot package and internationalizing it (making it possible to use multiple language files with Firstboot). Note that Pidora 19 is expected to use a Fedora 18-style Firstboot system (as was used in Pidora 18) rather than the firstboot system used in Fedora 19 and higher. Skills required: python, i11n using gettext, packaging
Maximum number of participants: 1
== Package Expected result: A version of firstboot and the Raspberry Pi kernel utility ==firstboot modules that are fully internationalized
The Raspi bootloader requires a special header at the start of the kernel file in order to correctly load it into memory. The tool which creates this header needs to be packaged in Fedora.== New Firstboot for Pidora 20 ==
Expected outcome: Firstboot on the Pi varies a bit from firstboot on PCs, because the software isn't installed onto storage in the same way as PCs. This project involves updating the Fedora 20 firstboot package for the Raspberry Pi kernel utilityto work with Pidora 20.
Skills required: python programming, packaging, testing
Maximum number of participants: 1
== Modify Grubby to work with Expected result: A version of the Fedora 19 or Fedora 20 firstboot that works on the Raspberry Pi kernel ==and has full support for the Pidora options (such as rootfs resizing)
On ARM systems, kernels are shipped as vmlinuz images (as == Compiler Flags on other platforms). The ''grubby'' utility is a tool which is used to configure the bootloader when a new kernel is installed, by adjusting the appropriate boot configuration (such as grub/grub2/lilo/elilo/...). On ARM systems, grubby generally calls mkimage to generate a uImage file from the vmlinuz file. On the Raspi, it will need to additionally call the Raspberry Pi kernel utility (described above) to convert the uImage into the kernel.img file.Pidora ==
Expected outcome: patches We're not sure if the compiler flags being used for grubby submitted upstream; Pidora are optimal. This project involves building a number of packages with different combinations of compiler flags, observing the ARM grubby package will correctly install results (in terms of binary size and performance) and recommending the Raspi kerneloptimal set of flags.
Skills required: packagingbuilding, scripting (bash and/or python)benchmarking
Maximum number of participants: 1
== Systemd ==Expected result: Modified RPM macros that include the optimal flags for Pidora
In Fedora 15 and later, the ''upstart'' startup system is replaced by ''systemd''. Systemd needs to be tested on the Raspi, and as much as possible, tuned to use as little memory as possible.== Avahi Configuration for Pidora ==
Expected outcome: systemd is tested and ready Avahi (zeroconf) enables discovery of computers without DNS or IP numbers. This project involves configuring Avahi for use on the Raspi Pi, so that other computers can connect to it by name without DNS support. This configuration must then be packaged in F17such a way that it can be included in the Pidora composes without causing conflicts.
Skills required: debuggingtesting, sysadmin problem solving, testing/QApackaging
Maximum number of participants: 1
== Firstboot ==Expected results: A configuration package that, when installed, will correctly set up Avahi for local discovery on the Pi
The ''firstboot'' package asks == Upstream the user specific questions when the system starts for the first time. Since Raspberry Pi systems are installed by copying the SD card, additional questions should be asked during the first boot -- for example, the root password and timezone should be set. This project involves writing and packaging additional modules for firstboot for use with the Raspi (and potentially other ARM systems).Pidora RPM Changes ==
Expected outcome: There are some small changes to the RPM system that have been done for firstboot committed Pidora. These changes need to be included in the upstream version of RPM. This project involves working with upstream, or a package to ensure that extends firstboot packaged these changes are in the correct format and included in Fedorasubsequent releases of RPM.
Skills required: scripting (python)interpersonal skills - negotiation, patch creation, packaging
Maximum number of participants: 1
== Package Scratch ==Expected results: Pidora RPM changes will be upstreamed
''Scratch'' is an educational programming environment from MIT. It's not licensed under an OSI-approved license, but the upstream project has indicated a willingness to relicense it. An OSI-approved license should be negotiated, and the software packaged for Fedora.== Wayland ==
Fedora 20 includes support for the Wayland display system. The RaspberryPi foundation has been working on a Wayland implementation for the Pi. This project involves getting the two to work well together. Skills required: system administration, debugging, possibly some programming, packaging Maximum number of participants: 2 Expected outcomeresults: 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 == The Raspberry Pi Foundation maintains a Fedora kernel fork that is updated frequently. We would like to package kernel and firmware changes on a daily basis, and have these available in a testing repository so that anyone can use them. Periodically, we will select a kernel-firmware combination from this testing repository and make it available as the main Pidora kernel. Skills required: scripting (python and/or bash), packaging Maximum number of Scratchparticipants: 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 == Originally, the VideoCore IV GPU on the Pi was used with proprietary libraries which were only available in compiled form, so the raspberrypi-vc package was originally set up to package prebuilt binaries and not build from source. The source code for these libraries is now available, and the raspberrypi-vc package should be changed to build from source (this will help with SELinux compatibility).
Skills required: packaging
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 == Package KidsRuby Write an Updated Boot Screen ==
''KidsRuby'' is Pidora includes an educational programming editor/IDE for RubyOpenGL-powered boot screen, which should be packaged for uses the Raspberry Pi FedoraRemix logo. The current code does not use OpenGL very effectively.
Expected outcome: a Fedora This package of KidsRubyshould be updated to use OpenGL better and to use the Pidora logo.
Skills required: C programming, OpenGL programming, packaging
Maximum number of participants: 1
Expected result: A visually appealing boot screen, packaged as a drop-in replacement for the current boot screen == Create a SD Card Installation Tool Update rootfs-resize == The rootfs-resize package resizes the Pidora rootfs after installation. It works with primary partitions, and it works with the NOOBS system, but it doesn't work with a NOOBS-style layout outside of NOOBS (i.e., where the rootfs is placed in an extended partition). This project involves extending rootfs-resize so that it can resize extended and logical partitions as well as primary partitions.
The Fedora LiveUSB-Creator tool can run on a Fedora or on a Windows Skills required: Python scripting/programming, system and can be used to download and install a Fedora live disc image on a USB flash drive. This tool should be adapted so that it can also create an SD card for the Raspberry Pi (and hopefully other devices) -- so that a user can install the Raspberry Pi remix without using commands such as fdisk, ddadministration, and resize2fs.packaging
Note: the liveusb-creator tool goes through a Maximum number of setup steps that are not required for an SD card. On the other hand, creating an SD card involves a few steps that are not necessary for a live USB. Therefore it might be appropriate to create a separate tool rather than modifying the liveusb-creator tool. Also, there are other efforts taking place within the Raspberry Pi community which might do the same thing; if one of those efforts reaches a stable release, it might be possible to package that for Fedora.participants: 1
Expected outcomeresult: a Fedora An updated rootfs-resize package of a tool to install the Raspi distribution image on an SD card. Ideally, a Windows version as well.
Skills required: scripting (python), system administration, testing/QA== Packaging Pi-compatible Software ==
Maximum There are a number of participants: 3 (scriptingPi-specific software packages that could/should be included in Pidora. Select one, Fedora packaging and testingpackage it, Windows packaging and testingget it into Fedora (preferred)or directly into Pidora.
== Create {{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 F17 Raspberry Pi image ==, in order to be approved as a project.}}
Based on feedback on the F14 Raspberry Pi image, create an F17 alphaSome 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/beta image for vc so that source code expecting to find the Raspberry Pi.VC libraries there will work successfully)* Quick2wire python library
This will involve modifying (or creating) a script to produce See the Raspi rootfs, putting the rootfs and image into the final format [http://trac.proximity.on.ca/projects/rpfr/report/1 Pidora Bug Tracker] for ideas for distributionother packages that people want included in Pidora.
NoteSkills required: the final version of F17 won't be ready until just after this course ends. The image will need to be based on the F17 alpha/beta package set.packaging
Expected outcomeMaximum number of participants: a F17 image creation script.1 per package (identify the package!)
Skills requiredExpected result: system administrationA working, scripting, testing/QAPidora-compatible package that has gone through package review
Maximum number of participants: 2 (scripting, testing)== Clean Up the Pidora Kickstart File ==
== Create the Raspi Repositories ==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.
Set up the repositories to distribute the F17 Raspberry Pi remix files, including:* Setting up the signing keys* Creating a standard signing procedure Recent (SOPbut not necessarily latest) for signing* Creating a 'release' package containing the public keys and repo fileskickstart: http://scotland.proximity.on.ca/raspberrypi/test-releases/rpfr18v6/latest/pidora-18.ks
Expected outcomeSkills required: repospackaging, release package, SOPcomposing
Maximum number of participants: 1
= Fedora-ARM Projects =Expeccted result: A clean kickstart file for Pidora 19
== Set up a Koji Test Hub =Infrastructure Projects =
We have a Koji Hub to run the Fedora ARM build farm. However, we should have a separate hub == Bug Tracker for testing configurations before deploying them to the production server. This project involves setting up a test hub so that koji hub/builder configurations can be tested independently from the production server.Pidora ==
Expected outcome: Pidora currently uses a koji test server set up Trac instance for bug tracking. However, there is a lot of spammer activity on that system. Implement an effective spam prevention system on EnglandTrac, or implement an alternative bug tracking system such as Bugzilla. Document the solution for future maintainability.
Skills required: system administration, documentation
Maximum number of participants: 1
Expected result: A spam-resistant bug tracking system == Document YUM Api 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
Yum is written in Python, but the yum API is poorly documented: the usual answer to a question about the API is: "ask Seth Vidal".== Mirrorlist CGI Script ==
'''Yum uses a mirrorlist retrieved from a server to determine which mirrors to use for downloading packages. This is mirrorlist can be generated by a hard projectscript (e.''' Do not take it on unless you are really willing g., to randomize or to optimize mirror selection), but at the present time a static file is just passed through to complete this taskthe yum client.
Expected outcomeSkills required: a guide to the yum API.scripting, testing
Skills requiredMaximum number of participants: investigation, scripting (python), writing1
Maximum number of participantsExpected result: 2An updated mirrorlist script
