Re: [Discuss][VOTE] Move Chainsaw to dormant status
On Thu, Sep 21, 2023, at 19:38, Ralph Goers wrote: > At this point in time I will abstain from voting. As far as I am > concerned only 1 vote counts - Scott’s. He has steadfastly asked that > the project not be retired and until he positively says he will no > longer maintain it I am not willing to override that. Agreed. I don’t think this discussion is already due for a vote. Even when we consider it dormant, we should consider to fix the problem. Unlike log4j1, chainsaw was never considered EOL. I would like to hear from Scott but also Robert, who did the last commits. Christian > I should also note that AFAIK we have never “archived” a dormant > project. We simply change its status on the web site. That said, a > read-only repo does make some sense for a dormant project I guess. > > Ralph > >> On Sep 21, 2023, at 10:00 AM, Volkan Yazıcı wrote: >> >> As earlier discussions[1] indicate, Chainsaw has been lacking on >> maintenance and no PMC member stepped up to perform necessary chores. >> This is a vote to retire the Chainsaw by means of >> >> - Move it to the list of dormant projects[2] >> - Making it clear in its README and website that the project is not >> maintained anymore >> - Archive its repository[3] >> >> Please cast your votes on this mailing list. >> >> [ ] +1, retire the project >> [ ] -1, don't retire, because... >> >> This vote is open for 72 hours and will pass unless getting a net >> negative vote count. All votes are welcome and we encourage everyone, >> but only the Logging Services PMC votes are officially counted. At >> least 3 +1 votes and more positive than negative votes are required. >> >> [1] https://lists.apache.org/thread/fsykp5hxr9z0c2h85snnhnj2pq553t6q >> [2] https://logging.apache.org/dormant.html >> [3] https://github.com/apache/chainsaw
Re: [VOTE] Move Chainsaw to dormant status
-1 While changes may be infrequent, the project is still useful and works well. I'll continue to contribute to maintenance. Scott On Thu, Sep 21, 2023, 10:00 AM Volkan Yazıcı wrote: > As earlier discussions[1] indicate, Chainsaw has been lacking on > maintenance and no PMC member stepped up to perform necessary chores. > This is a vote to retire the Chainsaw by means of > > - Move it to the list of dormant projects[2] > - Making it clear in its README and website that the project is not > maintained anymore > - Archive its repository[3] > > Please cast your votes on this mailing list. > > [ ] +1, retire the project > [ ] -1, don't retire, because... > > This vote is open for 72 hours and will pass unless getting a net > negative vote count. All votes are welcome and we encourage everyone, > but only the Logging Services PMC votes are officially counted. At > least 3 +1 votes and more positive than negative votes are required. > > [1] https://lists.apache.org/thread/fsykp5hxr9z0c2h85snnhnj2pq553t6q > [2] https://logging.apache.org/dormant.html > [3] https://github.com/apache/chainsaw >
Re: `chainsaw` vs `logging-chainsaw`
On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote: > I think #1 is a mirror of SVN( > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a > mirror of the gitbox repository. Looks like the SVN mirror is outdated. Can we safely remove it? If there are no objections, I will create a ticket with infra Christian > -Robert > > On Thu, Sep 21, 2023 at 1:59 PM Volkan Yazıcı wrote: > >> Does anybody know the difference between these two repositories[1][2] >> and why the mirroring does not work? [1] hasn't been updated since >> 2014. >> >> [1] https://github.com/apache/chainsaw >> [2] https://github.com/apache/logging-chainsaw >>
Re: `chainsaw` vs `logging-chainsaw`
An svn mirror should be useless. Would you please do a sanity check? Is the last commit from repo in our git repo? TY, Gary On Fri, Sep 22, 2023, 1:50 PM Christian Grobmeier wrote: > > On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote: > > I think #1 is a mirror of SVN( > > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a > > mirror of the gitbox repository. > > Looks like the SVN mirror is outdated. Can we safely remove it? > If there are no objections, I will create a ticket with infra > > Christian > > > -Robert > > > > On Thu, Sep 21, 2023 at 1:59 PM Volkan Yazıcı wrote: > > > >> Does anybody know the difference between these two repositories[1][2] > >> and why the mirroring does not work? [1] hasn't been updated since > >> 2014. > >> > >> [1] https://github.com/apache/chainsaw > >> [2] https://github.com/apache/logging-chainsaw > >> >
Re: `chainsaw` vs `logging-chainsaw`
On Fri, Sep 22, 2023, at 20:16, Gary Gregory wrote: > An svn mirror should be useless. Would you please do a sanity check? Is the > last commit from repo in our git repo? Yes, the Git repo: Updated on Jul 19, 2023 1,134 commits SVN: Updated on Jul 8, 2022, 934 commits > > TY, > Gary > > On Fri, Sep 22, 2023, 1:50 PM Christian Grobmeier wrote: > >> >> On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote: >> > I think #1 is a mirror of SVN( >> > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a >> > mirror of the gitbox repository. >> >> Looks like the SVN mirror is outdated. Can we safely remove it? >> If there are no objections, I will create a ticket with infra >> >> Christian >> >> > -Robert >> > >> > On Thu, Sep 21, 2023 at 1:59 PM Volkan Yazıcı wrote: >> > >> >> Does anybody know the difference between these two repositories[1][2] >> >> and why the mirroring does not work? [1] hasn't been updated since >> >> 2014. >> >> >> >> [1] https://github.com/apache/chainsaw >> >> [2] https://github.com/apache/logging-chainsaw >> >> >>
[chainsaw] Developing for Chainsaw
Hi, I tried to start Chainsaw from the official build, using Maven (mvn package) and even starting it using the LogUI main class. All methods failed for various reasons. What is the best method to get Chainsaw started, when trying to fix an issue? Kind regards, Christian When running using IntelliJ: 20:33:04.814 [AWT-EventQueue-0] INFO org.apache.log4j.chainsaw.LogUI - SecurityManager is now: null 20:33:17.611 [AWT-EventQueue-0] WARN org.apache.log4j.chainsaw.help.HelpManager - Could not find any local JavaDocs, you might want to consider running 'ant javadoc'. The release version will be able to access Javadocs from the Apache website. 20:33:26.420 [AWT-EventQueue-0] DEBUG org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel - Can't find new GTK L&F, might be Windows, or (ApplicationPreferenceModelPanel.java:127) at org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel.createTreeModel(ApplicationPreferenceModelPanel.java:86) at org.apache.log4j.chainsaw.AbstractPreferencePanel.initComponents(AbstractPreferencePanel.java:67) at org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel.(ApplicationPreferenceModelPanel.java:57) at org.apache.log4j.chainsaw.LogUI.initGUI(LogUI.java:406) at org.apache.log4j.chainsaw.LogUI.activateViewer(LogUI.java:528) at java.desktop/java.awt.event.InvocationEvent.dispatch$$$capture(InvocationEvent.java:318) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716) at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) -- The Apache Software Foundation V.P., Data Privacy
Migrating the landing page
Hello, the current landing page: https://logging.apache.org/ is done with JBake. We have rather complicated instructions on how to re-generate the landing page: https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites The Infra team recommends Pelican or Jekyll to create these kinds of pages. I have in-depth knowledge of Jekyll and would like to propose migrating the current landing page to Jekyll. The benefits: - autodeploy of our changes - great support of blogging (I'd like to create one) - easy handling and supported by Infra - writing content in Markdown I am aware that we have a discussion open on how to do documentation in the future. I would still like to migrate the page asap and - if deemed necessary - touch it again later. So far, I will leave all design/content intact until migrated, and come back with additional changes (as the blog) after migration to be discussed separately. If there are no objections, I will start with this move sometime next week. Thanks! Christian -- The Apache Software Foundation V.P., Data Privacy
Re: `chainsaw` vs `logging-chainsaw`
Any repos we own that don’t start with logging- are almost guaranteed to be SVN mirrors. I think we’ve migrated everything by now. > On Sep 21, 2023, at 1:00 PM, Volkan Yazıcı wrote: > > Does anybody know the difference between these two repositories[1][2] > and why the mirroring does not work? [1] hasn't been updated since > 2014. > > [1] https://github.com/apache/chainsaw > [2] https://github.com/apache/logging-chainsaw
Re: [chainsaw] Developing for Chainsaw
What version of Java are you using here? Chances are that you’ll need to use Java 8 for this. > On Sep 22, 2023, at 1:34 PM, Christian Grobmeier wrote: > > Hi, > > I tried to start Chainsaw from the official build, using Maven (mvn package) > and even starting it using the LogUI main class. > > All methods failed for various reasons. > > What is the best method to get Chainsaw started, when trying to fix an issue? > > Kind regards, > Christian > > When running using IntelliJ: > > 20:33:04.814 [AWT-EventQueue-0] INFO org.apache.log4j.chainsaw.LogUI - > SecurityManager is now: null > 20:33:17.611 [AWT-EventQueue-0] WARN > org.apache.log4j.chainsaw.help.HelpManager - Could not find any local > JavaDocs, you might want to consider running 'ant javadoc'. The release > version will be able to access Javadocs from the Apache website. > 20:33:26.420 [AWT-EventQueue-0] DEBUG > org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel - Can't find new > GTK L&F, might be Windows, or java.util.NoSuchElementException: Key 'statusBar' does not map to an existing > object! > at > org.apache.commons.configuration2.AbstractConfiguration.throwMissingPropertyException(AbstractConfiguration.java:1902) > at > org.apache.commons.configuration2.AbstractConfiguration.checkNonNullValue(AbstractConfiguration.java:1889) > at > org.apache.commons.configuration2.AbstractConfiguration.getBoolean(AbstractConfiguration.java:1165) > at > org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel$VisualsPrefPanel.updateModel(ApplicationPreferenceModelPanel.java:280) > at > org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel$VisualsPrefPanel.(ApplicationPreferenceModelPanel.java:127) > at > org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel.createTreeModel(ApplicationPreferenceModelPanel.java:86) > at > org.apache.log4j.chainsaw.AbstractPreferencePanel.initComponents(AbstractPreferencePanel.java:67) > at > org.apache.log4j.chainsaw.ApplicationPreferenceModelPanel.(ApplicationPreferenceModelPanel.java:57) > at org.apache.log4j.chainsaw.LogUI.initGUI(LogUI.java:406) > at org.apache.log4j.chainsaw.LogUI.activateViewer(LogUI.java:528) > at > java.desktop/java.awt.event.InvocationEvent.dispatch$$$capture(InvocationEvent.java:318) > at > java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java) > at > java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722) > at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716) > at > java.base/java.security.AccessController.doPrivileged(AccessController.java:399) > at > java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) > at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741) > at > java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) > at > java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) > at > java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) > at > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) > at > java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at > java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) > > > > -- > The Apache Software Foundation > V.P., Data Privacy
Re: Migrating the landing page
I like this idea. I’m less experienced with any of those tools, but I do use Jekyll for my own blog and some random GitHub page websites. > On Sep 22, 2023, at 1:47 PM, Christian Grobmeier wrote: > > Hello, > > the current landing page: > https://logging.apache.org/ > > is done with JBake. We have rather complicated instructions on how to > re-generate the landing page: > https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites > > The Infra team recommends Pelican or Jekyll to create these kinds of pages. I > have in-depth knowledge of Jekyll and would like to propose migrating the > current landing page to Jekyll. > > The benefits: > > - autodeploy of our changes > - great support of blogging (I'd like to create one) > - easy handling and supported by Infra > - writing content in Markdown > > I am aware that we have a discussion open on how to do documentation in the > future. I would still like to migrate the page asap and - if deemed > necessary - touch it again later. > > So far, I will leave all design/content intact until migrated, and come back > with additional changes (as the blog) after migration to be discussed > separately. > > If there are no objections, I will start with this move sometime next week. > > Thanks! > Christian > > -- > The Apache Software Foundation > V.P., Data Privacy
Re: Migrating the landing page
Personally, I hate all these tools. I picked JBake simply because I could figure out how to run it with a simple Maven command. I really don’t see how you can make it any simpler by changing the tooling. If you look at the instructions they are all git commands except for “mvn install”. The current web site supports markdown and asciidoc. I am not in favor of changing the tooling for the sake of changing the tooling. I am in favor of changing the tooling if there is some major tangible benefit. I have always wanted to use tooling that would let us edit the pages in a GUI editor similar to like Wix or Squarespace do. I despise having to write things in Markdown or Asiciidoc and then run a tool so I can preview what it is going to look like. In other words, I want the ease of editing and maintaining the web site to drive the tooling decision, not the other way around. Ralph > On Sep 22, 2023, at 11:47 AM, Christian Grobmeier > wrote: > > Hello, > > the current landing page: > https://logging.apache.org/ > > is done with JBake. We have rather complicated instructions on how to > re-generate the landing page: > https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites > > The Infra team recommends Pelican or Jekyll to create these kinds of pages. I > have in-depth knowledge of Jekyll and would like to propose migrating the > current landing page to Jekyll. > > The benefits: > > - autodeploy of our changes > - great support of blogging (I'd like to create one) > - easy handling and supported by Infra > - writing content in Markdown > > I am aware that we have a discussion open on how to do documentation in the > future. I would still like to migrate the page asap and - if deemed > necessary - touch it again later. > > So far, I will leave all design/content intact until migrated, and come back > with additional changes (as the blog) after migration to be discussed > separately. > > If there are no objections, I will start with this move sometime next week. > > Thanks! > Christian > > -- > The Apache Software Foundation > V.P., Data Privacy
Re: `chainsaw` vs `logging-chainsaw`
On Fri, Sep 22, 2023 at 2:28 PM Christian Grobmeier wrote: > > > > On Fri, Sep 22, 2023, at 20:16, Gary Gregory wrote: > > An svn mirror should be useless. Would you please do a sanity check? Is the > > last commit from repo in our git repo? > > Yes, the Git repo: Updated on Jul 19, 2023 1,134 commits > SVN: Updated on Jul 8, 2022, 934 commits TY for checking Christian. Gary > > > > > TY, > > Gary > > > > On Fri, Sep 22, 2023, 1:50 PM Christian Grobmeier wrote: > > > >> > >> On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote: > >> > I think #1 is a mirror of SVN( > >> > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a > >> > mirror of the gitbox repository. > >> > >> Looks like the SVN mirror is outdated. Can we safely remove it? > >> If there are no objections, I will create a ticket with infra > >> > >> Christian > >> > >> > -Robert > >> > > >> > On Thu, Sep 21, 2023 at 1:59 PM Volkan Yazıcı wrote: > >> > > >> >> Does anybody know the difference between these two repositories[1][2] > >> >> and why the mirroring does not work? [1] hasn't been updated since > >> >> 2014. > >> >> > >> >> [1] https://github.com/apache/chainsaw > >> >> [2] https://github.com/apache/logging-chainsaw > >> >> > >>
Re: Migrating the landing page
On Fri, Sep 22, 2023, at 22:08, Ralph Goers wrote: > Personally, I hate all these tools. I picked JBake simply because I > could figure out how to run it with a simple Maven command. > > I really don’t see how you can make it any simpler by changing the > tooling. If you look at the instructions they are all git commands > except for “mvn install”. > > The current web site supports markdown and asciidoc. > > I am not in favor of changing the tooling for the sake of changing the > tooling. I am in favor of changing the tooling if there is some major > tangible benefit. I have always wanted to use tooling that would let us > edit the pages in a GUI editor similar to like Wix or Squarespace do. I > despise having to write things in Markdown or Asiciidoc and then run a > tool so I can preview what it is going to look like. > > In other words, I want the ease of editing and maintaining the web site > to drive the tooling decision, not the other way around. Currently, there are 10 steps listed for deploying the website. I do "git commit && push" Currently, we have to install JBake In my scenario, I use Docker. As an example, for the privacy website to check: docker run --rm -p 4000:4000 --mount type=bind,src=$PWD,dst=/root/build --mount type=volume,dst=/root/build/node_modules -it apache/privacy_apache_org serve --watch --incremental There are significant benefits in this, such as speed of deployment, support of infra, etc pp. I don't see any reason to stick with JBake. I understand you don't like static site generators, but in this case, a less frequently updated website, I see benefits: easy blogging support and ASF support. Additionally, Docker support. There is also GUI support for Jekyll and Hugo, but I don't like it. There is none for JBake to my knowledge. I an not changing the tooling because I like Jekyll better, but because it is a standard, I have autodeploy tools ready and it generally is better understood than JBake. Kind regards, Christian > > Ralph > >> On Sep 22, 2023, at 11:47 AM, Christian Grobmeier >> wrote: >> >> Hello, >> >> the current landing page: >> https://logging.apache.org/ >> >> is done with JBake. We have rather complicated instructions on how to >> re-generate the landing page: >> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites >> >> The Infra team recommends Pelican or Jekyll to create these kinds of pages. >> I have in-depth knowledge of Jekyll and would like to propose migrating the >> current landing page to Jekyll. >> >> The benefits: >> >> - autodeploy of our changes >> - great support of blogging (I'd like to create one) >> - easy handling and supported by Infra >> - writing content in Markdown >> >> I am aware that we have a discussion open on how to do documentation in the >> future. I would still like to migrate the page asap and - if deemed >> necessary - touch it again later. >> >> So far, I will leave all design/content intact until migrated, and come back >> with additional changes (as the blog) after migration to be discussed >> separately. >> >> If there are no objections, I will start with this move sometime next week. >> >> Thanks! >> Christian >> >> -- >> The Apache Software Foundation >> V.P., Data Privacy
Re: Migrating the landing page
You have to be kidding me. I now need to use Docker to build the web site? And that is somehow simpler? Ralph > On Sep 22, 2023, at 2:03 PM, Christian Grobmeier wrote: > > > >> On Fri, Sep 22, 2023, at 22:08, Ralph Goers wrote: >> Personally, I hate all these tools. I picked JBake simply because I >> could figure out how to run it with a simple Maven command. >> >> I really don’t see how you can make it any simpler by changing the >> tooling. If you look at the instructions they are all git commands >> except for “mvn install”. >> >> The current web site supports markdown and asciidoc. >> >> I am not in favor of changing the tooling for the sake of changing the >> tooling. I am in favor of changing the tooling if there is some major >> tangible benefit. I have always wanted to use tooling that would let us >> edit the pages in a GUI editor similar to like Wix or Squarespace do. I >> despise having to write things in Markdown or Asiciidoc and then run a >> tool so I can preview what it is going to look like. >> >> In other words, I want the ease of editing and maintaining the web site >> to drive the tooling decision, not the other way around. > > Currently, there are 10 steps listed for deploying the website. > I do "git commit && push" > > Currently, we have to install JBake > In my scenario, I use Docker. > > As an example, for the privacy website to check: > docker run --rm -p 4000:4000 --mount type=bind,src=$PWD,dst=/root/build > --mount type=volume,dst=/root/build/node_modules -it > apache/privacy_apache_org serve --watch --incremental > > There are significant benefits in this, such as speed of deployment, support > of infra, etc pp. > I don't see any reason to stick with JBake. > > I understand you don't like static site generators, but in this case, a less > frequently updated website, I see benefits: easy blogging support and ASF > support. Additionally, Docker support. > > There is also GUI support for Jekyll and Hugo, but I don't like it. There is > none for JBake to my knowledge. > > I an not changing the tooling because I like Jekyll better, but because it is > a standard, I have autodeploy tools ready and it generally is better > understood than JBake. > > Kind regards, > Christian > > >> >> Ralph >> On Sep 22, 2023, at 11:47 AM, Christian Grobmeier wrote: >>> >>> Hello, >>> >>> the current landing page: >>> https://logging.apache.org/ >>> >>> is done with JBake. We have rather complicated instructions on how to >>> re-generate the landing page: >>> https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites >>> >>> The Infra team recommends Pelican or Jekyll to create these kinds of pages. >>> I have in-depth knowledge of Jekyll and would like to propose migrating the >>> current landing page to Jekyll. >>> >>> The benefits: >>> >>> - autodeploy of our changes >>> - great support of blogging (I'd like to create one) >>> - easy handling and supported by Infra >>> - writing content in Markdown >>> >>> I am aware that we have a discussion open on how to do documentation in the >>> future. I would still like to migrate the page asap and - if deemed >>> necessary - touch it again later. >>> >>> So far, I will leave all design/content intact until migrated, and come >>> back with additional changes (as the blog) after migration to be discussed >>> separately. >>> >>> If there are no objections, I will start with this move sometime next week. >>> >>> Thanks! >>> Christian >>> >>> -- >>> The Apache Software Foundation >>> V.P., Data Privacy
Re: Migrating the landing page
Hmm, and how much disk space do you need for that image? Gary On Fri, Sep 22, 2023, 8:30 PM Apache wrote: > You have to be kidding me. I now need to use Docker to build the web site? > And that is somehow simpler? > > Ralph > > > On Sep 22, 2023, at 2:03 PM, Christian Grobmeier > wrote: > > > > > > > >> On Fri, Sep 22, 2023, at 22:08, Ralph Goers wrote: > >> Personally, I hate all these tools. I picked JBake simply because I > >> could figure out how to run it with a simple Maven command. > >> > >> I really don’t see how you can make it any simpler by changing the > >> tooling. If you look at the instructions they are all git commands > >> except for “mvn install”. > >> > >> The current web site supports markdown and asciidoc. > >> > >> I am not in favor of changing the tooling for the sake of changing the > >> tooling. I am in favor of changing the tooling if there is some major > >> tangible benefit. I have always wanted to use tooling that would let us > >> edit the pages in a GUI editor similar to like Wix or Squarespace do. I > >> despise having to write things in Markdown or Asiciidoc and then run a > >> tool so I can preview what it is going to look like. > >> > >> In other words, I want the ease of editing and maintaining the web site > >> to drive the tooling decision, not the other way around. > > > > Currently, there are 10 steps listed for deploying the website. > > I do "git commit && push" > > > > Currently, we have to install JBake > > In my scenario, I use Docker. > > > > As an example, for the privacy website to check: > > docker run --rm -p 4000:4000 --mount type=bind,src=$PWD,dst=/root/build > --mount type=volume,dst=/root/build/node_modules -it > apache/privacy_apache_org serve --watch --incremental > > > > There are significant benefits in this, such as speed of deployment, > support of infra, etc pp. > > I don't see any reason to stick with JBake. > > > > I understand you don't like static site generators, but in this case, a > less frequently updated website, I see benefits: easy blogging support and > ASF support. Additionally, Docker support. > > > > There is also GUI support for Jekyll and Hugo, but I don't like it. > There is none for JBake to my knowledge. > > > > I an not changing the tooling because I like Jekyll better, but because > it is a standard, I have autodeploy tools ready and it generally is better > understood than JBake. > > > > Kind regards, > > Christian > > > > > >> > >> Ralph > >> > On Sep 22, 2023, at 11:47 AM, Christian Grobmeier < > grobme...@apache.org> wrote: > >>> > >>> Hello, > >>> > >>> the current landing page: > >>> https://logging.apache.org/ > >>> > >>> is done with JBake. We have rather complicated instructions on how to > re-generate the landing page: > >>> > https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Sites > >>> > >>> The Infra team recommends Pelican or Jekyll to create these kinds of > pages. I have in-depth knowledge of Jekyll and would like to propose > migrating the current landing page to Jekyll. > >>> > >>> The benefits: > >>> > >>> - autodeploy of our changes > >>> - great support of blogging (I'd like to create one) > >>> - easy handling and supported by Infra > >>> - writing content in Markdown > >>> > >>> I am aware that we have a discussion open on how to do documentation > in the future. I would still like to migrate the page asap and - if deemed > necessary - touch it again later. > >>> > >>> So far, I will leave all design/content intact until migrated, and > come back with additional changes (as the blog) after migration to be > discussed separately. > >>> > >>> If there are no objections, I will start with this move sometime next > week. > >>> > >>> Thanks! > >>> Christian > >>> > >>> -- > >>> The Apache Software Foundation > >>> V.P., Data Privacy > >
Re: [VOTE] Move Chainsaw to dormant status
I think Chainsaw /can/ be useful, but it currently is not. If people are willing to work on it a bit more, I can help out a bit. I can see it potentially being useful for the type of work that I do(embedded work) but it needs a fair amount of attention in order to get to the useful level IMO. I have spent a fair amount of time getting it into a state where it will run with newer JVMs and removing the old dependencies and re-architecting the backend to be more generic and allow for inputs from all types of sources. I think the basic architecture is sound at this point, but I think the GUI is much too busy to make it useful. I have been thinking about how it could be re-done though, I do have some ideas that I can put in a new thread. Latest staging site for reference: https://logging.staged.apache.org/chainsaw/2.2.0/ -Robert Middleton On Fri, Sep 22, 2023 at 10:30 AM Scott Deboy wrote: > -1 > > While changes may be infrequent, the project is still useful and works > well. I'll continue to contribute to maintenance. > > Scott > > On Thu, Sep 21, 2023, 10:00 AM Volkan Yazıcı wrote: > > > As earlier discussions[1] indicate, Chainsaw has been lacking on > > maintenance and no PMC member stepped up to perform necessary chores. > > This is a vote to retire the Chainsaw by means of > > > > - Move it to the list of dormant projects[2] > > - Making it clear in its README and website that the project is not > > maintained anymore > > - Archive its repository[3] > > > > Please cast your votes on this mailing list. > > > > [ ] +1, retire the project > > [ ] -1, don't retire, because... > > > > This vote is open for 72 hours and will pass unless getting a net > > negative vote count. All votes are welcome and we encourage everyone, > > but only the Logging Services PMC votes are officially counted. At > > least 3 +1 votes and more positive than negative votes are required. > > > > [1] https://lists.apache.org/thread/fsykp5hxr9z0c2h85snnhnj2pq553t6q > > [2] https://logging.apache.org/dormant.html > > [3] https://github.com/apache/chainsaw > > >
Re: [VOTE] Move Chainsaw to dormant status
Most of the ui elements can be hidden. The explicit hidden expression filter and real time update support are indispensable. I use it to aggregate results from multiple hosts into a single tab and filter in that view. Scott On Fri, Sep 22, 2023, 7:35 PM Robert Middleton wrote: > I think Chainsaw /can/ be useful, but it currently is not. If people are > willing to work on it a bit more, I can help out a bit. I can see it > potentially being useful for the type of work that I do(embedded work) but > it needs a fair amount of attention in order to get to the useful level > IMO. > > I have spent a fair amount of time getting it into a state where it will > run with newer JVMs and removing the old dependencies and re-architecting > the backend to be more generic and allow for inputs from all types of > sources. I think the basic architecture is sound at this point, but I > think the GUI is much too busy to make it useful. I have been thinking > about how it could be re-done though, I do have some ideas that I can put > in a new thread. > > Latest staging site for reference: > https://logging.staged.apache.org/chainsaw/2.2.0/ > > -Robert Middleton > > On Fri, Sep 22, 2023 at 10:30 AM Scott Deboy > wrote: > > > -1 > > > > While changes may be infrequent, the project is still useful and works > > well. I'll continue to contribute to maintenance. > > > > Scott > > > > On Thu, Sep 21, 2023, 10:00 AM Volkan Yazıcı wrote: > > > > > As earlier discussions[1] indicate, Chainsaw has been lacking on > > > maintenance and no PMC member stepped up to perform necessary chores. > > > This is a vote to retire the Chainsaw by means of > > > > > > - Move it to the list of dormant projects[2] > > > - Making it clear in its README and website that the project is not > > > maintained anymore > > > - Archive its repository[3] > > > > > > Please cast your votes on this mailing list. > > > > > > [ ] +1, retire the project > > > [ ] -1, don't retire, because... > > > > > > This vote is open for 72 hours and will pass unless getting a net > > > negative vote count. All votes are welcome and we encourage everyone, > > > but only the Logging Services PMC votes are officially counted. At > > > least 3 +1 votes and more positive than negative votes are required. > > > > > > [1] https://lists.apache.org/thread/fsykp5hxr9z0c2h85snnhnj2pq553t6q > > > [2] https://logging.apache.org/dormant.html > > > [3] https://github.com/apache/chainsaw > > > > > >
