Jeff wrote:
> Pc Design Manual - Overview
> 
> The Preface to the Manual says: The word "permaculture" can be used
> by anybody adhering to the ethics and principles expressed herein.
> The only  restriction on the use is that of teaching; only
> graduates of a Permaculture Institute can teach "permaculture", and they
> adhere to agreed-on curriculae developed by the college of Graduates
> of the institutes of Permaculture.

Scott Pitman's recent post to the Permaculture list (restating Bill's
copyright to the word Permaculture and the cirriculum laid out in the
manual) seemed to echo what Jeff has written.  I find if an obsticle to the
growth of permaculture as a design methodolgy.  I think it will, to some
degree, restrict the ability of permaculture to take on new ideas and adapt
to a changing society.  It also assumes that Bill had it all figured out.
Perhaps this is not relavent to this discussion, but I thought I'd throw it
out.


> My bias is that culture should be about half of a Pc Design manual
> and its absence is a huge hole.

Agreed.  There is also some discord between permaculture as a design system
and the emphasis on a huge variety of exanples of this design system
applied to different fields and situations.  This emphasis can easily lead
one away from permaculture as design to permaculture as a list of
technologies and techniques.

[Jeff wrote something along these lines: For me Pc is a way of thinking and
isn't greenhouses or gardens or any of the physical representations of ones
design.  If we focus totally on the results of design i think we will not
be talking about Pc.]

> Thoughts about the difference between a course and a discussion?

So far, it feels like a discussion.  As long as we don't get into listing
the ideas and explaining the principles (covered in the book), and stick to
observations about the book, I think this could continue as an interesting
discussion.  Of course, a "discussion" requires input from more than just
one, or even two, so I encourage all of you staying in the sidelines to get
in and enjoy the discussion.  We'd all like to hear your perspectives.
(Even if you have never had a course, or don't own the book.)  Without much
input it could get pretty dull.

Eric Storm

Reply via email to