Derek Hohls wrote:
Reinhard
The broad structure seems fine; and I think the brutus
site should reflect this i.e. there is currently a
'Tutorial', 'Documentation' and 'Blocks' tabs; maybe
add/change these to :
'Getting Started','Tutorials', 'Reference Docs' (with
blocks being a subtopic under
Reinhard Poetz wrote:
Upayavira and I rewored the ref docs so that they reflect Cocoon 2.2
and not a mixture of Cocoon 2.0 and Cocoon 2.1
uups, strange typo: read reworked instead of rewored
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open
avr. 05, à 19:44, Nicolas Maisonneuve a écrit :
...I would like to know the state of the documentation effort...
There's some info at http://wiki.apache.org/cocoon/22NewDocuments,
including a how can you help section.
The existing 2.1 docs are being moved to a legacy tab in the new docs
(see
Upayavira
Is there any possibility of putting drafts of the new framework
on the Wiki (perhaps with notifications of major updates on
the mailing lists)? - I think this is the easiest and fastest way to
get people's comments.
Thanks
Derek
[EMAIL PROTECTED] 2005/04/12 09:37:45 PM
Sebastien
Derek Hohls wrote:
Upayavira
Is there any possibility of putting drafts of the new framework
on the Wiki (perhaps with notifications of major updates on
the mailing lists)? - I think this is the easiest and fastest way to
get people's comments.
See
- general information
Reinhard
This looks good - what still seems to be missing is an
overall information structure - the wood and not the
trees - for me, assessing the detail is much easier if
I can see the big picture. I also think it makes it easier
to see if new pages eg. from the wiki, need to be added
in to
Derek Hohls wrote:
Reinhard
This looks good - what still seems to be missing is an
overall information structure - the wood and not the
trees - for me, assessing the detail is much easier if
I can see the big picture. I also think it makes it easier
to see if new pages eg. from the wiki, need to
Reinhard
The broad structure seems fine; and I think the brutus
site should reflect this i.e. there is currently a
'Tutorial', 'Documentation' and 'Blocks' tabs; maybe
add/change these to :
'Getting Started','Tutorials', 'Reference Docs' (with
blocks being a subtopic under Reference Docs
Hy,
I would like to know the state of the documentation effort.
Actually I'm afraid that after the development the new documentation
system (another excuse for not beginning the documentation ;-)) ,
there won't be a real effort to build a new documentation (= all
committers will stop to code et
both dev and doc mail lists as
it's a matter of coordinating both kinds of efforts.
But maybe this organization still exists... Does it ?
On Apr 12, 2005 12:44 PM, Nicolas Maisonneuve [EMAIL PROTECTED] wrote:
Hy,
I would like to know the state of the documentation effort.
Actually I'm afraid
Nicolas Maisonneuve wrote:
Hy,
I would like to know the state of the documentation effort.
Actually I'm afraid that after the development the new documentation
system (another excuse for not beginning the documentation ;-)) ,
there won't be a real effort to build a new documentation (= all
newbies
are a little... chomping at the bit !
On Apr 12, 2005 1:31 PM, Reinhard Poetz [EMAIL PROTECTED] wrote:
Nicolas Maisonneuve wrote:
Hy,
I would like to know the state of the documentation effort.
Actually I'm afraid that after the development the new documentation
system (another
Le 12 avr. 05, à 19:44, Nicolas Maisonneuve a écrit :
...I would like to know the state of the documentation effort...
There's some info at http://wiki.apache.org/cocoon/22NewDocuments,
including a how can you help section.
The existing 2.1 docs are being moved to a legacy tab in the new docs
Sebastien Arbogast wrote:
It's always the same paradox : the people who need documentation the
most, are the ones that are less qualified to participate in its
writing, otherwise they wouldn't need documentation. For Cocoon
experts, it's a matter of realizing that you can code marvelous
features,
Sebastien Arbogast wrote:
And this is a debate that would fit both dev and doc mail lists as
it's a matter of coordinating both kinds of efforts.
We don't discuss on the docs mailing lists.
Its purpose is supposed to be for the Wiki diff
autmoted notifications.
The docs discussion is
Ok thanks for the information I didn't know that. I supposed that docs
mailing list was for discussion regarding documentation effort and so
I just wanted to explain why it was worth discussing that out of this
list. But obviously I was wrong.
Anyway I've subscribed to all Cocoon lists to see if I
Le 13 avr. 05, à 05:15, Sebastien Arbogast a écrit :
Ok thanks for the information I didn't know that. I supposed that docs
mailing list was for discussion regarding documentation effort...
It was when it was created, but we felt that separating the (mostly
inexistent) docs team from the rest
17 matches
Mail list logo
