You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Jesse Kuhnert <jk...@gmail.com> on 2006/02/20 18:27:23 UTC

Fwd: tapestry component sub-project

Oops...meant this to be on tapestry-dev .


---------- Forwarded message ----------
From: Jesse Kuhnert <jk...@gmail.com>
Date: Feb 20, 2006 12:26 PM
Subject: tapestry component sub-project
To: Tapestry users <ta...@jakarta.apache.org>

It has been voiced on a few occassions that an official tapestry sub-project
based around components and contributors to those components may be
beneficial.

I think it would be nice to have a project like this, it would allow
tapestry to have a clearer/safer feeling repository of components that are
community maintained, while also providing all of the valuable resources
that being a part of apache provides. It makes sense to have a sub-project
as well, because it would allow (in theory?) people to be voted in to the
sub-project as committers without going through as much red tape as might be
required to be on tapestr itself.

Is there a formal definition of how to propose something like this? Would it
more or less look similar to incubator proposals?

I'm thinking initially that I'd like to try and more or less move some of
the tacos stuff into this repository. Whatever developers feel like coming
along with me would be voted into this sub-project and we could start
building out an infrastructure. I think this would also involve trying to
reach out to some of the other component respositories and seeing if we
can't find a solution that fits all needs.

thoughts?

jesse