LSB-Futures - Identification Process
The lsb-futures subcommittee seeks to expand the scope of the LSB. We are continually evaluating the body of open source software to determine what the community seeks in a standard. This includes documenting existing practices and sometimes working to build consensus toward a standard. This page is intended to document proposed ideas and processes. If you have additional ideas please send them to the mailing list.
Input from Standards Audience
The most important source of input in the standards process is from the intended audience of that standard.
Developers' Requirements
Assumption: Developers targeting Linux have dependencies on components that are not currently standardized.
Data: An input submittal form is in development.
Kernel related issues
We tend to get a lot of request for Linux kernel standards, even though we have a policy against adding anything kernel related to the LSB. This document explains that policy and records the requests we've received as a resource for requestors and kernel hackers.
Analysis of Existing Code
We can use existing code to help determine accepted practices that could be standardized. These processes are meant to aid identification and selection of potential components, not replace the judgement of those working on the standards.
Linux Distribution Dependencies
Assumption: By examining packaging dependencies of the major distributions we can quantify what packages are most depended on. These packages might be good candidates for standardization.
More
Linux Distribution Base Components
Assumption: The packages that major distributions include in their "base install" are important and represent the collective wisdom of the distributions' users and maintainers. These packages might be good candidates for standardization.
Data: In progress.
Debian: Some initial work was done to split the Debian "base install". The results are available here. The need to be cleaned up and moved to this page.
Other Distributions: Needed. If you have expertise please volunteer.
Existing Commercial Application Dependencies
Assumption: By examining existing commercial application binaries we can determine what they depend on.
Data: Not yet started.
Volunteers needed. George Kraft suggests,
"You can uses the LSB's lsbappchk or admin/scripts/lsbapidump.pl to determine compliance or detailed dependency information."
maintained by: Matt Taggart <taggart@fc.hp.com>