Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
The docs will be the ones generated by forrest.
+1 for b) as well.
max
Ross Gardler wrote:
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
+1 for b too.
For __future__ releases, we will have a third option:
c) include the forrest block and cocoon docs configuration files
-1 for this, although
hepabolu wrote:
Ross Gardler wrote:
...
For __future__ releases, we will have a third option:
c) include the forrest block and cocoon docs configuration files
-1 for this, although it should be moved to another thread.
I don't think it's a good idea to give all users access to the
Ross Gardler wrote:
In this way people only see what either we want them to see, or they
choose to see. This is akin to users only having access to the bundled
docs in a release, but devs having access to the development docs in SVN.
True, but if we point the users to the cocoon.zones site
hepabolu wrote:
Ross Gardler wrote:
In this way people only see what either we want them to see, or they
choose to see. This is akin to users only having access to the bundled
docs in a release, but devs having access to the development docs in SVN.
True, but if we point the users to the
Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
+1 for b). I myself
Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
-0, mostly because we're trying to slim down the core
b) Provide a
On Wed, 2005-10-19 at 19:27 +0200, Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs
Le 19 oct. 05, à 19:27, Carsten Ziegeler a écrit :
Ok, I think it's safer to just vote on this as well - again the
majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
-0
b) Provide a separate docs package
On 19.10.2005 19:27, Carsten Ziegeler wrote:
b) Provide a separate docs package to download
+1
Jörg
Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
The docs will be the
Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
+1 for b)
For
Carsten Ziegeler wrote:
b) Provide a separate docs package to download
+1
On Oct 19, 2005, at 10:27 AM, Carsten Ziegeler wrote:
b) Provide a separate docs package to download
+1
Carsten Ziegeler wrote:
b) Provide a separate docs package to download
+1
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
The docs will
16 matches
Mail list logo
