Re: Announcement: EPEL Steering Committee Changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 19, 2020 at 1:01 AM John M. Harris Jr <johnmh@xxxxxxxxxxxxx> wrote:
>
> On Tuesday, February 18, 2020 10:35:26 AM MST Stephen John Smoogen wrote:
> > Hi,
> >
> > It has been a pleasure for me to be a part of and help lead the
> > EPEL steering committee for the last couple of years. It has not
> > always been smooth sailing but I have found it an enjoyable experience.
> >
> > However, as you may know the Fedora project will be moving to a
> > different data-center later this spring (from Phoenix to northern
> > Virginia). Being involved in the planning and implementation of this
> > project, I do not think that I will be able to give EPEL the time
> > investment it deserve for the next 6 to 9 months. With EPEL-8 still
> > ramping up and the various opportunities with modularity, I do
> > not think it is a fair that EPEL suffers from this lack of time.
> >
> > As such, I would like to step down as chair/member of the steering
> > committee and nominate Troy Dawson as my replacement. Troy formerly
> > worked on Scientific Linux and has worked on OpenShift and other
> > projects at Red Hat for the last several years.  It is clear he has a
> > good eye on the concerns and problems enterprise users have. Recently,
> > Troy helped get the initial RHEL-8 and EPEL-8 out the door with
> > multiple builds and updates to various macro files.
> >
> > Once the move is completed and the close down of the old site is done,
> > I look forward to getting involved again in EPEL.
>
> Based on this, I'm not so sure that Troy is the best person to take that place
> within EPEL's Steering Committee. As an enterprise admin, RHEL8 has been
> nothing but a nightmare to deal with because of Modularity. I know Troy didn't
> singlehandedly sign off on that nonsense, but, as he is a member of the
> Modularity team, this is not a good sign for what's to come.

I also dislike modularity: it's costing me time and money resolving
mismatched dependencies for components I use that pull dependencies
that are both base packages and modularity published. Fedora seems to
have stepped back from their early enthusiasm as the difficulties
become more clear. But if he's got the skills and is willing to do the
work, Someone at EPEL needs to be comfortable enough with modularity
to resolve the overlaps with RHEL 8/CentOS 8 built-in modularity.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux