requirements for default apps
Patrick Boutilier
boutilpj at ednet.ns.ca
Mon Jan 18 18:40:00 UTC 2010
On 01/18/2010 09:11 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
No comment, use yum.
> 2. networkmanager frontend
I like knetworkmanager
> 3. bluetooth device support
No comment.
> 4. phonon backend
Xine backend has always worked well for me.
> 5. anything else you can think of...
>
> Thanks.
>
> -- Rex
>
> _______________________________________________
> kde mailing list
> kde at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boutilpj.vcf
Type: text/x-vcard
Size: 286 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/kde/attachments/20100118/abb3b7a3/attachment.vcf
More information about the kde
mailing list