Re: [CONF] Apache Camel > Scalate

Dan's unilateral decision to scrub the Scalate component from the Camel site, while simply adding the others to a new table, does not send the "we are happy about good external components" message. It sends the message that Dan is the new Camel cop and we need to do things his way or else. I'm su

Re: [CONF] Apache Camel > Scalate

On 20 July 2011 17:43, Eric Johnson wrote: > My understanding of what Dan is saying is that since the Scalate > component is not developed as part of the Apache Camel project it > cannot be documented in a way that makes it look like it is a part of > the Apache Camel project. Thing is though, it

Re: [CONF] Apache Camel > Scalate

BTW the very first paragraph of the scalate camel page clearly showed the groupId of the component - which highlights that its never been part of the camel distro nor was it pretending to be. The components page has always been about all components for camel - irrespective of which distro they come

Re: [CONF] Apache Camel > Scalate

Hi Claus, I think we should also list external components. We only need to make sure it is visible that they are not part of the package and not supported by the camel community. So I think we could have an external components header at the end of the components page where we list external c

Re: [CONF] Apache Camel > Scalate

Hi Yeah I seemed a bit rushed. On the components page, Dan added since in the bottom a table with much related components, but as the components is not included in the Camel source tree, he separated them from the top table. http://camel.apache.org/components Maybe we could add the scalete compo

Re: [CONF] Apache Camel > Scalate

Yes. I also think it was the right thing to do, but the wrong way... We should act with more respect for each other - independently whether or not we have different point of views. ... and as Claus always says: We love contributions... ;-) Best, Christian On Wed, Jul 20, 2011 at 5:58 PM, James S

Re: [CONF] Apache Camel > Scalate

Well, another option would be to ask for the camel scalate component code to move to Camel.Scalate is ASL so that's possible. On Wed, Jul 20, 2011 at 18:43, Eric Johnson wrote: > My understanding of what Dan is saying is that since the Scalate > component is not developed as part of the Apach

Re: [CONF] Apache Camel > Scalate

My understanding of what Dan is saying is that since the Scalate component is not developed as part of the Apache Camel project it cannot be documented in a way that makes it look like it is a part of the Apache Camel project. It, and any similarly developed 3rd party components, should be clearly

Re: [CONF] Apache Camel > Scalate

On 20 July 2011 16:43, Daniel Kulp wrote: > On Wednesday, July 20, 2011 8:47:19 AM James Strachan wrote: >> Dan could you please explain why you're deleting pages from the wiki which >> describe open source camel components without first at least having a >> discussion about it? > > Because in thi

Re: [CONF] Apache Camel > Scalate

I still don't get it - maybe I'm just dumb. So we need to delete all web pages hosted at apache that even talk about using, say, JAXB - since its not some source code in an Apache repo? A web page at Apache can only talk about source code hosted by Apache and absolutely nothing else? Can we mentio

Re: [CONF] Apache Camel > Scalate

On Wednesday, July 20, 2011 8:47:19 AM James Strachan wrote: > Dan could you please explain why you're deleting pages from the wiki which > describe open source camel components without first at least having a > discussion about it? Because in this case, there is nothing really to discuss. That

Re: [CONF] Apache Camel > Scalate

Dan could you please explain why you're deleting pages from the wiki which describe open source camel components without first at least having a discussion about it? On 19 July 2011 18:54, wrote: >Scalate Page *removed* by Daniel > Kulp >