Re: Updating the Logging Services Logo
We can make the interim logo the 🪵 (log emoji), possibly with four J’s next to it, until the new ASF logo is available. Speaking of logos, it may be a good time to design an updated logo for the project anyways. > On Jul 19, 2024, at 13:14, Christian Grobmeier wrote: > > Hello, > > following this blog post: > https://news.apache.org/foundation/entry/evolving-the-asf-brand > > I would like to propose to remove all feathers as here: > https://logging.apache.org/ > https://logging.apache.org/log4j/2.x/images/ls-logo.jpg > > And all sub-websites with simlar images. > > I would like to move on with this now, since it will take quite a while to > complete it anyway. > > Thoughts? > > Kind regards, > Christian
Re: JDK 23 RDP2 | Removal of the legacy COMPAT locale provider and more heads-up!
Well this is an interesting project! These sorts of improvements would help a lot with the startup time with Log4j I imagine, especially without doing the work of code generation and such to avoid any reflection at startup. > On Jul 22, 2024, at 00:30, David Delabassee > wrote: > > Welcome to the OpenJDK Quality Outreach summer update. > > JDK 23 is now in Rampdown Phase Two [1], its overall feature has been frozen > a few weeks ago. Per the JDK Release Process, we have now turned our focus to > P1 and P2 bugs, which can be fixed with approval [2]. Late enhancements are > still possible, with approval, but the bar is now extraordinarily high. That > also means that the JDK 23 Initial Release Candidates are fast approaching, > i.e., August 8th [3]! So, and in addition to testing your projects with the > latest JDK 23 early-access builds, it is now a good time to start testing > with the JDK 24 early-access builds. > > Make sure to also check the heads-up below as some are related to JDK 23 and > might have some impact, i.e., the first one being related to the eventual > removal of the Security Manager and the second one discusses the removal of > the legacy COMPAT locale provider. > > [1] https://mail.openjdk.org/pipermail/jdk-dev/2024-July/009252.html > [2] https://openjdk.org/jeps/3#rdp-2 > [3] https://openjdk.org/projects/jdk/23/ > > > ## Heads-up - JDK 23: Subject.getSubject API Requires Allowing the Security > Manager > > In JDK 17 and as announced in JEP 411 [4], the Security Manager was > deprecated for removal. As part of that change, several Security Manager > APIs, such as `AccessControlContext`, were deprecated for removal. The > `Subject::doAs` and `Subject::getSubject` APIs depend on Security Manager > related APIs even though they do not require Security Manager to be installed > to use them. > > As of JDK 23 [5], to help applications prepare for the eventual removal of > the Security Manager, subject authorization and the Subject APIs' behavior > depend on allowing the Security Manager: > - If the system property `java.security.manager` is set on the command line > to the empty string, a class name, or the value `allow` then there is no > behavior change compared to previous releases. > - If the system property `java.security.manager` is not set on the command > line or has been set on the command line to the value `disallow`, invoking > the `Subject.getSubject` method will throw `UnsupportedOperationException`. > > Yet, running an application with `-Djava.security.manager=allow` is a > temporary workaround to keep older code working. Maintainers of code using > `Subject.doAs` and `Subject.getSubject` are strongly encouraged to migrate it > with utmost priority to the replacement APIs, `Subject.callAs` and > `Subject.current`. Make sure to check [5] and [6] for additional details. > > The jdeprscan tool [7] scans a JAR file for usage of deprecated API elements > and is helpful to find code using these methods. Additionally, consider > migrating as soon as possible code that stores a `Subject` in an > `AccessControlContext` and invokes `AccessController.doPrivileged` with that > context. Such code will stop working when the Security Manager is removed. > > [4] https://openjdk.org/jeps/411 > [5] https://jdk.java.net/23/release-notes#b15 > [6] https://inside.java/2024/07/08/quality-heads-up/ > [7] https://dev.java/learn/jvm/tools/core/jdeprscan/ > > > ## Heads-up - JDK 23: Unicode / Removal of COMPAT Locale Provider > > ### A Quick History of Locale Data in the JDK > > Before the Unicode Consortium created the Common Locale Data Repository > (CLDR) in 2003 to manage locale data, the JDK had to provide its own > collection. It did so successfully and in JDK 8 supported about 160 locales. > To reduce maintenance effort, allow better interoperability between > platforms, and improve locale data quality, the JDK started to move towards > CLDR in 2014: > - JDK 8 comes with two locale data providers, which can be selected with the > system property java.locale.providers: > . JRE/COMPAT for the JDK’s legacy data collection (default) > . CLDR for the CLDR data > . a custom locale provider can be implemented > - JDK 9 picks CLDR by default > - JDK 21 issues a warning on JRE/COMPAT > > There are plenty of minor and a few notable differences between the legacy > data and CLDR - the recently rewritten JEP 252 [8] lists a few of them. > > ### Locale Data in JDK 23 > > JDK 23 [9] removes legacy locale data. As a consequence, setting > java.locale.providers to JRE or COMPAT has no effect. > > Projects that are still using legacy locale data are highly encouraged to > switch to CLDR as soon as possible. Where that is infeasible, two > alternatives remain: > - Create custom formatters with patterns that mimic the legacy behavior and > use them everywhere where locale-sensitive data is written or parsed. > - Implement a custom locale data prov
Re: Updating the Logging Services Logo
Btw, here is a more official blog post on this change: https://news.apache.org/foundation/entry/evolving-the-asf-brand On Mon, Jul 22, 2024, at 21:32, Christian Grobmeier wrote: > I am only asking to remove native american imagery as the feathers. > As I was involved in the branding process, I am confident we can remove them. > > We can update the 1980-style logo after the ASF logo was voted on. > Until then, we will be compliant almost immediately by dropping the feathers. > > I didn't expect any negative feedback for removing the feathers, but > please let me know if anyone is really opposed to it or if it is just a > general comment > > On Sat, Jul 20, 2024, at 12:01, Gary Gregory wrote: >> That sounds good. >> >> I'm not doing the work here but I would imagine that if I did I'd only want >> to do it once ;-) For my time, I'd either strip the images and call it >> done, or wait for new images. >> >> Gary >> >> On Sat, Jul 20, 2024, 1:45 AM Dominik Psenner wrote: >> >>> The blog post mentions the 7 oct 2024 as the deadline to be compliant. This >>> coincides with the day when the new marketing guidelines are unveiled. It >>> is probably impossible to implement this within hours. Therefore I propose >>> to ask Marketing for assistance/guiding/new marketing material right now in >>> the light of the upcoming deadline. It will take some time anyway until we >>> receive a feedback, maybe even several feedback loops. With this action we >>> can be well ahead of any upcoming deadline and do not have to rush for any >>> changes. And we may even be able to evaluate whether we want to remove OR >>> replace existing images. Primarily to avoid breaking links, but ultimately >>> also updating marketing material in a retrospective. >>> >>> On Fri, 19 Jul 2024, 21:41 Gary Gregory, wrote: >>> >>> > I think this is a bad idea because it is putting the cart before the >>> horse >>> > as we say in English. Let Apache come up with our new branding and then >>> use >>> > that. It seems all feathers of any kind are not allowed? >>> > >>> > Gary >>> > >>> > On Fri, Jul 19, 2024, 2:15 PM Christian Grobmeier >>> > wrote: >>> > >>> > > Hello, >>> > > >>> > > following this blog post: >>> > > https://news.apache.org/foundation/entry/evolving-the-asf-brand >>> > > >>> > > I would like to propose to remove all feathers as here: >>> > > https://logging.apache.org/ >>> > > https://logging.apache.org/log4j/2.x/images/ls-logo.jpg >>> > > >>> > > And all sub-websites with simlar images. >>> > > >>> > > I would like to move on with this now, since it will take quite a while >>> > to >>> > > complete it anyway. >>> > > >>> > > Thoughts? >>> > > >>> > > Kind regards, >>> > > Christian >>> > > >>> > >>>
Re: Updating the Logging Services Logo
I am only asking to remove native american imagery as the feathers. As I was involved in the branding process, I am confident we can remove them. We can update the 1980-style logo after the ASF logo was voted on. Until then, we will be compliant almost immediately by dropping the feathers. I didn't expect any negative feedback for removing the feathers, but please let me know if anyone is really opposed to it or if it is just a general comment On Sat, Jul 20, 2024, at 12:01, Gary Gregory wrote: > That sounds good. > > I'm not doing the work here but I would imagine that if I did I'd only want > to do it once ;-) For my time, I'd either strip the images and call it > done, or wait for new images. > > Gary > > On Sat, Jul 20, 2024, 1:45 AM Dominik Psenner wrote: > >> The blog post mentions the 7 oct 2024 as the deadline to be compliant. This >> coincides with the day when the new marketing guidelines are unveiled. It >> is probably impossible to implement this within hours. Therefore I propose >> to ask Marketing for assistance/guiding/new marketing material right now in >> the light of the upcoming deadline. It will take some time anyway until we >> receive a feedback, maybe even several feedback loops. With this action we >> can be well ahead of any upcoming deadline and do not have to rush for any >> changes. And we may even be able to evaluate whether we want to remove OR >> replace existing images. Primarily to avoid breaking links, but ultimately >> also updating marketing material in a retrospective. >> >> On Fri, 19 Jul 2024, 21:41 Gary Gregory, wrote: >> >> > I think this is a bad idea because it is putting the cart before the >> horse >> > as we say in English. Let Apache come up with our new branding and then >> use >> > that. It seems all feathers of any kind are not allowed? >> > >> > Gary >> > >> > On Fri, Jul 19, 2024, 2:15 PM Christian Grobmeier >> > wrote: >> > >> > > Hello, >> > > >> > > following this blog post: >> > > https://news.apache.org/foundation/entry/evolving-the-asf-brand >> > > >> > > I would like to propose to remove all feathers as here: >> > > https://logging.apache.org/ >> > > https://logging.apache.org/log4j/2.x/images/ls-logo.jpg >> > > >> > > And all sub-websites with simlar images. >> > > >> > > I would like to move on with this now, since it will take quite a while >> > to >> > > complete it anyway. >> > > >> > > Thoughts? >> > > >> > > Kind regards, >> > > Christian >> > > >> > >>
Re: Updating the Logging Services Logo
I find it peculiar that ALL feathers are now illegal. What about the feather of a Phoenix? On Mon, Jul 22, 2024, 3:37 PM Christian Grobmeier wrote: > I am only asking to remove native american imagery as the feathers. > As I was involved in the branding process, I am confident we can remove > them. > > We can update the 1980-style logo after the ASF logo was voted on. > Until then, we will be compliant almost immediately by dropping the > feathers. > > I didn't expect any negative feedback for removing the feathers, but > please let me know if anyone is really opposed to it or if it is just a > general comment > > On Sat, Jul 20, 2024, at 12:01, Gary Gregory wrote: > > That sounds good. > > > > I'm not doing the work here but I would imagine that if I did I'd only > want > > to do it once ;-) For my time, I'd either strip the images and call it > > done, or wait for new images. > > > > Gary > > > > On Sat, Jul 20, 2024, 1:45 AM Dominik Psenner > wrote: > > > >> The blog post mentions the 7 oct 2024 as the deadline to be compliant. > This > >> coincides with the day when the new marketing guidelines are unveiled. > It > >> is probably impossible to implement this within hours. Therefore I > propose > >> to ask Marketing for assistance/guiding/new marketing material right > now in > >> the light of the upcoming deadline. It will take some time anyway until > we > >> receive a feedback, maybe even several feedback loops. With this action > we > >> can be well ahead of any upcoming deadline and do not have to rush for > any > >> changes. And we may even be able to evaluate whether we want to remove > OR > >> replace existing images. Primarily to avoid breaking links, but > ultimately > >> also updating marketing material in a retrospective. > >> > >> On Fri, 19 Jul 2024, 21:41 Gary Gregory, > wrote: > >> > >> > I think this is a bad idea because it is putting the cart before the > >> horse > >> > as we say in English. Let Apache come up with our new branding and > then > >> use > >> > that. It seems all feathers of any kind are not allowed? > >> > > >> > Gary > >> > > >> > On Fri, Jul 19, 2024, 2:15 PM Christian Grobmeier < > grobme...@apache.org> > >> > wrote: > >> > > >> > > Hello, > >> > > > >> > > following this blog post: > >> > > https://news.apache.org/foundation/entry/evolving-the-asf-brand > >> > > > >> > > I would like to propose to remove all feathers as here: > >> > > https://logging.apache.org/ > >> > > https://logging.apache.org/log4j/2.x/images/ls-logo.jpg > >> > > > >> > > And all sub-websites with simlar images. > >> > > > >> > > I would like to move on with this now, since it will take quite a > while > >> > to > >> > > complete it anyway. > >> > > > >> > > Thoughts? > >> > > > >> > > Kind regards, > >> > > Christian > >> > > > >> > > >> >
Re: Updating the Logging Services Logo
What am I missing here? In looking at all the project sites none of our logos have a feather in them. Once the ASF provides a replacement logo we can simply replace it. Why are we talking about new logos? FWIW none of our projects existed in the 1980s so I don’t know where that comment came from. I believe it was Gary who won the contest for that 10 or so years ago. I still like it. Ralph > On Jul 22, 2024, at 12:58 PM, Gary Gregory wrote: > > I find it peculiar that ALL feathers are now illegal. What about the > feather of a Phoenix? > > On Mon, Jul 22, 2024, 3:37 PM Christian Grobmeier > wrote: > >> I am only asking to remove native american imagery as the feathers. >> As I was involved in the branding process, I am confident we can remove >> them. >> >> We can update the 1980-style logo after the ASF logo was voted on. >> Until then, we will be compliant almost immediately by dropping the >> feathers. >> >> I didn't expect any negative feedback for removing the feathers, but >> please let me know if anyone is really opposed to it or if it is just a >> general comment >> >> On Sat, Jul 20, 2024, at 12:01, Gary Gregory wrote: >>> That sounds good. >>> >>> I'm not doing the work here but I would imagine that if I did I'd only >> want >>> to do it once ;-) For my time, I'd either strip the images and call it >>> done, or wait for new images. >>> >>> Gary >>> >>> On Sat, Jul 20, 2024, 1:45 AM Dominik Psenner >> wrote: >>> The blog post mentions the 7 oct 2024 as the deadline to be compliant. >> This coincides with the day when the new marketing guidelines are unveiled. >> It is probably impossible to implement this within hours. Therefore I >> propose to ask Marketing for assistance/guiding/new marketing material right >> now in the light of the upcoming deadline. It will take some time anyway until >> we receive a feedback, maybe even several feedback loops. With this action >> we can be well ahead of any upcoming deadline and do not have to rush for >> any changes. And we may even be able to evaluate whether we want to remove >> OR replace existing images. Primarily to avoid breaking links, but >> ultimately also updating marketing material in a retrospective. On Fri, 19 Jul 2024, 21:41 Gary Gregory, >> wrote: > I think this is a bad idea because it is putting the cart before the horse > as we say in English. Let Apache come up with our new branding and >> then use > that. It seems all feathers of any kind are not allowed? > > Gary > > On Fri, Jul 19, 2024, 2:15 PM Christian Grobmeier < >> grobme...@apache.org> > wrote: > >> Hello, >> >> following this blog post: >> https://news.apache.org/foundation/entry/evolving-the-asf-brand >> >> I would like to propose to remove all feathers as here: >> https://logging.apache.org/ >> https://logging.apache.org/log4j/2.x/images/ls-logo.jpg >> >> And all sub-websites with simlar images. >> >> I would like to move on with this now, since it will take quite a >> while > to >> complete it anyway. >> >> Thoughts? >> >> Kind regards, >> Christian >> > >>
