|
Size: 2234
Comment:
|
Size: 2163
Comment: Removing superfluous 'should' from first sentence.
|
| 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 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 etc. |
| Line 10: | Line 11: |
| * 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 buildsys etc. |
* We'll have two main repos in the beginning: |
| Line 15: | Line 13: |
| * The main new repo will contain add-on packages and not replacements in relation to the base package set that. Whereby the base package set is defined as the set the packages get build against, e.g.: 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 Fedora Packaging Guidelines) which can't be included in Fedora because it might be patent encumbered in the US * one named "nonfree" for non-free software, e.g. everything else which can't be in freeworld; this includes software with public available source-code that has "no commercial use"-like restrictions |
| Line 21: | Line 17: |
| 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 will depend on the free repository; Open Source Software which depends on non-free software needs to be shipped in the nonfree repository. |
| Line 25: | Line 19: |
| * rpmfusion will contain kernel module packages in the main repo | Both repositories will 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 will contain kernel module packages in the main repo, even if Fedora will drop them (which looks likely as of August 2007) |
| Line 29: | Line 27: |
| * kernel packages maybe packaged using the kmod(FE) dkms(freshrpms) or kdmls(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. |
* kernel packages -- needs to be discussed again (other stuff is higher on the todo list right now) how to actually package them; it might be possible to package them with both the kmod (fedora) or dkms (freshrpms) kernel module packaging schemes in one repository. * after the freeworld and nonfree repositories are running we might start an additional repository where with proper motivation replacements are allowed. This repo which will NOT be enabled by default. |
| Line 38: | Line 33: |
| (1) Assuming EPEL ever lifts off and becomes a success (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. |
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 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 etc.
- We'll have two main repos in the beginning:
- one named "free" for Open Source Software (as defined by the Fedora Packaging Guidelines) which can't be included in Fedora because it might be patent encumbered in the US
- one named "nonfree" for non-free software, e.g. everything else which can't be in freeworld; this includes software with public available source-code that has "no commercial use"-like restrictions
- RPM Fusion will contain kernel module packages in the main repo, even if Fedora will drop them (which looks likely as of August 2007)
Principles under discussion
- kernel packages -- needs to be discussed again (other stuff is higher on the todo list right now) how to actually package them; it might be possible to package them with both the kmod (fedora) or dkms (freshrpms) kernel module packaging schemes in one repository.
- after the freeworld and nonfree repositories are running we might start an additional repository where with proper motivation replacements are allowed. This repo which will NOT be enabled by default.
Footnotes
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.