...

Lukasz Dywicki, who is helping update the design of the ServceMix ServiceMix site, has volunteered some design effort to the Camel community. Attached are two of his proposals:

• a more serious (kinda angry) camel (link to original)
• a funny, happier camel (link to original)

Daphne Vichot, contributed four more proposals for a logo:

• camel with apache feather carrying messages

Please provide your feedback on the mailing lists and the irc channel to select a logo.

Site Generation

The three current ideas for generating the site include:

...

Scalate sites can be viewed by pointing your Web browser to http://localhost:8080^{Image Removed}.

Issues

Barrier to Entry for Contributors

...

Putting the site content in SVN means that contributors will be required to submit changes as patches through JIRA and committers explicitly grant license to the ASF for inclusion in the Camel project. Committers will be required to review and apply the patches. This changes aligns the nature of the barrier since submitting a patch does not require a signed CLA, but it does require using SVN and JIRA. It also requires more process of contributing documentation with contributing code and requires an extra effort from the committers.

Using SVN directly changes the nature of the barrier to entry. Opinions vary about the merits of changing the barrier to entry. Some feel that making people use SVN and JIRA will scare away some newbies and people who just want to contribute documentation. Others argue that it is no big deal and that the barrier for making documentation changes should be the same.

In the long run, this will be a moot point since Infrastructure is going to require that a project's static site is stored in SVN. A wiki based system such as the Confluence based one is not ideal for a few reasons. Ideally we should have an SVN based CMS that would allow a user to edit content online and automate the workflow of submitting the patch. In principle there is consensus that moving to an SVN based system is the right thing to do. The question is when to make the change. Should we implement it now, or wait for the availability of a better CMS?