;
> A few times I read "we will solve this by putting the documentation into
> our SCM", if I remember right.
> - Do we have concrete plans to solve it?
> - What are the plans in detail?
> - When do we plan to solve it?
>
> Thanks in advance for your ideas,
And I thought my English professor was a curmudgeon
On Wednesday, December 28, 2011, Glen Mazza wrote:
> Sorry, Claus, anything above 10 grammar errors activates the harsh,
unforgiving veto buzzer. :)
>
> On 12/28/2011 07:38 AM, davscl...@apache.org wrote:
>
> Modified: camel/trunk/examples/
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
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
+1 to a single source distro in a zip file.
On Thu, Jun 23, 2011 at 9:07 AM, Hadrian Zbarcea wrote:
> +1 from me as well for single source.
> I also believe zip is better than tgz. This would avoid many Windows users
> assuming that a Windows version of the source distro doesn't exist imho.
>
> H
It may be a bit of a "new puppy" item, but I think it is a great idea.
Self documenting code is always a good idea.
On Wed, Apr 20, 2011 at 10:50 AM, Charles Moulliard
wrote:
> Hi,
>
> I would like to suggest that we add annotation to document the
> properties of the Camel Component class which
I've started a Wiki page at
https://cwiki.apache.org/confluence/display/CAMEL/Site+Update+Ideas to
start collecting ideas for a Web refresh.
It hasn't rolled to the static site yet
--
Principle Technical Writer
Phone (781) 280-4174
Skype finnmccumial
E-Mail emjohn...@fusesource.com
Blog http
Hadrian,
As it turns out, not anyone with a signed CLA can edit the Camel wiki.
The Apache Confluence wiki allows each community to determine who can
edit the pages in their space.
I went create a page listing the ideas/issues around a site update and
was confronted with a "Permission Denied" page.
I want to make sure I understand a few of the issues here:
We want to make it as easy as possible for people to make changes to
the documentation.
Before a person can edit the wiki they need to sign an icla.
We don't let anyone change the code who hasn't been vetted by the
community and made a com
start with a page proposing
> a new look-and-feel and let the community vote.
>
> We highly appreciate your contribution,
> Hadrian
>
>
> On Nov 9, 2010, at 2:44 PM, Eric Johnson wrote:
>
>> I'm a committer on CXF and have been helping out with the ServiceMix
&
I'm a committer on CXF and have been helping out with the ServiceMix
site redesign. I'm interested in helping Camel maintain its Web site
as well. Are there any tasks that need tackling that I can get started
on?
--
Principle Technical Writer
Phone (781) 280-4174
Skype finnmccumial
E-Mail emjohn.
11 matches
Mail list logo
