Following up briefly...
As Ted says. In addition, if your 'project' is a taglib, you can just
fold it into jakarta-taglibs without having to create a new jakarta
project. As I've seen it, that part of the process involves discussing
the taglib functionality in the mailing list and showing enough of your
taglib (possibly with pointers to the code elsewhere) to get approval
from within the taglib community.
The jakarta-taglibs process possibly needs to become a bit more formal
and explicit, but from the beginning the intention of jakarta-taglibs
was to hold multiple tag libraries, and although there is a natural
desire for the libraries to build on each other and to have some
consistency, that is not necessarily so. Experience seems to show that
the libraries tend to become consistent, though, through a natural
process of building up synergy and minimizing development cost.
My .5 cents,
- eduard/o
Ted Husted wrote:
>
> "Ward, Jeff" wrote:
> > I have a taglib / project that my company has been working on that I would
> > like to open source. Before the decision to release any source code for the
> > project is made I need to gather all the legal info for my company. I
> > scanned the Apache site but all I found was the Apache Constitution and
> > Project Guidelines. Is there anything more? I would be looking for the rules
> > regarding use of the code, modification and distribution, liability, etc.
> > Any suggestions of where to find this? Also, what is the process for
> > proposing a new project?
>
> The legalities are all covered by the Apache Software License
>
> < http://apache.org/LICENSE >
>
> Basically, the deal is that you donate the code to the Apache Software
> Foundation, who then accepts the liabilities, holding you harmless.
>
> The Jakarta project is designed to provide a place where your donated
> code can be distributed and maintained by a team of volunteers, so that
> the codebase can live on even if you go on to something else ;-)
>
> > Now on another note... This library contains pure view logic tags, its
> > aim is to allow for a clean abstraction of view from model/business logic.
> > It does this, I feel, in a fundamentally different way to systems such as
> > Struts and the J2EE MVC pattern. (I believe it implements MVC in a much
> > cleaner way, like struts, by allowing multiple named signals as opposed to
> > the J2EE's one signal, post.) Being a framework I don't know where to put
> > it. It contains several sub groupings of functionality that come together as
> > the framework but are viable on their own as well. If it was accepted, where
> > should it go? Here? A main project? Some other open-source initiative? Any
> > suggestions on this front would be greatly appreciated.
>
> Actual Jakarta subprojects can be proposed to the jakarta-general list.
> The process is outlined at <
> http://jakarta.apache.org/site/management.html > at the bottom.
>
> If you were able to make the code available in some way, it would be
> easier to determine where it would fit within Jakarta.
>
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Custom Software ~ Technical Services.
> -- Tel 716 737-3463.
> -- http://www.husted.com/about/struts/
