cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: [RT] Rules for adding blocks and functionality?
Date Mon, 24 Oct 2005 16:28:28 GMT
Upayavira wrote:
> No it wouldn't, because we wouldn't agree what should go there. My
> suggestion is to, as you did with the samples, leave all blocks as they
> are, and start _hightlighting_ the ones we consider to be best
> practices. Then, after some extended period if time we may decide to
> purge the ones that have not received any highlighting, but highlighting
> core blocks works much better than deprecating old blocks that people
> may be using.
> 
> (And by way of recommendation of this approach :-) this is the approach
> that Buddhists throughout the centuries used to deal with teachings that
> had grown stale. They didn't say "that is a bad teaching", they said,
> "hey, we've got a higher teaching".)
> 
> So, basically, until we've got blocks functioning, and have had them so
> for _some_ time, we should do nothing more than highlighting and marking
> up with meta-data for our blocks. Our blocks system and block repository
> is going to create a new organism (which, yes, could well want a contrib
> group elsewhere such as Niclas suggested), but I want to allow for that
> organism to grow, well, organically :-)

Amen!

Vadim

Mime
View raw message