checkout todo-doc.xml and see where
I can help.
Let's keep this train rolling!
Cheers,
> -Original Message-
> From: Steven Noels [mailto:[EMAIL PROTECTED]]
> Sent: maandag 6 mei 2002 20:11
> To: [EMAIL PROTECTED]
> Subject: RE: [vote] cocoon-docs
>
>
> Dian
Ivelin Ivanov wrote:
>
>
> Is there a easy way to create a docs list and have a server side robot
> automatically prepend [DOCS] to the subject and forward each
> message to the users and dev list?
>
> I am +1 if this is doable.
We certainly should explore some solutions. I wonder about your
pr
Ivelin Ivanov wrote:
> The discussion on where the DOCS should be discussed is burning a lot of
> energy which could be used to build the DOCS.
>
> Yes, newbie friendly documentation is a must for Cocoon's survival. I am
> also having difficulties helping people get up to speed on simple problems,
d dev list?
I am +1 if this is doable.
Cheers,
Ivelin
- Original Message -
From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 09, 2002 7:30 AM
Subject: Re: [vote] cocoon-docs
> Diana Shannon wrote:
>
> &g
On May 9, 2002, Nicola Ken Barozzi wrote:
>> If it doesn't work, too bad, but at least we tried but this list is
>> focused on entirely different things and it's driven by psycological
>> fuel which is not the proper one for the other community to prosper.
>
> Ok, this makes sense, even if I
Actually, when I said developers I ment people with
commit access. But, thinking about it, if you don't
care about the code or the documentation, I don't believe
you should be using the -dev list; just the -user one.
Personally, I'll monitor the documentation emails whether
they come through -de
David, John, et al:
I would very strongly recommend against increasing traffic on one list by
piping another lists output to it. I believe that the nature documentation
discussion is parallel to the development process.
I would also caution against mass subscribing people to cocoon-docs. I woul
+1 for the cocoon-docs list
I feel developers have little patience for the issues/details of
document management and would some squash threads that might need
further exploration.
best,
-Rob
-
To unsubscribe, e-mail: [EMAIL
Gerhard Froehlich wrote:
> +0 here.
>
> I'm not 100% convinced, that we can seperate the document
> process from the development process this clear.
>
> I'm afraid that will cause lots of cross postings in both
> lists.
I too am concerned on this front. However, i think that there
is a solution
+0 here.
I'm not 100% convinced, that we can seperate the document process
from the development process this clear.
I'm afraid that will cause lots of cross postings in both
lists.
greets
gerhard
--
Gerhard Fröhlich
IBM Account Au
> From: David Crossley [mailto:[EMAIL PROTECTED]]
Personally I'm +0 on a new list, I already subscribe to *far* too many,
having said that...
> *) It would be an easy matter for all Developers to subscribe
> to the new list. This should not make any difference to them,
> as they can easily filte
On Tuesday 07 May 2002 08:18, David Crossley wrote:
> I vote +1 for the formation of a new cocoon-docs list.
> My reasons ...
>. . .
+1 on all of David's points - I think your points are much stronger
than all the "against" points that have been mentioned.
-Bertrand
---
I vote +1 for the formation of a new cocoon-docs list.
My reasons ...
*) The main aim of this effort is to get Users involved in the
process. If they are forced to subscribe to cocoon-dev to
do this, then they could easily be frightened away by the
intensity of the general dev discussions. Pre-pe
On Monday 06 May 2002 14:03, Diana Shannon wrote:
> I'm ready to put my full support behind the creation of a separate docs
> lists for the documentation effort. . .
+1 for a separate docs list.
I'm assuming (dreaming?) some users who would not participate in cocoon-dev
will find it less intim
Diana,
No voting rights on cocoon issues, but since I correspond on Cocoon and
Forrest doco issues on this and the forrest-dev list, I think we have
enough lists already. So here goes my informal -1.
What I would really like however is having the infrastructural topics of
documentation issues to
>
>
>
>If I remember well I already -1d the docs list, but if it wasn't clear, here
>is my -1.
>
>The motivation: XSP list has been a failure at a time when there were *tons*
>of mails on xsps on the dev and user list, more than now.
>
>Let's put a [DOC] header in front of each doc mail, and if/wh
From: "Ivelin Ivanov" <[EMAIL PROTECTED]>
> I am ready to keep monitor and be responsive to any expertise questions
that
> may arise on the dev-list.
>
> Like Crhistian, I am not sure a separate doc list would survive. Seems
like
> the dev-list can still handle some more traffic. Maybe we should
On May 6, 2002, Carlos wrote:
> Cris:
>
> There are two types of documentation for any given project. The first
> type
> is the one you mentioned where the user writes the documentation of
> what he
> learnt and the process he followed to get things working.
Very important point of clarificat
Cris:
There are two types of documentation for any given project. The first type
is the one you mentioned where the user writes the documentation of what he
learnt and the process he followed to get things working.
The second type, which I think Diana is looking for, is the more formal
documenta
day are exceeded the doc list can
split.
Remember the XSP list...
Cheers,
Ivelin
- Original Message -
From: "Diana Shannon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 06, 2002 7:03 AM
Subject: [vote] cocoon-docs
> I'm ready to put my fu
On 06.May.2002 -- 08:03 AM, Diana Shannon wrote:
> I'm ready to put my full support behind the creation of a separate docs
> lists for the documentation effort *if* enough developers on this list
> will agree to monitor the list and participate when their expertise is
> needed. Otherwise, the l
Diana Shannon wrote:
>
> I'm ready to put my full support behind the creation of a separate docs
> lists for the documentation effort *if* enough developers on this list
> will agree to monitor the list and participate when their expertise is
> needed. Otherwise, the list will die, and we'll have
I'm ready to put my full support behind the creation of a separate docs
lists for the documentation effort *if* enough developers on this list
will agree to monitor the list and participate when their expertise is
needed. Otherwise, the list will die, and we'll have to move the
discussion back
23 matches
Mail list logo
