requirements for default apps
Dennis Gilmore
dennis at ausil.us
Mon Jan 18 20:33:40 UTC 2010
On Monday 18 January 2010 07:11:38 am Rex Dieter wrote:
> While at FUDCon back in Dec, it occurred to me to come up with
> 1. some specs and requirements to use as objective criteria when it comes
> to choices about default applications in fedora-kde.
> 2. general wishlist/todo items to make better
>
> https://fedoraproject.org/wiki/User:Rdieter/FUDCon_Toronto_KDE_F13_TODOs
>
> In general, these are items that are doable in the F13-development
> timeframe.
>
> I have a couple of ulterior motives when it comes to requirements and
> default applications:
> 1. It's inevitably a FAQ about "why did you include app <foo> instead of
> <bar>?"
> 2. I'm disgruntled about a couple of our current default choices (*cough*
> kbluetooth, kpackagekit *cough*), and would like to explore other
> possibilities
>
> So, please comment on what you consider to be core requirements when it
> comes to:
> 1. packagekit frontend/integration
not randomly crashing
> 2. networkmanager frontend
working openvpn/vpnc support
> 3. bluetooth device support
working pairing to all devices. right now to to pair a bluetooth headset i
have to log into gnome. pair then log back into kde. it works fine once
paired.
> 4. phonon backend
> 5. anything else you can think of...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.fedoraproject.org/pipermail/kde/attachments/20100118/0dd0db52/attachment.bin
More information about the kde
mailing list