Re: About 20th anniversary plans

[Keith N. McKenna]

On 9/7/2020 5:52 AM, Pedro Lino wrote:
> Hi Jörg
> 
>> On 09/07/2020 9:24 AM Jörg Schmidt  wrote:
> 
>> I had recently suggested replacing the yellow (at 20 years) with a color 
>> that would be more recognizable.
>>
>> I mentioned orange as an alternative color, but I can't say if this would be 
>> the best choice.
>> Maybe you should just use the red-brown of the Apache lettering?
> 
> I agree. Maybe some colour from the Apache feather
> https://upload.wikimedia.org/wikipedia/commons/7/7e/Apache_Feather_Logo.svg
>  
>> Unfortunately it is not so easy to create an example directly because "20 
>> years" contains antialiasing.
> 
> Yes, this requires that the original author does that (or shares a vector 
> version of the original)
> 
> This raises another question: in some versions of the AOO logos there is a TM 
> and in others a R. Which is correct?
> 
> https://commons.wikimedia.org/wiki/File:Apache_OpenOffice_logo_and_wordmark_(2014).svg
> 
> Regards,
> Pedro
> 
Pedro

® is the preferred as OpenOffice is now a registered TM in the United States

Regards
Keith




signature.asc
Description: OpenPGP digital signature

Re: About 20th anniversary plans

[Pedro Lino]

Hi Czeslaw, all

