On Fri, Oct 01, 2010 at 03:01:25PM -0400, Brian Pepple wrote:
On Fri, 2010-10-01 at 14:44 -0400, Bill Nottingham wrote:
> Brian Pepple (bpepple(a)fedoraproject.org) said:
> > > So, as I see it, there's three options here:
> > >
> > > * ship a fixed pino
> > > * ship something else
> > > * don't ship a twitter client by default
> > >
> > > Just wanted to start a thread to flag up the issue and prompt a
> > > discussion of an appropriate resolution. thanks!
> >
> > I'd vote for option #3 - don't ship a twitter client by default, and
put
> > something in the release notes regarding the available options for folks
> > that want to install one.
>
> I would just include gwibber, personally (assuming it fits.)
Yeah, if we want to ship one, gwibber is pretty much the only option,
since it's most likely too late to fix pino before F14 is released. The
big cons about gwibber, in my opinion is the fairly poor performance
I've experienced with it (tho I last used it about 2 months ago) and the
number of dependencies it would pull into the livecd.
Doesn't post-Beta seem too late to do this? Better to have people
simply use their browser I'd think.
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
Where open source multiplies:
http://opensource.com