Thanks for your feedback. I removed the change to existing releases documentation and I think those need more discussion like you said, or we just keep it.
However, for page titles and general description, keeping the "ActiveMQ" in Artemis or "Classic" in ActiveMQ on the current website will confuse users. As the announcement was made, more people will start going to the website to check the news. If we don't change page headings and titles, they will get confused about the messaging. IMO, changing the existing website (and publishing the new sites for both going forward) should be prioritized. Additionally, it will be nice to push some features and bug fixes to ActiveMQ to release ActiveMQ 6.3. It provides an obvious signal for the community about the new direction. Thanks, Ken On Fri, Nov 21, 2025 at 2:05 AM Robbie Gemmell <[email protected]> wrote: > I didnt mean the plan around updating the future site / its generation > /etc , I obviously agree there is no harm in starting that work as > there will be much to do on both sites before anything can be > published. > > I meant more general changes to the current site content such as > several of the ones just proposed on > https://github.com/apache/activemq-website/pull/165/files > > On Thu, 20 Nov 2025 at 17:38, Matt Pavlovich <[email protected]> wrote: > > > > Robbie- > > > > Yeah, I don’t think anyone is suggesting removing or changing Artemis > content until the Artemis website is up and running. > > > > At the same time, no harm in starting to put together plans and even > drafting up mock-ups of an updated L&F for the ActiveMQ site. > > > > Thanks for updating the asf.yaml— I wasn’t aware that was self-service. > Thanks =) > > > > -Matt > > > > > On Nov 20, 2025, at 10:58 AM, Robbie Gemmell <[email protected]> > wrote: > > > > > > Probably makes sense to wait until we actually do have the new Artemis > > > TLP and site before changing the current ActiveMQ one too > > > significantly. > > > > > > Evaluating new ways to build whilst updating content on the future > > > ActiveMQ site does seem wise, and similarly for the new Artemis site > > > going forward. Though it may also be more expedient for establishing > > > an initial Artemis site to just rework what is there now for it at > > > first, given it already has multiple per-version documentation sets, > > > most of the content is produced out of the main artemis repo during > > > the release process, etc. > > > > > > On Thu, 20 Nov 2025 at 16:13, Jean-Baptiste Onofré <[email protected]> > wrote: > > >> > > >> Hi folks, > > >> > > >> Now that we have two Top-Level Projects (ActiveMQ and Artemis), I > > >> would like to propose the following action plan across five key areas > > >> for discussion: > > >> > > >> 1. Website > > >> I propose two immediate actions regarding the ActiveMQ website: > > >> a. We should quickly remove the term "Classic" from the project name > > >> and all mentions across the website. > > >> b. I propose an important refactoring of the website structure, > > >> leveraging a modern static site generator such as Antora, Docusaurus, > > >> or Hugo (see Point 2 for related details). > > >> > > >> 2. Documentation > > >> We have a significant amount of work ahead to ensure the documentation > > >> content is current and complete. To facilitate this, I propose > > >> adopting a framework like Hugo to manage documentation across multiple > > >> versions effectively. > > >> > > >> 3. GitHub Issues > > >> I plan to restart the discussion regarding migrating our issue > > >> tracking from Jira to GitHub Issues. This will be initiated in a > > >> separate thread. > > >> > > >> 4. GitHub Actions (CI) > > >> I have started implementing GitHub Actions for our Continuous > > >> Integration (CI) process (as demonstrated in > > >> https://github.com/apache/activemq/pull/1497 > > >> (https://github.com/apache/activemq/pull/1497)). This setup will also > > >> allow us to manage dependency updates automatically via Dependabot. > > >> > > >> 5. Automated Release/ATR > > >> Building upon the work in Point 4, we will be able to transition > > >> toward Automatic Release CI/ATR. This topic will also be discussed in > > >> a separate, dedicated thread. > > >> > > >> I will initiate separate threads for each of these points to allow for > > >> focused discussion. Additionally, I would like to make a call for > > >> contributions for anyone interested in helping with these important > > >> topics. > > >> > > >> Thanks, > > >> > > >> Regards, > > >> JB > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> For further information, visit: https://activemq.apache.org/contact > > >> > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > For further information, visit: https://activemq.apache.org/contact > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > For further information, visit: https://activemq.apache.org/contact > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > >
