FESCo Meeting Summary - 2009-03-03

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

 



=== Members Present ===
* Kevin Fenzi           (nirik)
* Dan Horák             (sharkcz) 
* Jarod Wilson          (j-rod)
* Josh Boyer            (jwb)
* Brian Pepple          (bpepple)
* Dennis Gilmore        (dgilmore)
* Bill Nottingham       (notting)

=== Members Absent ===
* David Woodhouse       (dwmw2)
* Jon Stanley           (jds2001)

== Summary ==

=== Features ===

* DBusPolicy - http://fedoraproject.org/wiki/Features/DBusPolicy

6 +1 votes, FESCo approved this Feature. Some contention over whether or
not this is really a Feature or just a security hole we need to fix
regardless, but since it touches so many areas, FESCo deemed that the
scope made it Feature-worthy.


* DRI2 - http://fedoraproject.org/wiki/Features/DRI2

6 +1 votes, FESCo approved this Feature. Release notes still need to be
fleshed out though.


* MultiplePAMStacksInGDM - http://fedoraproject.org/wiki/Features/MultiplePAMStacksInGDM

6 +1 votes, FESCo approved this Feature, with the caveat that the minimum
necessary code gets into rawhide TODAY so that it can be properly tested
in the F11 Beta release.


* Radeon3DUpdate - http://fedoraproject.org/wiki/Features/Radeon3DUpdate

6 +1 votes, FESCo approved this Feature. A bit of concern over the current
80% complete status listed on the Feature page, but the Feature owner was
unavailable for comment (middle of the night in .au). Assumption is that
its at least mostly testable and part of the remaining percentage of work
is dealing with any regressions introduced.


* TigerVNC - http://fedoraproject.org/wiki/Features/TigerVNC

FESCo previously approved a TightVNC Feature. The Feature was recently
renamed to TigerVNC, due to upstream issues resulting in a fork. The
changes prompted FESCo to re-review this Feature.

6 +1 votes, 1 -1 vote, FESCo approved this Feature. There is some concern
over the last-minute change to the Feature page from TightVNC to TigerVNC
and over why TightVNC was forked, rather than resolving issues with the
TightVNC upstream folks. FESCo would like to hear more explanation and
justification for the fork, but in theory, we'll get the same code
regardless of the package name, assuming the TigerVNC package can be
approved *today* so that it makes it into the F11 Beta release, so the
Feature was re-approved, with one dissenting vote.


IRC log can be found at:
http://bpepple.fedorapeople.org/fesco/FESCo-2009-03-03.html


-- 
Jarod Wilson
jarod@xxxxxxxxxx

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[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