> Pedro's proposal
> seems to me sort of "embarras de richesses" (in French: "confusing
> abundance").

I warned in advance that I am not a designer. In any case, without a vector 
version there is little that can be done...

> "Open-source for 20 years" does the job properly.

Fine by me. Can I move forward with this option?
Any votes against?

Regards,
Pedro

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

Re: About 20th anniversary plans

[Czesław Wolański]

Hi all,

@ Matthias
> While I like the graphic from the French list
> I don't see it
> in the context of AOO dialogs.

+1

Additional remark:
As I already pointed out (dev@ subject "OpenOffice 20 years event", 29
August)
I like the idea of combining the "O/0" character and the seagull logo.
Image provided by the French volunteer is a self-standing entity and
Pedro's proposal
seems to me sort of "embarras de richesses" (in French: "confusing
abundance").
I see the bigger seagull logo on the one side of "Apache/OpenOffice 4" and
its reduced copy on the other.
That doesn't look very appealing and IMHO strains one's eyes - no matter
what colour "20 years" would take.

"Open-source for 20 years" does the job properly.

Regards,

Czesław Wolański



пн, 7 сент. 2020 г. в 16:12, Matthias Seidel :

> Hi Pedro,
>
> Am 07.09.20 um 11:52 schrieb Pedro Lino:
> > Hi Jörg
> >
> >> On 09/07/2020 9:24 AM Jörg Schmidt  wrote:
> >> I had recently suggested replacing the yellow (at 20 years) with a
> color that would be more recognizable.
> >>
> >> I mentioned orange as an alternative color, but I can't say if this
> would be the best choice.
> >> Maybe you should just use the red-brown of the Apache lettering?
> > I agree. Maybe some colour from the Apache feather
> >
> https://upload.wikimedia.org/wikipedia/commons/7/7e/Apache_Feather_Logo.svg
> >
> >> Unfortunately it is not so easy to create an example directly because
> "20 years" contains antialiasing.
> > Yes, this requires that the original author does that (or shares a
> vector version of the original)
> >
> > This raises another question: in some versions of the AOO logos there is
> a TM and in others a R. Which is correct?
>
> There is only one source for the logos:
>
> https://www.apache.org/logos/?#openoffice
>
> As you might have noticed graphics were changed in the source and on the
> homepages recently.
> But as only one person (guess who?) does this it can take a while until
> everything is up to date.
>
> >
> >
> https://commons.wikimedia.org/wiki/File:Apache_OpenOffice_logo_and_wordmark_(2014).svg
>
> This should be updated. The artwork is the same, except for the
> registered trademark.
>
> Regards,
>
> Matthias
>
> >
> > Regards,
> > Pedro
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>

Re: AOO418 cherry picks

[Matthias Seidel]

Hi Jim,

Am 07.09.20 um 15:14 schrieb Jim Jagielski:
> For 4.1.x we have always supported 10.7 as the min macOS version. Changing 
> supported versions via a patch release does not seem right. IMO, we pull the 
> rug out from under people when bumping patch revs.

That's one of the reasons why it was backed out of 4.1.6 and why I
wanted you to have a look.

Maybe the patch works also with 10.7?

Regards,

   Matthias

>
>> On Sep 4, 2020, at 9:18 AM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim, Don,
>>
>> Am 28.08.20 um 15:17 schrieb Jim Jagielski:
>>> Let's commit and work after pushed.
>> We should try
>>
>> https://bz.apache.org/ooo/show_bug.cgi?id=127887
>>
>> again for 4.1.8.
>>
>> Regards,
>>
>>Matthias
>>
 On Aug 27, 2020, at 2:02 PM, Don Lewis  wrote:

 On 27 Aug, Matthias Seidel wrote:
> Am 27.08.20 um 19:32 schrieb Matthias Seidel:
>> Hi Don,
>>
>> Am 24.08.20 um 04:04 schrieb Don Lewis:
>>> I've got a bunch of cherry picks that I'm planning to merge into AOO418.
>>> There are two categories:
>>> * Fixes from the FreeBSD port that have been upstreamed to the trunk
>>>   and AOO42X branches, but I'm still carrying around in the FreeBSD
>>>   port of 4.1.7.
>>>
>>> * Updates of a bunch of the bundled dependencies.  These have been
>>>   updated in AOO42X and trunk for a while, but haven't been merged to
>>>   AOO418.  The FreeBSD port mostly usees the system versions of these.
>>>
>>> I'd like to revisit:
>>>
>>> commit 7a3beb322b74df1b6c96e03605837df34781c68f
>>> Author: Matthias Seidel 
>>> Date:   Thu Oct 11 16:53:51 2018 +
>>>
>>> Rollback to Rev. 1843088 due to build errors.
>>>
>>> git-svn-id: 
>>> https://svn.apache.org/repos/asf/openoffice/branches/AOO416@18438571 
>>> 13f79535-47bb-0310-9956-ffa450edef68
>>>
>>> I'm still using the patch for the FreeBSD port.  Without it, a build
>>> with --enable-odk will fail with Java 8 or newer.  I don't see how it
>>> would break the build since the changes are just to structured comments
>>> that are parsed to generate the documentation in the ODK.  When this was
>>> backed out, I thought the reason was that building with a newer version
>>> of the JDK would prevent runtime detection of older versions of the JDK.
>>> So far asa I know, that's not a problem with AOO42X and trunk, which
>>> have the changes.
>> If I remember it right the Rollback included:
>>
>> - Issue 127887 - update bundled redland/raptor/rasqal
>> - Issue 127875 - fix a loop that visits all objects on a page so that
>> all objects get visited
>> - Issue 127874 - fix bad potential invalid subscript bug when using
>> Microsoft Uniscribe text layout API
>>
>> We should commit all of the above again, one after the other.
>>
> Correcting myself: I had re-committed Issue 127874 and Issue 127875 to
> 4.1.6 after the Rollback.
>
> So Issue 127887 could now be committed to 4.1.8.
> We should discuss the change in configure.in regarding MacOS with Jim.
 I'm working on a fairly large update to the bundled software.  I should
 be able to create a pull request in a day or so.  127887 will be
 included.  I'll test it on Linux and Windows.  I'll take a stab at the
 MacOS bits, but won't be able to test it.

> Regards,
>
>   Matthias
>
>> "Issue 127876 - unbreak ODK build with Java 8" should be double
>> checked because of the known issue with Java 7 JRE.
 Since 127876 only changes comments in our Java code, it should not
 affect detection.  Without this change, is the Java 7 JRE detected if we
 build with Java 8?


 -
 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: About 20th anniversary plans

[Matthias Seidel]

Hi Pedro,

Am 07.09.20 um 11:52 schrieb Pedro Lino:
> Hi Jörg
>
>> On 09/07/2020 9:24 AM Jörg Schmidt  wrote:
>> I had recently suggested replacing the yellow (at 20 years) with a color 
>> that would be more recognizable.
>>
>> I mentioned orange as an alternative color, but I can't say if this would be 
>> the best choice.
>> Maybe you should just use the red-brown of the Apache lettering?
> I agree. Maybe some colour from the Apache feather
> https://upload.wikimedia.org/wikipedia/commons/7/7e/Apache_Feather_Logo.svg
>  
>> Unfortunately it is not so easy to create an example directly because "20 
>> years" contains antialiasing.
> Yes, this requires that the original author does that (or shares a vector 
> version of the original)
>
> This raises another question: in some versions of the AOO logos there is a TM 
> and in others a R. Which is correct?

There is only one source for the logos:

https://www.apache.org/logos/?#openoffice

As you might have noticed graphics were changed in the source and on the
homepages recently.
But as only one person (guess who?) does this it can take a while until
everything is up to date.

>
> https://commons.wikimedia.org/wiki/File:Apache_OpenOffice_logo_and_wordmark_(2014).svg

This should be updated. The artwork is the same, except for the
registered trademark.

Regards,

Matthias

>
> Regards,
> Pedro
>
> -
> 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: About 20th anniversary plans

[Matthias Seidel]

Hi Peter,

Am 07.09.20 um 01:47 schrieb Peter Kovacs:
> I am +1, if not Matthias is the one who does everything.

Over the last years I've created templates for most of our graphics, so
there is no technical reason that prevents doing another one.

BUT:

 - Some weeks ago, I proposed a graphic for the About dialog and got
minimal feedback.

 - Now Pedro likes to add the Intro graphic.

 - Maybe next week someone wants to add the StartCenter (which I am
totally against)

So, basically we must first come to a conclusion and then start to work...

>
> It should be a community thing. We got some pictures from the french
> List.
>
> If i.e. Pedro can create a patch to add them in, I think it is great.

While I like the graphic from the French list I don't see it in the
context of AOO dialogs.

Have we ever got a reply or a vector based version?

>
> I am kind of negative if in the End Matthias has to do it all alone.
>
> We have to get more people get involved in such stuff.

There were always only a handful (literally) of people doing all the
work for a release.

It would be great if that situation could be improved.

Regards,

   Matthias

>
>
> I hope I could make myself clear on the constraints I see ;)
>
>
> All the Best
>
> Peter
>
> Am 07.09.20 um 00:16 schrieb Matthias Seidel:
>> Hi Pedro,
>>
>> Am 07.09.20 um 00:00 schrieb Pedro Lino:
>>> Hi Matthias
>>>
 On 09/06/2020 5:44 PM Matthias Seidel 
 wrote:
 Well, I didn't create a graphic for the Intro because I really
 think it
 is not needed.

 If others want one, this should be discussed.
>>>   Then let's discuss :)
>>> I think that for a matter of consistency both screens should be kept
>>> similar. Is it not what is done for a Test build or a Developer build?
>> I do it for my personal Test Builds and we did it for Dev Builds. But
>> there is no rule for it.
>>
>> AOO 4.1.8 being a "normal" build (just happening around the 20th
>> anniversary) only needs a modified About graphic (IMO).
>>
>> But I will step back, since I would be the one to do the work (as I
>> already did) and wait what others think of it.
>>
>> So, which would be the proper folder and why don't you crate a Pull
>> Request? ;-)
> I would say main/default_images/introabout?
 Yes, but that would override our "original" graphic.
