(Adding a lead person for each goal -- plus a few entries where I'm fairly confident of who that person is, corrections welcome) |
(Note on lead individual) |
||
| Line 3: | Line 3: | ||
Please note this is not a comprehensive list. Many team members have numerous additional goals for contribution to the project. In addition, all team members work with the community ad-hoc throughout the year to troubleshoot problems, mentor new contributors, and create additional opportunities for community participation. | Please note this is not a comprehensive list. Many team members have numerous additional goals for contribution to the project. In addition, all team members work with the community ad-hoc throughout the year to troubleshoot problems, mentor new contributors, and create additional opportunities for community participation. | ||
While Red Hat employees on the team are accountable for the progress of these goals, each one is fully open to the community to participate. Contribution is essential to achieving these goals, and we want and need the community's help! In Fedora, there is no such thing as "someone else's problem." We are all part of the solution. | While Red Hat employees on the team are accountable for the progress of these goals, each one is fully open to the community to participate. Contribution is essential to achieving these goals, and we want and need the community's help! In Fedora, there is no such thing as "someone else's problem." We are all part of the solution. The indicator of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overall project. | ||
== Infrastructure and General == | == Infrastructure and General == | ||
Revision as of 15:45, 19 March 2015
This is a summary of important goals for the Fedora Engineering team for Red Hat Fiscal Year 2016 (March 2015 - February 2016).
Please note this is not a comprehensive list. Many team members have numerous additional goals for contribution to the project. In addition, all team members work with the community ad-hoc throughout the year to troubleshoot problems, mentor new contributors, and create additional opportunities for community participation.
While Red Hat employees on the team are accountable for the progress of these goals, each one is fully open to the community to participate. Contribution is essential to achieving these goals, and we want and need the community's help! In Fedora, there is no such thing as "someone else's problem." We are all part of the solution. The indicator of a lead person shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overall project.
Infrastructure and General
To help with these goals, contact the Infrastructure team -- #fedora-admin[?].
| Description | Lead Person | Target |
|---|---|---|
| Migrate old OpenStack cloud to new Icehouse release. This is the new long-term support release for OpenStack. We will migrate the old cloud to the new one. This is the first of a two-part goal (see below). | Q1 | |
| Migrate remaining hosts to RHEL 7. While there may be a few boxes that must be maintained on RHEL 6, we want to make use of all the innovation in RHEL 7 that comes from Fedora. Migrate remaining hosts that can be moved to RHEL 7. | Q2 | |
| Migrate from Puppet to Ansible. We believe Ansible is the best new technology for systems deployment and management. So we intend to move all remaining Puppet recipes (78 at start of FY2016) in the infrastructure to Ansible playbooks. If you're interested in helping, start by exploring the Ansible docs and then get in touch with us. | Q2 | |
| Make new cloudlet ready (with 2-3 nodes) with latest OpenStack and make available for testing | Q2 | |
| Finish storage research. Consult with other consumers and Red Hat owners/users of storage products to ensure in the future we are buying the best solution for our needs, with a preference to fully open source products. This must be completed in advance of the next Red Hat budget cycle. | Q3 | |
| Wiki upgrade Move to the new upstream LTR of mediawiki, switch to openid plugin | Patrick Uiterwijk | Q3 |
| Bring secondary arch infra into Fedora infra s390, ppc and arm secondary arches currently manage their own infra in a add hoc and less than ideal manner. Merge them into main Fedora infrastructure for common CM, updates, support and monitoring | Q3 | |
| ...more to come... |
Application development
To help with these goals, contact the Infrastructure Applications team -- #fedora-apps[?].
| Description | Lead Person | Target |
|---|---|---|
| Deploy HyperKitty. HyperKitty is a web front end to the new Mailman version 3 which allows users to browse topics in a more familiar, forum-like interface. We will complete development of this application and deploy for use with Fedora mailing lists. | Aurélien Bompard | Q1 |
| MirrorManager 2 The code is mostly ready, we just need a few more tests and a deployment plan. | Q1 | |
| python3-fedora We need to get python-fedora ready for python3. Other efforts are waiting on this. | Q1 | |
| anitya/hotness These currently have about 20 open bugs on them. It would be nice to at least cut that in half to reduce any broken window effect. | Q1 | |
| Bodhi 2 Finishing up rewrite and tests in Q1, look to deploy in Q2. | Luke Macken | Q2 |
| pkgdb2 admin actions New releng tools as a part of pkgdb2. This is in staging now, waiting for the next release of Fedora. | Pierre-Yves Chibon | Q2 |
| auto sign-in Enable all of our apps with the auto-sign-in JS shim. | Q2 | |
| fedmenu Enable all of our apps with the fedmenu popup. | Ralph Bean | Q2 |
| fedora-packages revamp We need to rewrite the backend which is subject to data corruption and race conditions. | Q3 | |
| FAS 3 Tentative, pending discussion with here and team | Q3 | |
| composedb Still unsure what the extent of this project is. Maxamillion will be taking lead in consultation with the releng group. | Adam Miller | Q4 |
| Hubs Implementation Not entirely sure what this will entail yet, but we'll know more after collab design process gets underway. | Q4 |
Design and content
To help with these goals, contact the Design team -- #fedora-design[?].
| Description | Lead Person | Target |
|---|---|---|
| Hubs design | Máirín Duffy | |
| <Bootstrap?> everywhere | Ryan Lerch |
Kernel
To help with these goals, contact the Kernel team -- #fedora-kernel[?].
| Description | Lead Person | Target |
|---|---|---|
| Specific driver efforts? | ||
| Kernel test system - what's next | Justin Forbes |