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)1
== Package Expected result: An improved kernel configuration in the Raspberry Pi libraries ==raspberrypi-kernel package
The Raspberry == Profile and Improve RPM and YUM performance on the Pi includes a number of proprietary libraries. These libraries are expected to be re-licensed under an open source license in the coming months. These libraries should be packaged ready for inclusion in Fedora; until they are licensed under an open-source license, only the SRPMs should be released.==
Note that RPM/YUM appear to perform slowly on the libray headers (Pi -devel package) should - which is appropriate, since the Pi has a slower processor and storage system than most modern PCs -- but the performance can probably be released improved. This project involves profileing the RPM/YUM operations to determine which parts of the processing are slowest, and then examining how those parts work to see if any improvements in source formspeed are possible.
Expected outcome: a raspberrypi-firmware (or bcm2835-firmware) package containing the GPU firmware. 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
== Create Expected result: A version of the raspi-logos Fedora 19 or Fedora 20 firstboot that works on the Pi and raspi-fedora-remix-release-notes packages ==has full support for the Pidora options (such as rootfs resizing)
Fedora usually contains three packages that cannot be redistributed with derived (remixed) versions:* fedora-logos* fedora-release* fedora-release-notes== Compiler Flags on Pidora ==
Dummy versions We're not sure if the compiler flags being used for Pidora are optimal. This project involves building a number of these packages are availablewith different combinations of compiler flags, substituting generic- for fedora- observing the results (i.e., generic-logos, generic-release, in terms of binary size and generic-release-notesperformance)and recommending the optimal set of flags.
The fedora-release package has been replaced by the raspberrypi-fedora-remix-release package.Skills required: building, benchmarking
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.* 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. Expected outcome: two packages. Skills required: documentation writing, graphics, packaging Maximum number of peopleparticipants: 2 (logos, release notes)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
[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, and the software packaged for Fedora.== Wayland ==
Expected outcome: Fedora 20 includes support for the Wayland display system. The RaspberryPi foundation has been working on a Fedora package of ScratchWayland 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: 12
== Package KidsRuby ==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://kidsruby.com/download KidsRuby] is an educational programming editor/IDE for Ruby, which should be packaged for Fedora.== Automate Pidora Kernel and Firmware Building ==
Expected outcome: The Raspberry Pi Foundation maintains a Fedora kernel fork that is updated frequently. We would like to package of KidsRubykernel 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
== Create Expected results: Raspberry Pi kernel and firmware updates will be included in a SD Card Installation Tool ==package in a testing repository through an automated (cron'd) process
The Fedora LiveUSB== Change raspberrypi-Creator tool can run on a Fedora or on a Windows system and can be used vc Package 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, dd, and resize2fs.Build from Source ==
Note: Originally, the liveusb-creator tool goes through a number of setup steps that are not required for an SD card. On VideoCore IV GPU on the other handPi was used with proprietary libraries which were only available in compiled form, 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 so the liveusbraspberrypi-creator toolvc package was originally set up to package prebuilt binaries and not build from source. AlsoThe source code for these libraries is now available, there are other efforts taking place within and the Raspberry Pi community which might do the same thing; if one of those efforts reaches a stable release, it might raspberrypi-vc package should be possible changed to package that for Fedorabuild from source (this will help with SELinux compatibility).
'''NoteSkills required:'''Maximum number of participants: 3packaging
= Project Name =<!-- Replace "Project Name" with the actual name Maximum number of the project in the line above. -->participants: 1
== Project Description ==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
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->== Write an Updated Boot Screen ==
== Project Leader(s) ==Pidora includes an OpenGL-powered boot screen, which uses the Raspberry Pi Fedora Remix logo. The current code does not use OpenGL very effectively.
<!-- Name(s) of primary people working on the project. If you want This package should be updated to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki use OpenGL better and to blog sitesuse the Pidora logo. -->
== Project Contributor(s) ==Skills required: C programming, OpenGL programming, packaging
<!-- Name(s) Maximum number of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.participants: 1
NOTEExpected result: only Project Leader(s) should add names here. You should not add your own name to A visually appealing boot screen, packaged as a drop-in replacement for the Contributor list. -->current boot screen
== Project Details Update rootfs-resize ==
<!The rootfs-- Provides more depth than resize package resizes the Project DescriptionPidora rootfs after installation. This is It works with primary partitions, and it works with the place for technical discussionsNOOBS system, project specsbut it doesn't work with a NOOBS-style layout outside of NOOBS (i.e., or other detailswhere the rootfs is placed in an extended partition). If this gets very long, you might consider breaking this part into multiple pages This project involves extending rootfs-resize so that it can resize extended and linking to themlogical partitions as well as primary partitions. -->
== Project Plan ==Skills required: Python scripting/programming, system administration, packaging
Tracking mechanism (bugzilla, trac, github, ...)Maximum number of participants:1
Key contactsExpected result:<!An updated rootfs-- Add links to any mentors or key participants in the community. -->resize package
Goals for each release and plans for reaching those goals:<!== Packaging Pi-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->* 0.1* 0.2* 0.3compatible Software ==
== Communication ==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.
=== Mailing Lists ===<!{{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- Add any appropriate mailing lists to which you are subscribed specific software, or (e.g.b) a substantial software package that would be generally useful in Fedora and specifically on the Pi, see http://lists.fedoraprojectin order to be approved as a project.org -->}}
=== Upsteam Wiki and Web ===Some possible packages ideas to get you started:* Adafruit WebIDE* Adafruit libraries/tools/etc (select a specific piece of software)* OMXplayer<!-- Links * Vidcore library compatibility package (symlink farm in /opt/vc so that source code expecting to upstream wiki/web pages -->find the VC libraries there will work successfully)* Quick2wire python library
=== LinksSee the [http:/Bugs/Tracking ===<!-- Add a link to any page(s) related to your work, including the bug numbers (trac.proximity.on bugzilla or trac) -->.ca/projects/rpfr/report/1 Pidora Bug Tracker] for ideas for other packages that people want included in Pidora.
=== Source Code Control ===<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->Skills required: packaging
=== Blogs ===<Maximum number of participants: 1 per package (identify the package!-- Links to the blogs of people involved, both inside and outside Seneca -->)
==== Seneca Particpants ====Expected result: A working, Pidora-compatible package that has gone through package review
==Clean Up the Pidora Kickstart File == Non-Seneca Participants ====<!-- Links to the blogs of any non-Seneca participants in this project -->
==== Planets ====<!The Pidora images are composed using a kickstart-based process. The kickstart file could be cleaned up for better readability and smallest- Links to any planets related to this project -->functional package selection.
== Project News ==Recent (but not necessarily latest) kickstart: http://scotland.proximity.on.ca/raspberrypi/test-releases/rpfr18v6/latest/pidora-18.ks
<!-- This is where a permanent record of your releases and updates will go. In these you should discuss the status or your workSkills required: packaging, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->composing
== Create the F17 Raspberry Pi image ==Maximum number of participants: 1
Based on feedback on the F14 Raspberry Pi image, create an F17 alpha/beta image Expeccted result: A clean kickstart file for the Raspberry Pi.Pidora 19
This will involve modifying (or creating) a script to produce the Raspi rootfs, putting the rootfs and image into the final format for distribution.= Infrastructure Projects =
Note: 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.== Bug Tracker for Pidora ==
Expected outcome: Pidora currently uses a F17 image creation scriptTrac instance for bug tracking. However, there is a 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 solution for future maintainability.
Skills required: system administration, scripting, testing/QAdocumentation
Maximum number of participants: 2 (scripting, testing)1
== Create the Raspi Repositories ==Expected result: A spam-resistant bug tracking system
Set up the repositories to distribute the F17 Raspberry Pi remix files, including:* Setting up the signing keys* Creating == Create a standard signing procedure (SOP) Fedpkg-compatible Package Repository for signing* Creating a 'release' package containing the public keys and repo filesPidora ==
Expected outcome: reposFedpkg 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, release a packagedatabase (pkgdb), SOPGIT 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.
Maximum number of participantsSkills required: 1system administration, testing, packaging
= Fedora-ARM Projects =Maximum number of participants: 3
== Set Expected result: A working Fedpkg repository, plus configuration files packaged up a Koji Test Hub ==in an RPM
We have a Koji Hub to run the Fedora ARM build farm. However, we should have a separate hub 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.== Mirrorlist CGI Script ==
Expected outcome: Yum uses a mirrorlist retrieved from a koji test server set up on Englandto 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: system administrationscripting, testing
Maximum number of participants: 1
== Document YUM Api == 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". '''This is a hard project.''' Do not take it on unless you are really willing to complete this task. Expected outcome: a guide to the yum API. Skills required: investigation, scripting (python), writing Maximum number of participantsresult: 2An updated mirrorlist script