>>> But only for branch 4.1.8 which will not be further developed?
>> Of course we can restore the old graphic in branch 419 when it is
>> branched off 418.
>>
>> But I will not decide that, since it is easier for me to specify it in
>> configure.
>>
>>> I assume this does not affect the other branches. If it does, then
>>> it should be somewhere else
>>>  
 A Pull Request cannot break stuff. It is easy to do on GitHub.
>>> Pull? Shouldn't it be Push? I'm not sure if I won't break stuff and
>>> it's less than a month for release...
>> Git calls it Pull requests: https://github.com/apache/openoffice/pulls
>>
>> Branch 418 is almost 12 month old. And it will be released when it is
>> "ready"
>>
>> Regards,
>>
>>     Matthias
>>
>>> Regards
>>> Pedro
>>>
>>> -
>>> 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: AOO418 cherry picks

[Jim Jagielski]

For 4.1.x we have always supported 10.7 as the min macOS version. Changing 
supported versions via a patch release does not seem right. IMO, we pull the 
rug out from under people when bumping patch revs.

> On Sep 4, 2020, at 9:18 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim, Don,
> 
> Am 28.08.20 um 15:17 schrieb Jim Jagielski:
>> Let's commit and work after pushed.
> 
> We should try
> 
> https://bz.apache.org/ooo/show_bug.cgi?id=127887
> 
> again for 4.1.8.
> 
> Regards,
> 
>Matthias
> 
>> 
>>> On Aug 27, 2020, at 2:02 PM, Don Lewis  wrote:
>>> 
>>> On 27 Aug, Matthias Seidel wrote:
 Am 27.08.20 um 19:32 schrieb Matthias Seidel:
