[Job] Cocoon developer required (London)

2009-11-30 Thread Robin Wyles

Hi everyone,

It's been a very long time since I've posted here (apologies, and  
hopefully more on that soon!)...


We're looking for a Cocoon developer to help me out with the support  
and further development of our Cocoon based applications.


We need strong skills in Cocoon, Spring, Linux, and preferably  
someone based in or near to London, UK. We're looking for someone  
which we can work with on a regular basis, and possibly even as a  
full-time position.


If you're at all interested drop me an email with a little info about  
yourself: ro...@jacaranda.co.uk


Thanks!

Robin









Re:[OT] [Job] Cocoon developer required (London)

2009-11-30 Thread David Legg

Hi Robin,

I thought I'd take a peek at your site jacaranda.co.uk and do you know 
what it crashed my Firefox browser!  Thinking it was some 
peculiarity of Firefox I tried IE7 and do you now what... it crashed 
that too :-)


Regards,
David Legg

Robin Wyles wrote:

Hi everyone,

It's been a very long time since I've posted here (apologies, and 
hopefully more on that soon!)...


We're looking for a Cocoon developer to help me out with the support 
and further development of our Cocoon based applications.


We need strong skills in Cocoon, Spring, Linux, and preferably someone 
based in or near to London, UK. We're looking for someone which we can 
work with on a regular basis, and possibly even as a full-time position.


If you're at all interested drop me an email with a little info about 
yourself: ro...@jacaranda.co.uk


Thanks!

Robin











Cocoon documentation

2009-11-30 Thread Matt Whipple
I'm a recent transplant to Cocoon (and Java), in particular because
Cocoon 3 appears as though it is/will be closely in line with my own
perspective on web application development.  I'm interested in
contributing to the development of the framework itself, but likely
won't be able to produce anything remotely useful  for a couple months
as I familiarize myself with all of the related technologies. 

I've just read some of the attacks on the poor documentation of the
project and the resulting difficult entry for those unfamiliar.  This
is, of course, easily confirmed by the combination of woefully out of
date references and dead links on the Web site (i.e. to the Daisy
site).  As I am (obviously) hopeful to see Cocoon succeed, I certainly
don't want it to become mired in isolation like so many good projects. 

As such I'd like to try to contribute some documentation.  Is there any
idea among the community as to where documentation should end up, or
should I just create a new site?  Also, I'd lean towards focusing on
Cocoon 3, as having documentation in place for a new release would
likely have larger impact than attaching possibly overdue docs to an
older, in the process of being superseded one.  This would be premature
if there's no foreseeable beta


RE: [OT] [Job] Cocoon developer required (London)

2009-11-30 Thread Robby Pelssers
What did you do to make it crash? ;-)  I can open the home page without
any issues.

Robby

-Original Message-
From: David Legg [mailto:david.l...@searchevent.co.uk] 
Sent: Monday, November 30, 2009 3:42 PM
To: dev@cocoon.apache.org
Subject: Re:[OT] [Job] Cocoon developer required (London)

Hi Robin,

I thought I'd take a peek at your site jacaranda.co.uk and do you know 
what it crashed my Firefox browser!  Thinking it was some 
peculiarity of Firefox I tried IE7 and do you now what... it crashed 
that too :-)

Regards,
David Legg

Robin Wyles wrote:
 Hi everyone,

 It's been a very long time since I've posted here (apologies, and 
 hopefully more on that soon!)...

 We're looking for a Cocoon developer to help me out with the support 
 and further development of our Cocoon based applications.

 We need strong skills in Cocoon, Spring, Linux, and preferably someone

 based in or near to London, UK. We're looking for someone which we can

 work with on a regular basis, and possibly even as a full-time
position.

 If you're at all interested drop me an email with a little info about 
 yourself: ro...@jacaranda.co.uk

 Thanks!

 Robin











Re: Cocoon documentation

2009-11-30 Thread Jos Snellings
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs

The cocoon community will be delighted at some good documentation.
Talking about community I fear such as an active community is to be
reestablished, so I think we'd better provide some sweet stuff.

What would Reinhard think of starting with as a table of contents?
I will be glad to write some documentation as well. I have some goose
feathers available after Christmas, when I will be through the
experience of creating a first app.

How about you? 
Jos


On Mon, 2009-11-30 at 08:07 -0500, Matt Whipple wrote:
 I'm a recent transplant to Cocoon (and Java), in particular because
 Cocoon 3 appears as though it is/will be closely in line with my own
 perspective on web application development.  I'm interested in
 contributing to the development of the framework itself, but likely
 won't be able to produce anything remotely useful  for a couple months
 as I familiarize myself with all of the related technologies. 
 
 I've just read some of the attacks on the poor documentation of the
 project and the resulting difficult entry for those unfamiliar.  This
 is, of course, easily confirmed by the combination of woefully out of
 date references and dead links on the Web site (i.e. to the Daisy
 site).  As I am (obviously) hopeful to see Cocoon succeed, I certainly
 don't want it to become mired in isolation like so many good projects. 
 
 As such I'd like to try to contribute some documentation.  Is there any
 idea among the community as to where documentation should end up, or
 should I just create a new site?  Also, I'd lean towards focusing on
 Cocoon 3, as having documentation in place for a new release would
 likely have larger impact than attaching possibly overdue docs to an
 older, in the process of being superseded one.  This would be premature
 if there's no foreseeable beta