[VOTE][RESULT] Graduate CouchDB from Incubation
Ok, so here are the results of the vote. There were only +1 votes cast, and all the committers, as well as all the mentors voted in favor of graduation. +1 votes Ted Leung (binding, mentor) Gianugo Rabellion (binding, mentor) Damien Katz (binding) Jacob Torrey Jan Lenhardt (binding) Johan Sorensen Andreas Wenk Noah Slater (binding) Chris Anderson (binding) Paul Davis Ben Browning Kevin Jackson Christopher Lenz Jim Jagielski (binding, mentor) Mahehs Paolini-Subramanya Nikas Gustavsson Copying general@incubator.apache.org, which I forgot to do when calling for the vote. The next step is for us to assemble a board resolution prior to asking for a vote of the Incubator PMC: http://incubator.apache.org/guides/graduation.html#tlp-resolution . It would be a good thing for the PPMC to take up development of the resolution. We are one step closer to graduation! Thanks, Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
new tool clutch assist oversight of all podlings
I recently found that some new projects get a little lost at the acceptance phase. Also we have a large number of projects in Incubation (36) which is becoming difficult to keep in touch. We need to be able to see at a glance the status of the set of podlings. I developed a tool called clutch. Below are some notes from its generated web page. http://incubator.apache.org/clutch.html The coloured summary table is intended to encourage and nuture. - Clutch is a tool which gathers details about projects currently in incubation. It reads the Wiki page at ReportingSchedule then builds a list of projects, adds some attributes, does some validation. Then it reads the source file for the projects currently in incubation table, ensures that each new project has an entry, adds some more attributes. The clutch is the set of eggs which have been laid. The mother hen (our Incubator PMC) needs to continually gather them, to ensure that none have rolled from the nest or moved to the outside, being forgotten or becoming cold. Clutch also means to grasp eagerly. So please interpret this table from the point-of-view of encouragement and nurture. Anything red is an issue that should be addressed ASAP. The orange means that they are new and on the monthly reporting schedule. Otherwise we are looking for healthy gold yolks. Cooling off into the murk also needs attention. Data files are also generated so that other tools can easily re-use the metadata for the set of projects currently in incubation. * clutch.txt - list of project names, one per line. * Structured list of various details. Not yet happening - need to decide which format (N3, DOAP, etc.) and which attributes to be stored. Any Incubator committer can run 'clutch'. In the top-level of the incubator SVN, do: 'python clutch.py' which will generate a source xml file in site-author directory. Then build and deploy the site as normal. - It is my first foray into Python. Please improve my attempt. That language was chosen as it seems to have all necessary facilities available without needing additional dependencies. So all Incubator committers should be able to utilise the tool. Later i found INCUBATOR-78 which sees some other issues. Clutch addresses some of them. https://issues.apache.org/jira/browse/INCUBATOR-78 -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640831#action_12640831 ] David Crossley commented on INCUBATOR-78: - Today i added a tool called clutch which addresses some of this need. See r705975. See the notice to the general mailing list: Re: new tool clutch assist oversight of all podlings http://markmail.org/message/yy6cb2gokk5p2ur7 and the website at http://incubator.apache.org/clutch.html Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz Assignee: David Crossley As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley reassigned INCUBATOR-78: --- Assignee: (was: David Crossley) Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool clutch assist oversight of all podlings
Really cool, useful and in one word: wow. Additional features could be * to scan the svn logs for to see if there's any activity (last week, last month, ever), and by how many different committers * to scan the dev@ list archives to see if there's any activity (last week, last month, ever) * to scan the issue tracker (or issue list) for any action * to list the number of committers (and growth since incubation started, requires date added column in status file), added in the last quarter, half year, year Controversial (could be considered intruding on the mentor role): * to scan the private@ list archives to see if there's any activity (or more than there should be) Martijn On Sun, Oct 19, 2008 at 12:37 PM, David Crossley [EMAIL PROTECTED] wrote: I recently found that some new projects get a little lost at the acceptance phase. Also we have a large number of projects in Incubation (36) which is becoming difficult to keep in touch. We need to be able to see at a glance the status of the set of podlings. I developed a tool called clutch. Below are some notes from its generated web page. http://incubator.apache.org/clutch.html The coloured summary table is intended to encourage and nuture. - Clutch is a tool which gathers details about projects currently in incubation. It reads the Wiki page at ReportingSchedule then builds a list of projects, adds some attributes, does some validation. Then it reads the source file for the projects currently in incubation table, ensures that each new project has an entry, adds some more attributes. The clutch is the set of eggs which have been laid. The mother hen (our Incubator PMC) needs to continually gather them, to ensure that none have rolled from the nest or moved to the outside, being forgotten or becoming cold. Clutch also means to grasp eagerly. So please interpret this table from the point-of-view of encouragement and nurture. Anything red is an issue that should be addressed ASAP. The orange means that they are new and on the monthly reporting schedule. Otherwise we are looking for healthy gold yolks. Cooling off into the murk also needs attention. Data files are also generated so that other tools can easily re-use the metadata for the set of projects currently in incubation. * clutch.txt - list of project names, one per line. * Structured list of various details. Not yet happening - need to decide which format (N3, DOAP, etc.) and which attributes to be stored. Any Incubator committer can run 'clutch'. In the top-level of the incubator SVN, do: 'python clutch.py' which will generate a source xml file in site-author directory. Then build and deploy the site as normal. - It is my first foray into Python. Please improve my attempt. That language was chosen as it seems to have all necessary facilities available without needing additional dependencies. So all Incubator committers should be able to utilise the tool. Later i found INCUBATOR-78 which sees some other issues. Clutch addresses some of them. https://issues.apache.org/jira/browse/INCUBATOR-78 -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool clutch assist oversight of all podlings
On Sun, Oct 19, 2008 at 11:37 AM, David Crossley [EMAIL PROTECTED] wrote: I recently found that some new projects get a little lost at the acceptance phase. Also we have a large number of projects in Incubation (36) which is becoming difficult to keep in touch. We need to be able to see at a glance the status of the set of podlings. I developed a tool called clutch. Below are some notes from its generated web page. http://incubator.apache.org/clutch.html cool thanks for kick start this effort :-) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool clutch assist oversight of all podlings
On Sun, Oct 19, 2008 at 11:37 AM, David Crossley [EMAIL PROTECTED] wrote: snip Data files are also generated so that other tools can easily re-use the metadata for the set of projects currently in incubation. * clutch.txt - list of project names, one per line. * Structured list of various details. Not yet happening - need to decide which format (N3, DOAP, etc.) and which attributes to be stored. RDFa has the advantage that the X(HT)ML document can be viewed adequately in a browser - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][RESULT] Graduate CouchDB from Incubation
On Oct 19, 2008, at 5:58 AM, Christopher Lenz wrote: On 19.10.2008, at 08:20, Ted Leung wrote: Ok, so here are the results of the vote. There were only +1 votes cast, and all the committers, as well as all the mentors voted in favor of graduation. +1 votes Ted Leung (binding, mentor) Gianugo Rabellion (binding, mentor) Damien Katz (binding) Jacob Torrey Jan Lenhardt (binding) Johan Sorensen Andreas Wenk Noah Slater (binding) Chris Anderson (binding) Paul Davis Ben Browning Kevin Jackson Christopher Lenz (binding), I'm a committer here too :) Mea culpa! I knew that, and I remember thinking that, but obviously there was a disconnect between my brain and my fingers. Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Accepting OpenWebBeans into the Incubator
Hi; Incubator PMC, this is the repetition for the [VOTE] process for the OpenWebBeans proposal. If acceptable, please vote on the proposal until 27 Oct. PS : The following fellows voted positively so far; * Niklas Gustavsson +1 (non-binding) * Matt Hogstrom +1 (binding) * Martijn Dashorst +1 (binding) * Niclas Hedhman +1 (binding) Sincerely; Gurkan Erdogdu - Forwarded Message From: Gurkan Erdogdu [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Sunday, October 12, 2008 5:50:15 PM Subject: [VOTE] Accepting OpenWebBeans into the Incubator Incubator PMC, Please vote on accepting the OpenWebBeans project for incubation. The full OpenWebBeans proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/OpenWebBeansProposal. Here is my +1 = OpenWebBeans, Web Beans Container Implementation = === Abstract === Open Web Beans will be an ASL-licensed implementation of the Web Beans Specification which is defined as JSR-299. . === Proposal === Web Beans specification is an effort for defining stateful, contextual component models and its management for the enterprise applications that run on the Java EE 6 containers. It is a big step that it unifies the EJB (Enterprise Java Beans) and JSF (Java Server Faces) standart component models easily with simplifying the complex programming model from the developer perspective. Currently there is no standard based approach for integrating EJB session beans as a JSF based managed bean. Moreover, EJB does not define any contextual component model. Developer is responsible for managing all the lifecycle of the EJB components. Web Beans provides the management and lifecycle of the components within the container with a standart fashion. It uses the Java 5.0 annotation capability to further easing the configuration efforts. Altough Web Beans simplifies the EJB programming model within the enterprise projects, it could also be used outside of the Java EE containers, such as Apache Tomcat with its powerful component and context model. Open Web Beans Project is responsible for implementing the runtime container contract for the Web Beans specification. Besides the implementation, Open Web Beans Project will implement the core built-in components that further simplifies the developer complex interactions with other Java EE specific enterprise operations. For example, it defines the JMS (Java Messaging Service) Web Beans Component used for enterprise messaging, Logging Component for logging, Security Component for security etc. === Background === The development of this project is started by the individual developer as an open source project that is hosted on the sourceforge. Using the Open Web Beans project, enterprise developers unifies the EJB and JSF technlogies together easily. Neither of these standarts solves the all problems of the Java EE environment. While the EJB components solves the security, transactions, concurrency and scalability problems, JSF defines the web-tier presentation framework with its graphical component models, events and managed bean facility. Web Beans enables the developers to unify these component models easily within well defined semantics. Applications that uses the Open Web Beans Project may get more advanced context and component model provided by the project. === Rationale === Current Web Beans specificatin is in the EDR (Early Draft Review) level now, and no reference implementation is available yet. Introducing the early implementation of the specification to the enterprise community with using other Apache related projects, such as Open EJB, Open JPA and MyFaces, will attract a diverse community. Moreover, Open Web Beans will work closely with the other Apache projects such that it depends on the Open EJB, Open JPA and My Faces. Moreover, Geronimo may include it as a Web Beans Container when it implements Java EE 6 specification as a runtime environment in which Web Beans executes. Current Web Beans specification may be used in the Java EE 5 environment. Its very powerful type safe and EL component model injection mechanisms and other very useful stuffs could attracts the community that will use it in their current enterprise projects. === Initial Goals === The initial goals of the Open Web Beans Project are * Fully implement the JSR-299 specification. * Attracts a community around the current code base. * Active relationship with the other dependent projects to further develop some useful Web Beans Components. == Current Status == === Meritocracy === Initial developer of the project is familiar with the meritocracy principles of Apache. He knows that the open source gets power from its great developers and freedom. He also developed some other open source projects. We will follow the normal meritocracy rules also with other potential contributors. === Community === There is a great community within the Open
Re: [VOTE] Accepting OpenWebBeans into the Incubator
+1 (non-binding) On Sun, Oct 19, 2008 at 2:48 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: Hi; Incubator PMC, this is the repetition for the [VOTE] process for the OpenWebBeans proposal. If acceptable, please vote on the proposal until 27 Oct. PS : The following fellows voted positively so far; * Niklas Gustavsson +1 (non-binding) * Matt Hogstrom +1 (binding) * Martijn Dashorst +1 (binding) * Niclas Hedhman +1 (binding) Sincerely; Gurkan Erdogdu - Forwarded Message From: Gurkan Erdogdu [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Sunday, October 12, 2008 5:50:15 PM Subject: [VOTE] Accepting OpenWebBeans into the Incubator Incubator PMC, Please vote on accepting the OpenWebBeans project for incubation. The full OpenWebBeans proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/OpenWebBeansProposal. Here is my +1 = OpenWebBeans, Web Beans Container Implementation = === Abstract === Open Web Beans will be an ASL-licensed implementation of the Web Beans Specification which is defined as JSR-299. . === Proposal === Web Beans specification is an effort for defining stateful, contextual component models and its management for the enterprise applications that run on the Java EE 6 containers. It is a big step that it unifies the EJB (Enterprise Java Beans) and JSF (Java Server Faces) standart component models easily with simplifying the complex programming model from the developer perspective. Currently there is no standard based approach for integrating EJB session beans as a JSF based managed bean. Moreover, EJB does not define any contextual component model. Developer is responsible for managing all the lifecycle of the EJB components. Web Beans provides the management and lifecycle of the components within the container with a standart fashion. It uses the Java 5.0 annotation capability to further easing the configuration efforts. Altough Web Beans simplifies the EJB programming model within the enterprise projects, it could also be used outside of the Java EE containers, such as Apache Tomcat with its powerful component and context model. Open Web Beans Project is responsible for implementing the runtime container contract for the Web Beans specification. Besides the implementation, Open Web Beans Project will implement the core built-in components that further simplifies the developer complex interactions with other Java EE specific enterprise operations. For example, it defines the JMS (Java Messaging Service) Web Beans Component used for enterprise messaging, Logging Component for logging, Security Component for security etc. === Background === The development of this project is started by the individual developer as an open source project that is hosted on the sourceforge. Using the Open Web Beans project, enterprise developers unifies the EJB and JSF technlogies together easily. Neither of these standarts solves the all problems of the Java EE environment. While the EJB components solves the security, transactions, concurrency and scalability problems, JSF defines the web-tier presentation framework with its graphical component models, events and managed bean facility. Web Beans enables the developers to unify these component models easily within well defined semantics. Applications that uses the Open Web Beans Project may get more advanced context and component model provided by the project. === Rationale === Current Web Beans specificatin is in the EDR (Early Draft Review) level now, and no reference implementation is available yet. Introducing the early implementation of the specification to the enterprise community with using other Apache related projects, such as Open EJB, Open JPA and MyFaces, will attract a diverse community. Moreover, Open Web Beans will work closely with the other Apache projects such that it depends on the Open EJB, Open JPA and My Faces. Moreover, Geronimo may include it as a Web Beans Container when it implements Java EE 6 specification as a runtime environment in which Web Beans executes. Current Web Beans specification may be used in the Java EE 5 environment. Its very powerful type safe and EL component model injection mechanisms and other very useful stuffs could attracts the community that will use it in their current enterprise projects. === Initial Goals === The initial goals of the Open Web Beans Project are * Fully implement the JSR-299 specification. * Attracts a community around the current code base. * Active relationship with the other dependent projects to further develop some useful Web Beans Components. == Current Status == === Meritocracy === Initial developer of the project is familiar with the meritocracy principles of Apache. He knows that the open source gets power from its great developers and freedom. He also developed
Re: [VOTE] Accepting OpenWebBeans into the Incubator
Hey James; Sorry for forgetting to add your vote sending before into the list Thanks for re-vote; Gurkan Erdogdu 2008/10/20 James Carman [EMAIL PROTECTED] +1 (non-binding) On Sun, Oct 19, 2008 at 2:48 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: Hi; Incubator PMC, this is the repetition for the [VOTE] process for the OpenWebBeans proposal. If acceptable, please vote on the proposal until 27 Oct. PS : The following fellows voted positively so far; * Niklas Gustavsson +1 (non-binding) * Matt Hogstrom +1 (binding) * Martijn Dashorst +1 (binding) * Niclas Hedhman +1 (binding) Sincerely; Gurkan Erdogdu - Forwarded Message From: Gurkan Erdogdu [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Sunday, October 12, 2008 5:50:15 PM Subject: [VOTE] Accepting OpenWebBeans into the Incubator Incubator PMC, Please vote on accepting the OpenWebBeans project for incubation. The full OpenWebBeans proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/OpenWebBeansProposal. Here is my +1 = OpenWebBeans, Web Beans Container Implementation = === Abstract === Open Web Beans will be an ASL-licensed implementation of the Web Beans Specification which is defined as JSR-299. . === Proposal === Web Beans specification is an effort for defining stateful, contextual component models and its management for the enterprise applications that run on the Java EE 6 containers. It is a big step that it unifies the EJB (Enterprise Java Beans) and JSF (Java Server Faces) standart component models easily with simplifying the complex programming model from the developer perspective. Currently there is no standard based approach for integrating EJB session beans as a JSF based managed bean. Moreover, EJB does not define any contextual component model. Developer is responsible for managing all the lifecycle of the EJB components. Web Beans provides the management and lifecycle of the components within the container with a standart fashion. It uses the Java 5.0 annotation capability to further easing the configuration efforts. Altough Web Beans simplifies the EJB programming model within the enterprise projects, it could also be used outside of the Java EE containers, such as Apache Tomcat with its powerful component and context model. Open Web Beans Project is responsible for implementing the runtime container contract for the Web Beans specification. Besides the implementation, Open Web Beans Project will implement the core built-in components that further simplifies the developer complex interactions with other Java EE specific enterprise operations. For example, it defines the JMS (Java Messaging Service) Web Beans Component used for enterprise messaging, Logging Component for logging, Security Component for security etc. === Background === The development of this project is started by the individual developer as an open source project that is hosted on the sourceforge. Using the Open Web Beans project, enterprise developers unifies the EJB and JSF technlogies together easily. Neither of these standarts solves the all problems of the Java EE environment. While the EJB components solves the security, transactions, concurrency and scalability problems, JSF defines the web-tier presentation framework with its graphical component models, events and managed bean facility. Web Beans enables the developers to unify these component models easily within well defined semantics. Applications that uses the Open Web Beans Project may get more advanced context and component model provided by the project. === Rationale === Current Web Beans specificatin is in the EDR (Early Draft Review) level now, and no reference implementation is available yet. Introducing the early implementation of the specification to the enterprise community with using other Apache related projects, such as Open EJB, Open JPA and MyFaces, will attract a diverse community. Moreover, Open Web Beans will work closely with the other Apache projects such that it depends on the Open EJB, Open JPA and My Faces. Moreover, Geronimo may include it as a Web Beans Container when it implements Java EE 6 specification as a runtime environment in which Web Beans executes. Current Web Beans specification may be used in the Java EE 5 environment. Its very powerful type safe and EL component model injection mechanisms and other very useful stuffs could attracts the community that will use it in their current enterprise projects. === Initial Goals === The initial goals of the Open Web Beans Project are * Fully implement the JSR-299 specification. * Attracts a community around the current code base. * Active relationship with the other dependent projects to further develop some useful Web Beans Components. == Current Status == === Meritocracy ===
Re: [VOTE] Accepting OpenWebBeans into the Incubator
No worries. It's non-binding anyway. :) On Sun, Oct 19, 2008 at 5:51 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: Hey James; Sorry for forgetting to add your vote sending before into the list Thanks for re-vote; Gurkan Erdogdu 2008/10/20 James Carman [EMAIL PROTECTED] +1 (non-binding) On Sun, Oct 19, 2008 at 2:48 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: Hi; Incubator PMC, this is the repetition for the [VOTE] process for the OpenWebBeans proposal. If acceptable, please vote on the proposal until 27 Oct. PS : The following fellows voted positively so far; * Niklas Gustavsson +1 (non-binding) * Matt Hogstrom +1 (binding) * Martijn Dashorst +1 (binding) * Niclas Hedhman +1 (binding) Sincerely; Gurkan Erdogdu - Forwarded Message From: Gurkan Erdogdu [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Sunday, October 12, 2008 5:50:15 PM Subject: [VOTE] Accepting OpenWebBeans into the Incubator Incubator PMC, Please vote on accepting the OpenWebBeans project for incubation. The full OpenWebBeans proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/OpenWebBeansProposal. Here is my +1 = OpenWebBeans, Web Beans Container Implementation = === Abstract === Open Web Beans will be an ASL-licensed implementation of the Web Beans Specification which is defined as JSR-299. . === Proposal === Web Beans specification is an effort for defining stateful, contextual component models and its management for the enterprise applications that run on the Java EE 6 containers. It is a big step that it unifies the EJB (Enterprise Java Beans) and JSF (Java Server Faces) standart component models easily with simplifying the complex programming model from the developer perspective. Currently there is no standard based approach for integrating EJB session beans as a JSF based managed bean. Moreover, EJB does not define any contextual component model. Developer is responsible for managing all the lifecycle of the EJB components. Web Beans provides the management and lifecycle of the components within the container with a standart fashion. It uses the Java 5.0 annotation capability to further easing the configuration efforts. Altough Web Beans simplifies the EJB programming model within the enterprise projects, it could also be used outside of the Java EE containers, such as Apache Tomcat with its powerful component and context model. Open Web Beans Project is responsible for implementing the runtime container contract for the Web Beans specification. Besides the implementation, Open Web Beans Project will implement the core built-in components that further simplifies the developer complex interactions with other Java EE specific enterprise operations. For example, it defines the JMS (Java Messaging Service) Web Beans Component used for enterprise messaging, Logging Component for logging, Security Component for security etc. === Background === The development of this project is started by the individual developer as an open source project that is hosted on the sourceforge. Using the Open Web Beans project, enterprise developers unifies the EJB and JSF technlogies together easily. Neither of these standarts solves the all problems of the Java EE environment. While the EJB components solves the security, transactions, concurrency and scalability problems, JSF defines the web-tier presentation framework with its graphical component models, events and managed bean facility. Web Beans enables the developers to unify these component models easily within well defined semantics. Applications that uses the Open Web Beans Project may get more advanced context and component model provided by the project. === Rationale === Current Web Beans specificatin is in the EDR (Early Draft Review) level now, and no reference implementation is available yet. Introducing the early implementation of the specification to the enterprise community with using other Apache related projects, such as Open EJB, Open JPA and MyFaces, will attract a diverse community. Moreover, Open Web Beans will work closely with the other Apache projects such that it depends on the Open EJB, Open JPA and My Faces. Moreover, Geronimo may include it as a Web Beans Container when it implements Java EE 6 specification as a runtime environment in which Web Beans executes. Current Web Beans specification may be used in the Java EE 5 environment. Its very powerful type safe and EL component model injection mechanisms and other very useful stuffs could attracts the community that will use it in their current enterprise projects. === Initial Goals === The initial goals of the Open Web Beans Project are * Fully implement the JSR-299 specification. * Attracts a community around the current code base. * Active relationship with the other
Re: new tool clutch assist oversight of all podlings
Martijn Dashorst wrote: Really cool, useful and in one word: wow. Additional features could be * to scan the svn logs for to see if there's any activity (last week, last month, ever), and by how many different committers * to scan the dev@ list archives to see if there's any activity (last week, last month, ever) * to scan the issue tracker (or issue list) for any action * to list the number of committers (and growth since incubation started, requires date added column in status file), added in the last quarter, half year, year Controversial (could be considered intruding on the mentor role): * to scan the private@ list archives to see if there's any activity (or more than there should be) Other columns could be added. Please add whatever you reckon. Some of those features are addressed by some Apache Labs. This Clutch tool will become rather cumbersome. It would be ideal if other tools could focus on specific tasks and generate output that can just be gathered by Clutch. Now that we have a reliable list of projects in incubation (i.e. clutch.txt) other tools have a list to work with. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new tool clutch assist oversight of all podlings
Robert Burrell Donkin wrote: David Crossley wrote: Data files are also generated so that other tools can easily re-use the metadata for the set of projects currently in incubation. * clutch.txt - list of project names, one per line. * Structured list of various details. Not yet happening - need to decide which format (N3, DOAP, etc.) and which attributes to be stored. RDFa has the advantage that the X(HT)ML document can be viewed adequately in a browser I had wondered about that too. Is it easy to generate that output without the support of an rdf module? Note that i am trying to keep the dependencies of Clutch to an absolute minimum, so that any incubator committer can run it. One approach that i have been considering is to dump the data from clutch to a Python pickle file, then run a separate process which connects to people.apache.org (like you do with the audit scanner) where we could have the necessary Python modules installed to easily generate other data output files. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accepting OpenWebBeans into the Incubator
+1 (binding) --kevan On Oct 19, 2008, at 2:48 PM, Gurkan Erdogdu wrote: Hi; Incubator PMC, this is the repetition for the [VOTE] process for the OpenWebBeans proposal. If acceptable, please vote on the proposal until 27 Oct. PS : The following fellows voted positively so far; * Niklas Gustavsson +1 (non-binding) * Matt Hogstrom +1 (binding) * Martijn Dashorst +1 (binding) * Niclas Hedhman +1 (binding) Sincerely; Gurkan Erdogdu - Forwarded Message From: Gurkan Erdogdu [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Sunday, October 12, 2008 5:50:15 PM Subject: [VOTE] Accepting OpenWebBeans into the Incubator Incubator PMC, Please vote on accepting the OpenWebBeans project for incubation. The full OpenWebBeans proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/OpenWebBeansProposal. Here is my +1 = OpenWebBeans, Web Beans Container Implementation = === Abstract === Open Web Beans will be an ASL-licensed implementation of the Web Beans Specification which is defined as JSR-299. . === Proposal === Web Beans specification is an effort for defining stateful, contextual component models and its management for the enterprise applications that run on the Java EE 6 containers. It is a big step that it unifies the EJB (Enterprise Java Beans) and JSF (Java Server Faces) standart component models easily with simplifying the complex programming model from the developer perspective. Currently there is no standard based approach for integrating EJB session beans as a JSF based managed bean. Moreover, EJB does not define any contextual component model. Developer is responsible for managing all the lifecycle of the EJB components. Web Beans provides the management and lifecycle of the components within the container with a standart fashion. It uses the Java 5.0 annotation capability to further easing the configuration efforts. Altough Web Beans simplifies the EJB programming model within the enterprise projects, it could also be used outside of the Java EE containers, such as Apache Tomcat with its powerful component and context model. Open Web Beans Project is responsible for implementing the runtime container contract for the Web Beans specification. Besides the implementation, Open Web Beans Project will implement the core built- in components that further simplifies the developer complex interactions with other Java EE specific enterprise operations. For example, it defines the JMS (Java Messaging Service) Web Beans Component used for enterprise messaging, Logging Component for logging, Security Component for security etc. === Background === The development of this project is started by the individual developer as an open source project that is hosted on the sourceforge. Using the Open Web Beans project, enterprise developers unifies the EJB and JSF technlogies together easily. Neither of these standarts solves the all problems of the Java EE environment. While the EJB components solves the security, transactions, concurrency and scalability problems, JSF defines the web-tier presentation framework with its graphical component models, events and managed bean facility. Web Beans enables the developers to unify these component models easily within well defined semantics. Applications that uses the Open Web Beans Project may get more advanced context and component model provided by the project. === Rationale === Current Web Beans specificatin is in the EDR (Early Draft Review) level now, and no reference implementation is available yet. Introducing the early implementation of the specification to the enterprise community with using other Apache related projects, such as Open EJB, Open JPA and MyFaces, will attract a diverse community. Moreover, Open Web Beans will work closely with the other Apache projects such that it depends on the Open EJB, Open JPA and My Faces. Moreover, Geronimo may include it as a Web Beans Container when it implements Java EE 6 specification as a runtime environment in which Web Beans executes. Current Web Beans specification may be used in the Java EE 5 environment. Its very powerful type safe and EL component model injection mechanisms and other very useful stuffs could attracts the community that will use it in their current enterprise projects. === Initial Goals === The initial goals of the Open Web Beans Project are * Fully implement the JSR-299 specification. * Attracts a community around the current code base. * Active relationship with the other dependent projects to further develop some useful Web Beans Components. == Current Status == === Meritocracy === Initial developer of the project is familiar with the meritocracy principles of Apache. He knows that the open source gets power from its great developers and freedom. He also developed some other open source projects.