> Hi Don,
> 
> Am 24.08.20 um 04:04 schrieb Don Lewis:
>> I've got a bunch of cherry picks that I'm planning to merge into AOO418.
>> There are two categories:
>> * Fixes from the FreeBSD port that have been upstreamed to the trunk
>>   and AOO42X branches, but I'm still carrying around in the FreeBSD
>>   port of 4.1.7.
>> 
>> * Updates of a bunch of the bundled dependencies.  These have been
>>   updated in AOO42X and trunk for a while, but haven't been merged to
>>   AOO418.  The FreeBSD port mostly usees the system versions of these.
>> 
>> I'd like to revisit:
>> 
>> commit 7a3beb322b74df1b6c96e03605837df34781c68f
>> Author: Matthias Seidel 
>> Date:   Thu Oct 11 16:53:51 2018 +
>> 
>> Rollback to Rev. 1843088 due to build errors.
>> 
>> git-svn-id: 
>> https://svn.apache.org/repos/asf/openoffice/branches/AOO416@18438571 
>> 13f79535-47bb-0310-9956-ffa450edef68
>> 
>> I'm still using the patch for the FreeBSD port.  Without it, a build
>> with --enable-odk will fail with Java 8 or newer.  I don't see how it
>> would break the build since the changes are just to structured comments
>> that are parsed to generate the documentation in the ODK.  When this was
>> backed out, I thought the reason was that building with a newer version
>> of the JDK would prevent runtime detection of older versions of the JDK.
>> So far asa I know, that's not a problem with AOO42X and trunk, which
>> have the changes.
> If I remember it right the Rollback included:
> 
> - Issue 127887 - update bundled redland/raptor/rasqal
> - Issue 127875 - fix a loop that visits all objects on a page so that
> all objects get visited
> - Issue 127874 - fix bad potential invalid subscript bug when using
> Microsoft Uniscribe text layout API
> 
> We should commit all of the above again, one after the other.
> 
 Correcting myself: I had re-committed Issue 127874 and Issue 127875 to
 4.1.6 after the Rollback.
 
 So Issue 127887 could now be committed to 4.1.8.
 We should discuss the change in configure.in regarding MacOS with Jim.
>>> I'm working on a fairly large update to the bundled software.  I should
>>> be able to create a pull request in a day or so.  127887 will be
>>> included.  I'll test it on Linux and Windows.  I'll take a stab at the
>>> MacOS bits, but won't be able to test it.
>>> 
 Regards,
 
   Matthias
 
> "Issue 127876 - unbreak ODK build with Java 8" should be double
> checked because of the known issue with Java 7 JRE.
>>> Since 127876 only changes comments in our Java code, it should not
>>> affect detection.  Without this change, is the Java 7 JRE detected if we
>>> build with Java 8?
>>> 
>>> 
>>> -
>>> 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: About 20th anniversary plans

[Jörg Schmidt]

Hello Pedro,

> -Original Message-
> From: Pedro Lino [mailto:pedro.l...@mailbox.org] 
> Sent: Monday, September 07, 2020 11:53 AM
> To: dev@openoffice.apache.org
> Subject: RE: About 20th anniversary plans
> 
> Hi Jörg
> 
> > On 09/07/2020 9:24 AM Jörg Schmidt  wrote:
> 
> > I had recently suggested replacing the yellow (at 20 years) 
> with a color that would be more recognizable.
> > 
> > I mentioned orange as an alternative color, but I can't say 
> if this would be the best choice.
> > Maybe you should just use the red-brown of the Apache lettering?
> 
> I agree. Maybe some colour from the Apache feather
> https://upload.wikimedia.org/wikipedia/commons/7/7e/Apache_Fea
> ther_Logo.svg

Yes. 

Basically, all colors of the feather are suitable, my personal taste would be 
the 'upper' colors from about #F69923 to #D43831.



greetings,
Jörg


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

RE: About 20th anniversary plans

[Pedro Lino]

Hi Jörg

> On 09/07/2020 9:24 AM Jörg Schmidt  wrote:

> I had recently suggested replacing the yellow (at 20 years) with a color that 
> would be more recognizable.
> 
> I mentioned orange as an alternative color, but I can't say if this would be 
> the best choice.
> Maybe you should just use the red-brown of the Apache lettering?

I agree. Maybe some colour from the Apache feather
https://upload.wikimedia.org/wikipedia/commons/7/7e/Apache_Feather_Logo.svg
 
