Peter Donald wrote:
Forrest, we are talking about Forrest. And Forrest is really simple to use, not complex.On Fri, 27 Dec 2002 23:41, Nicola Ken Barozzi wrote:You recall incorrectly. I would oppose dropping the ability to use anakia or whatever because those tools are much simpler and majority of our docs do not require complexities of cocoon.Paul Hammant wrote:Folks, Have we chosen a xdocs->html technology for the avalon-site depot? Forrest, Anakia, Cocoon?Given that Forrest is to prefer to plain Cocoon since it's Cocoon based but tailored for our use, and that the only one holding back IIRC on Anakia has since then decided to use Forrest (see Phoenix docs), I'd choose Forrest.
I would be happy to see our complex doc processes (ie phoenix/framework) use forrest because they can benefit from the power.Forrest is not more complex to use. So it isn't at all related with maintainability with regards to this aspect.
However I notice that our doc builds are still not being maintained in any way shape or form and our website is still screwed in places ... Is it just me or would anyone else like to see them being maintained before any effort at changing to a more complex system that will take even more effort to maintain?
On the contrary, if we move all docs to the *same* format and buildtool, it will certainly be easier to maintain.
Finally, I'd like to comment about our documentation system fragmentation, that started IIRC when you started using Anakia.
You have always had a "Just Do It" attitude on it. There was an interesting discussion on the community list about it, and here is part of it. IMHO it shows how not having consensus about doc generation is a barrier to keeping it maintained by others.
> On Wed, Jan 08, 2003 at 02:17:38PM -0500, Noel J. Bergman wrote:
>
>>"Just Do It" is a great ad slogan, but it doesn't seem to me to
>>always be the appropriate model for group projects.
[...]
> On Wed, Jan 08, 2003 at 02:17:38PM -0500, Noel J. Bergman wrote:
>
>> Yes, it makes things happen. But
>> when people are actively discussing an issue of communal interest,
>> it makes sense to me that the issue be discussed, various ways
>> to doing something examined, tradeoffs weighed, and then execute
>> a change based upon some concensus. Otherwise, when more than
>> one person cares about a subject, "Just Do It" results in
>> one person's vision being realized, and a cycle of
>> potentially conflicting changes necessary to stablize the code.
[...]
Greg Stein wrote:
> a "just do it" attitude can be totally inconsiderate towards your
> peers. "I don't care about your opinion, I'm just getting it done."
> It certainly doesn't help foster a community based on mutual respect.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
