On 12/31/05, Craig L Russell <[EMAIL PROTECTED]> wrote: > I haven't been involved in any history here, so please forgive my naivete. > > I think I understand the rationale for developing spec jars here at Apache. > Please correct me if I'm wrong. In order to use a spec jar from the JCP, you > have to click a license every time you download it. And this can be a real > usability problem if every user of a project needs to manually download just > to click a license that they don't read anyway (oops, gotta stop that).
Yep. Some are a real pain to find too; jdbc-stdext-2.0.jar springs to mind :) > I doubt that there is enough in common among the spec jar developers to > build a community around "spec jars". But certainly there is a community > among the developers of Servlet and a different community among the > developers of JDO and a different community for MyFaces, etc. You need community for two parts: 1) Someone has to work on said website. 2) There needs to be a place for people to talk about said specs; not in terms of development, but in terms of "is anyone working on a Foo spec yet?", "here's a patch for the website" and "what's the best way for us to handle the naming scheme?". The apache-jcp website is well on the way to this [http://www.apache.org/jcp/]. In addition to a simple site, browseable spec javadoc and download links(ibiblio?) would be nicer than having to dig into the particular TLP that happened to develop the code. ---- Then we get onto the details: * Should the source be in a shared location, or in the original TLP. * Do we put it under JCP [ie: www.apache.org/jcp and [EMAIL PROTECTED] or Jakarta [ie: jakarta.apache.org/specs and [EMAIL PROTECTED] I'm +1 to either. [sales pitch :)] Really the second question is less about specs and more about whether/how we want a Java Federation at Apache. JCP is effectively the 'Java Community Process Federation at Apache', so it's natural that we'll have overlap issues between the two. This very conversation is an example of why I think we need a Java federation; we're using [EMAIL PROTECTED] to discuss the Apache Java strategy because there's nowhere else more fitting. [/sales pitch] I'm rambling a bit; hopped up on flu medication at the moment :) Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
