I think one of the most interesting part of hawtio is that the same console
can be used in OSGi or in a non-OSGi environment and that's is pluggable
with dynamic discovery. That's really what we needed for years, back to
the ServiceMix 4 early stage.
Having a single console that can adapt multiple
- Will check more in depth next week hawt.io and have a look to your
remarks.
- For sure, hawt.io should be the house about camel webconsole and I would
appreciate that everybody fully agree about that idea instead of
continuying to re-invent new webconsole every next major realease of Camel.
- Per
On 25 January 2013 08:07, Charles Moulliard wrote:
> +1 for the project plan and if you are interested I can play the role of
> Project Manager to coordinate all the different tasks, actions, define a
> plan and
> following
> manage it
>
> Concerning the webconsole, http://hawt.io project should b
+1 for the project plan and if you are interested I can play the role of
Project Manager to coordinate all the different tasks, actions, define a
plan and
following
manage it
Concerning the webconsole, http://hawt.io project should be the way to go
(or at least jolokia - http://jolokia.org/ ) even
For the webconsole, I'd make sure to have a look at http://hawt.io/
On Wed, Jan 23, 2013 at 11:03 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Lukasz, could you have a look at [1]!?
> We are looking for a champion for the task "Light-weight web console" (if
> it has enough endors
Anybody. We need to hear the ideas of even non-committers actually.
However if there are enough endorsements I'd think there is no need to
add another one. What is more important is to see if anybody has
anything against an idea and what kind of arguments he'd bring to the table.
Hadrian
On
> (if
> it has enough endorsements).
Talking about endorsements... Can all committers endorse or is this
privilege reserved for the PMC masonic lodge? :)
--
Henryk Konsek
http://henryk-konsek.blogspot.com
On Tue, Jan 22, 2013 at 10:25 PM, Christian Müller
wrote:
> Hi Willem,
>
> that's the reason why I wrote "IRC/Skype session for discussion" and not
> "IRC/Skype session to make discussions"... ;-)
> The proposed procedure is to use IRC to be able to discuss multiple topics
> in short time. Afterwa
Lukasz, could you have a look at [1]!?
We are looking for a champion for the task "Light-weight web console" (if
it has enough endorsements). If I remember right, you are playing with
something what could be this light-weight web console. ;-)
Do you consider to take a stab on this?
[1] http://came
Christian, could you have a look at [1]!?
We are looking for a champion for the task "Split camel-core into multiple
parts". We already talked about it in the past and if I remember correct,
you are willing to take a stab on this. Right? Still the same?
[1] http://camel.apache.org/camel-30-ideas.h
Hi
As much as the time permits I will try to follow this move and maybe give my
ideas & feedback to the cool new enhancements/features you are thinking
about. However my involvement in this area will not be as active as many
others.
Looking forward to Camel 3.0
Babak
--
View this message in
Hi Willem,
that's the reason why I wrote "IRC/Skype session for discussion" and not
"IRC/Skype session to make discussions"... ;-)
The proposed procedure is to use IRC to be able to discuss multiple topics
in short time. Afterwards the IRC log and may be a summery should be shared
with the communi
I'm OK for the discussion in the IRC and post the discussion back to dev list
so every one have a chance to express his opinion.
And we made decision in the mailing list.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Bl
Willem, yeah it's tough with your time zone, but you can find many of us
on irc at various time. And btw, your statement that it's "not an Apache
Way" is not quite accurate. The channel is logged and the relevant
content of the discuss (and/or link) will be posted on dev@ anyway. The
Apache Way
Looks like we're starting to get more feedback. Awesome. More inline...
Also moved back from users@ to dev@. I really don't think this should be
on dev. If we want to make users aware of this discussions, I'd do that
via announcements on the site and maybe occasional posts to users@, but
I thin
Hi Christian
Just one comments for the meeting in IRC.
It is not an Apache Way to make decision through the IRC.
As you know the time you chose is the middle night (3 AM) in my timezone.
Maybe we can drop a discussion lines in the wiki page, so every one who wants
to join the discussion can ha
> +1 for having discussion on mailing list.
Oh, and the idea with separated wiki pages - just great :) .
--
Henryk Konsek
http://henryk-konsek.blogspot.com
> Discussions *should* happen on the @dev mailing list, so everybody can
> be in the loop and participate.
> Its the Apache way.
+1 for having discussion on mailing list.
Not only due to the fact that I want to be in the loop, but also
because the discussion should be "googlable" for users intere
Hi
Oh been too busy with work, than having the time to read this thread
and respond.
On Wed, Jan 16, 2013 at 10:12 PM, Christian Müller
wrote:
> I find it very difficult to start a such huge and important challenge as
> Camel 3.0 will be, for sure. I think the most difficult part is to get
> c
Hmm, why did this go to users? Because Christian sent it to 3 lists.
Both me and Willem only replied to users@ :). Oops. Let's just use dev@
going forward.
Hadrian
Original Message
Subject: Re: [CAMEL-3.0] Start moving forward
Date: Thu, 17 Jan 2013 08:47:11 -0500
I find it very difficult to start a such huge and important challenge as
Camel 3.0 will be, for sure. I think the most difficult part is to get
consensus about what we do it and how we do it. We already collect some
useful ideas at [1], but I have the feeling we have to review these ideas.
First of
21 matches
Mail list logo
