Thanks for sharing this.
It's really a great news for us that you will help to maintain the TG1 stack in EPEL7
and will start the un-retiring process. Hope they will be available again soon.
Yes, when talking about real projects, when schedules, requirements, efforts, resources,
risks, etc, are involved, the reality is always far away from the theory.
We should have planned the migration from TG1 in this release. However, probably because
there is no obvious benefit that we can get from it, it's never been given a high
I think this show-stopper will push us to really consider the migration seriously in
future releases, either to TG2 or to Django.
For co-maintaining the TG1 stack, I would like to and will start to look into how to do
that, but I hope it could be recovered before I can really offer any help, because our
currently release is kind of blocked by this issue.
A lot of tasks, plans depend on whether TG1 would be availble on EPEL7. We are going to
discuss our platform support stuff early next week and hope there would be some more good
From: Dan Callaghan [mailto:firstname.lastname@example.org]
Sent: Friday, 11 July 2014 10:42 AM
To: Zhiwei Zhu
Cc: EPEL Development List
Subject: Re: EPEL Orphan or retire the TurboGears (v1) stack in 7
Excerpts from Zhiwei Zhu's message of 2014-07-11 09:31:37 +1000:
Thanks. Understand the situation now.
Will discuss with my lead about the possibility to maintain the
packages by ourselves.
BTW, as we don't have experience of maintaining packages on epel, we
have no idea how much effort will be required to do that or how
difficult it would be.
Could you help to share something about this? I understand that there
is some kind of co-maintainer path to take for new maintainers but
don't how to start it.
I had hoped we would have Beaker ported off TG1 long before now, and I was going to use
the retirement of the EPEL7 TG1 stack as extra motivation to get it done, but
realistically we will be depending on it for quite a while still, just like you Zhiwei.
So I can maintain the TG1 stack in EPEL7. I will start the un-retiring process for all the
packages we need and post the exact list here.
Zhiwei, if you would like to co-maintain that would be a great help. I'm not able to
sponsor you into the packager group, but I think you can be a co-maintainer without a
sponsor (actually I'm not sure about that...)
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Hosted & Shared Services Red Hat, Inc.