Re: Thoughts on refactoring the ActiveMQ website

[Bruce Snyder]

I had the following empty git repo created to hold the HTML from the
current website:

https://github.com/apache/activemq-web

However, I have a conundrum -- content cannot be pushed directly to a
Github ASF repo. Content can only be added via pull request but Github does
not allow a pull request on an empty repo.

Any ideas on how to get the HTML into the repo? I guess I could ask ASF
Infra to push it.

Bruce

On Tue, Dec 12, 2017 at 8:17 PM, Bruce Snyder 
wrote:

> I'm going to address all the questions to me in this single reply.
>
> My original suggestion was that we export the HTML from Confluence,
> convert to Markdown and put the Markdown and the images in a git repo.
> Markdown is much easier to edit than raw HTML, especially the HTML exported
> from Confluence (blech!). The idea was that we could use Jekyll + SAAS to
> craft a new website. In fact, Michael Andre Pearce produced a mockup of
> this using the Apache Metro website as an example (because it already makes
> use of Jekyll + SAAS). It was enough to convince me that we should take
> this path, so I started looking into doing a full, new export of Confluence
> pages to HTML. If you have not seen Michael's mockup, you should really
> take a look.
>
> So, I manually grabbed the raw HTML that is automagically exported from
> Confluence and is hosting the current site that we see at
> http://activemq.apache.org. I did some testing on it using text2html and
> the conversion it does is pretty awful and would require a lot of hand work
> to fix it. So, we discussed the point that there are 1600+ pages of HTML to
> manually edit. But I later realized that it was only about 950 HTML pages
> (from what I can tell so far).
>
> Then, Dan Kulp found a Confluence HTML to raw HTML converter built on top
> of PanDoc. So, I have also been trying to export the HTML from Confluence
> in order to try out the PanDoc converter (it works based on the Confluence
> export function which is different from how the HTML is automagically
> converted). Unfortunately, I am running into a NullPointerException from
> Confluence. ASF Infra is telling me that the NPE is due to the CDATA in the
> search function on the Navigation page and is suggesting that the solution
> is to remove the Navigation page. The problem with this suggestion is that
> it would fundamentally remove all the navigation on the right-hand side of
> the site -- not what we want.
>
> I have also given some thought to the idea that removing the current site
> will break all links to old site. This is something that cannot be
> overlooked and must be prevented as we do not want to leave users who have
> bookmarked a page high and dry. This is a fairly easy problem to solve this
> using some mod_rewrite rules, the question is if ASF Infra is willing to
> allow us to deploy such custom rules. This should be investigated when we
> get to that point, but we are not there yet. First, we need to decide the
> best path forward based on what I have described above in the preceding
> paragraphs.
>
>
> Bruce
>
> On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor 
> wrote:
>
>> I was thinking there would be a single css file for all the pages.  But I
>> haven't seen the files yet. Let's have a play around when Bruce pushes the
>> export.
>>
>> Cheers
>>
>> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
>> michael.andre.pea...@me.com>
>> wrote:
>>
>> > What’s 1600 pages between friends
>> >
>> > I agree it will be easier to covert to md than to start doing css
>> styles.
>> > It’s all from a wiki anyhow so it’s can’t be that far off.
>> >
>> > It be good to get some samples (eg 50 pages) if not all just to try and
>> > see what it is like.
>> >
>> >
>> >
>> > On 12 Dec 2017, at 17:04, Clebert Suconic 
>> > wrote:
>> >
>> > >> Exporting to MD and creating a gitbook seems like a big task, I
>> suspect
>> > any
>> > >> tool we use will cause a bunch of styling/content issues.
>> > >>
>> > >> At least initially, how about we just create a nice landing page that
>> > >> brings the ActiveMQ site and Artemis site together, and refresh/align
>> > the
>> > >> existing content with some CSS?
>> > >
>> > > I was just looking for the minimal effort task. I thought that
>> > > converting these pages into a doc would be easier than converting them
>> > > to another .css...
>> > >
>> > > if the conversion needed to be done anyways... I thought .md would be
>> > > easier and having a better final presentation.
>> >
>>
>
>
>
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&
> 5R\"F)R=6-E+G-N>61E
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bsnyder.org/ 
> Twitter: http://twitter.com/brucesnyder
>



-- 
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E
Twitter: 

Re: Thoughts on refactoring the ActiveMQ website

[Bruce Snyder]

I'm going to address all the questions to me in this single reply.

My original suggestion was that we export the HTML from Confluence, convert
to Markdown and put the Markdown and the images in a git repo. Markdown is
much easier to edit than raw HTML, especially the HTML exported from
Confluence (blech!). The idea was that we could use Jekyll + SAAS to craft
a new website. In fact, Michael Andre Pearce produced a mockup of this
using the Apache Metro website as an example (because it already makes use
of Jekyll + SAAS). It was enough to convince me that we should take this
path, so I started looking into doing a full, new export of Confluence
pages to HTML. If you have not seen Michael's mockup, you should really
take a look.

