Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-23 Thread Matthias Seidel

Hi All,

Am 23.08.23 um 14:30 schrieb Aivaras Stepukonis:
For this channel of revenue to be more effective, it should be 
promoted on the AOO website, like other FOSS do: for instance, both 
GIMP and Inkscape have Donate links in their navigation bar.


We should ask Groovy, how they do it...

I am not even sure if we should use ASF mailing lists to discuss this topic.

However, I would be interested in more opinions, esp. from members of 
our PMC.


Regards,

   Matthias



--
Pagarbiai / Sincerely,
 Aivaras Stepukonis 

2023-08-23 12:35, Pedro Lino rašė:

Hi again

There is also an Europe based host

https://opencollective.com/europe/apply

which is based in Brussels and charges only 6% (as opposed to the 10% 
charged by the US based host linked in the previous message)


Best,
Pedro

On 08/23/2023 10:12 AM WEST Pedro 
Lino  wrote:


  Good morning all

I can push the plan a little further.

I think we should ask Open Collective to remove the OpenOffice 
project but meanwhile we can push on with "Friends of OpenOffice".


I already created my account but to create an Open Source Collective
https://opencollective.com/opensource
I believe it has to be one of the managers of the github project
https://github.com/apache/openoffice-project

I am a Contributor for the project, but I'm not sure that is enough?

Best,
Pedro


On 08/22/2023 8:26 PM WEST Arrigo Marchiori  wrote:

  Dear All,

On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote:


Hi Pedro,

Good find!

"OpenOffice" (exactly written like that) is a registered trademark 
of the

ASF.

I think we need to add that to our list of trademark violations?

+1

If we wanted to follow this way, we should probably establish a
"Friends of OpenOffice" collective as Groovy did.

[...]

[1]https://opencollective.com/friends-of-groovy#category-ABOUT

--
Arrigo

-
To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:dev-h...@openoffice.apache.org



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-23 Thread Aivaras Stepukonis
For this channel of revenue to be more effective, it should be promoted 
on the AOO website, like other FOSS do: for instance, both GIMP and 
Inkscape have Donate links in their navigation bar.


--
Pagarbiai / Sincerely,
 Aivaras Stepukonis 

2023-08-23 12:35, Pedro Lino rašė:

Hi again

There is also an Europe based host

https://opencollective.com/europe/apply

which is based in Brussels and charges only 6% (as opposed to the 10% charged 
by the US based host linked in the previous message)

Best,
Pedro


On 08/23/2023 10:12 AM WEST Pedro Lino  wrote:

  
Good morning all


I can push the plan a little further.

I think we should ask Open Collective to remove the OpenOffice project but meanwhile we 
can push on with "Friends of OpenOffice".

I already created my account but to create an Open Source Collective
https://opencollective.com/opensource
I believe it has to be one of the managers of the github project
https://github.com/apache/openoffice-project

I am a Contributor for the project, but I'm not sure that is enough?

Best,
Pedro


On 08/22/2023 8:26 PM WEST Arrigo Marchiori  wrote:

  
Dear All,


On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote:


Hi Pedro,

Good find!

"OpenOffice" (exactly written like that) is a registered trademark of the
ASF.

I think we need to add that to our list of trademark violations?

+1

If we wanted to follow this way, we should probably establish a
"Friends of OpenOffice" collective as Groovy did.

[...]

[1]https://opencollective.com/friends-of-groovy#category-ABOUT

--
Arrigo

-
To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:dev-h...@openoffice.apache.org


Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-23 Thread Pedro Lino
Hi again

There is also an Europe based host

https://opencollective.com/europe/apply

which is based in Brussels and charges only 6% (as opposed to the 10% charged 
by the US based host linked in the previous message)

Best,
Pedro

> On 08/23/2023 10:12 AM WEST Pedro Lino  wrote:
> 
>  
> Good morning all
> 
> I can push the plan a little further.
> 
> I think we should ask Open Collective to remove the OpenOffice project but 
> meanwhile we can push on with "Friends of OpenOffice".
> 
> I already created my account but to create an Open Source Collective
> https://opencollective.com/opensource
> I believe it has to be one of the managers of the github project
> https://github.com/apache/openoffice-project
> 
> I am a Contributor for the project, but I'm not sure that is enough?
> 
> Best,
> Pedro
> 
> > On 08/22/2023 8:26 PM WEST Arrigo Marchiori  wrote:
> > 
> >  
> > Dear All,
> > 
> > On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote:
> > 
> > > Hi Pedro,
> > > 
> > > Good find!
> > > 
> > > "OpenOffice" (exactly written like that) is a registered trademark of the
> > > ASF.
> > > 
> > > I think we need to add that to our list of trademark violations?
> > 
> > +1
> > 
> > If we wanted to follow this way, we should probably establish a
> > "Friends of OpenOffice" collective as Groovy did.
> > 
> > [...]
> > > > > [1] https://opencollective.com/friends-of-groovy#category-ABOUT
> > 
> > -- 
> > Arrigo
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-23 Thread Pedro Lino
Good morning all

I can push the plan a little further.

I think we should ask Open Collective to remove the OpenOffice project but 
meanwhile we can push on with "Friends of OpenOffice".

I already created my account but to create an Open Source Collective
https://opencollective.com/opensource
I believe it has to be one of the managers of the github project
https://github.com/apache/openoffice-project

I am a Contributor for the project, but I'm not sure that is enough?

Best,
Pedro

> On 08/22/2023 8:26 PM WEST Arrigo Marchiori  wrote:
> 
>  
> Dear All,
> 
> On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote:
> 
> > Hi Pedro,
> > 
> > Good find!
> > 
> > "OpenOffice" (exactly written like that) is a registered trademark of the
> > ASF.
> > 
> > I think we need to add that to our list of trademark violations?
> 
> +1
> 
> If we wanted to follow this way, we should probably establish a
> "Friends of OpenOffice" collective as Groovy did.
> 
> [...]
> > > > [1] https://opencollective.com/friends-of-groovy#category-ABOUT
> 
> -- 
> Arrigo
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-22 Thread Arrigo Marchiori
Dear All,

On Tue, Aug 22, 2023 at 05:23:50PM +0200, Matthias Seidel wrote:

> Hi Pedro,
> 
> Good find!
> 
> "OpenOffice" (exactly written like that) is a registered trademark of the
> ASF.
> 
> I think we need to add that to our list of trademark violations?

+1

If we wanted to follow this way, we should probably establish a
"Friends of OpenOffice" collective as Groovy did.

[...]
> > > [1] https://opencollective.com/friends-of-groovy#category-ABOUT

-- 
Arrigo

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-22 Thread Matthias Seidel

Hi Pedro,

Good find!

"OpenOffice" (exactly written like that) is a registered trademark of 
the ASF.


I think we need to add that to our list of trademark violations?

Regards,

   Matthias

Am 22.08.23 um 17:13 schrieb Pedro Lino:

I think it is a good idea. As I mentioned before, I'm available to contribute 
and implementing ODF 1.3 is a good goal.

However, there is already an Open Collective for OpenOffice, although I'm not 
sure if it refers to this Office suite...

https://opencollective.com/openoffice

Best,
Pedro


On 08/21/2023 4:08 PM WEST Matthias Seidel  wrote:

  
Hi Rony, All,


Am 20.08.23 um 12:47 schrieb Matthias Seidel:

Hi Rony,

Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache):

Has there been any work on this since? It seems that not supporting
1.3 causes troubles for AOO users who receive 1.3 documents.

Acknowledged.

But to my knowledge we have no volunteer working on that topic...

Personally, I think we need a payed developer for such a task.

We would need to collect money outside the ASF, maybe the way Groovy
does it [1] could be a solution.

Opinions?

Regards,

     Matthias

[1] https://opencollective.com/friends-of-groovy#category-ABOUT


Regards,

    Matthias


---rony


On 12.10.2021 00:00, Kay Schenk wrote:

Hello all --

If you'd like an opinion from someone who hasn't contributed to the
project in about 3 years...

I think using the filter API is the way to go. I remember getting
very curious about the filter API quite some time ago for something
I wanted to work on -- maybe generic XML docs, and realized this API
seemed very useful but I wasn't sure how it had been used. So, one
opinion for you in any case.

On 10/10/21 4:35 AM, Peter Kovacs wrote:

Hi all,

ODF 1.3 becomes more relevant soon. MS Office 2021 will support
only ODF 1.3

So I try to look into this, however our implementation on ODF
currently uses not the filter API but office Document model directly.

Should we stay with this architecture or should we use this
opportunity to migrate on a API driven filter?

What is your opinion on this?


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-22 Thread Pedro Lino
I think it is a good idea. As I mentioned before, I'm available to contribute 
and implementing ODF 1.3 is a good goal.

However, there is already an Open Collective for OpenOffice, although I'm not 
sure if it refers to this Office suite...

https://opencollective.com/openoffice

Best,
Pedro

> On 08/21/2023 4:08 PM WEST Matthias Seidel  wrote:
> 
>  
> Hi Rony, All,
> 
> Am 20.08.23 um 12:47 schrieb Matthias Seidel:
> > Hi Rony,
> >
> > Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache):
> >> Has there been any work on this since? It seems that not supporting 
> >> 1.3 causes troubles for AOO users who receive 1.3 documents.
> >
> > Acknowledged.
> >
> > But to my knowledge we have no volunteer working on that topic...
> 
> Personally, I think we need a payed developer for such a task.
> 
> We would need to collect money outside the ASF, maybe the way Groovy 
> does it [1] could be a solution.
> 
> Opinions?
> 
> Regards,
> 
>     Matthias
> 
> [1] https://opencollective.com/friends-of-groovy#category-ABOUT
> 
> >
> > Regards,
> >
> >    Matthias
> >
> >>
> >> ---rony
> >>
> >>
> >> On 12.10.2021 00:00, Kay Schenk wrote:
> >>> Hello all --
> >>>
> >>> If you'd like an opinion from someone who hasn't contributed to the 
> >>> project in about 3 years...
> >>>
> >>> I think using the filter API is the way to go. I remember getting 
> >>> very curious about the filter API quite some time ago for something 
> >>> I wanted to work on -- maybe generic XML docs, and realized this API 
> >>> seemed very useful but I wasn't sure how it had been used. So, one 
> >>> opinion for you in any case.
> >>>
> >>> On 10/10/21 4:35 AM, Peter Kovacs wrote:
>  Hi all,
> 
>  ODF 1.3 becomes more relevant soon. MS Office 2021 will support 
>  only ODF 1.3
> 
>  So I try to look into this, however our implementation on ODF 
>  currently uses not the filter API but office Document model directly.
> 
>  Should we stay with this architecture or should we use this 
>  opportunity to migrate on a API driven filter?
> 
>  What is your opinion on this?
> 
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-21 Thread Matthias Seidel

payed = paid ;-)

Am 21.08.23 um 17:08 schrieb Matthias Seidel:

Hi Rony, All,

Am 20.08.23 um 12:47 schrieb Matthias Seidel:

Hi Rony,

Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache):
Has there been any work on this since? It seems that not supporting 
1.3 causes troubles for AOO users who receive 1.3 documents.


Acknowledged.

But to my knowledge we have no volunteer working on that topic...


Personally, I think we need a payed developer for such a task.

We would need to collect money outside the ASF, maybe the way Groovy 
does it [1] could be a solution.


Opinions?

Regards,

   Matthias

[1] https://opencollective.com/friends-of-groovy#category-ABOUT



Regards,

   Matthias



---rony


On 12.10.2021 00:00, Kay Schenk wrote:

Hello all --

If you'd like an opinion from someone who hasn't contributed to the 
project in about 3 years...


I think using the filter API is the way to go. I remember getting 
very curious about the filter API quite some time ago for something 
I wanted to work on -- maybe generic XML docs, and realized this 
API seemed very useful but I wasn't sure how it had been used. So, 
one opinion for you in any case.


On 10/10/21 4:35 AM, Peter Kovacs wrote:

Hi all,

ODF 1.3 becomes more relevant soon. MS Office 2021 will support 
only ODF 1.3


So I try to look into this, however our implementation on ODF 
currently uses not the filter API but office Document model directly.


Should we stay with this architecture or should we use this 
opportunity to migrate on a API driven filter?


What is your opinion on this?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-21 Thread Matthias Seidel

Hi Rony, All,

Am 20.08.23 um 12:47 schrieb Matthias Seidel:

Hi Rony,

Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache):
Has there been any work on this since? It seems that not supporting 
1.3 causes troubles for AOO users who receive 1.3 documents.


Acknowledged.

But to my knowledge we have no volunteer working on that topic...


Personally, I think we need a payed developer for such a task.

We would need to collect money outside the ASF, maybe the way Groovy 
does it [1] could be a solution.


Opinions?

Regards,

   Matthias

[1] https://opencollective.com/friends-of-groovy#category-ABOUT



Regards,

   Matthias



---rony


On 12.10.2021 00:00, Kay Schenk wrote:

Hello all --

If you'd like an opinion from someone who hasn't contributed to the 
project in about 3 years...


I think using the filter API is the way to go. I remember getting 
very curious about the filter API quite some time ago for something 
I wanted to work on -- maybe generic XML docs, and realized this API 
seemed very useful but I wasn't sure how it had been used. So, one 
opinion for you in any case.


On 10/10/21 4:35 AM, Peter Kovacs wrote:

Hi all,

ODF 1.3 becomes more relevant soon. MS Office 2021 will support 
only ODF 1.3


So I try to look into this, however our implementation on ODF 
currently uses not the filter API but office Document model directly.


Should we stay with this architecture or should we use this 
opportunity to migrate on a API driven filter?


What is your opinion on this?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-20 Thread Matthias Seidel

Hi Rony,

Am 20.08.23 um 12:40 schrieb Rony G. Flatscher (Apache):
Has there been any work on this since? It seems that not supporting 
1.3 causes troubles for AOO users who receive 1.3 documents.


Acknowledged.

But to my knowledge we have no volunteer working on that topic...

Regards,

   Matthias



---rony


On 12.10.2021 00:00, Kay Schenk wrote:

Hello all --

If you'd like an opinion from someone who hasn't contributed to the 
project in about 3 years...


I think using the filter API is the way to go. I remember getting 
very curious about the filter API quite some time ago for something I 
wanted to work on -- maybe generic XML docs, and realized this API 
seemed very useful but I wasn't sure how it had been used. So, one 
opinion for you in any case.


On 10/10/21 4:35 AM, Peter Kovacs wrote:

Hi all,

ODF 1.3 becomes more relevant soon. MS Office 2021 will support only 
ODF 1.3


So I try to look into this, however our implementation on ODF 
currently uses not the filter API but office Document model directly.


Should we stay with this architecture or should we use this 
opportunity to migrate on a API driven filter?


What is your opinion on this?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [Discussion] ODF 1.3 filter implementation strategy

2023-08-20 Thread Rony G. Flatscher (Apache)
Has there been any work on this since? It seems that not supporting 1.3 causes troubles for AOO 
users who receive 1.3 documents.


---rony


On 12.10.2021 00:00, Kay Schenk wrote:

Hello all --

If you'd like an opinion from someone who hasn't contributed to the project in 
about 3 years...

I think using the filter API is the way to go. I remember getting very curious about the filter 
API quite some time ago for something I wanted to work on -- maybe generic XML docs, and realized 
this API seemed very useful but I wasn't sure how it had been used. So, one opinion for you in any 
case.


On 10/10/21 4:35 AM, Peter Kovacs wrote:

Hi all,

ODF 1.3 becomes more relevant soon. MS Office 2021 will support only ODF 1.3

So I try to look into this, however our implementation on ODF currently uses not the filter API 
but office Document model directly.


Should we stay with this architecture or should we use this opportunity to migrate on a API 
driven filter?


What is your opinion on this?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] ODF 1.3 filter implementation strategy

2021-10-11 Thread Kay Schenk

Hello all --

If you'd like an opinion from someone who hasn't contributed to the 
project in about 3 years...


I think using the filter API is the way to go. I remember getting very 
curious about the filter API quite some time ago for something I wanted 
to work on -- maybe generic XML docs, and realized this API seemed very 
useful but I wasn't sure how it had been used. So, one opinion for you 
in any case.


On 10/10/21 4:35 AM, Peter Kovacs wrote:

Hi all,

ODF 1.3 becomes more relevant soon. MS Office 2021 will support only 
ODF 1.3


So I try to look into this, however our implementation on ODF 
currently uses not the filter API but office Document model directly.


Should we stay with this architecture or should we use this 
opportunity to migrate on a API driven filter?


What is your opinion on this?


--
---
"Do what you can, with what you've got,
  where you are."
  -- Theodore Roosevelt
MzK