[[Category:SBR600]][[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]]).
* 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.
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 Fedora-ARM Remix Projects =
== System Administration Tools for Update the ARM Build Farm raspberrypi-config package ==
The [[Fedora ARM Koji Buildsystem]] or "farm" consists of 23 ARM builder systems which will grow raspberrypi-config package contains the default configuration files for Pidora. These files need to 38 by be updated to reflect new options available in the end of this semester. As it growsRaspberry Pi firmware, the need as well as options that are not commonly used and may conflict with common use-cases - for efficient system management tools increases. The previous semesters' students started example, the work of setting current configuration files cause kernel start-up [http://wwwmessages to be reported on the serial port.nagiosThis is rarely used, any may cause conflicts with other devices connected to that port (e.org/ nagios] (monitoring) and [[https://fedorahostedg.org/func/ func]] (group control, LCD displays) 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 [httpSkills required://www.puppetlabs.com/ puppet] (configuration management) tool.packaging
* Maximum number of studentsparticipants: 2* Skills required: Linux system administration, problem solving, documentation writing* Resources: wiki notes from previous semesters (e.g., [[How to Setup and configure Nagios]]), [[Fedora ARM Koji Buildsystem]], [[CDOT Development Systems]]* 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]]1
== Koji Hub on ARM ==Expected result: An updated, working raspberrypi-config package
The [[Fedora ARM Koji Buildsystem]] system uses [[CDOT_Development_Systems#Machine_names.2C_IPs.2C_and_Status|HongKong]], an x86_64 system, as the [[:fedora:Koji|Koji]] hub, along with a group of [[Fedora ARM Secondary Architecture/ARM hardware|ARM builders]].== Kernel Configuration Files ==
Ideally, it would be nice The build process for the kernel uses a configuration file to prove control which kernel capabilities are built into the ability 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-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)configuration file. This project involves configuring reviewing the [http://www.globalscaletechnologies.com/tPidora kernel configuration to optimize it for the widest possible range of use-openrdcdetails.aspx OpenRD-Client] system as Koji hub and determining if this is cases while ensuring a viable configurationfairly small kernel image size.
* Maximum number of students: 1* Skills required: Linux system administrationkernel configuration/building, problem solving, documentation writing* Resources: wiki notes from previous 2 semesters, access to the OpenRD and a GuruPlug or BeagleBoard* Expected result: koji-hub running on the OpenRD; a recommendation 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]]packaging
== Device Support and TestingMaximum number of participants: PandaBoard ==1
Various ARM devices need different driver sets and/or kernels. This project will test the Fedora-ARM system on the [httpExpected result://pandaboard.org/ PandaBoard], creating a An improved kernel that works well with it, and figuring out how to use as many of configuration in the builtraspberrypi-in peripherals as possible.kernel package
* Maximum number of students: 1* Skills required: Linux system administration, kernel building, research, documentation writing* Resources: a [http://pandaboard.org/ PandaBoard], notes from other [http://www.omappedia.com/wiki/PandaBoard PanadaBoard support projects],* Expected result: a kernel (or kernels) for use with the PanadaBoard == Profile and Improve RPM and the Fedora 12 or Fedora 13 root filesystems; user documentation YUM performance on how to set up the PandaBoard with Fedora; wiki notes on setting up other ARM devices* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]Pi ==
== Add PandaBoards RPM/YUM appear to perform slowly on the FedoraPi -ARM Build System ==- 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.
We have 15 [httpSkills required://pandaboard.org/ PandaBoards] on order for the [[Fedora ARM Koji Buildsystem|Fedora-ARM build farm]]. These machines need to be configured and added into the farmprofiling, and then optimized to build packages as quickly as possible.programming, packaging
* Maximum number of studentsparticipants: 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 to the build farm; new PandaBoards actively building* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]1
== iSCSIExpected result: Either a report proving that RPM/AoE Support * ==YUM are as fast as can be expected on the Pi, or changes to affected packages to improve performance
[http://en.wikipedia.org/wiki/ISCSI iSCSI] (SCSI over TCP/IP) and [http://en.wikipedia.org/wiki/ATA_over_Ethernet AoE] (ATA-over-ethernet) are different SAN protocols that can be used on a standard ethernet network.[[Fedora ARM Secondary Architecture/iSCSI|iSCSI did not work reliably == Internationalization Support in Fedora 12 on ARM systems]], but will be needed by future ARM server systems. AoE has not been well-tested on ARM systems.Firstboot for Pidora 19 ==
Goals of this This project:involves taking the Pidora 19 Firstboot package and internationalizing it (1making it possible to use multiple language files with Firstboot) iSCSI and AoE need . Note that Pidora 19 is expected to be tested for stability and performance. (2) The ARM builders, which currently use loopbacka Fedora 18-mounted filessystems on top of NFS, should be reconfigured to use iSCSI or AoE style Firstboot system (whichever is the optimal solutionas was used in Pidora 18) providing it is faster rather than the current solutionfirstboot system used in Fedora 19 and higher.
* Maximium number of students: 2* Skills required: Linux system administration, debugging and troubleshooting, kernel building, benchmarkingpython, documentation writing* Resources: an ARM systemi11n using gettext, 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]]packaging
== CreateRepo Performance Improvements * ==Maximum number of participants: 1
The [[Fedora ARM Koji Buildsystem|Fedora-ARM build farm]] consists Expected result: A version of the koji-hub/koji-web system (on [[CDOT_Development_Systems#Machine_names.2C_IPs.2C_and_Status|HongKong]], an x86_64 machine) firstboot and a group of ARM builders. HongKong also handles the [http://createrepo.baseurl.org/ CreateRepo] tasks, which heavily load firstboot modules that machine. It might make sense to move those tasks to another machine, but doing so makes the CreateRepo jobs take a lot longer (15 minutes on HongKong vs. 55 minutes on another x86_64 server). This is presumably due to the overhead of sharing files between HongKong and the other server over NFS on the 100 Mbps Seneca network.are fully internationalized
This project involves figuring out how to run the CreateRepo jobs more quickly. Possible solutions include a 1 Gbps LAN, a redistribution of the file storage or a change to a different file storage technology, or optimizing the CreateRepo tasks on HongKong == New Firstboot for best speed.Pidora 20 ==
* Maximum number of students: 1* Skills required: system administrationFirstboot on the Pi varies a bit from firstboot on PCs, benchmarking* Resources: CDOT server systems (HongKong, Ireland, Scotland)* Expected result: significant reduction because the software isn't installed onto storage in CreateRepo times, especially when multiple CreateRepo tasks are running* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paulthe same way as PCs. This project involves updating the Fedora 20 firstboot package to work with Pidora 20.W|PaulW]]
== RPM-based Kernels for Fedora ARM * ==Skills required: python programming, packaging, testing
On PC architecture systems (x86_64 and i386), Fedora manages and updates kernels as RPM packages, which modify [httpMaximum number of participants://www.gnu.org/software/grub/grub-legacy.en.html grub] boot parameters and the initial ram disk ([http://en.wikipedia.org/wiki/Initrd initrd], configured by [[:fedora:Dracut|dracut]]).1
On Expected result: A version of the Fedora 19 or Fedora-ARM systems, 20 firstboot that works on the kernel is not managed via RPMs, grub is not used, Pi and has full support for the initrd system is rarely used.Pidora options (such as rootfs resizing)
This project involves understanding how the PC (i386/x86_64) kernel/boot/initrd system works, determining which pieces can be reused == Compiler Flags on Fedora-ARM and which pieces need to be adapted or replaced, and implementing RPM-based kernel management for ARM.Pidora ==
* Maximum We're not sure if the compiler flags being used for Pidora are optimal. This project involves building a number of students: 3* Skills required: Linux system administration, script writing, RPM packaging, kernel building, initrd debugging* Resources: an ARM system* Expected result: RPM-based Kernels work on Fedora-ARMpackages with different combinations of compiler flags, with changes committed upstream; documentation about observing the differences between kernel management on ARM results (in terms of binary size and performance) and on PCs* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paulrecommending the optimal set of flags.W|PaulW]]
== Fedora-ARM Communication * ==Skills required: building, benchmarking
We're not doing a great job Maximum number of communicating how the [[participants:fedora:Architectures/ARM|Fedora-ARM]] project is doing, especially how [http://arm.koji.fedoraproject.org current builds] are progressing. The [http://arm.koji.fedoraproject.org/status status page] is very bare-bones and doesn't convey a lot of information, the Fedora-ARM wiki pages (on the [[:fedora:Architectures/ARM Fedora]] and [[:Category:Fedora_ARM_Secondary_Architecture|Seneca]] wikis) need to be made more useful to prospective users, and we need an effective communication strategy with the rest of the [http://fedoraproject.org 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.1
* Maximum number of students: 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 Modified RPM macros that include the arm@lists.fedoraproject.org mailing list and the #fedora-arm IRC channel* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]optimal flags for Pidora
== Automatic ExclusiveArch Addition/Removal * Avahi Configuration for Pidora ==
RPM packages may be specified as being suitable only for particular architectures through the use of ExclusiveArch and [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-EXCLUDEARCH-TAG ExcludeArch] tags in the spec file. If a base package, such as a language Avahi (interpreter or compilerzeroconf) enables discovery of computers without DNS or a library does not build IP numbers. This project involves configuring Avahi for use on a particular architecturethe Pi, then dozens or hundreds of so that other packages cannot be builtcomputers can connect to it by name without DNS support. These packages should all This configuration must then be marked as ExcludeArch packaged in the upstream git package repository. Later, if such a way that base package is updated to work on that arch, it can be included in the ExcludeArch lines will need to be removedPidora composes without causing conflicts.
This project involves writing a script that will mass-add or mass-remove ExcludeArch tags (orSkills required: testing, if those tags exist, add or remove a particular architecture), pushing the changes to the upstream [[:fedora:Using_Fedora_GIT|git repo]].packaging
* Maximum number of studentsparticipants: 1* Skills required: scripting (Python and/or bash), packaging* Expected result: a script that will do mass adds/removals of ExcludeArch tags given a list of packages* Resources: [https://fedorahosted.org/fedora-packager/ fedpkg libraries and source], Fedora package repo* Initial contacts: [[User:Paul.W|PaulW]], [[User:Chris Tyler|ctyler]]
== Fedora-ARM Package Building and Troubleshooting ==Expected results: A configuration package that, when installed, will correctly set up Avahi for local discovery on the Pi
The [[Fedora ARM Secondary Architecture|Fedora-ARM]] project is building Fedora 13/14/15 for == Upstream 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 ([http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-Pidora RPM-INSIDE-EXCLUDEARCH-TAG 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.Changes ==
Note There are some small changes to the RPM system that one package build issue will often block many other packageshave 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.
This project involves working with other members of the Fedora ARM build team to resolve package build problems and get F13/F14/F15 released for ARM as soon as possible.Skills required: interpersonal skills - negotiation, patch creation, packaging
* Maximum number of studentsparticipants: 4* 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 results: Pidora RPM changes will be upstreamed
== Package the Weave Server * Wayland ==
Mozilla Sync is a technology Fedora 20 includes support for synchronizing personal data (bookmarks, passwords, form values, and cookies) across multiple machinesthe Wayland display system. It uses The RaspberryPi foundation has been working on a server known as [https://wiki.mozilla.org/Labs/Weave/Sync/1Wayland implementation for the Pi.0/Setup Weave]This project involves getting the two to work well together.
This project involves packaging Weave for Fedora and getting it through the [[Skills required:fedora:Package Review Process|package review]] process. (Why package the Weave server? So that people can run a private versionsystem administration, debugging, possibly some programming, either for enhanced security or for testing).packaging
* Maximum number of studentsparticipants: 1* Skills required: Apache administration, packaging* Resources: CDOT systems* Expected result: the Weave server will be available in the main Fedora repositories (yum install weave)* Initial contacts: [[User:Mhoye|mhoye]]2
== Package Hadoop ==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://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.== Automate Pidora Kernel and Firmware Building ==
* Maximum number of students: 3* Skills required: packaging, system administration; familiarity with Java programming/packaging* Resources: [[CDOT Development Systems]], [https://adminThe Raspberry Pi Foundation maintains a kernel fork that is updated frequently.fedoraproject.org/mailman/listinfo/devel devel mailing list] (some work We would like to package kernel and firmware changes on Hadoop packaging has already been done)* Expected result: the three Apache Hadoop subprojects (Hadoop Commona daily basis, HDFSand 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 MapReduce) will be make it available in as the main Fedora repositories (yum install hadoop-common hdfs mapreduce)* Initial contacts: [[User:Chris Tyler|ctyler]]Pidora kernel.
== Package the WIX Toolchain * ==Skills required: scripting (python and/or bash), packaging
[httpMaximum number of participants://wix.sourceforge.net/ 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, the WIX tools themselves can run on Linux, which is useful for cross-development (writing software on Linux for use on Windows, e.g., the virt-manager utilities for Windows virtual machine guests).1
This project involves packaging WIX for Fedora Expected results: Raspberry Pi kernel and getting it firmware updates will be included in a package in a testing repository through the [[:fedora:Package Review Process|package review]] an automated (cron'd) process.
* Maximum number of students: 1* Skills required: packaging* Resources: [[CDOT Development Systems]]* Expected result: the WIX software will be available in the main Fedora repositories (yum install wix)* Initial contacts: [[User:Mhoye|mhoye]], sdowne<!--== fedpkg Test Suite Change raspberrypi-vc Package to Build from Source ==
''fedpkg'' is a new Fedora packager tool written by Jesse Keating; it's one of Originally, the VideoCore IV GPU on the Pi was used with proprietary libraries which were only available in compiled form, so the main commandraspberrypi-line tools that a packager will usevc package was originally set up to package prebuilt binaries and not build from source. It needs a test suiteThe source code for these libraries is now available, so that as new features are added, regressions can and the raspberrypi-vc package should be detectedchanged to build from source (this will help with SELinux compatibility).
* Maximum number of studentsSkills required: 2* Initial contacts: [http://jkeating.livejournal.com/ Oxf13]-->packaging
== Koji Setup Documentation ==Maximum number of participants: 1
The [[Expected result:fedora:Koji|Koji documentation]] needs an overhaul. This project involves reading A new version of the raspberrypi-vc package that build from source, is compatible with the current documentation, updating and editing itPidora package, and testing it by setting up a Koji system.can be easily updated/maintained
* Maximum number of students: 2* Skills required: writing, system administration* Resources: [[CDOT Development Systems]], [[:fedora:Main Page|Fedora wiki]]* Expected result: a complete, well-written guide to setting up a Koji system (from A-Z)* Initial contacts: [[User:Chris Tyler|ctyler]], dgilmore== Write an Updated Boot Screen ==
== AutoQA ==[[:fedora:AutoQA|AutoQA]] is Pidora includes an automated test system for OpenGL-powered boot screen, which uses the Raspberry Pi FedoraRemix logo. At present there are event watchers for koji builds, bodhi updates, repo changes, and nightly installed images; these events trigger a small number of tests, but more tests are neededThe current code does not use OpenGL very effectively.
* Maximum number of students: 3* Skills requires: Python scripting, scripting, system administration, packaging* Resources: CDOT systems* Expected results: additional tests for AutoQA, accepted/committed into This package should be updated to use OpenGL better and to use the main AutoQA codebase* Initial contacts: [[:fedora:User:JLaska|JLaska]]Pidora logo.
= Fedora-Mozilla Projects =Skills required: C programming, OpenGL programming, packaging
== Repository Setup for Mozilla Nightlies and Betas * ==Maximum number of participants: 1
Many web developers want access to the latest Firefox pre-releasesExpected result: A visually appealing boot screen, including the nightly builds and beta releases. Mozilla's build team wants to make these accessible packaged as parallel-installable binaries, released through a Fedora-compatible repository. Last semester, a group of SBR600 students set most of this up; this project involves extending and improving their work.<!-drop- Subprojects:* Build configuration in replacement for the RPM files.* Repository configuration RPMs.* Getting SELinux to work with the nightlies.-->current boot screen
See [https://bugzilla.mozilla.org/show_bug.cgi?id=600317 bug 600317].= Update rootfs-resize ==
* Maximum number of students: 2* Skills required: The rootfs-resize package resizes the Pidora rootfs after installation. It works with primary partitions, and it works with the NOOBS system administration, scriptingbut it doesn't work with a NOOBS-style layout outside of NOOBS (i.e., packaging* Resources: scripts and configuration from where the previous semester* Expected result: fullyrootfs is placed in an extended partition). This project involves extending rootfs-functioning repository configuration ready for installation on Mozilla's systems; resize so that it can resize extended and logical partitions as well-written documentation* Initial contacts: [[User:Armenzg|armenzg]], [[User:Chris Tyler|ctyler]]as primary partitions.
<!-- = 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 [httpsSkills required:Python scripting//bugzilla.mozilla.org/show_bug.cgi?id=589885#c11 this conversation from IRC] you can see the benefits of this and [https://bug506404.bugzilla.mozilla.org/attachment.cgi?id=476270 a patch] that has the initial work.Initial contacts: [[User:Armenzg|Armenzg]] -->programming, system administration, packaging
<!-- == MozHarness ==Maximum number of participants: 1
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?Expected result: An updated rootfs-resize package
It would be good if we could create scripts that told a machine how to generate an optimized build, a debug build, unit tests, talos runs, locale repackages.If you look in the [http://hg.mozilla.org/build/tools/file/tip/scripts tools/scripts] repo you can see that we have a simple shell file 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 simple.== Packaging Pi-compatible Software ==
Initial contacts: [[User:Armenzg|Armenzg]]There are a number of Pi--><!-- == 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 specific software packages that could/should be adding bugs to this [https://bugzillaincluded in Pidora.mozilla.org/show_bug.cgi?id=598175 tracking bug] to optimizeour infrastructureSelect one, package it, and get it into Fedora (preferred) or directly into Pidora.
Initial contacts: [[User:Armenzg{{Admon/tip|Armenzg]]--><!-- == I don't like waiting Finding Your Own Package|You can find any Pi- give me a CPU! ==We have a hundred jobs running per hour specific software and we sometimes have jobs that have to wait propose packaging it for something before getting startedyour project. If we optimized the load we could use the build resources more effectively. I will Note that it must be adding bugs to this [http://www.themoviemind.com/wp(a) broadly-content/uploads/2008/08/chuckuseful Pi-norris-2.jpg tracking bug] specific software, or (b) a substantial software package that would be generally useful in Fedora and specifically on the Pi, in order to reduce our load on our pools and therefore reduce our waiting timesbe approved as a project.}}
Initial contactsSome 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 See the [[Userhttp:Armenzg|Armenzg]//trac.proximity.on.ca/projects/rpfr/report/1 Pidora Bug Tracker]for ideas for other packages that people want included in Pidora. 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 = == Bug Tracker for Pidora == Pidora currently uses a Trac 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, documentation 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
