Re: Security (was bugzilla)

Since this is getting into specifics of security issues, I think it should be moved to the security list. On 5/22/2017 1:22 AM, Peter Kovacs wrote: Well, I see only 2 attack path for us. Ssh interface and the macro/scripting interface. SSH or web we need to update libs, so wee need a flexible

Re:Bugzilla information

It's a very good point Peter. Diversity in the office software space is good. And you're right; People aren't going to stop using AOO if the PMC decided to stop releasing new versions. Please note to others I'm not some TDF/LO stooge. I actually use MS Office for work and OnlyOffice for

Re: Bugzilla information

I disagree. You have to make your point. Not to object will only strengthen other position because your view remains unheard. The best weapon against haters is love and dignity. Am 22. Mai 2017 18:32:39 MESZ schrieb esh1907 : >The way to treat such people: >1. Change our

Security (was bugzilla)

Well, I see only 2 attack path for us. Ssh interface and the macro/scripting interface. SSH or web we need to update libs, so wee need a flexible way to reference both. Scripting I don't know, not my area of expertise. Anyone with insights? Please note I start splitting because we get more

Re: Fwd: Problem with Open Office before and after installing new update

So we have 3 ) critical bugs? 1) # issue 2) spell checker 3) I don't have in mind but Hagar mentioned it in his bugzilla thread. :( I whish I could start immediately to find solution for them. Am 21. Mai 2017 22:17:02 MESZ schrieb Dave Fisher : >For what it's worth >

Re: Fwd: Problem with Open Office before and after installing new update

On Mon, 22 May 2017 09:57:31 +0200 Peter Kovacs wrote: > Thanks for the sum up. > > Still I think we should find a solution. > So i adf backup at the start of editing session to the list. > > Is there a bug for this? There certainly ought be, but I cannot point to

Re: Bugzilla

Honestly I agree with Dave. It does not help us. I think for now let Libre and Apache go different ways. That is the outcome of the past. Am 21. Mai 2017 17:02:43 MESZ schrieb Dave Fisher : > > >Sent from my iPhone > >> On May 21, 2017, at 10:44 AM, Jörg Schmidt

Release Cycle( was Re: Bugzilla)

I agree we are round about at 1 release per year. We should target reliable 2 releases per year cycle. Important releases as needed. I think that cycle would be tough for us. Am 21. Mai 2017 16:34:31 MESZ schrieb "Jörg Schmidt" : > >> From: Dave Fisher

Project organisation (was Re: Bugzilla)

I do not disagree, Raphael. However I believe in making one step after another. First step is building up a core community. (Maybe it is there I just to blind to see it) If we have that we found a community organisation And stabilized our current situation, we can make the next step. We

Re: Bugzilla information

The other offices are doing well. And competition is awesomely great. You have forgotten to mention some competitors that also put some awesome offers on the table. I like the diversity this is causing. I have joined in September last year and do not plan to swap project soon. I joined the

Re: Fwd: Problem with Open Office before and after installing new update

On Mon, 22 May 2017 08:23:54 +0200 Peter Kovacs wrote: > So we have 3 ) critical bugs? > > 1) # issue > 2) spell checker > 3) I don't have in mind but Hagar mentioned it in his bugzilla thread. The # issue seems caused usually by overhasty close down of the computer,

Re: Fwd: Problem with Open Office before and after installing new update

Thanks for the sum up. Still I think we should find a solution. So i adf backup at the start of editing session to the list. Is there a bug for this? Am 22. Mai 2017 09:43:52 MESZ schrieb Rory O'Farrell : >On Mon, 22 May 2017 08:23:54 +0200 >Peter Kovacs

Re: Bugzilla

> From: Dave Fisher [mailto:dave2w...@comcast.net] > > And the TDF should apologize for the FUD of the past and > dissociate oneself from the people who are today FUD! Public > and clear! > > If you care about this then you should discuss on the TDF > lists as an individual. This is not my

Re: Bugzilla information

The way to treat such people: 1. Change our software license so any code sharing between us and them becomes impossible. 2. Arrange legally for the brand name they so desire to be forever unavailable even if our project will be terminated in the future. 3. Ignore them. On Sun, May 21, 2017 at