----- Original Message -----
> On Tue, Mar 25, 2014 at 9:15 AM, Matthew Miller
> <mat...@fedoraproject.org> wrote:
> > On Mon, Mar 24, 2014 at 05:07:35PM -0700, Toshio Kuratomi wrote:
> >> Alternative idea -- maybe identify all packages which are not ciritcal and
> >> have an open merge review.  Take those packages out of the repository.
> >> Then revisit the list and formulate a plan on what to do with thoes (even
> >> if
> >> the plan is then, these were critical enough to leave in so we'll give
> >> them
> >> a pass on going through a formal review).
> >
> > I like the idea of actually revisiting the list and deciding what to do,
> > although pulling them out of the repository seems unnecessarily drastic.
> 
> This always winds up being the suggestion.  Nobody actually does
> anything about it.  I'd only be supportive of this on two conditions:
> 
> 1) Actual bugs impacting actual people as a result of an improper spec
> file were present
> 2) One of the bodies responsible for packages in Fedora (FESCo, FPC,
> ?) agreed to conduct audits across all packages for guideline
> adherence at regular intervals.
> 
> I'd be willing to not require item 1 if item 2 were actually done.  It
> never has been, and if it had it would already suffice for the purpose
> the merge review tickets would serve today.
> 
> We have a lot of guidelines.  Enough that it can be rather daunting to
> a new packager to even start packaging something.  What we have always
> lacked is enforcement and accountability on those guidelines _after_
> something is in the distro.

+ unlimited to the last paragraph.

Jaroslav

> Fix that problem and everything else
> relating to it will be solved.
> 
> josh
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to