EPEL Django deprecated

[Stephen John Smoogen]

On 7 June 2013 10:48, Karsten 'quaid' Wade <kwade at redhat.com> wrote:

>
>
> Just to continue down this path for a moment, what are the ways we can
> track or get ideas of what is important to EPEL users? If we could
> improve what we have already, how would we do so? (Let's pretend for a
> moment that we can get a developer to help build and maintain something
> ... what would we have that person do?)
>
>
Most of the methods would require the user running something that tells us
what they have installed.. which usually violates various business rules
and/or needs approval via management chain. Since getting anything like a
census application would require all kinds of approval it would only get
installed on volunteer systems which tend to be atypical in usage.

The easiest way I could see is just get a better sampling method which
would be to have funding for a mirror which we then put into mirror-manager
and we know that this is a sampling versus a request info. (basically we
would see what packages are downloaded directly and then extend that sample
from the amount of downloads to the 500,000 systems that check in via
mirrormanager). The problems involved are paying for systems, storage, and
bandwidth for such items.

-- 
Stephen J Smoogen.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20130607/f377642b/attachment.html>