Note

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Funtoo Media Project

From Funtoo
Revision as of 07:55, February 12, 2022 by Drobbins (talk | contribs)
Jump to navigation Jump to search
   Summary
This is the Funtoo Media-Kit project, which manages the contents of media-kit as well as all media-related mix-ins.
   People
Leads

Welcome to the Funtoo Media-Kit project! This project is focused on the maintenance of media-kit, and the various types of media support in Funtoo, plus the media-related multi-profiles.

Goals

The goal of the Funtoo Media project is to provide essential functionality related to media support in Funtoo Linux, and to curate/maintain the media packages.

What's Supported

The dynamic table, below, defines what we consider part of media-kit, and also includes guidance on frameworks that we may not fully support yet.

Current Work

Work has begun on 'beard trimming' excess packages in media-kit in next-release. The goal here is to limit the scope of media-kit somewhat, so it is a curated collection of packages of importance to Funtoo, rather than a bucket for anything in the universe that is related to media. Next-release has its own packages.yaml file which has been significantly pruned, as well as organized. At the top of the file, there are some packages identified that are mis-categorized and should be moved out of media-kit.

Packages that do not related to the core mission of media-kit will likely be moved to a relaunched flora (see FL-9393) and maintained by the user community. The packages remaining within media-kit will be more actively maintained and autogenned.

How To Get Involved

Our efforts are focused on media-kit in next-release. Here are some things that we are totally open to in the form of PRs:

  1. Help us move the 'miscategorized' packages (labelled in the YAML as miscategorized: in packages.yaml to the correct kits.
  2. Help us autogen various media libraries in next-release. These packages are generally fairly "autogen-friendly", as they tend to be somewhat mature and have a clear scope of functionality and set of dependencies. The lower-level libraries tend to have few or no real dependencies.

For any of these tasks, first open a bug on the bug tracker to indicate what you're going to be working on. Once it's moved to "Ready to Fix" state, a PR can be submitted.