On Wed, Feb 25, 2009 at 11:51 AM, Thorsten Leemhuis
<fedora(a)leemhuis.info> wrote:
# CCed to epel-devel-list, as the audience there might be interested
in
# this mail as well; nevertheless please send replies to
# rpmfusion-developers(a)lists.rpmfusion.org only, tia!
Hi!
As some of you may know: RPM Fusion (
http://rpmfusion.org/ ) not only
supports Fedora, it also wants to support EL (e.g. RHEL and
clones/derivatives like CentOS) & EPEL for EL >=5 similar to how RPM Fusion
supports Fedora(¹), as a lot of people asked for such a repo. The testing
repositories for this are online and filled with the most important RPM
Fusion packages for quite a while now; see
http://thorstenl.blogspot.com/2008/11/rpm-fusion-for-el-in-early-testing....
for details how to enable those repos.
In the past weeks there hasn't been much progress to move the packages to
the normal repos and to officially announce support for EL & EPEL. The main
reason for that: We have quite a few packagers that are interested in having
the most important RPM Fusion packages available in a RPM Fusion for EL &
EPEL, but afaics nobody really wants to do the surrounding work that is
needed. Hence RPM Fusions look for a volunteers (or maybe two) that act a
bit as "Release-Engineers/-Managers" for RPM Fusion's EL repos.
The position means a bit of work, but not to much if everything works well.
And the latter (making sure everything works well) is basically the job
description already; e.g. make sure the repo as a whole work is in healthy
state and now and in the future makes users and contributors glad. That
means things like:
Are there legal aspects to be considered? I'm a non-US citizen
residing in the US, and I'm interested in this, but would rather stay
away from having official responsibility for packages such as
gstreamer-plugins-{ugly,bad}.
Regards,
--
miʃel salim •
http://hircus.jaiku.com/
IUCS • msalim(a)cs.indiana.edu
Fedora • salimma(a)fedoraproject.org
MacPorts • hircus(a)macports.org