< Community Platform Engineering(Redirected from Fedora Engineering/FY17 Plan)
This is a summary of important goals for the Fedora Engineering team for Red Hat Fiscal Year 2017 (March 2016 - February 2017).
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.
The release engineering priority pipeline includes additional back end technical work going on in Fedora teams.
Infrastructure and General
To help with these goals, contact the Infrastructure team -- #fedora-admin[?].
|Additional Basset work. Further integrations with Pagure and other apps to prevent spam from making sysadmins' and contributors' lives miserable.||Patrick Uiterwijk||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.||Stephen Smoogen||Q3|
|Ipsilon OpenID Connect. Complete the core support in Ipsilon for OIDC; then ensure integration of apps across our infra with single sign-on/logout.||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||Kevin Fenzi||Q3|
|Data-driven ansible config. Make our nagios and fedmsg configs dynamically generated from our inventory and group/host vars.||Stephen Smoogen||Q4|
|Start effort to containerize applicable infrastructure. Evaluate various infrastructure applications to see if they make sense as containers. This makes Fedora Infrastructure a driver for developing best practices or policies for containerizing apps.||Kevin Fenzi||Patrick Uiterwijk||Q3|
|Automation of statistics. Automatically generate and host statistics/metrics for FPL and other usage.||Stephen Smoogen||Ricky Elrod||Q4|
|Sunset FedoraHosted. Transition hosted projects away from old decrepit Trac, and replace with Pagure. Handle critical bugs/RFEs to make useful for the majority of active project maintainers.||Kevin Fenzi||Pierre-Yves Chibon||Q4|
Team members participate in rel-eng work as well, especially Adam Miller, Randy Barlow, Kushal Das, and Sayan Chowdhury. Note that additional release infrastructure development is tracked at ReleaseEngineering/PriorityPipeline.
|Bodhi step-up. Reinvigorate Bodhi v2 development, and engage with stakeholders to handle roadmap on a regular release cycle.||Randy Barlow||Jeremy Cline||Q2|
|Compose based testing for autocloud. Have autocloud testing of deliverables based on composes created by rel-eng.||Kushal Das||Sayan Chowdhury||Q2|
|Automated testing of layered image builds. Define and deploy this automation in cooperation with Fedora QA team, updating tests as needed to account for new test failures.||Kushal Das||Sayan Chowdhury||Q3|
To help with these goals, contact the Infrastructure Applications team -- #fedora-apps[?].
|API keys Implement central API key stuff, and give less messy CLI login.||Patrick Uiterwijk||Q2|
|SSO/SLO Add single sign on and single logout to core webapps.||Patrick Uiterwijk||Q2|
|Rework fedimg. Code cleanup, bug fixes, and generally making this a more resilient app.||Sayan Chowdhury||Q3|
|Hubs Implementation Prepare at least one (1) community hub running in production in time for Flock 2016.||Devel:
||Design: Máirín Duffy|
|Pagure integration. Enhancements and fixes that allow us to make Pagure the front-end for pkgs.fp.o. Clean up importer, add real namespaces, etc. Ideally Pagure forms the front-end for package dist-git.||Pierre-Yves Chibon||Jeremy Cline||Q4|
Design and content
To help with these goals, contact the Design team -- #fedora-design[?].
|Flock deliverables. Media, collateral, and other design work for Flock 2016.||General design||Ryan Lerch||Q2|
|Design mentorship. Provide mentoring and assistance to key FOSS interns e.g. Outreachy, working on active team projects. Cultivate new contribution via Fedora Design team.||Outreach||Máirín Duffy||Q2, Q4|
|Vagrant everywhere. Make it easier for contributors to bootstrap a dev environment for our apps, including Bodhi, Pagure, Hyperkitty, and others.||Development assistance, new contributor UX||Ryan Lerch||Q3|
|Hubs design||New Contributor UX||Máirín Duffy||Q4|
|Bootstrap -- Modernpaste, Bodhi, Elections, pkgdb, kernel tests, Badges, FAS3, Wiki, Planet, fedocal, koji||Web design UX||Ryan Lerch||Q4|
|Magazine editorial. Drive record number of pageviews in FY2017 through contributor outreach and content curation. Turn over editorial reins.||Collateral/marketing||Ryan Lerch||Q1-4 (continuous)|
To help with these goals, contact the Kernel team -- #fedora-kernel[?].
Team High Level Goals
- Plan for and deliver high quality kernel for upcoming Fedora releases
- Improve team efficiency and community collaboration
- Increase participation in upstream kernel community
Specific action items will be derived from these goals.
|Increase upstream kernel reviews and bugfixes. Upstream is continually looking for additional patch reviews. By increasing our participation there we can help avoid bugs. We'll also use this to increase our team's overall knowledge by gaining a deeper understanding of various focus areas within the kernel.||Upstream|
|Publish various communications about the Fedora kernel. The kernel is often a hot topic in various communities. We'll look at continuing the upstream Fedora patch reports, and possibly writing articles for Fedora Magazine.||Collaboration|
|Community Outreach The Fedora kernel community has several active members but could always improve. Through efforts like Outreachy, we can grow the understanding and expertise of interested community members.||Outreach|
|Improved popular platform support People like to use their hardware with a minimum amount of fuss. Look into ways to accomplish this for popular hardware.||Hardware enablement|
|Architecture support The primary Fedora platform is x86_64. However, there are always interesting things happening on other architectures such as armv7hl, arm64, etc. We'll investigate possible areas where we as a team can help further progress or provide solutions with these architectures.||Architecture|
|Upstream patch reviews and bugfixes||All||FY|
|Blog/magazine postings on kernel topics||All||FY|