1,885
edits
Changes
no edit summary
* 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 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]]
* Expected result: a kernel (or kernels) 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]]
== Add PandaBoards to the Fedora-ARM Build System ==
We have 15 PandaBoards on order for the Fedora-ARM build farm. These machines need to be configured and added into the farm, and then optimized to build packages as quickly as possible.
* 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 to the build farm; new PandaBoards actively building
* Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]]
== iSCSI/AoE Support ==
= Fedora Projects =
== Package the Weave Server ==
This project involves packaging WIX for Fedora and getting it through the package-approval process.
* Maximum number of students: 1
* Skills required: packaging
* Resources: CDOT systems
* Expected result: the WIX software will be available in the main Fedora repositories (yum install wix)
* Initial contacts: mhoye
<!-- == fedpkg Test Suite ==
''fedpkg'' is a new Fedora packager tool written by Jesse Keating; it's one 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.
* Maximum number of students: 2
* Initial contacts: [http://jkeating.livejournal.com/ Oxf13]
-->
== Koji Setup Documentation ==
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 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
== AutoQA ==
[[:fedora:AutoQA|AutoQA]] is an automated test system for Fedora. 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 needed.
* 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 the main AutoQA codebase* Initial contacts: [[:fedora:User:JLaska|JLaska]]
= Fedora-Mozilla Projects =
= 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 of this and [https://bug506404.bugzilla.mozilla.org/attachment.cgi?id=476270 a patch] that has the initial work.
Initial contacts: [[User:Armenzg|Armenzg]]-->
<!-- == ScriptFactory MozHarness ==
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?
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.-->
Initial contacts: [[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 optimize
Initial contacts: [[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.
Initial contacts: [[User:Armenzg|Armenzg]]
-->