[Fwd: [VOTE] Tapestry / Incubator]

2002-12-29 Thread Sam Ruby
+1 on accepting Tapestry as a Jakarta subproject under the mentorship of 
Andy Oliver, conditional upon successful incubation.

Next steps would be identifying the list of initial committers, cvs 
tree(s), and mailing list(s).  But this can wait until the incubator PMC 
signs off on the subproject.

 Original Message 
Subject: [VOTE] Tapestry / Incubator
Date: Sun, 29 Dec 2002 11:35:31 -0500
From: Howard M. Lewis Ship [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Tapestry Contrib [EMAIL PROTECTED]
CC: Rodent of Unusual Size [EMAIL PROTECTED], [EMAIL PROTECTED], 
 Jakarta Project Management Committee List [EMAIL PROTECTED]
References: 005001c2ada2$e6846a20$3dc41e42@howardczkz2sl3

Ok, all the votes are in, except for Mind Bridge who I believe is
travelling.  Not unexpected, all the votes were +1.

Once again, we've voted to go forward and move Tapestry towards Jakarta, 
via Incubator.

We're eagerly awaiting word from Jakarta about what the next steps 
should be.

I've attached the proposal again, for reference.  Although we have to
migrate in through the Incubator, it looks like the proposal does not 
need to be changed.



- Original Message -
From: Howard M. Lewis Ship [EMAIL PROTECTED]
To: Tapestry Contrib [EMAIL PROTECTED]
Sent: Friday, December 27, 2002 7:24 AM
Subject: [Tapestry-contrib] [VOTE] Tapestry / Incubator


 As Andrew has pointed out, the roadmap into Jakarta is in transition.
Looks
 like Tapestry gets to be the first project through the Incubator.

 Anyway, I believe this is more of a correction than a change of course,
but
 deserves a vote anyway.

 Howard Lewis Ship +1


 - Original Message -
 From: Andrew C. Oliver [EMAIL PROTECTED]
 To: Tapestry Contrib [EMAIL PROTECTED]; Jim
 Jagielski [EMAIL PROTECTED]; [EMAIL PROTECTED]; Jakarta Project
 Management Committee List [EMAIL PROTECTED];
 [EMAIL PROTECTED]
 Sent: Monday, December 23, 2002 10:09 PM
 Subject: [Tapestry-contrib] Apache Proposal AGAIN


  Hi All,
 
  The process for accepting a project into Apache has changed.  Now all
  projects need to go through the Incubator
  [http://incubator.apache.org].  It is my opinion that this project
  already meets the criteria for acceptance into Jakarta
  however, the Apache board has added this step as a gate between 
here and
  Jakarta.
 
  I suspect the incubation period will be short.  There is a catch.  We
  will still have to apply to Jakarta after the incubation and
  the process for incubation is not very well defined.  There will be a
  number of bumps in the road and issues to be addressed.
 
  However, I have the utmost confidence in this community and your talent
  and abillity to work together and make decisions.
  I am positive that this will be a fine addition to Apache in the 
end, in
  particular Jakarta.
 
  With that being said, please consider this issue and signify whether I
  should move forward with submitting the proposal to the
  incubator.
 
  Thanks,
 
  -Andy
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Tapestry-contrib mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/tapestry-contrib
 



 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Tapestry-contrib mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/tapestry-contrib


[0] rationale

Tapestry, currently housed at the SourceForge (http://tapestry.sf.net), is a 
component-based web application framework.  Tapestry falls generally into the pull-MVC 
model of development.

Tapestry is designed specifically around the creation of completely re-usable 
components.  Components can easily be packaged into libraries and distributed within 
Jar files, even when they contain assets such as image files and stylesheets.

Tapestry is organized around an abstraction that isolates application-specific logic 
from the details of the servlet API, such as HttpSession, request, response, URLs and 
query parameters.

Tapestry is highly pluggable, allowing any and all behavior to be customized by 
subclassing appropriate base classes.

Tapestry is specifically not a JSP taglib.  Tapestry uses its own method for 
instrumenting HTML that is extremely non-obtrusive (it still previews properly in a 
WYSIWYG editor).  Tapestry has well specified, separate roles for HTML producers and 
Java developers, and allows them to work together without interfering with each other.

The goal of Tapestry is to shift much of the burden of developing web applications 
onto the framework, and free the developer to work cleanly and effectively without 
concern for the many small details of web application development.  The primary 
function of 

Re: [Fwd: [VOTE] Tapestry / Incubator]

2002-12-29 Thread Andrew C. Oliver
Note a correction: dIon Gillard  also agreed to be a sponsoring member.

Those things are listed in the proposal which is posted here:

http://nagoya.apache.org/wiki/apachewiki.cgi?TapestryProposal

-Andy

Sam Ruby wrote:


+1 on accepting Tapestry as a Jakarta subproject under the mentorship 
of Andy Oliver, conditional upon successful incubation.

Next steps would be identifying the list of initial committers, cvs 
tree(s), and mailing list(s).  But this can wait until the incubator 
PMC signs off on the subproject.

 Original Message 
Subject: [VOTE] Tapestry / Incubator
Date: Sun, 29 Dec 2002 11:35:31 -0500
From: Howard M. Lewis Ship [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Tapestry Contrib [EMAIL PROTECTED]
CC: Rodent of Unusual Size [EMAIL PROTECTED], [EMAIL PROTECTED], 
 Jakarta Project Management Committee List [EMAIL PROTECTED]
References: 005001c2ada2$e6846a20$3dc41e42@howardczkz2sl3

Ok, all the votes are in, except for Mind Bridge who I believe is
travelling.  Not unexpected, all the votes were +1.

Once again, we've voted to go forward and move Tapestry towards 
Jakarta, via Incubator.

We're eagerly awaiting word from Jakarta about what the next steps 
should be.

I've attached the proposal again, for reference.  Although we have to
migrate in through the Incubator, it looks like the proposal does not 
need to be changed.



- Original Message -
From: Howard M. Lewis Ship [EMAIL PROTECTED]
To: Tapestry Contrib [EMAIL PROTECTED]
Sent: Friday, December 27, 2002 7:24 AM
Subject: [Tapestry-contrib] [VOTE] Tapestry / Incubator


 As Andrew has pointed out, the roadmap into Jakarta is in transition.
Looks
 like Tapestry gets to be the first project through the Incubator.

 Anyway, I believe this is more of a correction than a change of course,
but
 deserves a vote anyway.

 Howard Lewis Ship +1


 - Original Message -
 From: Andrew C. Oliver [EMAIL PROTECTED]
 To: Tapestry Contrib [EMAIL PROTECTED]; Jim
 Jagielski [EMAIL PROTECTED]; [EMAIL PROTECTED]; Jakarta Project
 Management Committee List [EMAIL PROTECTED];
 [EMAIL PROTECTED]
 Sent: Monday, December 23, 2002 10:09 PM
 Subject: [Tapestry-contrib] Apache Proposal AGAIN


  Hi All,
 
  The process for accepting a project into Apache has changed.  Now all
  projects need to go through the Incubator
  [http://incubator.apache.org].  It is my opinion that this project
  already meets the criteria for acceptance into Jakarta
  however, the Apache board has added this step as a gate between 
here and
  Jakarta.
 
  I suspect the incubation period will be short.  There is a 
catch.  We
  will still have to apply to Jakarta after the incubation and
  the process for incubation is not very well defined.  There will be a
  number of bumps in the road and issues to be addressed.
 
  However, I have the utmost confidence in this community and your 
talent
  and abillity to work together and make decisions.
  I am positive that this will be a fine addition to Apache in the 
end, in
  particular Jakarta.
 
  With that being said, please consider this issue and signify 
whether I
  should move forward with submitting the proposal to the
  incubator.
 
  Thanks,
 
  -Andy
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Tapestry-contrib mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/tapestry-contrib
 



 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Tapestry-contrib mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/tapestry-contrib




[0] rationale

Tapestry, currently housed at the SourceForge (http://tapestry.sf.net), is a component-based web application framework.  Tapestry falls generally into the pull-MVC model of development.

Tapestry is designed specifically around the creation of completely re-usable components.  Components can easily be packaged into libraries and distributed within Jar files, even when they contain assets such as image files and stylesheets.

Tapestry is organized around an abstraction that isolates application-specific logic from the details of the servlet API, such as HttpSession, request, response, URLs and query parameters.

Tapestry is highly pluggable, allowing any and all behavior to be customized by subclassing appropriate base classes.

Tapestry is specifically not a JSP taglib.  Tapestry uses its own method for instrumenting HTML that is extremely non-obtrusive (it still previews properly in a WYSIWYG editor).  Tapestry has well specified, separate roles for HTML producers and Java developers, and allows them to work together without