Re: Software management: Call for RFEs results!

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

 



On Fri, Oct 4, 2013 at 5:34 AM, Jan Zelený <jzeleny@xxxxxxxxxx> wrote:
> Hello everyone,
> as you might remember I issued a call for RFEs on this list during the spring.
> The participation was not bad at all, we have collected so many data that it
> took us several months to discuss and process it.
>
> Now I have some results for you. Attached to this email you can find a strategy
> document that a) outlines the strategy that we will commit to in the next 3-5
> years and b) contains all the RFEs that were recognized as valid RFEs and were
> accepted to be implemented as a part of our strategy.
>
> Please note that the rest of the RFEs from the discussion was also evaluated
> but most likely rejected. If your RFE is not on the list, you can drop me an
> email and I'll tell you more specific reasons why we decided not to put it on
> the list.
>
> If you have any other questions, comments or notes regarding the document,
> feel free to to use this list for the discussion.
>
> Thanks
> Jan
>
> PS: I'll be AFK for the weekend so I'll comment on your replies on Monday
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

First off, thanks for this. I'm glad some people are really trying to
look at the path forward.   I'm also sorry I missed your RFE then.
High traffic-lists sometimes get skipped over :(


I like the goals of the paper. My main concerns is this addresses
technical issues that are already in play.  It doesn't address several
items that are not technical issues which IMHO, is the main reason RPM
isn't used for everything.

Developers don't do deployments with RPM...at least not inside Fedora.
Anything sane is actually against Packaging Guidelines. So that
becomes a problem, and developers skip it. If  developers (or
operations people) are savvy enough to make RPMs, they are used once
and not shared because they wouldn't get accepted into Fedora/EPEL.

Also, sometimes developers/deployments need multiple versions of
things installed.

Is there a an effort that complements this one on the policy/non-technical side?
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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