* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]

[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 in Fedora 12 on ARM systems]], but will be needed by future ARM server systems. AoE has not been well-tested on ARM systems.

* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]

The [[Fedora ARM Koji Buildsystem|Fedora-ARM build farm]] consists of the koji-hub/koji-web system (on [[CDOT_Development_Systems#Machine_names.2C_IPs.2C_and_Status|HongKong]], an x86_64 machine) and a group of ARM builders. HongKong also handles the [http://createrepo.baseurl.org/ CreateRepo] tasks, which heavily load 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.

* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]

On PC architecture systems (x86_64 and i386), Fedora manages and updates kernels as RPM packages, which modify [http://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]]).

* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]

We're not doing a great job of communicating how the [[: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.

* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]

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 (interpreter or compiler) or a library does not build on a particular architecture, then dozens or hundreds of other packages cannot be built. These packages should all be marked as ExcludeArch in the upstream git package repository. Later, if that base package is updated to work on that arch, the ExcludeArch lines will need to be removed.

= Fedora Projects =

Mozilla Sync is a technology for synchronizing personal data (bookmarks, passwords, form values, and cookies) across multiple machines. It uses a server known as [https://wiki.mozilla.org/Labs/Weave/Sync/1.0/Setup Weave].

* Initial contacts: [[User:Chris Tyler|ctyler]]

[http://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).

= Fedora-Mozilla Projects =

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 a Fedora-compatible repository. Last semester, a group of SBR600 students set most of this up; this project involves extending and improving their work.