F14: what to do about pino / twitter

[Matthias Clasen]

On Fri, 2010-10-01 at 16:44 -0400, Paul W. Frields wrote:
> On Fri, Oct 01, 2010 at 01:19:52PM -0700, Adam Williamson wrote:
> > On Fri, 2010-10-01 at 16:07 -0400, Paul W. Frields wrote:
> > 
> > > > 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.
> > 
> > well, we have to make *some* kind of post-beta change here, since as I
> > said the current situation blocks the release. I don't think subbing in
> > gwibber for pino is a particularly scary change, all we'd have to check
> > is if it goes over the size limit, and if it works, which is about half
> > an hour of effort.
> 
> Right, the uncertainty I have is really around the functionality of
> the new suggested default client, as opposed to "let's not do
> anything."  My preference would be a simple removal of pino for no
> other reason than least disturbance of the Force.

I agree that removing pino, together with a suitable note in the release
notes, is the safest route at this point.