>> On Wednesday 17 August 2011 06:07:16 Timothy Pearson wrote: >> >>> And you will guarantee that the upstream LibreOffice project continues >>> to >>> build an unmaintained plugin just for us? >> >> Once it is not included then fork it. There is no problem right now. >> > > I think it would be better to get a new plugin into LibreOffice before the > KDE3 one is dropped, as this will avoid the whole unpleasantness that goes > along with trying to re-add a dropped component (and many times prevents > the new component from being included in the upstream project). It would > also minimize the impact to users, who theoretically could end up without > Trinity integration for at least one LibreOffice release cycle. > > Tim > Thinking about this some more, I wonder if we can take ownership of the old KDE3 plugin and just rename it/patch it upstream. That would probably be easiest and produce a minimal amount of work for both us and LibreOffce. The downside, of course, is that KDE3 support for versions <= 3.5.10 would be removed. I will dig around in the build system a bit as I have time and see what can be done. Tim