Re: Heads up on potential move for Taglibs

--0016e64f6a661501df046e966808
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Seems reasonable. Any idea what happens to commit rights?

On Sun, Jul 12, 2009 at 1:30 AM, Henri Yandell <[email protected]> wrote:

> Jakarta is a slowly dwindling project at Apache. A long time ago we
> agreed that its deep structure created isolated sub communities and
> Apache decided to become a flat organization. Thus for all projects in
> Jakarta there is the question of where to go.
>
> I've been floating the idea to Jakarta and Tomcat of moving the active
> parts of Taglibs over to Tomcat. This idea seems to be getting +1s on
> all sides. The general idea is:
>
> * Move Standard, JSTL implementation, over to Tomcat. 1.0 would be
> deprecated.
> * Move RDC over to Tomcat.
> * Start a new taglib (my new favourite name is Extended; ie: Apache
> Extended Taglib to complement the Apache Standard Taglib) that is
> built from the undeprecated parts of Taglibs that find favour. Some
> might be refactored from Taglibs to EL functions. Think the Commons
> Lang of Taglibs.
> * Other taglibs to be retired within Jakarta and make their way over
> to the Apache Attic.
>
> Hen
>

-- 
Kris Schneider <mailto:[email protected]>
directThought  <http://www.directThought.com/>

--0016e64f6a661501df046e966808--