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 [[Winter 2012 Fall 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 required: packaging, kernel building Maximum number of participants: 2 (kernel package, initramfs/dracut setup) == Package the Raspberry Pi libraries ==1
The Raspberry Pi includes a number of proprietary libraries. These libraries are expected to be re-licensed under an open source license Expected result: An improved kernel configuration in the coming months. These libraries should be packaged ready for inclusion in Fedora; until they are licensed under an openraspberrypi-source license, only the SRPMs should be released.kernel package
Note that == Profile and Improve RPM and YUM performance on the libray headers (-devel package) should be released in source form.Pi ==
Expected outcome: RPM/YUM appear to perform slowly on the Pi -- which is appropriate, since the Pi has a raspberrypislower processor and storage system than most modern PCs -firmware (or bcm2835-firmware) package containing but the performance can probably be improved. This project involves profileing the RPM/YUM operations to determine which parts of the GPU firmwareprocessing are slowest, and then examining how those parts work to see if any improvements in speed are possible.
Skills required: profiling, programming, packaging
Maximum number of participants: 1
== Package Expected result: Either a report proving that RPM/YUM are as fast as can be expected on the Raspberry Pi kernel utility ==, or changes to affected packages to improve performance
The Raspi bootloader requires a special header at the start of the kernel file == Internationalization Support in order to correctly load it into memory. The tool which creates this header needs to be packaged in Fedora.Firstboot for Pidora 19 ==
Expected outcome: 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 package for 18-style Firstboot system (as was used in Pidora 18) rather than the Raspberry Pi kernel utilityfirstboot system used in Fedora 19 and higher.
Skills required: python, i11n using gettext, packaging
Maximum number of participants: 1
== Modify Grubby to work with Expected result: A version of firstboot and the Raspberry Pi kernel ==firstboot modules that are fully internationalized
On ARM systems, kernels are shipped as vmlinuz images (as 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.== New Firstboot for Pidora 20 ==
Expected outcome: patches for grubby submitted upstream; Firstboot on the ARM grubby 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 will correctly install the Raspi kernelto work with Pidora 20.
Skills required: python programming, packaging, scripting (bash and/or python), testing/QA
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) == Create the raspi-logos and raspi-fedora-remix-release-notes packages Compiler Flags on Pidora ==
Fedora usually contains three We're not sure if the compiler flags being used for Pidora are optimal. This project involves building a number of packages that cannot be redistributed with derived different combinations of compiler flags, observing the results (remixedin terms of binary size and performance) versions:* fedora-logos* fedora-release* fedora-release-notesand recommending the optimal set of flags.
Dummy versions Skills required: building, benchmarking Maximum number of these packages are available, substituting generic- for fedora- (i.e., generic-logos, generic-release, and generic-release-notes).participants: 1
The fedora-release package has been replaced by Expected result: Modified RPM macros that include the raspberrypi-fedora-remix-release package.optimal flags for Pidora
This project involves creating a replacement == Avahi Configuration 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.* raspberrypi-fedora-remix-release-notes -- This package will contain documentation on the Remix, including notes on how to install it on an SD card, trademarks, use of the GPIO controls, etc.Pidora ==
Expected outcome: two packagesAvahi (zeroconf) enables discovery of computers without DNS or IP numbers. This project involves configuring Avahi for use on the Pi, so that other computers can connect to it by name without DNS support. This configuration must then be packaged in such a way that it can be included in the Pidora composes without causing conflicts.
Skills required: documentation writing, graphicstesting, packaging
Maximum number of peopleparticipants: 2 (logos, release notes)1
== Systemd ==Expected results: A configuration package that, when installed, will correctly set up Avahi for local discovery on the Pi
In Fedora 15 and later, == Upstream 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.Pidora RPM Changes ==
Expected outcome: systemd is tested and ready There are some small changes to the RPM system that have been done for use on Pidora. These changes need to be included in the upstream version of RPM. This project involves working with upstream to ensure that these changes are in the Raspi correct format and included in F17subsequent releases of RPM.
Skills required: debugginginterpersonal skills - negotiation, sysadmin problem solvingpatch creation, testing/QApackaging
Maximum number of participants: 1
== Firstboot ==Expected results: Pidora RPM changes will be upstreamed
The ''firstboot'' package asks 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).== Wayland ==
Expected outcome: changes Fedora 20 includes support for firstboot committed upstream, or the Wayland display system. The RaspberryPi foundation has been working on a package that extends firstboot packaged in FedoraWayland implementation for the Pi. This project involves getting the two to work well together.
Skills required: scripting (python)system administration, debugging, possibly some programming, packaging
Maximum number of participants: 12
== Package Scratch ==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)
[http://scratch.mit.edu/ 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, == Automate Pidora Kernel and the software packaged for Fedora.Firmware Building ==
Expected outcome: The Raspberry Pi Foundation maintains a Fedora kernel fork that is updated frequently. We would like to package of Scratchkernel 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 participants: 1
== Package KidsRuby ==Expected results: Raspberry Pi kernel and firmware updates will be included in a package in a testing repository through an automated (cron'd) process
[http://kidsruby.com/download KidsRuby] is an educational programming editor/IDE for Ruby, which should be packaged for Fedora.== Change raspberrypi-vc Package to Build from Source ==
Expected outcome: a Fedora 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 of KidsRubywas 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 == Create a SD Card Installation Tool Write an Updated Boot Screen == Pidora includes an OpenGL-powered boot screen, which uses the Raspberry Pi Fedora Remix logo. The current code does not use OpenGL very effectively. This package should be updated to use OpenGL better and to use the Pidora logo.
The Fedora LiveUSB-Creator tool can run on a Fedora or on a Windows 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 fdiskSkills required: C programming, ddOpenGL programming, 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
'''NoteExpected result:''' Jon Chiappetta has started work on A visually appealing boot screen, packaged as a similar tool drop-- participants in this project should co-ordinate/work with Jon on this tool (fossjon in #seneca).replacement for the current boot screen
Expected outcome: a Fedora package of a tool to install the Raspi distribution image on an SD card. Ideally, a Windows version as well.== Update rootfs-resize ==
Skills required: scripting (python)The rootfs-resize package resizes the Pidora rootfs after installation. It works with primary partitions, and it works with the NOOBS system administration, testing/QAbut 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.
Maximum number of participantsSkills required: 3 (Python scripting/programming, Fedora packaging and testingsystem administration, Windows packaging and testing)----
ContentsMaximum number of participants: 1
[hide]Expected result: An updated rootfs-resize package
1 Project Name1.1 Project Description1.2 Project Leader(s)1.3 Project Contributor(s)1.4 Project Details1.5 Project Plan1.6 Communication1.6.1 Mailing Lists1.6.2 Upsteam Wiki and Web1.6.3 Links/Bugs/Tracking1.6.4 Source Code Control1.6.5 Blogs1.6.5.1 Seneca Particpants1.6.5.2 Non== Packaging Pi-Seneca Participants1.6.5.3 Planetscompatible Software ==
1There 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.7 Project News
[edit] Project Name [edit] Project Description [edit] Project Leader{{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 (sa) [edit] Project Contributorbroadly-useful Pi-specific software, or (sb) [edit] Project Details [edit] Project Plana substantial software package that would be generally useful in Fedora and specifically on the Pi, in order to be approved as a project.}}
Tracking mechanism 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 (bugzilla, trac, github, ...symlink farm in /opt/vc so that source code expecting to find the VC libraries there will work successfully):* Quick2wire python library
Key contactsSee the [http://trac.proximity.on.ca/projects/rpfr/report/1 Pidora Bug Tracker] for ideas for other packages that people want included in Pidora.
Goals for each release and plans for reaching those goalsSkills required:packaging
0.Maximum number of participants: 10.20.3per package (identify the package!)
[edit] Communication [edit] Mailing Lists [edit] Upsteam Wiki and Web [edit] Links/Bugs/Tracking [edit] Source Code Control [edit] Blogs [edit] Seneca Particpants [edit] NonExpected result: A working, Pidora-Seneca Participants [edit] Planets [edit] Project Newscompatible package that has gone through package review
== Create Clean Up the F17 Raspberry Pi image Pidora Kickstart File ==
Based on feedback on the F14 Raspberry Pi image, create an F17 alpha/beta image The Pidora images are composed using a kickstart-based process. The kickstart file could be cleaned up for the Raspberry Pibetter readability and smallest-functional package selection.
This will involve modifying Recent (or creatingbut not necessarily latest) a script to produce the Raspi rootfs, putting the rootfs and image into the final format for distributionkickstart: http://scotland.proximity.on.ca/raspberrypi/test-releases/rpfr18v6/latest/pidora-18.ks
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, composing
Expected outcomeMaximum number of participants: a F17 image creation script.1
Skills requiredExpeccted result: system administration, scripting, testing/QAA clean kickstart file for Pidora 19
Maximum number of participants: 2 (scripting, testing)= Infrastructure Projects =
== Create the Raspi Repositories Bug Tracker for Pidora ==
Set up the repositories to distribute the F17 Raspberry Pi remix files, including:* Setting up the signing keys* Creating Pidora currently uses a standard signing procedure (SOP) Trac instance for signing* Creating bug tracking. However, there is a 'release' package containing lot of spammer activity on that system. Implement an effective spam prevention system on Trac, or implement an alternative bug tracking system such as Bugzilla. Document the public keys and repo filessolution for future maintainability.
Expected outcomeSkills required: repossystem administration, release package, SOPdocumentation
Maximum number of participants: 1
= FedoraExpected result: A spam-ARM Projects = == Set up a Koji Test Hub ==resistant bug tracking system
We have == Create a Koji Hub to run the Fedora ARM build farm. However, we should have a separate hub Fedpkg-compatible Package Repository 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: Fedpkg is a koji test server 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 on EnglandFedpkg, 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: 13
== Document YUM Api ==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