So, I manually grabbed the raw HTML that is automagically exported from
Confluence and is hosting the current site that we see at
http://activemq.apache.org. I did some testing on it using text2html and
the conversion it does is pretty awful and would require a lot of hand work
to fix it. So, we discussed the point that there are 1600+ pages of HTML to
manually edit. But I later realized that it was only about 950 HTML pages
(from what I can tell so far).

Then, Dan Kulp found a Confluence HTML to raw HTML converter built on top
of PanDoc. So, I have also been trying to export the HTML from Confluence
in order to try out the PanDoc converter (it works based on the Confluence
export function which is different from how the HTML is automagically
converted). Unfortunately, I am running into a NullPointerException from
Confluence. ASF Infra is telling me that the NPE is due to the CDATA in the
search function on the Navigation page and is suggesting that the solution
is to remove the Navigation page. The problem with this suggestion is that
it would fundamentally remove all the navigation on the right-hand side of
the site -- not what we want.

I have also given some thought to the idea that removing the current site
will break all links to old site. This is something that cannot be
overlooked and must be prevented as we do not want to leave users who have
bookmarked a page high and dry. This is a fairly easy problem to solve this
using some mod_rewrite rules, the question is if ASF Infra is willing to
allow us to deploy such custom rules. This should be investigated when we
get to that point, but we are not there yet. First, we need to decide the
best path forward based on what I have described above in the preceding
paragraphs.


Bruce

On Tue, Dec 12, 2017 at 11:39 AM, Martyn Taylor  wrote:

> I was thinking there would be a single css file for all the pages.  But I
> haven't seen the files yet. Let's have a play around when Bruce pushes the
> export.
>
> Cheers
>
> On 12 Dec 2017 5:30 pm, "Michael André Pearce" <
> michael.andre.pea...@me.com>
> wrote:
>
> > What’s 1600 pages between friends
> >
> > I agree it will be easier to covert to md than to start doing css styles.
> > It’s all from a wiki anyhow so it’s can’t be that far off.
> >
> > It be good to get some samples (eg 50 pages) if not all just to try and
> > see what it is like.
> >
> >
> >
> > On 12 Dec 2017, at 17:04, Clebert Suconic 
> > wrote:
> >
> > >> Exporting to MD and creating a gitbook seems like a big task, I
> suspect
> > any
> > >> tool we use will cause a bunch of styling/content issues.
> > >>
> > >> At least initially, how about we just create a nice landing page that
> > >> brings the ActiveMQ site and Artemis site together, and refresh/align
> > the
> > >> existing content with some CSS?
> > >
> > > I was just looking for the minimal effort task. I thought that
> > > converting these pages into a doc would be easier than converting them
> > > to another .css...
> > >
> > > if the conversion needed to be done anyways... I thought .md would be
> > > easier and having a better final presentation.
> >
>



-- 
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E
Twitter: http://twitter.com/brucesnyder

Re: Thoughts on refactoring the ActiveMQ website

[Martyn Taylor]

I was thinking there would be a single css file for all the pages.  But I
haven't seen the files yet. Let's have a play around when Bruce pushes the
export.

Cheers

On 12 Dec 2017 5:30 pm, "Michael André Pearce" 
wrote:

> What’s 1600 pages between friends
>
> I agree it will be easier to covert to md than to start doing css styles.
> It’s all from a wiki anyhow so it’s can’t be that far off.
>
> It be good to get some samples (eg 50 pages) if not all just to try and
> see what it is like.
>
>
>
> On 12 Dec 2017, at 17:04, Clebert Suconic 
> wrote:
>
> >> Exporting to MD and creating a gitbook seems like a big task, I suspect
> any
> >> tool we use will cause a bunch of styling/content issues.
> >>
> >> At least initially, how about we just create a nice landing page that
> >> brings the ActiveMQ site and Artemis site together, and refresh/align
> the
> >> existing content with some CSS?
> >
> > I was just looking for the minimal effort task. I thought that
> > converting these pages into a doc would be easier than converting them
> > to another .css...
> >
> > if the conversion needed to be done anyways... I thought .md would be
> > easier and having a better final presentation.
>

Re: Thoughts on refactoring the ActiveMQ website

[Andy Taylor]

Id be happy to spend some time helping

On 12 December 2017 at 17:30, Michael André Pearce <
michael.andre.pea...@me.com> wrote:

> What’s 1600 pages between friends
>
> I agree it will be easier to covert to md than to start doing css styles.
> It’s all from a wiki anyhow so it’s can’t be that far off.
>
> It be good to get some samples (eg 50 pages) if not all just to try and
> see what it is like.
>
>
>
> On 12 Dec 2017, at 17:04, Clebert Suconic 
> wrote:
>
> >> Exporting to MD and creating a gitbook seems like a big task, I suspect
> any
> >> tool we use will cause a bunch of styling/content issues.
> >>
> >> At least initially, how about we just create a nice landing page that
> >> brings the ActiveMQ site and Artemis site together, and refresh/align
> the
> >> existing content with some CSS?
> >
> > I was just looking for the minimal effort task. I thought that
> > converting these pages into a doc would be easier than converting them
> > to another .css...
> >
> > if the conversion needed to be done anyways... I thought .md would be
> > easier and having a better final presentation.
>

