|
Size: 2453
Comment:
|
Size: 1433
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from FoundingPrincipals = rpmfusion founding principles = |
= RPM Fusion founding principles = |
| Line 4: | Line 3: |
| Before we start working on technical details, I think its very important to have a set of founding principles, much like the "Core Principles" of fedora: http://fedoraproject.org/wiki/Objectives | This page contains the set of founding principles, much like the "[[http://fedoraproject.org/wiki/Objectives|Core Principles]]" of Fedora. |
| Line 6: | Line 5: |
| I've split the principles into 2 sets for now, one we all agree on, and one for principles which are still under discussion. | == Principles we agree on == |
| Line 8: | Line 7: |
| == Principles we all agree on == | The RPM Fusion's repositories and the infrastructure to maintain them follow Fedora where possible. This means using [[http://fedoraproject.org/wiki/Packaging/Guidelines|Fedora's packaging guidelines]] (except for legal), Fedora's review process for new submissions, Fedora's VCS structure etc. |
| Line 10: | Line 9: |
| * The new repo will follow Fedora where possible. This means using Fedora's packaging guidelines (except for legal), Fedora's review process for new submissions, Fedora's VCS structure, Fedora's build system etc. |
We have two main repositories: |
| Line 15: | Line 11: |
| * The main new repo will contain add-on packages and not replacements in relation to the base package set. Whereby the base package set is defined as: RHEL/centos + EPEL (1) or Fedora (Fedora 7+) or Fedora Core + Fedora Extras (Fedora 6-) |
* one named "free" for Open Source Software (as defined by the [[http://fedoraproject.org/wiki/Licensing|Fedora Licensing Guidelines]]) which can't be included in Fedora because it might be patent encumbered in the US * one named "nonfree" for non-free software, that is everything else which can't be in free; this includes software with public available source-code that has "no commercial use"-like restrictions |
| Line 19: | Line 15: |
| As an exception, with proper motivation replacements are allowed, but the replacements and any packages requiring the replacements will be in a seperate repo which will NOT be enabled by default. |
The nonfree repository depends on the free repository; Open Source Software which depends on non-free software is shipped in the nonfree repository. |
| Line 23: | Line 17: |
| * rpmfusion will contain kernel module packages in the main repo | Both repositories contain only add-on packages and not replacements in relation to the base package set. Whereby the base package set is defined as: RHEL/CentOS + EPEL or Fedora (Fedora 7+) |
| Line 25: | Line 19: |
| == Principles under discussion == * kernel packages maybe packaged using the kmod (fedora) dkms (freshrpms) or kmdls(atrpms) kernel module packaging schemes (2). A module may be made available for more then one scheme. But the "Name: " tag of the packages must be unique, if this currently is the not the case then the maintainers of the conflicting packages will work this out together. Also different packages of the same module must explicitly Conflict each other. == Footnotes == (1) While EPEL is not available, we will assume an empty EPEL repo. As EPEL gets populated we will work together with EPEL to avoid conflicts/overlaps. This also means that where dependencies for certain packages are missing we will provide these by rebuilding (and adapting where nescesarry) those bits from Fedora. (2) This means that plague must be modified to support al these, or even that we may use a different buildsystem altogether if thats easier, as long as the buildsystem uses mock with the fedora minimal buildroot. Notice that this doesn't mention how we are actually going todo anything yet, nor with which base distro releases we will start. This is intentional as these (important) details are not part of our founding principles. |
RPM Fusion accepts kernel module packages in [[http://rpmfusion.org/Packaging/KernelModules/Kmods2|Kmod2 standard]]. |
RPM Fusion founding principles
This page contains the set of founding principles, much like the "Core Principles" of Fedora.
Principles we agree on
The RPM Fusion's repositories and the infrastructure to maintain them follow Fedora where possible. This means using Fedora's packaging guidelines (except for legal), Fedora's review process for new submissions, Fedora's VCS structure etc.
We have two main repositories:
one named "free" for Open Source Software (as defined by the Fedora Licensing Guidelines) which can't be included in Fedora because it might be patent encumbered in the US
- one named "nonfree" for non-free software, that is everything else which can't be in free; this includes software with public available source-code that has "no commercial use"-like restrictions
The nonfree repository depends on the free repository; Open Source Software which depends on non-free software is shipped in the nonfree repository.
Both repositories contain only add-on packages and not replacements in relation to the base package set. Whereby the base package set is defined as: RHEL/CentOS + EPEL or Fedora (Fedora 7+)
RPM Fusion accepts kernel module packages in Kmod2 standard.