Dominik 'Rathann' Mierzejewski wrote:
On Saturday, 09 May 2009 at 19:24, Jon Stanley wrote:
FESCo meeting summary for 2009/05/08
== Members Present ==
* Jon Stanley (jds2001)
* Kevin Fenzi (nirik)
* Dan Horak (sharkcz)
* Josh Boyer (jwb)
* Brian Pepple (bpepple)
* Bill Nottingham (notting)
* David Woodhouse (dwmw2)
* Jarod Wilson (j-rod)
== Members Absent ==
* Dennis Gilmore (dgilmore)
[...]
== Maven upgrade ==
Rel-eng brought a proposal during the open floor to allow the
inclusion of packages in a special tag (something like dist-f12-maven)
in preparation for the maven upgrade that had yet to be through a
formal package review. These packages are not yet in a state suitable
for inclusion in Fedora, and the Java team would prefer to get them
functional prior to cleaning up the packaging. FESCo approved this
propsal, with the caveat that the packages have to go through a
mini-review prior to inclusiion in this tag and therefore being used
in buildroots. This mini-review will be defined by FPC, and will
include things such as checking for lack of binaries, and legal
concerns.
As a packager and a member of the FPC, I think it is a very bad idea to let
packages in without proper review.
+1
I'd like to hear the very convincing
arguments which I expect were presented directly to some FESCo members
but were not included in the IRC meeting log for why this was allowed and
why the packages in question (which ones, exactly?) couldn't go through
the usual hoops like all new packages.
I don't see why the Java team (who, exactly?) or anyone else should
be allowed to import packages into Fedora CVS without proper review.
I also expect this will be brought up in similar cases in the future
with the justification that "we did this before".
I don't see why these people can't use an external VCS/repository, like
probably many developer groups do.
Ralf
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
