meetings and some issues

Stephen John Smoogen smooge at
Mon Feb 9 23:49:20 UTC 2009

2009/2/9 Kevin Fenzi <kevin at>:
> Greetings.
> Since we haven't had an epel meeting in quite a while, I would like to
> revisit the idea of a new meeting time. Perhaps we could setup a table
> in the wiki for people to fill in and choose the best time that way?
> Or perhaps someone would like to suggest a time?

Thanks Kevin.

> Some issues that are pending that we can just discuss here:
> - Did we ever decide to make a epel-announce list? I think this might
>  be good still to send important announcements about packages or other
>  changes that end epel users should be notified of. I am not sure, but
>  we could also send the package update announcements there (might be
>  too much traffic tho, perhaps just the stable ones?)

It was tabled to be discussed on list. I am for it.

> - Orphans. We have the following orphan packages. Some of them are more
>  'retired', but we should look at trying to find owners for the ones
>  that can still be maintained.
> abcde
> aget
> cd-discid
> csync2
> cvs2cl
> cvsps
> freetennis
> gkrellm
> gkrellm-volume
> gtkhtml38
> libid3tag
> libmodplug
> mach
> otrs
> pytz
> redet
> redet-doc
> svn2cl

Hmmm I though otrs just got put in.

> - Bugs. We are now just over 100 epel bugs. This is no good, IMHO.
> Would it be possible to get some interested folks to dig through these
> and see about fixing easy ones/poking maintainers/doing something to
> move them along. Especially in the case where it's a missing dep.

> EPEL&bug_status=NEW&bug_status=MODIFIED&bug_status=ASSIGNED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=RELEASE_PENDING&bug_status=POST&bug_status=FAILS_QA

Ok that sounds like something I can start on.

> - Do we need to do anything to prep for RHEL6? Do we just branch the
>  things that are already in EPEL5? Or can we look at more than that?


1) We need to get the build system to koji. David Gilmore says thats
real soon now (like this month).
2) We need to have a branch where we will build 'everything' against
the BETA when it comes out. That way we can keep track of where things
break and see if we can get some loving to EL-6 sooner versus later.
3) We need a TAM at Red Hat to keep us in contact with what is going
on with EL{4,5,6} so that we have better communication about changes.

> - How can we get better communication between EPEL and RHEL? ie, the
>  recent packages they put in 5.3 without notifying or even providing a
>  higher evr. ;(

Same old, same old. I think the issue is that inter departmental
communication has never been a good strength at Red Hat. [As was once
noted if it didn't happen on tech-list, it wasn't a technical

> - How can we get more packages branched for EPEL? Perhaps we could
>  approach some of the sigs, like the perl-sig and ask them to consider
>  their packages that work/make sense on EPEL (I have seen a bunch of
>  new perl packages in fedora that were not branched for EPEL).
> I'm sure there are other things, but those are the ones I can think of
> off the top of my head. ;)
> kevin

Thanks again kevin.

Stephen J Smoogen. -- BSD/GNU/Linux
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"

More information about the epel-devel-list mailing list