On 4 May 2011 15:24, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > Mule is also an open source project and that had more of a relevance when > Camel started and was a Mule competitor. That page can go away too. > > As James brilliantly stated: let's think of the Camel user's needs and > address them. For needs that go beyond a developer's need to understand and > use Camel, such as getting support or extra tools, the Camel community can > add subtle hints (on the Support page as mentioned), just because we're nice > guys, but going beyond that is wrong. That's not our mission/role. It may be > your role as individuals/employees. Blog about it!
I think you're twisting my words; if there's a good introduction/article/example/book/tool to help users use Camel we should be able to link to it within reason if its helpful to users; not have some draconian policy where we have only X pages frozen in stone forever as the only pages allowed to link to something off the camel.apache.org domain. Forcing users to make extra clicks & navigation just to get to the right sections of 'safe pages' seems silly and doesn't seem to help users at all. I'm all for tidying things up and trying to limit the spread of links; but at the same time, hiding useful information from users or forcing them to perform unnecessary navigation or searches doesn't seem to be helping users at all. Balance is required between helping users find things easily and complying with whatever todays apache policy is on external links. -- James ------- FuseSource Email: ja...@fusesource.com Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference http://camelone.com/
