Re: [VOTE] Approval to release Apache Aries (Incubating) version 0.2-incubating
+1 (non binding) Regards JB On 08/31/2010 10:45 PM, zoe slattery wrote: The Aries community has voted on its second release. From the Aries home page: The Aries project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes. Aries is a multi-module project. The vote thread on aries-dev for RC05: http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/201008.mbox/%3c4c77e9ef.30...@gmail.com%3e concluded with 10 votes (all of them +1) three of which were binding IPMC votes from Jarek Gawor, Kevan Miller and Guillaume Nodet. The following Aries top level modules are staged and tagged in https://svn.apache.org/repos/asf/incubator/aries/tags/. There are 13 Aries modules in the release, staged as follows: Modules staged athttps://repository.apache.org/content/repositories/orgapachearies-113/ are: parent, eba-maven-plugin, testsupport, org.apache.aries.util,web. Links to the source releases are given below: https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/parent/0.2-incubating/parent-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/eba-maven-plugin/0.2-incubating/eba-maven-plugin-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/testsupport/testsupport/0.2-incubating/testsupport-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/org.apache.aries.util/0.2-incubating/org.apache.aries.util-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/web/web/0.2-incubating/web-0.2-incubating-source-release.zip Modules staged at https://repository.apache.org/content/repositories/orgapachearies-129/ are: quiesce, jndi, transaction, application, samples. Links to the source releases are given below: https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/quiesce/quiesce/0.2-incubating/quiesce-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/jndi/jndi/0.2-incubating/jndi-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/transaction/transaction/0.2-incubating/transaction-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/application/application/0.2-incubating/application-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/samples/samples/0.2-incubating/samples-0.2-incubating-source-release.zip Modules staged athttps://repository.apache.org/content/repositories/orgapachearies-138/ are: jpa https://repository.apache.org/content/repositories/orgapachearies-138/org/apache/aries/jpa/jpa/0.2-incubating/jpa-0.2-incubating-source-release.zip Modules staged athttps://repository.apache.org/content/repositories/orgapachearies-152/ are: blueprint https://repository.apache.org/content/repositories/orgapachearies-152/org/apache/aries/blueprint/blueprint/0.2-incubating/blueprint-0.2-incubating-source-release.zip Modules staged athttps://repository.apache.org/content/repositories/orgapachearies-153/ are: jmx https://repository.apache.org/content/repositories/orgapachearies-153/org/apache/aries/jmx/jmx/0.2-incubating/jmx-0.2-incubating-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-153/org/apache/aries/jmx/jmx/0.2-incubating/jmx-0.2-incubating-source-release.zip The RAT and IANAL build checks passed. The KEYS file located here: https://svn.apache.org/repos/asf/incubator/aries/KEYS contains the code signing key for myself, Zoe Slattery, the release manager for this release. We have 3 binding +1 IPMC votes on the aries-dev list, and I'm opening up this thread for 72 hours for any further feedback on the staged artifacts for release. Thank you, Zoë - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Isis to enter the incubator
The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). The intent of these projects was to demonstrate the pluggable nature of the framework. Both Naked Objects and its sister projects
Re: [VOTE] Isis to enter the incubator
+1 (binding) -Matthias On Wed, Sep 1, 2010 at 11:42 AM, Dan Haywood dkhayw...@gmail.com wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). The intent of these projects
Re: [VOTE] Isis to enter the incubator
On Wed, Sep 1, 2010 at 5:42 AM, Dan Haywood dkhayw...@gmail.com wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason +1, binding... --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
+1 (binding) LieGrue, strub --- On Wed, 9/1/10, Dan Haywood dkhayw...@gmail.com wrote: From: Dan Haywood dkhayw...@gmail.com Subject: [VOTE] Isis to enter the incubator To: general@incubator.apache.org Cc: nakedobjects-contribut...@lists.sourceforge.net Date: Wednesday, September 1, 2010, 9:42 AM The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister
Re: [VOTE] Isis to enter the incubator
+1 (Not binding) On Wed, Sep 1, 2010 at 10:40 AM, Mark Struberg strub...@yahoo.de wrote: +1 (binding) LieGrue, strub --- On Wed, 9/1/10, Dan Haywood dkhayw...@gmail.com wrote: From: Dan Haywood dkhayw...@gmail.com Subject: [VOTE] Isis to enter the incubator To: general@incubator.apache.org Cc: nakedobjects-contribut...@lists.sourceforge.net Date: Wednesday, September 1, 2010, 9:42 AM The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will
Re: [VOTE] Isis to enter the incubator
[X ] +1, binding Cool to see a project enter incubation with already two books written ;-) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
+1 (binding) Regards, Alan On Sep 1, 2010, at 2:42 AM, Dan Haywood wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic
Re: [VOTE] Isis to enter the incubator
+1, binding On Wed, Sep 1, 2010 at 5:42 PM, Dan Haywood dkhayw...@gmail.com wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). The intent of these projects was to
Re: [VOTE] Isis to enter the incubator
On Sep 1, 2010, at 3:42 AM, Dan Haywood dkhayw...@gmail.com wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason +1 (not binding) -- Leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
(+1 binding) On Wed, Sep 1, 2010 at 9:18 AM, Niclas Hedhman nic...@hedhman.org wrote: +1, binding On Wed, Sep 1, 2010 at 5:42 PM, Dan Haywood dkhayw...@gmail.com wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using
You have already been subscribed ...
Jukka's template for email to new committers tell them that they are 'already subscribed' to river-private. How do I do that? I would have expected the new person to send in a subscription request and have the moderator add them. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: You have already been subscribed ...
Hi, On Wed, Sep 1, 2010 at 6:49 PM, Benson Margulies bimargul...@gmail.com wrote: Jukka's template for email to new committers tell them that they are 'already subscribed' to river-private. How do I do that? I would have expected the new person to send in a subscription request and have the moderator add them. I do that with a river-private-subscribe-account=apache.org@ subscription request with my moderator powers, but you can just as well edit the introductory email to instruct the new committers to subscribe themselves with a mail to river-private-subscr...@. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: You have already been subscribed ...
Could you please take care of 'pats' for me in that case this time? On Wed, Sep 1, 2010 at 1:06 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, Sep 1, 2010 at 6:49 PM, Benson Margulies bimargul...@gmail.com wrote: Jukka's template for email to new committers tell them that they are 'already subscribed' to river-private. How do I do that? I would have expected the new person to send in a subscription request and have the moderator add them. I do that with a river-private-subscribe-account=apache.org@ subscription request with my moderator powers, but you can just as well edit the introductory email to instruct the new committers to subscribe themselves with a mail to river-private-subscr...@. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: You have already been subscribed ...
Hi, On Wed, Sep 1, 2010 at 9:12 PM, Benson Margulies bimargul...@gmail.com wrote: Could you please take care of 'pats' for me in that case this time? She's now subscribed. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
new committers
root notified us of a raft of new committers. Is someone in stock with karma to grant karma? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
Done. Craig On Sep 1, 2010, at 4:50 PM, Benson Margulies wrote: root notified us of a raft of new committers. Is someone in stock with karma to grant karma? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
Thanks, sorry about the out-of-order email responses. On Wed, Sep 1, 2010 at 8:25 PM, Craig L Russell craig.russ...@oracle.com wrote: Done. Craig On Sep 1, 2010, at 4:50 PM, Benson Margulies wrote: root notified us of a raft of new committers. Is someone in stock with karma to grant karma? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
Generally the mentors will do this for their respective podlings. On 02/09/2010, at 9:50 AM, Benson Margulies wrote: root notified us of a raft of new committers. Is someone in stock with karma to grant karma? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
The site says that only the PMC chair, the ex-PMC chairs, and a shadowy underground of unnamed other individuals have access to grant commit karma ... not arbitrary mentors. The site couldn't possibly be inaccurate, could it? On Wed, Sep 1, 2010 at 9:05 PM, Brett Porter br...@apache.org wrote: Generally the mentors will do this for their respective podlings. On 02/09/2010, at 9:50 AM, Benson Margulies wrote: root notified us of a raft of new committers. Is someone in stock with karma to grant karma? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
On 02/09/2010, at 11:37 AM, Benson Margulies wrote: The site says that only the PMC chair, the ex-PMC chairs, and a shadowy underground of unnamed other individuals have access to grant commit karma ... not arbitrary mentors. The site couldn't possibly be inaccurate, could it? It's correct (the others with permission are infrastructure and the board, I'm not sure which of those you believe to be a shadowy underground of unnamed other individuals :). Quite often there's an overlap in those groups and at least one of the mentors - or they'll at least be able to ask someone to help them out. I may have misinterpreted your message - I thought you were looking for someone to do all the incubator ones just created, but at least as far as I'm familiar with it, I thought the podlings handled it with whomever they have available or can find. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
Leaving my snarky remark aside, I can now analyze the disconnect in question. I misinterpreted you as meaning that *any* mentor should be able to do it, not that projects generally have at least one mentor who can. In my defense, I read the tone of that web page as suggesting that the people with enough access (whatever their visibility) are not terribly numerous. So I thought a message to general was the most efficient way to put a lit-up bat in the sky to attract someone. On Wed, Sep 1, 2010 at 10:32 PM, Brett Porter br...@apache.org wrote: On 02/09/2010, at 11:37 AM, Benson Margulies wrote: The site says that only the PMC chair, the ex-PMC chairs, and a shadowy underground of unnamed other individuals have access to grant commit karma ... not arbitrary mentors. The site couldn't possibly be inaccurate, could it? It's correct (the others with permission are infrastructure and the board, I'm not sure which of those you believe to be a shadowy underground of unnamed other individuals :). Quite often there's an overlap in those groups and at least one of the mentors - or they'll at least be able to ask someone to help them out. I may have misinterpreted your message - I thought you were looking for someone to do all the incubator ones just created, but at least as far as I'm familiar with it, I thought the podlings handled it with whomever they have available or can find. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
Hi Benson, On Sep 1, 2010, at 7:38 PM, Benson Margulies wrote: Leaving my snarky remark aside, I can now analyze the disconnect in question. I misinterpreted you as meaning that *any* mentor should be able to do it, not that projects generally have at least one mentor who can. In my defense, I read the tone of that web page as suggesting that the people with enough access (whatever their visibility) are not terribly numerous. So I thought a message to general was the most efficient way to put a lit-up bat in the sky to attract someone. For what it's worth, +1 to your asking on general for someone with karma to do the necessary. Craig On Wed, Sep 1, 2010 at 10:32 PM, Brett Porter br...@apache.org wrote: On 02/09/2010, at 11:37 AM, Benson Margulies wrote: The site says that only the PMC chair, the ex-PMC chairs, and a shadowy underground of unnamed other individuals have access to grant commit karma ... not arbitrary mentors. The site couldn't possibly be inaccurate, could it? It's correct (the others with permission are infrastructure and the board, I'm not sure which of those you believe to be a shadowy underground of unnamed other individuals :). Quite often there's an overlap in those groups and at least one of the mentors - or they'll at least be able to ask someone to help them out. I may have misinterpreted your message - I thought you were looking for someone to do all the incubator ones just created, but at least as far as I'm familiar with it, I thought the podlings handled it with whomever they have available or can find. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: new committers
Hi Benson, On Sep 1, 2010, at 6:37 PM, Benson Margulies wrote: The site says that only the PMC chair, the ex-PMC chairs, and a shadowy underground of unnamed other individuals have access to grant commit karma ... not arbitrary mentors. The site couldn't possibly be inaccurate, could it? The site is correct. Officers have karma, not arbitrary others. Craig On Wed, Sep 1, 2010 at 9:05 PM, Brett Porter br...@apache.org wrote: Generally the mentors will do this for their respective podlings. On 02/09/2010, at 9:50 AM, Benson Margulies wrote: root notified us of a raft of new committers. Is someone in stock with karma to grant karma? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
