|
1 | 1 | # OpenELA TSC Goals |
2 | 2 |
|
3 | | -The OpenELA Technical Steering Committee(TSC) governs the technical aspects of the OpenELA community efforts. Details on the TSC role and responsibilities are outlined within the TSC policy document: [https://github.com/openela/governance/tree/main/TSC](https://github.com/openela/governance/tree/main/TSC) |
| 3 | +The OpenELA Technical Steering Committee (TSC) governs the technical aspects of the OpenELA community efforts. Learn more about the TSC role and responsibilities with the TSC policy document: [https://github.com/openela/governance/tree/main/TSC](https://github.com/openela/governance/tree/main/TSC) |
4 | 4 |
|
5 | | -To assist the community to better understand the current TSC top goals, the TSC has decided to focus their efforts on following: |
| 5 | +This document seeks to describe the upcoming goals of the TSC. |
6 | 6 |
|
7 | | -## Goal: Build a Common Foundation |
| 7 | +## Goal: Set the Enterprise Linux Standard |
8 | 8 |
|
9 | | -The TSC is focused on providing a common foundation across Enterprise Linux distributions. This foundation allows distributions to maintain interoperability with other members of the OpenELA and provides Vendors the assurance of compatibility between the distributions. The TSC is focused on providing simplicity and transparency in building this foundation. |
| 9 | +The TSC is focused on providing a common foundation across Enterprise Linux distributions that will define the standard of an Enterprise Linux distribution. This foundation helps to ensure that distributions interoperate with other members of the OpenELA and provides software vendors the assurance of compatibility between the distributions. The TSC is focused on providing simplicity and transparency in building this foundation. |
10 | 10 |
|
11 | 11 | ## Goal: Enhance Transparency and Participation |
12 | 12 |
|
13 | | -The members of the TSC are determined through the TSC policies. However others have expressed interest in listening in on the TSC meetings. To facilitate additional attendees, the meetings will move to a google workspace. Moving to this service will be jointly managed going forward. |
| 13 | +Membership of the TSC is determined through TSC policies and bylaws, but we also encourage members of the OpenELA to observe our meetings. This is also the best way to find new ways to contribute to the [TSC](http://TSC.We)[.](http://TSC.We) We also plan to instate an TSC Office Hour for interested community members to participate and discuss. |
14 | 14 |
|
15 | | -## Goal: Public TSC office hour |
| 15 | +## Goal: Increase contributions to openela-contrib |
16 | 16 |
|
17 | | -To facilitate additional collaboration with the community, the TSC will consider establishing an open office hour, inviting interested community members. |
| 17 | +From the beginning, we've had a goal of expanding the Enterprise Linux ecosystem. One way we've explored to increase the ecosystem is make more software available to members of our community. Whereas the openela-main repositories are intended for "bug-for-bug" compatible software that makes up the bulk of Enterprise Linux, we haven't lost sight of the openela-contrib area, which is intended to host the build files necessary to bring in additional software packages into the Enterprise Linux ecosystem. |
18 | 18 |
|
19 | | -## Goal: Solicit contributions for openela-contrib |
| 19 | +## Goal: Continue making Enterprise Linux upgrades easier |
20 | 20 |
|
21 | | -There is a distinction between openela-contrib and openela/ repositories. The openela-contrib repository houses packaging materials and metadata (spec files, sources, etc.) for existing projects. \`openela/\` is for development projects actively managed and supported by OpenELA members. Note that projects in both repositories may not be bug-for-bug compatible with each other." |
22 | | - |
23 | | -## Goal: Publish the Leapp repository and add further features |
24 | | - |
25 | | -Make the leapp repository public on [github.com/openela](http://github.com/openela) and add additional features to the project\! |
26 | | - |
27 | | -## Goal: Publish future Enterprise Linux versions as they become available |
28 | | - |
29 | | -The TSC will continue to leverage and improve the automated processes that make new enterprise Linux sources available as timely as possible. These processes monitor and process the source once the associated releases of new versions of Red Hat Enterprise Linux (RHEL) are available. |
| 21 | +Earlier this year we published the OpenELA enhancements for LEAPP, which intend to simplify complex upgrade scenarios for Enterprise Linux systems. We plan to continue to add features to LEAPP. [github.com/openela/leapp-repository](http://github.com/openela/leapp-repository) |
30 | 22 |
|
| 23 | +## Goal: Continue to publish future Enterprise Linux versions |
31 | 24 |
|
| 25 | +We're delighted to have OpenELA repositories for 8 and 9, and we plan to make newer Enterprise Linux source repos available within a timely fashion. |
0 commit comments