I am new to this list, so I hope noone minds me asking this question. What applications are we referring to? Are these really apps or sophisticated sys admin scripts?<br><br><br><br><div><span class="gmail_quote">On 5/29/07,
<b class="gmail_sendername">Rahul Sundaram</b> <<a href="mailto:sundaram@fedoraproject.org">sundaram@fedoraproject.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Toshio Kuratomi wrote:<br><br>> Do people think this is an allowable exception? These apps are in a<br>> grey area between one-off system administration scripts and applications<br>> that are present in multiple environments already. I think they must be
<br>> OSS and their source must be available but I'm not sure if the<br>> requirement that they be packaged for Fedora is necessary.<br><br>We had a policy in place before when I used to sys admin stuff that all
<br>the packages needs to be available in the distribution repository and<br>any local scripts be cleanly separated. It helps a lot. You get<br>packaging and legal checks. Even if a particular piece of software is<br>used only in one place in the Fedora infrastructure not having it in the
<br>repository means the team is solely responsible for keeping track of any<br>security issues. It is up to the team to decide to allow exceptions but<br>you have to weigh the benefits carefully.<br><br>> I also foresee us running into issues at some point with version
<br>> mismatches between the Fedora/EPEL packages and what we run on our<br>> servers. Maybe we want to upgrade the TurboGears stack on our servers<br>> but we don't want to change the API for EPEL. Maybe we are putting out
<br>> necessary updates for the apps we are working on but upgrading the bits<br>> in Fedora/EPEL every two days doesn't seem like a good idea. We need to<br>> have some ability to separate what we package for Fedora from what we
<br>> are actively developing in Infrastructure.<br><br>Again any deviations from what is in the repository is additional<br>burden for the team. Deciding on the details is why having good<br>documentation on the policies are helpful. Maybe this could be discussed
<br>in the next IRC meeting?<br><br>Rahul<br><br>_______________________________________________<br>Fedora-infrastructure-list mailing list<br><a href="mailto:Fedora-infrastructure-list@redhat.com">Fedora-infrastructure-list@redhat.com
</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list">https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list</a><br></blockquote></div><br><br clear="all"><br>-- <br>--Freddie