The first step consists in sending a project proposal to the
taglibs-dev mailing list.
The project proposal must include the following 4 sections:
I) Motivation
Why is this tag library useful? What specific problem does it solve?
II) Overview
Present the main use cases for the tag library, along with
sample JSP code.
III) Requirements
Specify the JSP version the proposal targets, as well as its dependencies
(JDK, other projects, etc.).
IV) Commitment
State your level of commitment.
The assumption is that whoever submits a tag library for consideration
will be willing to assume the role of committer to support the library.
As a guideline for sections I and II, you may want to refer to the
JSTL specification (section 2.1 - How Actions are Documented)..
The project should be made available as a compressed file either publicly
through a URL, or if a public URL is not available, sent directly to anyone requesting it to the submitter.
If a project is accepted for inclusion in the sandbox, it must comply
with the release framework used at Jakarta Taglibs and described
in the document Adding a Tag Library.
Developers should also be familiar with
the guidelines described in Taglib Developer Guidelines.
|