RE: AbiWord 3.next release plans

Hi Hub, everyone,

Sorry for not responding sooner. In general Hub I agree with your plans for abiword-3.1 however I would vote against depreciating the abicollab plugin. The abicollab.net service is up and running though I don’t know how much longer Marc Maurer will maintain it.

I didn't realise the gnutls API had changed. I don’t know if I'll get the time to fit it for GNUtls > 3.4 but I'd like to see if get it running again.

Thanks for keeping the fires burning for abiword Hub. I'll see what I can do. Sam, please feel free to jump in and fit it if you can.

Cheers

Martin

-----Original Message-----
From: owner-abiword-dev@abisource.com [mailto:owner-abiword-dev@abisource.com] On Behalf Of Hubert Figuière
Sent: Monday, 23 November 2015 8:24 AM
To: Sam P. <sam@sam.today>
Cc: Sugar-dev Devel <sugar-devel@lists.sugarlabs.org>; abiword-dev@abisource.com
Subject: Re: AbiWord 3.next release plans


On 21/11/15 04:51 PM, Sam P. wrote:
> Hello Hubert,
>
> (Sorry about the reply formatting, I saw this post on the archive and
> I suppose this is how to reply to things)
>
>> Proposal:
>> -I'd like to deprecate the collab plugin: for AbiCollab, we don't
>> have
> the server. For the other protocol, we can't maintain them.
> Deprecation would go by only allowing explicitely building it. I
> already had to disable the code based on GNUtls api breakage.
>
> I contribute downstream to Sugar and we use AbiWord in sugar because
> of the awesome AbiCollab plugin. Specifically, we use the sugar
> backend (which uses dbus), and then manage all the dbus over telepathy
> things from our side.
>
> It seems to work great, so I suppose that is a testimony to your good
> maintainership. If it's needed, I'm interested in getting involved to
> make sure that this plugin stays on.

For starter, the plugins is now disabled if you have gnutls >= 3.4 since it has been using deprecated TLS APIs that are now gone. See revision 35119
   http://bugzilla.abisource.com/show_bug.cgi?id=13742

Also I'm in the process of cleaning up some internals in AbiWord (mostly getting rid of legacy containers) which mean that I might have to fix plugins at the same time. I can't build AbiCollab anymore so it might not get done and the plugin might stay broken.

Now if you want to submit patches to keep things alive, please, do.
Several options can be evaluated. Ditching some backends, for example.


Hub
Received on Mon Nov 23 00:27:07 2015