You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/08/19 21:15:53 UTC
James End User Documentation
> solicit away.
1. Can we agree on some [DOCUMENTATION] prefix that people can use, so that
documentation submissions can be located in the archives?
2. How's:
If you have James related tips, documentation bits, or just questions about
things that you need help with, please submit them to the James project with
a [DOCUMENTATION] prefix on the subject. The more contributions, the better
the user documentation will get.
I don't supposed anyone on the list is a tech writer, eh? :-)
I'll post up an example of multiple mailing lists so that people can see
what needs to be done for EACH new mailing list. The current documentation
isn't clear on that (in fact, mine works but perhaps I missed a point).
--- Noel
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: James End User Documentation
Posted by "Andrew C. Oliver" <ac...@apache.org>.
On this we can all agree... wikis are very powerful tools for
generating documentation. I'm very impressed with the progress made on
the Cocoon wiki. Stephen Noles (sp?) will be very suprised when he gets
back from vacation.
-Andy
Noel J. Bergman wrote:
> Nicola,
>
> Assuming that folks vote for a wiki, can we set one up on apache, or did
> this require a server elsewhere?
>
> I like wikis. Been running vqWiki on several projects.
>
> --- Noel
>
> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
> Sent: Monday, August 19, 2002 15:25
> To: James Developers List
> Subject: Re: James End User Documentation
>
>
>
> Noel J. Bergman wrote:
>
>>>solicit away.
>>
>>
>> 1. Can we agree on some [DOCUMENTATION] prefix that people can use, so
>
> that
>
>>documentation submissions can be located in the archives?
>>
>> 2. How's:
>>
>>If you have James related tips, documentation bits, or just questions
>
> about
>
>>things that you need help with, please submit them to the James project
>
> with
>
>>a [DOCUMENTATION] prefix on the subject. The more contributions, the
>
> better
>
>>the user documentation will get.
>>
>>I don't supposed anyone on the list is a tech writer, eh? :-)
>>
>>I'll post up an example of multiple mailing lists so that people can see
>>what needs to be done for EACH new mailing list. The current
>
> documentation
>
>>isn't clear on that (in fact, mine works but perhaps I missed a point).
>
>
> On the Cocoon project, we have already done this.
>
> We started asking to commit doc stuff with [DOCS], then we moved to
> asking to put them in Bugzilla.
>
> Finally we set up a Wiki, and this last solution brought us more
> documentation inh a week than the other two in a month!
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: James End User Documentation
Posted by "Noel J. Bergman" <no...@devtech.com>.
Nicola,
Assuming that folks vote for a wiki, can we set one up on apache, or did
this require a server elsewhere?
I like wikis. Been running vqWiki on several projects.
--- Noel
-----Original Message-----
From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
Sent: Monday, August 19, 2002 15:25
To: James Developers List
Subject: Re: James End User Documentation
Noel J. Bergman wrote:
>>solicit away.
>
>
> 1. Can we agree on some [DOCUMENTATION] prefix that people can use, so
that
> documentation submissions can be located in the archives?
>
> 2. How's:
>
> If you have James related tips, documentation bits, or just questions
about
> things that you need help with, please submit them to the James project
with
> a [DOCUMENTATION] prefix on the subject. The more contributions, the
better
> the user documentation will get.
>
> I don't supposed anyone on the list is a tech writer, eh? :-)
>
> I'll post up an example of multiple mailing lists so that people can see
> what needs to be done for EACH new mailing list. The current
documentation
> isn't clear on that (in fact, mine works but perhaps I missed a point).
On the Cocoon project, we have already done this.
We started asking to commit doc stuff with [DOCS], then we moved to
asking to put them in Bugzilla.
Finally we set up a Wiki, and this last solution brought us more
documentation inh a week than the other two in a month!
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: James End User Documentation
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Noel J. Bergman wrote:
>>solicit away.
>
>
> 1. Can we agree on some [DOCUMENTATION] prefix that people can use, so that
> documentation submissions can be located in the archives?
>
> 2. How's:
>
> If you have James related tips, documentation bits, or just questions about
> things that you need help with, please submit them to the James project with
> a [DOCUMENTATION] prefix on the subject. The more contributions, the better
> the user documentation will get.
>
> I don't supposed anyone on the list is a tech writer, eh? :-)
>
> I'll post up an example of multiple mailing lists so that people can see
> what needs to be done for EACH new mailing list. The current documentation
> isn't clear on that (in fact, mine works but perhaps I missed a point).
On the Cocoon project, we have already done this.
We started asking to commit doc stuff with [DOCS], then we moved to
asking to put them in Bugzilla.
Finally we set up a Wiki, and this last solution brought us more
documentation inh a week than the other two in a month!
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>