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: local policy)
Message-ID: <54778.165.98.153.184.1110991045.squirrel@www.agssa.net>
In-Reply-To: <42385C26.6030407@nada.kth.se>
References: <4236A792.2020800@apache.org>      
    <52dc9a7562eb21a6c1b5122368bde425@apache.org>      
    <20050316003824.GE17237@igg.indexgeo.com.au>      
    <4237E1BE.70009@apache.org>      
    <08be1861ca697d2419145a3c579f09f7@apache.org>      
    <4237EE7A.1080201@apache.org>      
    <81b3db074894d1f651b7d5dbcff475b6@apache.org>      
    <4237FC3C.4090505@apache.org> <423824B9.5020801@reverycodes.com>      
    <423825BF.4090109@apache.org> <20050316134610.GC23086@localhost>      
    <42383B6B.70005@reverycodes.com> <423841D8.1090102@nada.kth.se>   
    <53310.165.98.153.184.1110987915.squirrel@www.agssa.net>   
    <423857E3.6040506@nada.kth.se>
    <54204.165.98.153.184.1110989258.squirrel@www.agssa.net>
    <42385C26.6030407@nada.kth.se>
Date: Wed, 16 Mar 2005 10:37:25 -0600 (CST)
Subject: Re: Supported and unsupported blocks
From: "Antonio Gallardo" <agallardo@agssa.net>
To: dev@cocoon.apache.org
User-Agent: SquirrelMail/1.4.3a-6.FC2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

On Mie, 16 de Marzo de 2005, 10:17, Daniel Fagerstrom dijo:
> Everything can be done in numerous ways.
>
> The directory structure is easy to understand, it is what we have
> discussed at the list for quite a while, it is what Reinhard actually
> have implemented and above all it moves us forward.
>
> There should of course be a metadata file for the block as well and
> documentation generated from that. But AFAIK no one have started to work
> on any such documentation functinonallity. So for the moment I think we
> should focus on the *important* question:
>
> Which blocks do we support?

Well, this is a hard question. I read all the mails related to this topic
and still I don't have a decision:

1-"The blocks used for my company will be supported by me". I guess every
committer already did that. So I don't see here a problem, but.....

2-"Blocks not used by 'me', but are interesting or have big potential
success". This is the hard question. How I can know if a block has
potential success between people?. Even we know that cocoon has potential,
but a lot of people don't use it. I hope this illustrate what I have in
mind.

In my case, in the first fill of the wiki Block poll, I added some blocks
that I don't need for my work and never used it, but I found interesting
and already worked on them just for fun. For example, qdox.

In the second raid, I checked other blocks where I already worked outside
my own interests, just for the community follwing some bugzilla reports
and I hope I can use some time in the future to support in this way again.

I know we have a problem, people wants to drops some blocks from his own
POV. But perhaps this blocks are used by other people.

Best Regards,

Antonio Gallardo.