Some packages are "leafy" - no dependencies, Shiny Marketing Features. Others are more crit-path/have dependencies looking.

Would like to get the following:
(a) Sanity check of Shiny vs. Critical/Dependency-oriented
(b) Exceptions for Shiny
(c) Feedback on how to proceed with critical/dependency-oriented features.

Shiny Features:
* XAPI: 40% https://fedoraproject.org/wiki/Features/XAPI
* Riak: 35% https://fedoraproject.org/wiki/Features/Riak
* Static Analysis of Python Ref Counts: https://fedoraproject.org/wiki/Features/StaticAnalysisOfPythonRefcounts
* Services in private /tmp: 75% https://fedoraproject.org/wiki/Features/ServicesPrivateTmp
* oVirt: 0% https://fedoraproject.org/wiki/Features/oVirt (this is dependent in some ways on JBoss AS7, which already has an exception request)
* OpenStack Essex: 50% https://fedoraproject.org/wiki/Features/OpenStack_Essex -- things are all in, just waiting on the upstream release on Apr. 5 to update the packages to newest release.
* OpenNebula: was blocked a bit by new Ruby landing, at 42% right now. https://fedoraproject.org/wiki/Features/OpenNebula
* Numad: 40%. https://fedoraproject.org/wiki/Features/numad
* Cloudstack: 40% https://fedoraproject.org/wiki/Features/Cloudstack
* Darkserver GNU Build ID service: 40% https://fedoraproject.org/wiki/Features/Darkserver
* DIET: 60% https://fedoraproject.org/wiki/Features/F17_DIET
* Eucalyptus: 70% https://fedoraproject.org/wiki/Features/Eucalyptus

Others may be more critical path / dependency oriented (NOTE: I AM NOT THE EXPERT HERE)
* Power Management: 75% https://fedoraproject.org/wiki/Features/PowerManagementF17
* NW Mgr Hotspots: 30% https://fedoraproject.org/wiki/Features/RealHotspot
* New mkdumprd: 60% https://fedoraproject.org/wiki/Features/NewMkdumprd
* Gnome-shell software rendering: 60%, https://fedoraproject.org/wiki/Features/Gnome_shell_software_rendering
* ABRT backtrace deduplication: 60% https://fedoraproject.org/wiki/Features/ABRTBacktraceDeduplication
* NW Mgr Enterprise Networking: 40% https://fedoraproject.org/wiki/Features/NMEnterpriseNetworking
* Eclipse Juno: 10% https://fedoraproject.org/wiki/Features/EclipseJuno <-- may be funky because we're putting in a prerelease, updating as soon as upstream releases in June.
* GCC 4.7: 50% https://fedoraproject.org/wiki/Features/GCC47 (I suspect this is along further than 50%)

One more (for the critical bucket, I suppose):
* SysV to systemd - 40%. https://fedoraproject.org/wiki/Features/SysVtoSystemd. I know this one is largely "as we can" but want to ensure that it's kosher to bump to 100% at some point for "we finished 100% of what we could humanly accomplish."

FESCo agreed at 2012-02-13 meeting on:

• New mkdumprd, Eclipse Juno, Power Management move to the 'Shiny' list

• PrivateTmp, SysVtoSystemd move to the 'critical' list

FESCo members will take action items to investigate the critical list, report back on status, start discussions on any potential contingency plans, etc. Assignments are:

• NM Hotspots -> nirirk
• GNOME Shell SW render -> notting
• ABRT backtrace dedup -> t8m
• PrivateTmp -> sgallagh
• NM Enterprise Networking -> limburgher
• GCC 4.7 -> pjones
• SysVtoSystemd -> mitr

Talked with ajax on GNOME Shell's software rendering:

• status is accurate (c.f. http://ajax.fedorapeople.org/software-gnome3-todo.txt)
• code is in F-17 and is testable
• more optimizations to land soon
• llvmpipe is enabled by default where applicable for both GNOME and KDE

IMO, sounds fine for alpha, no need to change course.

Talked with dcbw about NetworkManager Hotspots for f17.

It's not yet in and testable, so it sounds like it's going to be moved to target f18.

I talked with dwalsh about PrivateTmp.

The feature itself is ready, but there are some remaining packages that haven't updated themselves to take advantage of it. See https://bugzilla.redhat.com/showdependencytree.cgi?id=782466&hide_resolved=1 for details.

Also, systemd has broken PrivateTmp: https://bugzilla.redhat.com/show_bug.cgi?id=790522

Dan has updated the Feature page to 100% from his side of things.

I talked with mtoman about ABRT backtrace deduplication.

They will update the Feature page today with the current status. They are on time with the development and they expect to meet the 100% status by F17 Beta.

!SysvToSystemd: work ongoing, at this speed will be done sometime around F20. The only problems are the old known ones, no reason to consider the contingency plan.

Pinged dcbw about NMEnterpriseNetworking, no response, re-pinged today. libnl3 is in, but no commits to rawhide NetworkManager since 1/19/2012, so I'm guessing f18 for this as well.

I've also been working on systemd migrations, I don't have an exact count, but I think I've probably done 10-ish with the approval of their primary maintainers, building only for f18 so far, since most of this has been done since the enactment of bodhi for f17.

Still nothing from dcbw re: NMEnterpriseNetworking. No additional commits.

I talked to dcbw.

https://fedoraproject.org/wiki/Features/NMEnterpriseNetworking is still targeting F17

https://fedoraproject.org/wiki/Features/RealHotspot is not going to make f17, and will retarget f18.

With that I think we are all caught up here, and I will close this out. Feel free to reopen when/if we need to look more.