Re: Thoughts on refactoring the ActiveMQ website

[Michael André Pearce]

What’s 1600 pages between friends

I agree it will be easier to covert to md than to start doing css styles. It’s 
all from a wiki anyhow so it’s can’t be that far off. 

It be good to get some samples (eg 50 pages) if not all just to try and see 
what it is like. 



On 12 Dec 2017, at 17:04, Clebert Suconic  wrote:

>> Exporting to MD and creating a gitbook seems like a big task, I suspect any
>> tool we use will cause a bunch of styling/content issues.
>> 
>> At least initially, how about we just create a nice landing page that
>> brings the ActiveMQ site and Artemis site together, and refresh/align the
>> existing content with some CSS?
> 
> I was just looking for the minimal effort task. I thought that
> converting these pages into a doc would be easier than converting them
> to another .css...
> 
> if the conversion needed to be done anyways... I thought .md would be
> easier and having a better final presentation.

Re: Thoughts on refactoring the ActiveMQ website

[Clebert Suconic]

> Exporting to MD and creating a gitbook seems like a big task, I suspect any
> tool we use will cause a bunch of styling/content issues.
>
> At least initially, how about we just create a nice landing page that
> brings the ActiveMQ site and Artemis site together, and refresh/align the
> existing content with some CSS?

I was just looking for the minimal effort task. I thought that
converting these pages into a doc would be easier than converting them
to another .css...

if the conversion needed to be done anyways... I thought .md would be
easier and having a better final presentation.

Re: Thoughts on refactoring the ActiveMQ website

[Martyn Taylor]

On Tue, Dec 12, 2017 at 4:46 PM, Michael André Pearce <
michael.andre.pea...@me.com> wrote:

> I agree, gitbook or similar would be a great way to manage the docs for
> 5.x.
>
Exporting to MD and creating a gitbook seems like a big task, I suspect any
tool we use will cause a bunch of styling/content issues.

At least initially, how about we just create a nice landing page that
brings the ActiveMQ site and Artemis site together, and refresh/align the
existing content with some CSS?

