[Docutils-develop] Building the Docutils community

[David G. <go...@py...>]

I came across this thought-provoking quote via an article found on Slashdot:

    Anyway, it's an design pattern: "good ideas and bad code build
    communities, the other three combinations do not". This is
    extremely hard to understand, it's probably the most
    counter-intuitive thing about open source dynamics.

    Stefano Mazzocchi,
<http://archives.real-time.com/pipermail/cocoon-devel/2000-October/003023.ht
ml>

In order to build a more active community around Docutils, should I be
writing sloppier code?  I can see the relation: bad code in a good
project generates bug reports and patches from potential contributors,
and provides a gradual path to greater involvement.

Or is my code bad enough already?

;)

-- 
David Goodger  <go...@py...>  Open-source projects:
  - Python Docutils: http://docutils.sourceforge.net/
    (includes reStructuredText: http://docutils.sf.net/rst.html)
  - The Go Tools Project: http://gotools.sourceforge.net/