Hi Martyn, This is great news! How would we go about this? I guess a key bit will be to try authorship/commit history.
Currently I have a copy of the GitHub code that I've just manually patched in so I could work on getting a working solution with active branding. My working branch is here btw: https://github.com/michaelandrepearce/activemq-artemis/tree/ARTEMIS-1270?files=1 Cheers Mike Sent from my iPhone > On 4 Jul 2017, at 14:31, Martyn Taylor <[email protected]> wrote: > > Michael, > > If people think this is the way to go then I can't see there being any > problem with 3). > > Cheers > > On Mon, Jul 3, 2017 at 11:52 PM, Michael André Pearce < > [email protected]> wrote: > >> Ok, >> >> So i think we can do this. From a local build. >> >> Please see screenshots. >> >> https://gist.github.com/michaelandrepearce/98b4be98d20f407c2d745a41df9cef >> 03 <https://gist.github.com/michaelandrepearce/ >> 98b4be98d20f407c2d745a41df9cef03> >> >> For 1) I think we have managed to completely skin it, with all hawtio >> references removed, even the favicon. >> For 2) Only the artemis plugin and base jvm plugins, no extras for any >> other products. >> For 3) Im hoping we can come to agreement on this gets contributed in from >> the rh-messaging project @clebert @martyn @andy?, if not we can probably >> code up a simpler version of it for now without bells and whistles, and add >> in the future features later. >> >> So if we sort point three, i think we can make this “acceptable” >> >> Cheers >> Mike >> >>>> On 29 Jun 2017, at 19:17, Daniel Kulp <[email protected]> wrote: >>>> >>>> >>>> On Jun 29, 2017, at 1:59 PM, Michael André Pearce < >> [email protected] <mailto:[email protected]>> wrote: >>>> >>>> I believe we could make a simple activemq branding jar/war with the >> selected new logo ;) once decided without too much trouble. >>>> >>>> I'd be happy to step up to try do this if no objectors. >>> >>> I discussed previously, what would NEED to be done for this to be >> “acceptable”: >>> >>> 1) All branding/links/etc… in the console need to be re-skinned or >> whatever to be “ActiveMQ”. All mentions of hawtio and links off to other >> sites other than a possible small “powered by” type thing would need to be >> removed. >>> >>> 2) All “plugins” and functionality that don’t pertain to things related >> to ActiveMQ would need to be removed. >>> >>> 3) The “plugin" that presents ActiveMQ related stuff to the user MUST >> live here at Apache and part of the ActiveMQ community. We cannot use the >> one they provide (unless you can convince them to donate it to Apache). >>> >>> Unless all three happen, it’s a no-go. >>> >>> Dan >>> >>> >>>> >>>>> On 29 Jun 2017, at 16:51, Clebert Suconic <[email protected]> >> wrote: >>>>> >>>>> Speaking the plain truth... The issue is that the hawtio console that >>>>> was used years ago.. looked like a commercial product outside of >>>>> apache >>>>> >>>>> I think that if we clear that now.. if it looks an apache look & >>>>> feel.. people wouldn't have an issue with it. >>>>> >>>>> >>>>> That would require some cleanup.. move to a newer hawtio plugin maybe? >>>>> that's when we thought about trying new routes if we would need to do >>>>> a lot of work anyways. >>>>> >>>>> On Thu, Jun 29, 2017 at 11:42 AM, Michael André Pearce >>>>> <[email protected]> wrote: >>>>>> I don't think this is a blocker, for example artemis uses jboss >> logging, this doesn't have a notice file >>>>>> >>>>>> I think we just have to preserve them if present and for asf projects >> themselves eg artemis itself it's policy to provide one for the asf work. >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On 29 Jun 2017, at 01:09, W B D <[email protected]> wrote: >>>>>>> >>>>>>> I've been using hawtio alongside the classic web console in ActiveMQ >> 5.x >>>>>>> and have been quite happy with it. I find it easier to use for many >> common >>>>>>> operations as well as for general monitoring, and it is definitely a >> gap in >>>>>>> the current Artemis distribution, so I would certainly welcome >> built-in >>>>>>> hawtio support as a good addition. >>>>>>> >>>>>>> Although the source code already contains the standard license >> assignment >>>>>>> to ASF, it does not include a NOTICE file. We could ask Redhat for >> one, or >>>>>>> construct one crediting them with the original work, or add a stanza >> to the >>>>>>> top-level NOTICE file if that is more appropriate. IMO, the package >> and >>>>>>> class name org.jboss.plugin.PluginContextListener could probably be >> changed >>>>>>> in our copy, both to establish custody and to give a clearer name. >>>>>>> >>>>>>> On Wed, Jun 28, 2017 at 9:27 AM, MichaelAndrePearce < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Guys, >>>>>>>> >>>>>>>> It's been some time since this discussion thread without seemingly >> any >>>>>>>> movement. >>>>>>>> >>>>>>>> Artemis Project is really suffering from having any kind of >> management >>>>>>>> console. With continued questions and calls from users especially >> as it's >>>>>>>> picking up traction and deployment. >>>>>>>> >>>>>>>> As such could I propose, that as lack of movement on any other >> solution and >>>>>>>> Hawtio is pretty much in a usable state, with a plugin also out >> there in >>>>>>>> the >>>>>>>> wild. (It's ASL) >>>>>>>> >>>>>>>> That for the interim on artemis project we build and release with >> Hawtio >>>>>>>> and >>>>>>>> an artemis plugin (if RH would donate their plugin to artemis >> project?) >>>>>>>> >>>>>>>> Any objectors? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: http://activemq.2283324.n4. >>>>>>>> nabble.com/DISCUSS-Removing-the-Web-Console-tp4717136p4728020.html >>>>>>>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >>>>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Clebert Suconic >>> >>> -- >>> Daniel Kulp >>> [email protected] <mailto:[email protected]> - http://dankulp.com/blog < >> http://dankulp.com/blog> >>> Talend Community Coder - http://coders.talend.com < >> http://coders.talend.com/> >>
