[RESULT] Re: [VOTE] Accept Click for Incubation
And the results are in: +1 Alan D. Cabrera (*) Andrus Adamchik Bertrand Delacretaz (*) Davanum Srinivas (*) Eelco Hillenius Henning Schmiedehausen (*) Jim Jagielski (*) Les Hazlewood Martijn Dashorst (*) Niall Pemberton (*) Niklas Gustavsson Siegfried Goeschl Ted Husted (*) Will Glass-Husain William A. Rowe (*) (* == Incubator PMC) Note: Andrus and Will have requested to join the Incubator PMC but were no IPMC members at the time when they voted. 0: none -1: none Congratulations to the Click team, you have been accepted to the Incubator as a podling. Ciao Henning On Mon, 2008-07-14 at 13:14 +0200, Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-dev * click-private == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project
Re: [RESULT] Re: [VOTE] Accept Click for Incubation
That is great news, thanks for your support. regards Malcolm Edgar On Mon, Jul 21, 2008 at 7:42 PM, Henning Schmiedehausen [EMAIL PROTECTED] wrote: And the results are in: +1 Alan D. Cabrera (*) Andrus Adamchik Bertrand Delacretaz (*) Davanum Srinivas (*) Eelco Hillenius Henning Schmiedehausen (*) Jim Jagielski (*) Les Hazlewood Martijn Dashorst (*) Niall Pemberton (*) Niklas Gustavsson Siegfried Goeschl Ted Husted (*) Will Glass-Husain William A. Rowe (*) (* == Incubator PMC) Note: Andrus and Will have requested to join the Incubator PMC but were no IPMC members at the time when they voted. 0: none -1: none Congratulations to the Click team, you have been accepted to the Incubator as a podling. Ciao Henning On Mon, 2008-07-14 at 13:14 +0200, Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-dev * click-private == Subversion Directory == Migrate the current subversion code from sourceforge
Re: [RESULT] Re: [VOTE] Accept Click for Incubation
On Jul 21, 2008, at 12:42 PM, Henning Schmiedehausen wrote: Note: Andrus and Will have requested to join the Incubator PMC but were no IPMC members at the time when they voted. I can vote one more time with my IPMC member hat on ;-) Not that we don't have enough votes. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Click for Incubation
+1 Craig On Jul 14, 2008, at 4:14 AM, Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = Craig L Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
[VOTE]: Buildr 1.3.2 release
Up for vote, the Buildr 1.3.2 release. The release vote passed within the PPMC with +3 (+5 including non-binding votes) and no -1: http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/[EMAIL PROTECTED] We're voting on the source distributions available here: http://people.apache.org/~assaf/buildr/1.3.2/distro/ Specifically: http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip The documentation generated for this release is available here: http://people.apache.org/~assaf/buildr/1.3.2/site/ http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdf The official specification against which this release was tested: http://people.apache.org/~assaf/buildr/1.3.2/site/specs.html Changes since 1.3.1: * Added: --prereqs command line argument to show all tasks and their dependencies. You can also follow with regular expression to narrow down the list of tasks. * Changed: Upgraded to Rubyforge 1.0.0. * Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems. * Changed: BUILDR-88 Test classes/resources should come before compile classes/resources so they load up earlier in java classpath. * Changed: BUILDR-102 Update JUnit Version to 4.4. * Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the sources paths. * Fixed: BUILDR-76 Added more specs and fixes to compile task. * Fixed: BUILDR-77 Layout feature not working. * Fixed: BUILDR-79 Remove :source option for Scala compiler * Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon. * Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to load Pageant DLLs when running on JRuby/Windows. * Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include abstract classes. * Fixed: BUILDR-90 Installing from source doesn't work with JRuby. * Fixed: BUILDR-91 When doing a release, buildr should spawn the same version of buildr * Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath. * Fixed: BUILDR-95: Only download Scala test framework artifacts when required * Fixed: BUILDR-100 Directory structure documentation needs updating. * Fixed: Installation instructions updated for RubyGems 1.2.0. Assaf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jt Pattern Oriented Framework (looking for champion/mentors)
Hi folks, We've put together a draft proposal for the Jt pattern Oriented Framework. I hope it answers some of the questions regarding project status, community, licensing, etc. Regards, Ed Jt Pattern Oriented Framework Introduction This proposal describes a Pattern Oriented Framework for the rapid implementation of Java applications. This integrated framework is based on a messaging architecture which provides strong encapsulation and loose coupling; framework components can be interchangeably plugged into complex framework applications using a “Lego approach. This framework provides capabilities for the implementation of applications based on design patterns. The framework itself is conceived, from the ground up, based on design patterns. Jt is probably one of the first Pattern Oriented Frameworks (open source). Goals The framework addresses the following goals: A) The pattern oriented framework implements and/or facilitates the implementation of well-known design patterns like Gang Of Four design patterns (GoF) and J2EE Design patterns. The framework itself is conceived and implemented based on design patterns (from the ground up). The framework also facilitates and accelerates the implementation of applications based on design patterns. B) The framework architecture is based on a messaging design pattern: framework objects are able to interchange information and perform computations by sending, receiving and processing messages. A messaging API provides strong encapsulation and loose coupling; framework components can be interchangeably plugged into complex framework applications using a “lego/messaging” architecture. The framework takes full advantage of the power and simplicity of the messaging design pattern/API. C) The framework lego/messaging architecture provides transparent access to remote components: remote framework objects are treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) make this possible by hiding the complexities associated with remote APIs. D) The framework provides transparent integration with other technologies via framework adapters, proxies and the implementation of related design patterns. These technologies include BPM, Data Access Object implementations (DAO), Model View Controller implementations (MVC), EJBs, AJAX, JMS, XML and Web Services. E) The framework is designed to be lightweight and fast (low overhead/small footprint). F) The framework messaging/lego architecture should improve and simplify design/development efforts. There should be a tight correspondence between UML design diagrams and the framework messaging based applications and components needed for the implementation. The framework should provide wizards and automated capabilities for generating framework applications. Framework components should be easily added to BPM process diagrams. In future versions of the framework, it should be possible for application modules to be generated directly from the UML design diagrams. This goal is still work in progress. There is an early version of the Jt Wizard. G) The framework messaging architecture facilitates testing and debugging efforts. It provides capabilities for testing components as independent units by sending messages to the component and verifying the expected reply messages.. H) In order to provide additional productivity, the framework has been integrated with open source IDEs. Criteria Current Status The current release of the framework (2.6) meets most of the goals outlined above. Item F is still work in progress. The software base is very stable (production quality). Several production applications have been built based on the Jt framework. Documentation, reference framework applications and examples are available. Meritocracy Meritocracy will be fostered and encouraged within the project. We will follow the guidelines of the Apache Software Foundation. Community contributions and feedback are always welcome.We also plan to actively encourage individuals to get involved in the project and be recognized based on Merit. Community One of the next objectives is to continue growing an active community of users and contributors. It is expected that community will continue to grow. So far the main focus has been the completion of the core framework functionality. We see Jt becoming an ASF incubator project as a next step in its evolution. We plan to open the project to a wider audience in order to achieve a larger and more diverse community. Alignment Jt is aligned well with existing Apache projects and technologies. The framework has been integrated with several Apache technologies including Struts (MVC design pattern) and Axis (Web Services Adapter). The Jt automated Wizard capabilities has also been built based on Apache products. Known Risks Orphaned products: The projects has been
Re: Jt Pattern Oriented Framework (looking for champion/mentors)
David S (or rather Ed) wrote: Community One of the next objectives is to continue growing an active community of users and contributors. It is expected that community will continue to grow. So you already have an active community of users and contributors? Any public record of that? Names and/or numbers? Orphaned products: The projects has been growing as an open source project for several years. The team is committed to continue this work therefore the risk is fairly small. Names or numbers on the team? Public records of the growing? The CVS mails show no relevant activity before October 2007, nor afterwards. Homogenous developers: The people involved with the project work for several organizations who are geographically distributed across the world. The only account used on the project site is wwwfswcom, an obvious reference to a website that seems to belong to a software consulting company. Can you give some details on distributed across the world? Number of people by country or continent, for example? Reliance on salaried developers: This project does not rely on salaried contributors. They work on a volunteer basis. Is the above mentioned software consulting company aware of the fact that a diverse team of volunteers is indirectly referencing its website when releasing open source software? Project information and complete documentation/sources can be downloaded from http://jt.dev.java.net/. java.net forums and mailings lists are not used. So which forums and/or mailing lists do you use? As far as I can see you didn't use the CVS repo either, except for index.html and one drop of code in October 2007. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
