On 8/25/05, ir. ing. Jan Dockx <[EMAIL PROTECTED]> wrote:

> Trust me, I love the work you're doing. And I don't want to make
> enemies.

I'm standing on the sidelines on this particular issue, but it is
worth making a point here ... people who end up making major
contributions to the open source community tend not to pay any
attention to "we've always done it this way" sorts of limitations, and
go do their own thing.  In the context of the current discussion, you
are making a *horrendously* incorrect assumption.  Why do you *care*
if the existing MyFaces developers think a wiki is the right way to
accumulate sufficient useful documentation in the short term?

Just do it.

If your idea works ... that is, we see MyFaces users gather together
and actually create significant quantities of documentation of
significant quality, the very concept will catch on like wildfire. 
>From what I know of the PHP community, this certainly seems to be
possible.  On the other hand, if nobody contributes, you will have
turned out to be one of the many idealists who have a great idea for
what someone *else* should do, but nobody else buys in to doing the
actual grung work.

The assumption that whatever user-developed wiki based documentation
*must* be blessed by the MyFaces developers as "official" is
ridiculous -- *please* go create the documentation that you, and other
MyFaces users, need!!!!!   I can vouch for the fact that the MyFaces
developers are "smarter than the average bear" (yes, dating myself to
Yogi Bear cartoons :-).  If what you create causes a groundswell of
participation, the MyFaces developers would be foolish to ignore it.

On the other hand, maybe nobody else other than you actually cares
enough to contrbute to this effort.  Then, it's perfectly legitimate
for the MyFaces developers to switch over to a totally different (yes,
still US-centric :-) TV commercial paradigm, and ask "where's the
beef?"

For the last year or so, I've taken on the personal mantra (related to
open source involvement) that "code speaks louder than words".  In the
global context of making open source a globally used technology,
documentation is at *least* as important as code.

So, where's the beef?

Craig McClanahan

Reply via email to