10:13 a.m.
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.
--
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
10:26 a.m.
New subject: F14: what to do about pino / twitter
-----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/
iQIcBAEBAgAGBQJMqfIgAAoJEDbiLlqcYamx1qgQAIIyQwprX3PG8gRux1r2d/Fq
otJp4UyZ4eqe05YaTkULSxDsDZtTUs64Be0Qhkx5ZRPlM17eTZyCfAvcYaGSaxM+
WHWxL1t++lWsDbOlZuf4rHr1JH+T+8hGU21pJUwE+xlTBfSRsRtqLu+1mQOiEXLv
2H+plywOwgLl9DVjVcYALK/2rgy6L0I6o2z0TqaVUT3B2Jxt23P0XHZv/GNz2zFg
tcrguVUPd+FQEO5B3pwu6nD7sgXi21aTWV/H+/0+5D6j6VNV3Q8vcZvvjomcUscO
nqDiNbssKKoajRlZwpKAkOyb/VMJ6JgIqz5teCu3WPZuj43qCDlUuTsCDJCwOAxf
l65TSsEK7iFY111Uk2gkyYCwEV6lccDSSaUIiZh3DlBVSb/bT0CwIaM4cfGmK36U
HJyvYYIfZderK6mwU1MmbFWJnTBHZKgcppWJ0gqf6zBaV1JPHp2y7IoYAX7mwAUp
OY4Hu/inQS58FpGLt/9Y7hcjBNtqvwtvZ3rzOka12g42T8GjItyaCD7PM0nzb0Sm
RQm/H4NvTsq5Kv73893LZ6HEwHdqeHKmdz82zbYPYzXKFOb+ugtK6+VHQxQcZPCb
pqGK3MNgixWe4z/sNGQ7oUSrocRdSEdpl1x5Upq2Epy4iz8+aNnEwFZqBtMf4oBD
q6WQDHcO57iEypzI/DD5
=Sx0N
-----END PGP SIGNATURE-----
8:02 a.m.
New subject: F14: what to do about pino / twitter
On Mon, Oct 04, 2010 at 11:26:26AM -0400, Eric "Sparks" Christensen wrote:
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.
What is the final decision on this, so Docs can note the change? Pino
will be removed, but will Gwibber be replacing it or not?
--
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
8:20 a.m.
New subject: F14: what to do about pino / twitter
On Tue, 2010-10-05 at 09:02 -0400, Paul W. Frields wrote:
What is the final decision on this, so Docs can note the change?
Pino
will be removed, but will Gwibber be replacing it or not?
It seemed to me that there was more of a consensus to remove Pino, and
put something in the release notes explaining why it was removed
(similar to what Colin suggested earlier in the thread):
--
An application installed by default in Fedora 13, "pino" was removed
because the site no longer allows access.
For more information, see:
http://arstechnica.com/security/guides/2010/09/twitter-a-case-study-on-ho...
As a replacement, you can access previously supported sites
(identi.ca, Twitter, etc.) via their respective web sites, or by
installing one of several replacement applications such as "gwibber".
--
Later,
/B
--
Brian Pepple <bpepple(a)fedoraproject.org>
https://fedoraproject.org/wiki/User:Bpepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
11:03 a.m.
New subject: F14: what to do about pino / twitter
On Tue, 2010-10-05 at 09:02 -0400, Paul W. Frields wrote:
What is the final decision on this, so Docs can note the change? Pino
will be removed, but will Gwibber be replacing it or not?
I have just committed a change to comps to make pino optional in the
graphical-internet group, which should remove it from live media.
I haven't investigated gwibber as a replacement.
2:32 p.m.
New subject: F14: what to do about pino / twitter
On Tue, 2010-10-05 at 12:03 -0400, Matthias Clasen wrote:
On Tue, 2010-10-05 at 09:02 -0400, Paul W. Frields wrote:
>
> What is the final decision on this, so Docs can note the change? Pino
> will be removed, but will Gwibber be replacing it or not?
I have just committed a change to comps to make pino optional in the
graphical-internet group, which should remove it from live media.
I haven't investigated gwibber as a replacement.
I notice the main complaint about Gwibber is the deplist it pulls in
when installing it.
Current version 2.33 of Gwibber is a lot lighter on dependencies, and
supports OAuth for working with Twitter. Also works well with identi.ca,
as I use it to read/post to both.
gwibber-2.33.0-7.867bzr.fc13.noarch
A quick and unscientific 'yum deplist gwibber' gives this list (edited
somewhat for readability):
Finding dependencies:
package: gwibber.noarch 1:2.33.0-7.867bzr.fc13
dependency: python-feedparser >= 4.1
dependency: gnome-python2-gtkspell
dependency: python(abi) = 2.6
dependency: pywebkitgtk >= 1.0.1
dependency: python-kitchen
dependency: python-pycurl
dependency: gnome-python2-gnomekeyring
dependency: mx >= 3.0.0
dependency: python-mako >= 0.2.2
dependency: python-distutils-extra
dependency: python-imaging >= 1.1.6
dependency: notify-python >= 0.1.1
dependency: pyxdg >= 0.15
dependency: gnome-python2-libwnck
dependency: dbus-python >= 0.80.2
dependency: /usr/bin/python
dependency: gnome-python2-gconf >= 2.18.0
dependency: libsoup
dependency: python
dependency: python-simplejson >= 1.9.1
dependency: pygtk2 >= 2.10.4
dependency: python-oauth
The main noticeable difference, there are no couch or erlang
dependencies.
It may still not fit on a livecd image, but Gwibber has definitely
improved a lot with the work to support SQLite instead of the earlier
couchdb backend.
And the great work of the maintainer to get the updates into the repo
for us to use.
It also appears as 'Gwibber-Fedora' on Twitter, when making a post -
which is a nice little touch.
Having used Pino when F13 was released, and seeing the updates to
Gwibber, I can't see any reason why one wouldn't swap to Gwibber
(current UI is much better), but I don't see a problem with there being
no default application installed.
Just my few cents worth as a happy Gwibber user, and lurker on this
list.
Cheers,
Dagan
4958
days inactive
4959
days old
5 comments
5 participants
participants (5)
-
Brian Pepple -
Dagan McGregor -
Eric Christensen -
Matthias Clasen -
Paul W. Frields