> Unfortunately it is not so easy to create an example directly because "20 
> years" contains antialiasing.

Yes, this requires that the original author does that (or shares a vector 
version of the original)

This raises another question: in some versions of the AOO logos there is a TM 
and in others a R. Which is correct?

https://commons.wikimedia.org/wiki/File:Apache_OpenOffice_logo_and_wordmark_(2014).svg

Regards,
Pedro

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

RE: About 20th anniversary plans

[Jörg Schmidt]

Hello,  

> -Original Message-
> From: Pedro Lino [mailto:pedro.l...@mailbox.org] 
> Sent: Monday, September 07, 2020 9:05 AM
> To: dev@openoffice.apache.org
> Subject: Re: About 20th anniversary plans
> 
> Hi Peter, all
> 
> I'm not a designer but can hack stuff using Gimp :)
> 
> I adapted the idea submitted by the french volunteer (we can 
> not use the images as they are because they must have the 
> exact same pixel size to fit in the dialogs)
> 
> In the Intro screen the white space below the word OpenOffice 
> can not be used because it is where the progress bar is 
> displayed during loading.
> 
> https://imgur.com/a/ZNYjwDq
> 
> Comments/suggestions?

I had recently suggested replacing the yellow (at 20 years) with a color that 
would be more recognizable.

I mentioned orange as an alternative color, but I can't say if this would be 
the best choice.
Maybe you should just use the red-brown of the Apache lettering?

Unfortunately it is not so easy to create an example directly because "20 
years" contains antialiasing.



greetings,
Jörg


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

Re: About 20th anniversary plans

[Pedro Lino]

Hi Peter, all

I'm not a designer but can hack stuff using Gimp :)

I adapted the idea submitted by the french volunteer (we can not use the images 
as they are because they must have the exact same pixel size to fit in the 
dialogs)

In the Intro screen the white space below the word OpenOffice can not be used 
because it is where the progress bar is displayed during loading.

https://imgur.com/a/ZNYjwDq

Comments/suggestions?


> On 09/07/2020 12:47 AM Peter Kovacs  wrote:
> 
>  
> I am +1, if not Matthias is the one who does everything.
> 
> It should be a community thing. We got some pictures from the french List.
> 
> If i.e. Pedro can create a patch to add them in, I think it is great.
> 
> I am kind of negative if in the End Matthias has to do it all alone.
> 
> We have to get more people get involved in such stuff.
> 
> 
> I hope I could make myself clear on the constraints I see ;)
> 
> 
> All the Best
> 
> Peter
> 
> Am 07.09.20 um 00:16 schrieb Matthias Seidel:
> > Hi Pedro,
> >
> > Am 07.09.20 um 00:00 schrieb Pedro Lino:
> >> Hi Matthias
> >>
> >>> On 09/06/2020 5:44 PM Matthias Seidel  wrote:
> >>> Well, I didn't create a graphic for the Intro because I really think it
> >>> is not needed.
> >>>
> >>> If others want one, this should be discussed.
> >>   
> >> Then let's discuss :)
> >> I think that for a matter of consistency both screens should be kept 
> >> similar. Is it not what is done for a Test build or a Developer build?
> > I do it for my personal Test Builds and we did it for Dev Builds. But
> > there is no rule for it.
> >
> > AOO 4.1.8 being a "normal" build (just happening around the 20th
> > anniversary) only needs a modified About graphic (IMO).
> >
> > But I will step back, since I would be the one to do the work (as I
> > already did) and wait what others think of it.
> >
> > So, which would be the proper folder and why don't you crate a Pull
> > Request? ;-)
>  I would say main/default_images/introabout?
> >>> Yes, but that would override our "original" graphic.
> >> But only for branch 4.1.8 which will not be further developed?
> > Of course we can restore the old graphic in branch 419 when it is
> > branched off 418.
> >
> > But I will not decide that, since it is easier for me to specify it in
> > configure.
> >
> >> I assume this does not affect the other branches. If it does, then it 
> >> should be somewhere else
> >>   
> >>> A Pull Request cannot break stuff. It is easy to do on GitHub.
> >> Pull? Shouldn't it be Push? I'm not sure if I won't break stuff and it's 
> >> less than a month for release...
> > Git calls it Pull requests: https://github.com/apache/openoffice/pulls
> >
> > Branch 418 is almost 12 month old. And it will be released when it is
> > "ready"
> >
> > Regards,
> >
> >     Matthias
> >
> >> Regards
> >> Pedro
> >>
> >> -
> >> 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