Although all interested parties probably know (previously announced on
the devkit-devel mailing list a few times) UPower has branched from
0.9 and is now being tidied up for the journey to version 1.0.0. Part
of this was fixing some of the deeper architectural flaws, and my
thanks go to Bastien for fixing up so many thorny things in the last
I've just built the new release in rawhide ready for the GNOME
packages that depend on the newer API, but I'm certainly not planning
on building this for f19 or f20.
Any questions, either grab hadess or hughsie on irc. Thanks.
My apologies for the last minute agenda. We'll be holding our initial
WG meeting today at 14:00 UTC in #fedora-meeting on Freenode. We'll
cover the various items below. I will try and keep the meeting under
== Logistics ==
- mailing list(s)
- IRC channel(s)
- Meeting frequency and times
- Trac instance?
== Next Steps ==
- Discussions around the WG governance charter
== Open Floor ==
I am Suchakra. I was have been previously involved in Design and
Ambassadors team for Fedora but took a break from community work for
sometime. But I am back now :) As I am involved in projects here with the
LTTng team in my lab, I would like to package some tools which are related
to their project. I would also like to co-maintain some packages which
Yannick (aka greenscientist) maintains 
Also, Yannick guided me for my first package . I would be happy if some
one is willing to review it or sponsor me eventually if I turn out to be a
good packager ;)
Apart from that I frequently come across nifty utilities from time to time
which I would like to package in my free time.
For F21, I plan to orphan the following X video drivers:
Effectively this means that the graphics team will be focusing on KMS
for graphics support, with vesa and fbdev available as last-ditch
fallbacks. If anyone is interested in taking on support for these
chips, they're welcome to, though we would encourage anyone doing so to
work towards KMS support and not merely do "keep it building"
One other detail: the intel driver currently has both UMS support for
the i810 chipset, and KMS support for everything newer. To be
consistent with the above changes I'll be dropping the i810 support,
which will then fall back to vesa. Again, if someone wants to own the
i810 support, let me know and we can add you as a comaintainer.
Do I get this right? Except for the better management with multiple
GPU's would that mean we can in future also have multiseat on a single
multihead GPU logind style (also seen here
https://bugs.freedesktop.org/show_bug.cgi?id=66501 ) ?
btw. would anyone mind have a look at
at least a help where I should look myself would be greatly appreciated.
Does anyone if somebody works on a driver for displaylink 3XXX
devices, I know from displaylink they are doing nothing, but if there
is someone in the community working on something.
I know that was a lot but I promise that was it for me today :)
Thanks in advance,