Re: F14: what to do about pino / twitter

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/04/2010 11:13 AM, Paul W. Frields wrote:
> On Fri, Oct 01, 2010 at 11:48:07PM -0400, Matthias Clasen wrote:
>> 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.
>
> Adding the docs@ list to the cc so that they are aware of the need for
> a release note for this.  Docs folks, feel free to ask questions here
> on desktop@ as needed to figure out the best text.
>

So pino needs to be removed and replaced by Gwibber in the Release
Notes?  It will be tight but I think that change can be made.  I'd
appreciate someone to come with the text that needs to be used for this
replacement.

- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMqlwzAAoJEDbiLlqcYamxeUYP+wej+K6pL2PMpaFVETxEpiPA
aXw/D945w1+UW+yZYtW04/e/k+Ray84b1vZODSUx9GhOKbSzU0Gfdf9qW7OKS9ro
8qLO4B385kyZObBk+MjDpqlTxwWat0Eo1KvYcSxLsXyNGILTUm6OO0LMfh07H35g
znn90fi/+tNXYR6YB1uwUCxPsbbt+jTW5EP8vz/M9HCM7c2TdZKpYC6ER3erQhFH
HiQCQ3kgcHCbzT1GA5XqJB8wL6+mF6WC0gETuX33Z76I51vYCPZsalJ5JFlC5Bbh
xeqwReuBrNrOCzxIpiMnMN4YGHKK5PHXrkOVHbrGLJRUPXvYSLwIh5LjD7dn5I9z
/9mIYFx5aVRgS7+hsWiXR8JVPHmORyRDXlSglG4i6fvpTIDt8KgcCpzUaaKfBEzD
b480Rr1dmIk24N9DVinN3u/OtBAwMoLV5N+71r/B4iUGiSppxvpFWn+6fii9Xrjo
VdMZ82miIvmQKVNRXeWLPAC6NPrcUgK9E1Va4ICGcovW+kuuE962BzO+LLlqxHzG
fEKSEdKp/eaUULLu/8UTmxt0seSZoWyDpkATVldtxSiIvjpktJGhtDVlCoAx/ni9
tUQ7VVaQTZGHjust6OK6stQVmc+dXRVQmI488bDaS8yWB4QF8CXdRKGDGRHmprO6
mVNg/yDUB9eTjQDtvk0Y
=NG81
-----END PGP SIGNATURE-----
-- 
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/docs


[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Red Hat 9]     [Yosemite News]     [KDE Users]

  Powered by Linux