[[Category:SBR600]]{{Chris Tyler Draft}}[[Category:Winter 2012 SBR600]]
= 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 [[Winter 2011 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]]).
== Notes ==
Each project listing contains a general description, plus this information:
* Maximum number of students - Do not exceed this number without approval from [[User:Chris Tyler|your professor]].
* Skills required - This is a rough list of some of the skills required for this project. This list may be incomplete or inaccurate, but it will give you a starting point in evaluating whether this project is a good fit for you. It is not assumed that you will have all of these skills at the outset of the project -- some of them will be picked up as you do the project.
* 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.
{{Admon/important|Individual Deliverables|Note that when multiple people are working on the same project, they will have independent deliverables -- it's not really group work, but rather separate, closely related projects.}}
== [[Sample Project]] ==
NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the '''Project Leader(s)''' section on the project page. Otherwise, you can become a contributor later.
= Raspberry Pi FedoraRemix Projects = == Update the 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 firmware, as well as options that are not commonly used and may conflict with common use-cases - for example, the current configuration files cause kernel start-ARM Projects up messages to be reported on the serial port. This is rarely used, any may cause conflicts with other devices connected to that port (e.g., LCD displays). Skills required: packaging Maximum number of participants: 1 Expected result: An updated, working raspberrypi-config package == Kernel Configuration Files == The build process for the kernel uses a configuration file to 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 combination of the RaspberryPi default configuration file and the Fedora configuration file. This project involves reviewing the Pidora kernel configuration to optimize it for the widest possible range of use-cases while ensuring a fairly small kernel image size. Skills required: kernel configuration/building, packaging 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 == RPM/YUM appear to perform slowly on the Pi -- which is appropriate, since the Pi has a 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 the processing 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 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 Expected result: A version of firstboot and the firstboot modules that are fully internationalized == New Firstboot for Pidora 20 == 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 to work with Pidora 20. Skills required: python programming, packaging, testing 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 == We're not sure if the compiler flags being used for Pidora are optimal. This project involves building a number of packages with different combinations of compiler flags, observing the results (in terms of binary size and performance) and recommending the optimal set of flags. Skills required: building, benchmarking Maximum number of participants: 1 Expected result: Modified RPM macros that include the optimal flags for Pidora == Avahi Configuration for Pidora == Avahi (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: testing, packaging Maximum number of participants: 1 Expected results: A configuration package that, when installed, will correctly set up Avahi for local discovery on the Pi == Upstream the Pidora RPM Changes == There are some small changes to the RPM system that have been done for 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 correct format and included in subsequent releases of RPM. Skills required: interpersonal skills - negotiation, patch creation, packaging
== System Administration Tools for the ARM Build Farm ==Maximum number of participants: 1
As the ARM build farm grows with the addition of the PandaBoard systems, the need for efficient system management tools increases. The previous semesters' students started the work of setting up ''nagios'' (monitoring) and ''func'' (group control) tools. This project involves configuring these tools to work with all of the systems in the ARM build farm, as well as setting up and configuring the ''puppet'' (configuration file management) tool.Expected results: Pidora RPM changes will be upstreamed
* Maximum number of students: 2* Skills required: Linux system administration, problem solving, documentation writing* Resources: wiki notes from previous semesters* Expected result: nagios, func, and puppet working across the entire ARM build farm; documentation on how to use these tools on the farm and how to add additional devices* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]== Wayland ==
== Koji Hub Fedora 20 includes support for the Wayland display system. The RaspberryPi foundation has been working on ARM ==a Wayland implementation for the Pi. This project involves getting the two to work well together.
The [httpSkills required://arm.koji.fedoraproject.org Fedora-ARM koji] system uses [[CDOT_Development_Systems#Machine_names.2C_IPs.2C_and_Status|HongKong]]administration, an x86_64 systemdebugging, as the [[:fedora:Koji|Koji]] hubpossibly some programming, along with a group of ARM builders.packaging
Ideally, it would be nice to prove the ability Maximum number of the Fedora-ARM project to be entirely self-hosting by using an ARM system as the Koji hub (this is sometimes called "Eating your own dogfood" in the industry). This project involves configuring the [httpparticipants://www.globalscaletechnologies.com/t-openrdcdetails.aspx OpenRD-Client] system as Koji hub and determining if this is a viable configuration.2
* Maximum number of students: 1* Skills required: Linux system administration, problem solving, documentation writing* Resources: wiki notes from previous 2 semesters, access to the OpenRD and a GuruPlug or BeagleBoard* Expected resultresults: koji-hub running The Wayland snapshot in Fedora 20 will be usable on the OpenRDPi (Ideal: fully packaged; a recommendation Acceptable: Instructions on whether the OpenRD is suitable for use as a hub for the Fedora-ARM project* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]how to set it up)
== Device Support Automate Pidora Kernel and Testing: PandaBoard Firmware Building ==
Various ARM devices need different driver sets The Raspberry Pi Foundation maintains a kernel fork that is updated frequently. We would like to package kernel and/or kernels. This project will test the Fedora-ARM system firmware changes on the PandaBoarda daily basis, creating and have these available in a kernel testing repository so that works well with itanyone can use them. Periodically, we will select a kernel-firmware combination from this testing repository and figuring out how to use make it available as many of the built-in peripherals as possiblemain Pidora kernel.
* Maximum number of students: 1* Skills required: Linux system administration, kernel building, research, documentation writing* Resources: a PandaBoard, notes from other PanadaBoard support projects* Expected result: a kernel scripting (python and/or kernelsbash) for use with the PanadaBoard and the Fedora 12 or Fedora 13 root filesystems; user documentation on how to set up the PandaBoard with Fedora* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]packaging
== Add PandaBoards to the Fedora-ARM Build System ==Maximum number of participants: 1
We have 15 PandaBoards on order for the Fedora-ARM build farm. These machines need to Expected results: Raspberry Pi kernel and firmware updates will be configured and added into the farm, and then optimized to build packages as quickly as possible.included in a package in a testing repository through an automated (cron'd) process
* Maximum number of students: 2* Skills required: system administration, network administration, troubleshooting, benchmarking* Resources: PandaBoard systems* Expected result: a filesystem image and documented standard operating procedure for adding PanadaBoards == Change raspberrypi-vc Package to the build farm; new PandaBoards actively building* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]Build from Source ==
== iSCSI/AoE Support ==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).
iSCSI (SCSI over TCP/IP) and AoE (ATA-over-ethernet) are different SAN protocols that can use a standard network. iSCSI did not work reliably in Fedora 12, but will be needed by future ARM server systems. AoE has not been well-tested on ARM systems. iSCSI and AoE need to be tested for stability and performance, and the best solution implemented on the ARM build farm.Skills required: packaging
* Maximium Maximum number of studentsparticipants: 2* Skills required: Linux system administration, debugging and troubleshooting, C programming (?), benchmarking, documentation writing* Resources: an ARM system, CDOT PC systems* Expected result: iSCSI on ARM fixed and tested, and changes pushed upstream; AoE tested on ARM; report comparing iSCSI and AoE performance on ARM; ARM buildsystem configured to use a high-performing iSCSI or AoE storage solution in place of the existing NFS system* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]1
== RPMExpected result: A new version of the raspberrypi-based Kernels for Fedora ARM ==vc package that build from source, is compatible with the current Pidora package, and can be easily updated/maintained
On a PC, Fedora manages and updates kernels as RPM packages, which modify ''grub'' boot parameters and the initial ram disk (initrd, configured by ''dracut''). On Fedora-ARM systems, the kernel is not managed via RPMs, grub is not used, and the initrd system is rarely used. This project involves understanding how the PC (i386/x86_64) kernel/boot/initrd system works, determining which pieces can be reused on Fedora-ARM and which pieces need to be adapted or replaced, and implementing RPM-based kernel management for ARM.== Write an Updated Boot Screen ==
* Maximum number of students: 3* Skills required: Linux system administration, script writing, RPM packaging, kernel building, initrd debugging* Resources: Pidora includes an ARM system* Expected result: RPMOpenGL-based Kernels work on Fedora-ARMpowered boot screen, with changes committed upstream; documentation about which uses the differences between kernel management on ARM and on PCs* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:PaulRaspberry Pi Fedora Remix logo. The current code does not use OpenGL very effectively.W|PaulW]]
== Fedora-ARM Communication ==This package should be updated to use OpenGL better and to use the Pidora logo.
We're not doing a great job of communicating how the Fedora-ARM project is doing. The [httpSkills required://arm.koji.fedoraproject.org/status status page] is very bare-bones and doesn't convey a lot of informationC programming, the Fedora-ARM wiki pages need to be made more useful to prospective usersOpenGL programming, and we need an effective communication strategy with the rest of the Fedora community. This project involves writing some web scripts to create a easy-to-use, informative status page (showing, for example, the current state and progress of the ARM builds), creating user documentation on the Fedora wiki, and fostering effective communication within the Fedora-ARM project and the larger Fedora community.packaging
* Maximum number of studentsparticipants: 2* Skills required: Apache administration, script-writing, effective written communication skills* Resources: the web server on HongKong, various data sources within the Fedora-ARM build system, Fedora project communication tools, access to ARM systems* Expected result: a useful (easy-to-use, informative) and automatically-updated Fedora-ARM status page; improved user documentation on the Fedora wiki (e.g., how to set up Fedora-ARM on common devices); better communication on the arm@lists.fedoraproject.org mailing list and the #fedora-arm IRC channel* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]1
== FedoraExpected result: A visually appealing boot screen, packaged as a drop-ARM Package Building and Troubleshooting ==in replacement for the current boot screen
The [[Fedora ARM Secondary Architecture|Fedora== Update rootfs-ARM]] project is building Fedora 13/14/15 for the ARM architecture. As this proceeds, various problems arise. For example:* Some packages fail to build for ARM. They can be fixed up to build successfully on ARM, or if that's not possible, marked as unsuitable for ARM (ExlcudeArch).* If a group of packages is built to work with a specific version of a library, and a newer version of that library replaces the older version, then the packages that rely on that library can break. This can often be remedied simply by rebuilding the broken package; in other cases, patches are required.resize ==
Note 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 one package build issue will often block many other packagesit can resize extended and logical partitions as well as primary partitions.
This project involves working with other members of the Fedora ARM build team to resolve package build problems and get F13Skills required: Python scripting/F14/F15 released for ARM as soon as possible.programming, system administration, packaging
* Maximum number of studentsparticipants: 12* Skills required: packaging, troubleshooting* Expected result: problems with the Fedora-ARM builds are cleared as quickly as possible; F14-ARM released by the end of the semester* Resources: Fedora-ARM Koji build system, arm@lists.fedoraproject.org mailing list* Initial contacts: [[User:Paul.W|PaulW]], [[User:Chris Tyler|ctyler]]1
= Fedora Projects =Expected result: An updated rootfs-resize package
== Package the Weave Server Packaging Pi-compatible Software ==
Mozilla Sync is There are a technology for synchronizing personal data (bookmarksnumber of Pi-specific software packages that could/should be included in Pidora. Select one, passwords, form valuespackage it, and cookiesget it into Fedora (preferred) across multiple machines. It uses a server known as [https://wiki.mozilla.org/Labs/Weave/Sync/1.0/Setup Weave]or directly into Pidora.
This project involves {{Admon/tip|Finding Your Own Package|You can find any Pi-specific software and propose packaging Weave it for Fedora and getting your project. Note that it through the packagemust be (a) broadly-useful Pi-approval process. specific software, or (Why b) a substantial software package that would be generally useful in Fedora and specifically on the Weave server? So that people can run Pi, in order to be approved as a private version, either for enhanced security or for testing)project.}}
Some possible packages ideas to get you started:* Maximum number of students: 1Adafruit WebIDE* Skills required: Apache administration, packagingAdafruit libraries/tools/etc (select a specific piece of software)* Resources: CDOT systemsOMXplayer* Expected result: Vidcore library compatibility package (symlink farm in /opt/vc so that source code expecting to find the Weave server VC libraries there will be available in the main Fedora repositories (yum install weavework successfully)* Initial contacts: mhoyeQuick2wire python library
== Package Hadoop ==See the [http://trac.proximity.on.ca/projects/rpfr/report/1 Pidora Bug Tracker] for ideas for other packages that people want included in Pidora.
[httpSkills required://hadoop.apache.org/ Apache Hadoop] is a set of tools used for large-scale distributed computing. It would be great to get this packaged for Fedora.packaging
* Maximum number of studentsparticipants: 3* Skills required: packaging, system administration* Resources: CDOT systems* Expected result: the three Apache Hadoop subprojects 1 per package (Hadoop Common, HDFS, and MapReduce) will be available in identify the main Fedora repositories (yum install hadoop-common hdfs mapreducepackage!)* Initial contacts: [[User:Chris Tyler|ctyler]]
== Package the WIX Toolchain ==Expected result: A working, Pidora-compatible package that has gone through package review
WIX is an open-source packaging system for Microsoft Windows software. It is used to prepare software packages that can be installed on a Windows machine. However, == Clean Up the WIX tools themselves can run on Linux.Pidora Kickstart File ==
This project involves packaging WIX The Pidora images are composed using a kickstart-based process. The kickstart file could be cleaned up for Fedora better readability and getting it through the smallest-functional package-approval processselection.
* Maximum number of students: 1* Skills required: packaging* Resources: CDOT systems* Expected result: the WIX software will be available in the main Fedora repositories Recent (yum install wixbut not necessarily latest)* Initial contactskickstart: http: mhoye//scotland.proximity.on.ca/raspberrypi/test-releases/rpfr18v6/latest/pidora-18.ks
<!-- == fedpkg Test Suite ==Skills required: packaging, composing
''fedpkg'' is a new Fedora packager tool written by Jesse Keating; it's one Maximum number of the main command-line tools that a packager will use. It needs a test suite, so that as new features are added, regressions can be detected.participants: 1
* Maximum number of studentsExpeccted result: 2* Initial contacts: [http://jkeating.livejournal.com/ Oxf13]-->== Koji Setup Documentation ==A clean kickstart file for Pidora 19
Koji documentation is obsolete and needs a major overhaul. This project involves reading the current documentation, updating and editing it, and testing it by setting up a Koji system.= Infrastructure Projects =
* Maximum number of students: 2* Skills required: writing, system administration* Resources: CDOT systems, Wiki* Expected result: a complete, well-written guide to setting up a Koji system (from A-Z)* Initial contacts: [[User:Chris Tyler|ctyler]], dgilmore== Bug Tracker for Pidora ==
== AutoQA ==[[:fedora:AutoQA|AutoQA]] is an automated test system Pidora currently uses a Trac instance for Fedorabug tracking. At present However, there are event watchers for koji builds, bodhi updates, repo changes, and nightly installed images; these events trigger is a small number lot of testsspammer activity on that system. Implement an effective spam prevention system on Trac, but more tests are neededor implement an alternative bug tracking system such as Bugzilla. Document the solution for future maintainability.
* Maximum number of students: 3* Skills requiresrequired: Python scripting, scripting, system administration, packaging* Resources: CDOT systems* Expected results: additional tests for AutoQA, accepted/committed into the main AutoQA codebase* Initial contacts: [[:fedora:User:JLaska|JLaska]]documentation
= Fedora-Mozilla Projects =Maximum number of participants: 1
== Repository Setup for Mozilla Nightlies and Betas ==Expected result: A spam-resistant bug tracking system
Many web developers want access to the latest Firefox pre-releases, including the nightly builds and beta releases. Mozilla's build team wants to make these accessible as parallel-installable binaries, released through == Create a FedoraFedpkg-compatible repository. Last semester, a group of SBR600 students set most of this up; this project involves extending and improving their work.<!-- Subprojects:* Build configuration Package Repository for the RPM files.* Repository configuration RPMs.* Getting SELinux to work with the nightlies.-->Pidora ==
See [https://bugzillaFedpkg is a tool used to manage Fedora packages using GIT (and http).mozillaWe'd like to be able to use it for Pidora-specific (non-Fedora) packages as well.org/show_bugTo set up Fedpkg, a package database (pkgdb), GIT repository, http repository, and Fedpg configuration will be required.cgi?id=600317 bug 600317]Completion of the various components of this project should result in a usable, RPM-installable Fedpkg configuration for Pidora packages.
* Maximum number of students: 2* Skills required: system administration, scriptingtesting, packaging* Resources: scripts and configuration from the previous semester* Expected result: fully-functioning repository configuration ready for installation on Mozilla's systems; well-written documentation* Initial contacts: [[User:Armenzg|armenzg]], [[User:Chris Tyler|ctyler]]
<!-- = Mozilla Projects =--><!-- == hgtools ==What if the Mozilla builders were better at managing all the different working directories (from Mercurial checkouts) that we need at any give time? If you look at [https://bugzilla.mozilla.org/show_bug.cgi?id=589885#c11 this conversation from IRC] you can see the benefits Maximum number of this and [https://bug506404.bugzilla.mozilla.org/attachment.cgi?id=476270 a patch] that has the initial work.Initial contacts: [[Userparticipants:Armenzg|Armenzg]] -->3
<!-- == MozHarness ==Expected result: A working Fedpkg repository, plus configuration files packaged up in an RPM
Imagine that we did not have to touch the Mozilla buildbot factories but instead we maintained a bunch of script for all the different jobs they run?== Mirrorlist CGI Script ==
It would be good if we could create scripts that told Yum uses a mirrorlist retrieved from a machine how server to determine which mirrors to generate an optimized build, use for downloading packages. This mirrorlist can be generated by a debug buildscript (e.g., unit teststo randomize or to optimize mirror selection), talos runs, locale repackages.If you look in but at the [http://hg.mozilla.org/build/tools/file/tip/scripts tools/scripts] repo you can see that we have present time a simple shell static file is just passed through to do this for the fuzzing automation. The buildbot factory that calls it is called [http://hg.mozilla.org/build/buildbotcustom/file/a70b38b40088/process/factory.py#l7895 ScriptFactory] and it is very simpleyum client.
Initial contactsSkills required: [[User:Armenzg|Armenzg]]--><!-- == End-to-end project ==How can we build faster and provide tests results faster to our developers?That is what we are trying to figure out and we will be adding bugs to this [https://bugzilla.mozilla.org/show_bug.cgi?id=598175 tracking bug] to optimizeour infrastructure.scripting, testing
Initial contactsMaximum number of participants: [[User:Armenzg|Armenzg]]--><!-- == I don't like waiting - give me a CPU! ==We have a hundred jobs running per hour and we sometimes have jobs that have to wait for something before getting started. If we optimized the load we could use the build resources more effectively. I will be adding bugs to this [http://www.themoviemind.com/wp-content/uploads/2008/08/chuck-norris-2.jpg tracking bug] to reduce our load on our pools and therefore reduce our waiting times.1
Initial contactsExpected result: [[User:Armenzg|Armenzg]]-->An updated mirrorlist script
