forked from coreos/fedora-coreos-tracker
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
instructions for requesting new packages
An initial set of instructions on how to request a new package be added to FCOS. This can be folded into a chooser option for new issues, if desired. Closes coreos#641
- Loading branch information
Showing
2 changed files
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Request to Include a New Package in Fedora CoreOS | ||
|
||
If you would like to propose the inclusion of a new package into the base | ||
content set of Fedora CoreOS, please open a [new issue](https://github.com/coreos/fedora-coreos-tracker/issues/new) | ||
here on the [fedora-coreos-tracker repo](https://github.com/coreos/fedora-coreos-tracker) | ||
with the following questions answered. The more detail provided for each | ||
question, the better informed everyone will be. | ||
|
||
Please title the new issue: `Package Request: <name of package>` | ||
|
||
1. What, if any, are the additional dependencies on the package? (i.e. does it drag in Python, Perl, etc) | ||
2. What is the size of the package and its dependencies? | ||
3. What problem are you trying to solve with this package? Or what functionality does the package provide? | ||
4. Can the package be run from a container? Explain why or why not. | ||
5. Can the tool be helpful in debugging container runtime issues? | ||
6. Can the tool be helpful in debugging networking issues? | ||
7. Is it possible to layer the package onto the base OS as a day 2 operation? Explain why or why not. | ||
8. Can the packaging be adjusted to just deliver binaries? | ||
10. Can the tool be used to do things we’d rather users not be able to do in FCOS? (e.g. can it be abused as a Turing complete interpreter?) | ||
11. Does the tool have a history of CVEs? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters