gt; > >>
> > >>
> > >>> -Original Message-
> > >>> From: toki [mailto:toki.kant...@gmail.com]
> > >>> Sent: Wednesday, August 31, 2016 11:30
> > >>> To: dev@openoffice.apache.org
> > >>> Sub
> -Original Message-
> From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de]
> Sent: Wednesday, August 31, 2016 22:04
> To: dev@openoffice.apache.org
> Subject: Re: Independent Entity to Develop and Further AOO
>
> Am 01.09.2016 um 00:59 schrieb Sim
gt; Sent: Wednesday, August 31, 2016 11:30
>>> To: dev@openoffice.apache.org
>>> Subject: Re: Independent Entity to Develop and Further AOO
>>>
>>> On 31/08/2016 16:26, Dennis E. Hamilton wrote:
>>>
>> I think that is the case because downstream producers, who g
On Wed, Aug 31, 2016 at 11:44 PM, Dennis E. Hamilton <
dennis.hamil...@acm.org> wrote:
>
>
> > -Original Message-
> > From: toki [mailto:toki.kant...@gmail.com]
> > Sent: Wednesday, August 31, 2016 11:30
> > To: dev@openoffice.apache.org
> >
> -Original Message-
> From: toki [mailto:toki.kant...@gmail.com]
> Sent: Wednesday, August 31, 2016 11:30
> To: dev@openoffice.apache.org
> Subject: Re: Independent Entity to Develop and Further AOO
>
> On 31/08/2016 16:26, Dennis E. Hamilton wrote:
>
&
;> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
>> Sent: Monday, July 11, 2016 14:04
>> To: dev@openoffice.apache.org
>> Subject: RE: Independent Entity to Develop and Further AOO
>>
>> There is a bit to discuss about how "The entity should ensure the
On 31/08/2016 16:26, Dennis E. Hamilton wrote:
> One can always create an independent entity. It hasn't happened. By now,
> the odds are clearly that it will not.
The Document Foundation is an independent entity, building upon the OOo
3.x code base.
> My considered opinion is that the
016 14:04
> To: dev@openoffice.apache.org
> Subject: RE: Independent Entity to Develop and Further AOO
>
> There is a bit to discuss about how "The entity should ensure they work
> on the AOO codebase using the ASF way" is workable or not. In
> particular, no such entit
This is exactly what I had in mind also.
>
> AN ALTERNATIVE APPROACH
>
> Another way to interact and support Apache OpenOffice in terms of
> collaborative contributions is as follows.
>
> 1. Establish a downstream producer, TeamX (for example), that provides
> releases of derivative software
There is a bit to discuss about how "The entity should ensure they work on the
AOO codebase using the ASF way" is workable or not. In particular, no such
entity can direct the project at Apache or otherwise effectively govern it.
More about that later.
There is another option, summarized
Hello,
> From: Suminda Dharmasena [mailto:sirinath19...@gmail.com]
> I am writing to see if the current AOO Dev team would like to
> create an
> independent entity which can:
>
>- Do trainings
>- Accept funds and have pay developers
>- Write commercial books / online tutorials
Every remaining dev / concerned user must get together a take an
initiative. Things rarely workout on their own.
On 11 July 2016 at 13:11, JZA wrote:
> Sounds good, there have been some intention of these in the past, not sure
> how open the community is right now to be
Sounds good, there have been some intention of these in the past, not sure
how open the community is right now to be honest. But is a good idea if
somehow there is some strong backing.
On Mon, Jul 11, 2016 at 2:23 AM, Suminda Dharmasena wrote:
> Hello,
>
> I am writing
13 matches
Mail list logo