Changes

Jump to: navigation, search

SBR600 Potential Projects

986 bytes added, 15:35, 16 January 2011
no edit summary
== Fedora-ARM Communication ==
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.
* Maximum number of students: 2
== Automatic ExclusiveArch Addition/Removal ==
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 lines ] 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.
This project involves writing a script that will mass-add or mass-remove ExcludeArch tags (or, if those tags exist, add or remove a particular architecture), pushing the changes to the upstream [[:fedora:Using_Fedora_GIT|git repo]].
* Maximum number of students: 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]]
The [[Fedora ARM Secondary Architecture|Fedora-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 ([http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-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.
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].
This project involves packaging Weave for Fedora and getting it through the [[:fedora:Package Review Process|package-approval review]] process. (Why package the Weave server? So that people can run a private version, either for enhanced security or for testing).
* Maximum number of students: 1
* Resources: CDOT systems
* Expected result: the Weave server will be available in the main Fedora repositories (yum install weave)
* Initial contacts: [[User:Mhoye mhoye]]
== Package Hadoop ==
* Maximum number of students: 3
* Skills required: packaging, system administration; familiarity with Java programming/packaging
* Resources: [[CDOT systemsDevelopment Systems]], [https://admin.fedoraproject.org/mailman/listinfo/devel devel mailing list] (some work on Hadoop packaging has already been done)
* Expected result: the three Apache Hadoop subprojects (Hadoop Common, HDFS, and MapReduce) will be available in the main Fedora repositories (yum install hadoop-common hdfs mapreduce)
* Initial contacts: [[User:Chris Tyler|ctyler]]
== Package the WIX Toolchain ==
[[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).
This project involves packaging WIX for Fedora and getting it through the [[:fedora:Package Review Process|package-approval review]] process.
* Maximum number of students: 1
* Skills required: packaging
* Resources: [[CDOT systemsDevelopment Systems]]
* Expected result: the WIX software will be available in the main Fedora repositories (yum install wix)
* Initial contacts: mhoye, sdowne
== Koji Setup Documentation ==
The [[Koji|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.
* Maximum number of students: 2
* Skills required: writing, system administration
* Resources: [[CDOT systemsDevelopment Systems]], Wiki[[: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

Navigation menu