>
> @Bruce any luck with the extract of the current bits so can play around ?
>
> Sent from my iPhone
>
> > On 12 Dec 2017, at 16:19, Clebert Suconic 
> wrote:
> >
> > I wanted to emphasize an idea I spoke here:
> >
> >
> > Instead of converting the AMQ5 docs back into website format.. I think
> > it would be great to have the docs into a MD format so it would be
> > just a like a documentation format. gitbook convertible.
> >
> >
> > is there a requirement to keep the docs as website? we could think
> > differently here, right?
> >
> >
> >
> >
> >> On Fri, Dec 8, 2017 at 11:26 AM, Martyn Taylor 
> wrote:
> >> Yes.  I had been chatting with Michael for a while about website
> updates.
> >> We had a bit of back and forth with this design.  Code is always a good
> >> place to start.  Cheers.
> >>
> >>> On Fri, Dec 8, 2017 at 2:16 PM, Bruce Snyder 
> wrote:
> >>>
> >>> I agree with the idea of making the site the landing page for all the
> >>> sub-projects within the overall ActiveMQ project.
> >>>
> >>> You should take a look at the message from Michael Andre Pearce to see
> his
> >>> mockup using the new logo, it's an excellent starting point for a
> >>> discussion. Be sure to follow the instructions in the BUILD.md:
> >>>
> >>> https://github.com/michaelandrepearce/activemq-
> >>> site/blob/master/site/BUILD.md
> >>>
> >>> Bruce
> >>>
>  On Fri, Dec 8, 2017 at 3:48 AM, Martyn Taylor 
> wrote:
> 
>  Some ideas to kick off design discussion.
> 
>  Really what I am trying to convey here is that ActiveMQ is the home
> of a
>  more than just 5.x series.  And to have clear links to each project,
>  clicking through would take you to landing page for the project.  This
>  essentially would be the landing page for top level ActiveMQ.
> 
>  I realise the text in the message needs more work (it's also probably
>  worth having a bit of info for each project on the landing page too).
> 
>  On Fri, Dec 8, 2017 at 1:23 AM, Bruce Snyder 
>  wrote:
> 
> > This looks great, Michael. It's also a great proof-of-concept, nice
> >>> work.
> > I
> > like the look of it, but I don't think we want to completely copy the
> > Metron site, so we will need to change it up.
> >
> > I'm working on getting the exported HTML from the ActiveMQ Confluence
> > space
> > and I will dump it into a new git repo.
> >
> > Bruce
> >
> > On Thu, Dec 7, 2017 at 9:55 AM, Michael André Pearce <
> > michael.andre.pea...@me.com> wrote:
> >
> >> Agree on jekyll.
> >>
> >> Here’s a sample I’ve mocked up with an activemq look and feel (and
> >>> much
> >> lighter) based around the new logo
> >>
> >> https://github.com/michaelandrepearce/activemq-
> site/tree/master/site
> >>
> >> I forked from metrons to get most of the bits like Jekyll etc which
> is
> >> already working.
> >>
> >>
> >>
> >>
> >>
> >>
> >> Sent from my iPhone
> >>
> >>> On 7 Dec 2017, at 16:49, Bruce Snyder 
> >>> wrote:
> >>>
> >>> I would prefer to use Markdown with the Jekyll framework (
> >>> https://jekyllrb.com/). Jekyll handles Markdown, it handles CSS
> >>> (via
> >> SASS)
> >>> and it would allow the site to live in a git repo.
> >>>
> >>> Also, I found that other projects use Jekyll with great success,
> >>> here
> > is
> >>> just one example in the Flink project:
> >>>
> >>> https://flink.apache.org/
> >>>
> >>> Nice looking site, clearly more modern and fully customizable.
> >>>
> >>> Bruce
> >>>
> >>> On Thu, Dec 7, 2017 at 9:42 AM, Clebert Suconic <
> >> clebert.suco...@gmail.com>
> >>> wrote:
> >>>
>  +1
> 
>  I like the Markdown (or whatever easy format.. non xml based). We
> > will
>  need to choose a framework for that. do you have anything in mind?
> 
>  I also think we should have a consistent look and feel.
> 
> 
>  I will be supportive on this...
> 
> 
>  First thing will be to have a framework chosen..
>  Second to have a github we collaborate...
>  Third.. maybe we could use one of those video calls to talk about
> > how to
>  do it.
> 
>  On 

Re: Thoughts on refactoring the ActiveMQ website

[Clebert Suconic]

we would need to keep the current ones hidden somewhere.. these links
are 10+ years old.. it would break anyone referring linked docs. Think
of your customers with bookmarks.

@Bruce: WDYT?

On Tue, Dec 12, 2017 at 11:46 AM, Michael André Pearce
 wrote:
> I agree, gitbook or similar would be a great way to manage the docs for 5.x.
>
> @Bruce any luck with the extract of the current bits so can play around ?
>
> Sent from my iPhone
>
>> On 12 Dec 2017, at 16:19, Clebert Suconic  wrote:
>>
>> I wanted to emphasize an idea I spoke here:
>>
>>
>> Instead of converting the AMQ5 docs back into website format.. I think
>> it would be great to have the docs into a MD format so it would be
>> just a like a documentation format. gitbook convertible.
>>
>>
>> is there a requirement to keep the docs as website? we could think
>> differently here, right?
>>
>>
>>
>>
>>> On Fri, Dec 8, 2017 at 11:26 AM, Martyn Taylor  wrote:
>>> Yes.  I had been chatting with Michael for a while about website updates.
>>> We had a bit of back and forth with this design.  Code is always a good
>>> place to start.  Cheers.
>>>
 On Fri, Dec 8, 2017 at 2:16 PM, Bruce Snyder  
 wrote:

 I agree with the idea of making the site the landing page for all the
 sub-projects within the overall ActiveMQ project.

 You should take a look at the message from Michael Andre Pearce to see his
 mockup using the new logo, it's an excellent starting point for a
 discussion. Be sure to follow the instructions in the BUILD.md:

 https://github.com/michaelandrepearce/activemq-
 site/blob/master/site/BUILD.md

 Bruce

> On Fri, Dec 8, 2017 at 3:48 AM, Martyn Taylor  wrote:
>
> Some ideas to kick off design discussion.
>
> Really what I am trying to convey here is that ActiveMQ is the home of a
> more than just 5.x series.  And to have clear links to each project,
> clicking through would take you to landing page for the project.  This
> essentially would be the landing page for top level ActiveMQ.
>
> I realise the text in the message needs more work (it's also probably
> worth having a bit of info for each project on the landing page too).
>
> On Fri, Dec 8, 2017 at 1:23 AM, Bruce Snyder 
> wrote:
>
>> This looks great, Michael. It's also a great proof-of-concept, nice
 work.
>> I
>> like the look of it, but I don't think we want to completely copy the
>> Metron site, so we will need to change it up.
>>
>> I'm working on getting the exported HTML from the ActiveMQ Confluence
>> space
>> and I will dump it into a new git repo.
>>
>> Bruce
>>
>> On Thu, Dec 7, 2017 at 9:55 AM, Michael André Pearce <
>> michael.andre.pea...@me.com> wrote:
>>
>>> Agree on jekyll.
>>>
>>> Here’s a sample I’ve mocked up with an activemq look and feel (and
 much
>>> lighter) based around the new logo
>>>
>>> https://github.com/michaelandrepearce/activemq-site/tree/master/site
>>>
>>> I forked from metrons to get most of the bits like Jekyll etc which is
>>> already working.
>>>
>>>
>>>
>>>
>>>
>>>
>>> Sent from my iPhone
>>>
 On 7 Dec 2017, at 16:49, Bruce Snyder 
 wrote:

 I would prefer to use Markdown with the Jekyll framework (
 https://jekyllrb.com/). Jekyll handles Markdown, it handles CSS
 (via
>>> SASS)
 and it would allow the site to live in a git repo.

 Also, I found that other projects use Jekyll with great success,
 here
>> is
 just one example in the Flink project:

 https://flink.apache.org/

 Nice looking site, clearly more modern and fully customizable.

 Bruce

 On Thu, Dec 7, 2017 at 9:42 AM, Clebert Suconic <
>>> clebert.suco...@gmail.com>
 wrote:

> +1
>
> I like the Markdown (or whatever easy format.. non xml based). We
>> will
> need to choose a framework for that. do you have anything in mind?
>
> I also think we should have a consistent look and feel.
>
>
> I will be supportive on this...
>
>
> First thing will be to have a framework chosen..
> Second to have a github we collaborate...
> Third.. maybe we could use one of those video calls to talk about
>> how to
> do it.
>
> On Wed, Dec 6, 2017 at 11:20 PM, Bruce Snyder <
>> bruce.sny...@gmail.com>
> wrote:
>> Several opinions have been expressed recently that the ActiveMQ
>> website
>> needs some attention and that Artemis should be made more
 

[GitHub] activemq-artemis pull request #1704: ARTEMIS-1553 JSON values all being conv...

[jbertram]

GitHub user jbertram opened a pull request:

https://github.com/apache/activemq-artemis/pull/1704

ARTEMIS-1553 JSON values all being converted to String



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1553

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1704.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1704


commit 3ea41ab77bb2e566081fbe6b5a3972c345437614
Author: Justin Bertram 
Date:   2017-12-12T16:45:01Z

ARTEMIS-1553 JSON values all being converted to String




---

Re: Thoughts on refactoring the ActiveMQ website

[Michael André Pearce]

I agree, gitbook or similar would be a great way to manage the docs for 5.x. 

@Bruce any luck with the extract of the current bits so can play around ?

Sent from my iPhone

> On 12 Dec 2017, at 16:19, Clebert Suconic  wrote:
> 
> I wanted to emphasize an idea I spoke here:
> 
> 
> Instead of converting the AMQ5 docs back into website format.. I think
> it would be great to have the docs into a MD format so it would be
> just a like a documentation format. gitbook convertible.
> 
> 
> is there a requirement to keep the docs as website? we could think
> differently here, right?
> 
> 
> 
> 
>> On Fri, Dec 8, 2017 at 11:26 AM, Martyn Taylor  wrote:
>> Yes.  I had been chatting with Michael for a while about website updates.
>> We had a bit of back and forth with this design.  Code is always a good
>> place to start.  Cheers.
>> 
>>> On Fri, Dec 8, 2017 at 2:16 PM, Bruce Snyder  wrote:
>>> 
>>> I agree with the idea of making the site the landing page for all the
>>> sub-projects within the overall ActiveMQ project.
>>> 
>>> You should take a look at the message from Michael Andre Pearce to see his
>>> mockup using the new logo, it's an excellent starting point for a
>>> discussion. Be sure to follow the instructions in the BUILD.md:
>>> 
>>> https://github.com/michaelandrepearce/activemq-
>>> site/blob/master/site/BUILD.md
>>> 
>>> Bruce
>>> 
 On Fri, Dec 8, 2017 at 3:48 AM, Martyn Taylor  wrote:
 
 Some ideas to kick off design discussion.
 
 Really what I am trying to convey here is that ActiveMQ is the home of a
 more than just 5.x series.  And to have clear links to each project,
 clicking through would take you to landing page for the project.  This
 essentially would be the landing page for top level ActiveMQ.
 
 I realise the text in the message needs more work (it's also probably
 worth having a bit of info for each project on the landing page too).
 
 On Fri, Dec 8, 2017 at 1:23 AM, Bruce Snyder 
 wrote:
 
> This looks great, Michael. It's also a great proof-of-concept, nice
>>> work.
> I
> like the look of it, but I don't think we want to completely copy the
> Metron site, so we will need to change it up.
> 
> I'm working on getting the exported HTML from the ActiveMQ Confluence
> space
> and I will dump it into a new git repo.
> 
> Bruce
> 
> On Thu, Dec 7, 2017 at 9:55 AM, Michael André Pearce <
> michael.andre.pea...@me.com> wrote:
> 
>> Agree on jekyll.
>> 
>> Here’s a sample I’ve mocked up with an activemq look and feel (and
>>> much
>> lighter) based around the new logo
>> 
>> https://github.com/michaelandrepearce/activemq-site/tree/master/site
>> 
>> I forked from metrons to get most of the bits like Jekyll etc which is
>> already working.
>> 
>> 
>> 
>> 
>> 
>> 
>> Sent from my iPhone
>> 
>>> On 7 Dec 2017, at 16:49, Bruce Snyder 
>>> wrote:
>>> 
>>> I would prefer to use Markdown with the Jekyll framework (
>>> https://jekyllrb.com/). Jekyll handles Markdown, it handles CSS
>>> (via
>> SASS)
>>> and it would allow the site to live in a git repo.
>>> 
>>> Also, I found that other projects use Jekyll with great success,
>>> here
> is
>>> just one example in the Flink project:
>>> 
>>> https://flink.apache.org/
>>> 
>>> Nice looking site, clearly more modern and fully customizable.
>>> 
>>> Bruce
>>> 
>>> On Thu, Dec 7, 2017 at 9:42 AM, Clebert Suconic <
>> clebert.suco...@gmail.com>
>>> wrote:
>>> 
 +1
 
 I like the Markdown (or whatever easy format.. non xml based). We
> will
 need to choose a framework for that. do you have anything in mind?
 
 I also think we should have a consistent look and feel.
 
 
 I will be supportive on this...
 
 
 First thing will be to have a framework chosen..
 Second to have a github we collaborate...
 Third.. maybe we could use one of those video calls to talk about
> how to
 do it.
 
 On Wed, Dec 6, 2017 at 11:20 PM, Bruce Snyder <
> bruce.sny...@gmail.com>
 wrote:
> Several opinions have been expressed recently that the ActiveMQ
> website
> needs some attention and that Artemis should be made more
>>> prominent.
>> I'd
> like to discuss some ideas to see what we could achieve on this
> topic.
> 
> If we are going to make Artemis more prominent, the first concern
>>> I
> identified is that the ActiveMQ website and the Artemis website
>>> are
> authored differently. The ActiveMQ website is authored in the
>> Confluence
> wiki 

Re: Distribution of messages among multiple subscribers of a queue in activemq

[Arthur Naseef]

JMS queues automatically load share across consumers.  Make sure to set
prefetch size to 1 to get the level of fairness in distribution that you'll
want for this use-case.

For the chat portion, have you looked at a chat-based solution?  The
messaging for chat is a specific pattern - point-to-point connections, with
sessions, between a mix of endpoints that are fairly-fixed (the support
representatives) and constantly-changing (support end-users).  There are
solutions that do that part well.

Art


On Tue, Dec 12, 2017 at 1:21 AM, Donnieclark 
wrote:

> Hello Guys,
>
> How can messages be distributed among subscribers of a queue ? I have a
> customer-support chat scenario using activemq where multiple customers can
> chat with multiple support representatives. Customer can use a static queue
> or temporary queues for listening. But how can we distribute chat among
> different support representatives which uses a single support queue for
> listening? Also how a fixed chat session can be established between one
> customer and one support representative such that support representative
> will only respond to the current customer and if there is another request
> it
> will be forwarded to other subscriber of the support queue??
>
> Thanks
>
> I didn't find the right solution from the internet.
> References:
> -
> https://forums.manning.com/posts/list/30135.page;jsessionid=
> A5BB5C27B96D99E6C512051135A992A1
> -  Whiteboard Explainer Video
> 
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-
> f2368404.html
>

Re: Thoughts on refactoring the ActiveMQ website

[Clebert Suconic]

I wanted to emphasize an idea I spoke here:


Instead of converting the AMQ5 docs back into website format.. I think
it would be great to have the docs into a MD format so it would be
just a like a documentation format. gitbook convertible.


is there a requirement to keep the docs as website? we could think
differently here, right?




On Fri, Dec 8, 2017 at 11:26 AM, Martyn Taylor  wrote:
> Yes.  I had been chatting with Michael for a while about website updates.
> We had a bit of back and forth with this design.  Code is always a good
> place to start.  Cheers.
>
> On Fri, Dec 8, 2017 at 2:16 PM, Bruce Snyder  wrote:
>
>> I agree with the idea of making the site the landing page for all the
>> sub-projects within the overall ActiveMQ project.
>>
>> You should take a look at the message from Michael Andre Pearce to see his
>> mockup using the new logo, it's an excellent starting point for a
>> discussion. Be sure to follow the instructions in the BUILD.md:
>>
>> https://github.com/michaelandrepearce/activemq-
>> site/blob/master/site/BUILD.md
>>
>> Bruce
>>
>> On Fri, Dec 8, 2017 at 3:48 AM, Martyn Taylor  wrote:
>>
>> > Some ideas to kick off design discussion.
>> >
>> > Really what I am trying to convey here is that ActiveMQ is the home of a
>> > more than just 5.x series.  And to have clear links to each project,
>> > clicking through would take you to landing page for the project.  This
>> > essentially would be the landing page for top level ActiveMQ.
>> >
>> > I realise the text in the message needs more work (it's also probably
>> > worth having a bit of info for each project on the landing page too).
>> >
>> > On Fri, Dec 8, 2017 at 1:23 AM, Bruce Snyder 
>> > wrote:
>> >
>> >> This looks great, Michael. It's also a great proof-of-concept, nice
>> work.
>> >> I
>> >> like the look of it, but I don't think we want to completely copy the
>> >> Metron site, so we will need to change it up.
>> >>
>> >> I'm working on getting the exported HTML from the ActiveMQ Confluence
>> >> space
>> >> and I will dump it into a new git repo.
>> >>
>> >> Bruce
>> >>
>> >> On Thu, Dec 7, 2017 at 9:55 AM, Michael André Pearce <
>> >> michael.andre.pea...@me.com> wrote:
>> >>
>> >> > Agree on jekyll.
>> >> >
>> >> > Here’s a sample I’ve mocked up with an activemq look and feel (and
>> much
>> >> > lighter) based around the new logo
>> >> >
>> >> > https://github.com/michaelandrepearce/activemq-site/tree/master/site
>> >> >
>> >> > I forked from metrons to get most of the bits like Jekyll etc which is
>> >> > already working.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Sent from my iPhone
>> >> >
>> >> > > On 7 Dec 2017, at 16:49, Bruce Snyder 
>> wrote:
>> >> > >
>> >> > > I would prefer to use Markdown with the Jekyll framework (
>> >> > > https://jekyllrb.com/). Jekyll handles Markdown, it handles CSS
>> (via
>> >> > SASS)
>> >> > > and it would allow the site to live in a git repo.
>> >> > >
>> >> > > Also, I found that other projects use Jekyll with great success,
>> here
>> >> is
>> >> > > just one example in the Flink project:
>> >> > >
>> >> > > https://flink.apache.org/
>> >> > >
>> >> > > Nice looking site, clearly more modern and fully customizable.
>> >> > >
>> >> > > Bruce
>> >> > >
>> >> > > On Thu, Dec 7, 2017 at 9:42 AM, Clebert Suconic <
>> >> > clebert.suco...@gmail.com>
>> >> > > wrote:
>> >> > >
>> >> > >> +1
>> >> > >>
>> >> > >> I like the Markdown (or whatever easy format.. non xml based). We
>> >> will
>> >> > >> need to choose a framework for that. do you have anything in mind?
>> >> > >>
>> >> > >> I also think we should have a consistent look and feel.
>> >> > >>
>> >> > >>
>> >> > >> I will be supportive on this...
>> >> > >>
>> >> > >>
>> >> > >> First thing will be to have a framework chosen..
>> >> > >> Second to have a github we collaborate...
>> >> > >> Third.. maybe we could use one of those video calls to talk about
>> >> how to
>> >> > >> do it.
>> >> > >>
>> >> > >> On Wed, Dec 6, 2017 at 11:20 PM, Bruce Snyder <
>> >> bruce.sny...@gmail.com>
>> >> > >> wrote:
>> >> > >>> Several opinions have been expressed recently that the ActiveMQ
>> >> website
>> >> > >>> needs some attention and that Artemis should be made more
>> prominent.
>> >> > I'd
>> >> > >>> like to discuss some ideas to see what we could achieve on this
>> >> topic.
>> >> > >>>
>> >> > >>> If we are going to make Artemis more prominent, the first concern
>> I
>> >> > >>> identified is that the ActiveMQ website and the Artemis website
>> are
>> >> > >>> authored differently. The ActiveMQ website is authored in the
>> >> > Confluence
>> >> > >>> wiki and exported to HTML automagically whereas the Artemis
>> website
>> >> is
>> >> > >>> authored in raw HTML. As a result, the two sites have a very
>> >> different
>> >> > >> look
>> >> > >>> and feel to them. This presents some challenges to using the

[GitHub] activemq-artemis pull request #1690: ARTEMIS-1523 Allow MQTT with dynamic cl...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1690


---

Distribution of messages among multiple subscribers of a queue in activemq

[Donnieclark]

Hello Guys,

How can messages be distributed among subscribers of a queue ? I have a
customer-support chat scenario using activemq where multiple customers can
chat with multiple support representatives. Customer can use a static queue
or temporary queues for listening. But how can we distribute chat among
different support representatives which uses a single support queue for
listening? Also how a fixed chat session can be established between one
customer and one support representative such that support representative
will only respond to the current customer and if there is another request it
will be forwarded to other subscriber of the support queue??

Thanks

I didn't find the right solution from the internet.
References:
-
https://forums.manning.com/posts/list/30135.page;jsessionid=A5BB5C27B96D99E6C512051135A992A1
-  Whiteboard Explainer Video
  



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html

[GitHub] activemq-artemis pull request #1703: [ARTEMIS-1552] ensure gssapi sasl mech ...

[gtully]

GitHub user gtully opened a pull request:

https://github.com/apache/activemq-artemis/pull/1703

[ARTEMIS-1552] ensure gssapi sasl mech can deal with empty receive bu…

…ffer

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gtully/activemq-artemis ARTEMIS-1552

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1703.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1703


commit 94d871b60109f5c1849a3e4f1a5b9e36601d5097
Author: gtully 
Date:   2017-12-12T14:04:06Z

[ARTEMIS-1552] ensure gssapi sasl mech can deal with empty receive buffer




---

[GitHub] activemq-artemis issue #1697: ARTEMIS-1341 fix getBytes

[stanlyDoge]

Github user stanlyDoge commented on the issue:

https://github.com/apache/activemq-artemis/pull/1697
  
Oops with squashing. Should be ok now, let's wait for check.


---

[GitHub] activemq-artemis issue #1696: NO-JIRA fixed minor regression and broken test...

[pgfox]

Github user pgfox commented on the issue:

https://github.com/apache/activemq-artemis/pull/1696
  
Thanks @michaelandrepearce , @mtaylor 


---

[GitHub] activemq-artemis issue #1688: ARTEMIS-1537 broker was less strict while relo...

[jdanekrh]

Github user jdanekrh commented on the issue:

https://github.com/apache/activemq-artemis/pull/1688
  
wow!
such fix!
thanks much!


---

[GitHub] activemq-artemis issue #1697: ARTEMIS-1341 fix getBytes

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1697
  
@stanlyDoge unfortunately it seems there is a build failure of this PR, 
could you look at it? 


---

[GitHub] activemq-artemis issue #1688: ARTEMIS-1537 broker was less strict while relo...

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1688
  
@stanlyDoge all merged, thanks for this.


---

[GitHub] activemq-artemis issue #1696: NO-JIRA fixed minor regression and broken test...

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1696
  
@pgfox all merged now, thanks for this!


---

[GitHub] activemq-artemis pull request #1688: ARTEMIS-1537 broker was less strict whi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1688


---

[GitHub] activemq-artemis pull request #1696: NO-JIRA fixed minor regression and brok...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1696


---

[GitHub] activemq-artemis issue #1696: NO-JIRA fixed minor regression and broken test...

[mtaylor]

Github user mtaylor commented on the issue:

https://github.com/apache/activemq-artemis/pull/1696
  
@pgfox @michaelandrepearce This looks reasonable to me.  Nice work on 
catching these issues.  


---

[GitHub] activemq-artemis issue #1696: NO-JIRA fixed minor regression and broken test...

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1696
  
@mtaylor Ill look to merge this later today, if you wanted to check it 
before hand?


---

[GitHub] activemq-artemis issue #1697: ARTEMIS-1341 fix getBytes

[stanlyDoge]

Github user stanlyDoge commented on the issue:

https://github.com/apache/activemq-artemis/pull/1697
  
@michaelandrepearce Yes, it should be ready.


---

[GitHub] activemq-artemis issue #1684: ARTEMIS-1498: Openwire internal headers should...

[RaiSaurabh]

Github user RaiSaurabh commented on the issue:

https://github.com/apache/activemq-artemis/pull/1684
  
@michaelandrepearce I have taken your suggestion and implemented it. 
Currently, I am testing it will push it in a day or two. I am ensuring that all 
the headers are retained on conversion of protocols.  Hope it is alright for 
you.


---

[GitHub] activemq-artemis issue #1697: ARTEMIS-1341 fix getBytes

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1697
  
@stanlyDoge is this ready? If so could you squash the commits into one?


---

[GitHub] activemq-artemis issue #1684: ARTEMIS-1498: Openwire internal headers should...

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1684
  
@RaiSaurabh seems you've reverted this, are you working on an alternative 
solution? Is it worth closing this PR till ready?


---

[GitHub] activemq-artemis issue #1688: ARTEMIS-1537 broker was less strict while relo...

[michaelandrepearce]

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1688
  
@stanlyDoge good work :) +1, will look to merge later today if no one else 
does before me.


---

[GitHub] activemq-artemis issue #1696: NO-JIRA fixed minor regression and broken test...

[RaiSaurabh]

Github user RaiSaurabh commented on the issue:

https://github.com/apache/activemq-artemis/pull/1696
  
Thanks, @michaelandrepearce @pgfox for the details provided I will keep 
this in mind for future.


---

[GitHub] activemq-artemis issue #1644: ARTEMIS-1503 Added ng-grid plugin

[andytaylor]

Github user andytaylor commented on the issue:

https://github.com/apache/activemq-artemis/pull/1644
  
@mtaylor are we ok merging this?


---

[GitHub] activemq-artemis issue #1696: NO-JIRA fixed minor regression and broken test...

[pgfox]

Github user pgfox commented on the issue:

https://github.com/apache/activemq-artemis/pull/1696
  
- added in @michaelandrepearce  commit to the PR
- fixed a few minor check style infringements
- added testing to exercise some of the sorting code 

I did not squash the commits as I wanted to keep the commit history to show 
multiple contributors.



---