Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of
 mark.leicester@efurbishment.com designates 80.79.129.131 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <20050316231911.GC20959@igg.indexgeo.com.au>
References: <42281CF4.9050907@apache.org> <422F2607.7040907@apache.org>
 <422F2E2A.9040600@upaya.co.uk> <423018A8.3070609@apache.org>
 <42301D78.60201@nada.kth.se> <4236A792.2020800@apache.org>
 <ebde2ec036542ea00e438efffa0f3dd6@apache.org>
 <20050316231911.GC20959@igg.indexgeo.com.au>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <f8add7381b8a7e5f3284da230c4ae1bf@efurbishment.com>
Content-Transfer-Encoding: 7bit
From: Mark Leicester <mark.leicester@efurbishment.com>
Subject: Re: Supported and unsupported blocks
Date: Wed, 16 Mar 2005 23:36:32 +0000
To: dev@cocoon.apache.org

Hi Jeremy (et al),

Ahem... If someone is prepared to nominate me as a committer I'll 
gladly support the midi block. :)

I must admit I haven't had a lot of requests for MIDI block support 
since I cobbled it together back in 2003, and neither have I extended 
it in any of the ways that I thought I might. Nevertheless, I would 
like to see it survive as an example of how much fun Cocoon can be.

Thanks guys, for encouraging enthusiasts like me to create Cocoon 
blocks - of all sorts! Long may it continue.

BTW Jeremy, I always meant to thank you for this feedback. :)
 > I just updated Cocoon, and took a wizz around the samples ....
 > In the MIDI section, I clicked on "A Short MIDI File", and it played 
in my browser =:-()
 > I NEARLY DROPPED MY CHIPS !!!!!
 > Well done!!!
(from http://www.mail-archive.com/dev@cocoon.apache.org/msg02395.html)

Take care everyone,
Mark

On 16 Mar 2005, at 23:19, David Crossley wrote:

> Jeremy Quinn wrote:
>>
>> Don't get me wrong, I am happy you are being pro-active about this.
>>
>> However, I see several items on the "unsupported" list which are IMHO
>> important components of Cocoon, or are blocks that I use regularly in
>> my work. eg. chaperon, jms, naming, repository, webdav, xmldb (and
>> others). In most cases, the fact that they do not currently have >2
>> supporters does not effect their quality and usefulness.
>>
>> On reviewing this list again, I see several blocks that I have worked
>> on that I probably should have put my name to, and I notice several
>> blocks that I know people actively care about, that they have not put
>> their name to.
>>
>> Maybe I misunderstand the purpose of having "supported" and
>> "unsupported" blocks, but I would hate to useful work being sidelined
>> by not attracting usage or new contributions.
>
> Thanks for raising these issues. I wrote a similar mail but didn't
> yet send it ...
>
> I am concerned about the signals that this classification,
> and listing of committers, sends for community-building.
>
> Here are some random thoughts - sorry no time ...
>
> Some blocks have no committers listed, e.g. midi, asciiart
> However, they probably don't need much maintenance, so why would
> they be listed as unsupported, or worse, moved offsite because it
> appears that no-one cares.
>
> I am not putting my name against any blocks, but that doesn't mean
> that i won't help with them. Whenever i make some spare time
> to attend to Bugzilla, i will work on patches for any block.
>
> We try not to mention specific committers names. In fact, we voted
> a while ago to remove author tags from code (but not yet done).
> We really don't want to encourage the community to contact individuals.
>
> --David
>