Plan for tomorrows (20070801) EPEL SIG meeting

[Thorsten Leemhuis]

Hi all,

find below the list of topics that are planed to come up in the next
EPEL SIG meeting which is scheduled for tomorrow, Wednesday at 17:00 UTC
in #fedora-meeting on irc.freenode.org.

EPEL announcement happened -- are we satisfied with how everything
worked out?

branch for EPEL if Fedora maintainer does not react -- dgilmore

new push scripts for pushing to testing, adjust mock configs to use
testing -- dgilmore

EPEL announcement happened -- what next?

You want something to be discussed? Send a note to the list in reply to
this mail and I'll add it to the schedule (I can't promise we will get
to it tomorrow, but we'll most likely will if we don't run out of time).
You can also propose topics at the end of the meeting itself.

If your name/nick is on above list please give a update. That way all
the interested parties know what up ahead of the meeting; that will
avoid long delays and "status update monologues in the meeting.

Thanks!

CU
knurd

[Thorsten Leemhuis]

Hi all!

Sorry, I have to leave the keyboard in some minutes and will miss the
meeting. Nothing urgent, but a was not foreseeable. Some comments for
todays meeting:

On 31.07.2007 19:32, Thorsten Leemhuis wrote:
> find below the list of topics that are planed to come up in the next
> EPEL SIG meeting which is scheduled for tomorrow, Wednesday at 17:00 UTC
> in #fedora-meeting on irc.freenode.org.
>
> EPEL announcement happened -- are we satisfied with how everything
> worked out?

So far: yes. I'd hoped we would have had some more packages and more
media coverage, but it's a good start afaics. The broken deps problem
was worked around just in time afaics.
> branch for EPEL if Fedora maintainer does not react -- dgilmore

I'd really like to get this of the table. If somebody has concerns with
the latest proposal write them up please or (preferred) write a new
proposal that solves the problem that was raised with the current one in
the wiki -- if no ones does it soon I'd say let's go for
https://www.redhat.com/archives/epel-devel-list/2007-July/msg00104.html
as that's better then what we have
> new push scripts for pushing to testing, adjust mock configs to use
> testing -- dgilmore

Status? RHEL 5.1 is approaching and I'd say we copy the testing repo to
stable then again.
> EPEL announcement happened -- what next?

I'd like to see this discussed on the list. I have some ideas, but not
enough time to write all of the down now.

So: What do you guys want?

Note. I forgot the "yum for EPEL4" issue. Could you guys discuss this as
well? Jeff_S prepares some stuff iirc, we just need to say "go for it"
afaics. Someone raised concerns in the last meeting, but never took them
to the list which isn't helpful to get the problem solved. I'd say if
the concerns doesn#t make it to the list let's go for what Jeff proposed.

Cu
thl

[Orion Poplawski]

Thorsten Leemhuis wrote:
> > branch for EPEL if Fedora maintainer does not react -- dgilmore
>
> I'd really like to get this of the table. If somebody has concerns with
> the latest proposal write them up please or (preferred) write a new
> proposal that solves the problem that was raised with the current one in
> the wiki -- if no ones does it soon I'd say let's go for
> https://www.redhat.com/archives/epel-devel-list/2007-July/msg00104.html
> as that's better then what we have

I like this.

[Karsten Wade]

On Tue, 2007-07-31 at 19:32 +0200, Thorsten Leemhuis wrote:
> EPEL announcement happened -- are we satisfied with how everything
> worked out?

In retrospect ...

* Someone else (not @redhat.com) could have sent the email and avoided
some confusion.

* A few people contacted me who had interest in being EPEL maintainers,
so publicity was good.

* I saw some Q&A go by that showed that many people clearly understand
the reason and value of EPEL.

* Timing it to also go to RHEL user lists would have been good, but that
might have caused delay in arranging.

* Be careful of last minute changes in content, they are the biggest
risk to typos/incomplete sentences.

[Rahul Sundaram]

Karsten Wade wrote:
> On Tue, 2007-07-31 at 19:32 +0200, Thorsten Leemhuis wrote:
> > EPEL announcement happened -- are we satisfied with how everything
> > worked out?
>
> In retrospect ...
> Someone else (not @redhat.com) could have sent the email and avoided
>
> some confusion.

True. EPEL repository media coverage has not been bad but by no means large.

http://www.linuxelectrons.com/news/application/10941/red-hat-launches-new-pa...

Linux electrons assumed it was a Red Hat effort since you send the mail 
and so did Distrowatch which used it as a reference in

http://distrowatch.com/weekly.php?issue=20070730#news

Linux.com had a article with extensive references to the EPEL FAQ

http://www.linux.com/feature/118304

We have had some discussions in fedora marketing list and with some 
other product management folks about how it relates to RHEL. Short 
outlook is supportive but wait and watch for more input.

If there are no announcements to RHEL announce lists being send out 
someone should atleast do it informally in the user lists.

Rahul

[Marek Mahut]

Hello all,

I'm very sorry. I missed this meeting, I just screw up the timezone and
came one hour later :(

Thorsten Leemhuis wrote:
> Hi all,
>
> find below the list of topics that are planed to come up in the next
> EPEL SIG meeting which is scheduled for tomorrow, Wednesday at 17:00 UTC
> in #fedora-meeting on irc.freenode.org.
>
> EPEL announcement happened -- are we satisfied with how everything
> worked out?
>
> branch for EPEL if Fedora maintainer does not react -- dgilmore
>
> new push scripts for pushing to testing, adjust mock configs to use
> testing -- dgilmore
>
> EPEL announcement happened -- what next?
>
> You want something to be discussed? Send a note to the list in reply to
> this mail and I'll add it to the schedule (I can't promise we will get
> to it tomorrow, but we'll most likely will if we don't run out of time).
> You can also propose topics at the end of the meeting itself.
>
> If your name/nick is on above list please give a update. That way all
> the interested parties know what up ahead of the meeting; that will
> avoid long delays and "status update monologues in the meeting.
>
> Thanks!
>
> CU
> knurd