Re: [VOTE] Apache Sirona as an incubated project
+1 (binding) Best, Christian Am 09.10.2013 03:30 schrieb Olivier Lamy ol...@apache.org: Hi, Since discussion about the Sirona seems done, I'd like to call a vote for Sirona to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/SironaProposal Let's keep this vote open for three business days. [ ] +1 Accept Sirona into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Sirona because... ## page was renamed from MonitoringProposal = Apache Sirona = == Abstract == Apache Sirona aims to provide a simple but extensible monitoring solution for Java applications. Apache Sirona provides two kind of components : * Apache Sirona Core to provide a base framework for monitoring/recording a Java application. * Default based plugins * Apache Sirona base reporting web application (provide a basic reporting on recorded figures). == Background == Currently, Apache Sirona source is hosted in Apache Commons Sandbox scm. The development has begun few years ago but goes to dormant statut. == Rationale == Currently users who need some monitoring need to use some non Open Source solutions or GPL solutions. The goal is to provide a solution based on the Apache License. == Initial Goals == Apache Sirona doesn't have any release currently. The initial goal of this project will be to build community in the spirit of the Apache Way, and to address new features and bug-fixes of the first releases. === Current Status === Intent of the proposal is to build a diverse community of developers around Sirona. Sirona started in the Apache Commons Sandbox, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Apache Sirona stakeholders desire to expand the user and developer base of Apache Sirona further in the future == Known Risks == === Orphaned Products === Sirona is a new product. So without community adoption the risks of it being orphaned exist. === Inexperience with Open Source === The code has been developed in Apache Commons Sandbox mostly by Romain Manni-Bucau and Olivier Lamy who intimately familiar with the Apache model for open-source development and is experienced with working with new contributors. === Homogeneous Developers === The initial set of committers is from a small set of organizations. However, we expect that once approved for incubation, the project will attract new contributors from diverse organizations and will thus grow organically. The participation of developers from several different organizations in the mailing list is a strong indication for this assertion. === Reliance on Salaried Developers === It is expected that Apache Sirona will be developed on salaried and volunteer time. === Relationships with Other Apache Products === Apache Sirona depends upon other Apache Projects: Velocity and various Apache Commons components and build systems like Maven. === A Fascination with the Apache Brand === The reason for joining Apache is to foster a healthy community of contributors and consumers around the project. This is facilitated by ASF and that is the primary reason we would like Apache Sirona to become an Apache project. == Documentation == Docs: http://commons.apache.org/sandbox/commons-monitoring/ == Initial Source == https://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk == Source and Intellectual Property Submission Plan == The initial source is already Apache 2.0 licensed. == External Dependencies == The required external dependencies are all Apache License or compatible licenses. Following components with non-Apache licenses are enumerated : == Cryptography == Apache Sirona does not depend upon any cryptography tools or libraries. == Required Resources == === Mailing lists === * sirona-private (with moderated subscriptions) * sirona-dev * sirona-commits * sirona-user == Subversion Directory == https://svn.apache.org/repos/asf/incubator/sirona == Issue Tracking == JIRA Sirona (key: SIRONA) == Other Resources == The existing code already has unit and integration tests so we would like to use Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committer == * Romain Manni-Bucau (rmannibu...@apache.org) * Jean-Louis Monteiro (jlmonte...@apache.org) * Fred Zhang (no ASF account) * Fabrice Bacchella (no ASF account) * Christian Grobmeier (grobme...@apache.org) == Affiliations == * Olivier Lamy, Ecetera * Fred Zhang, Ecetera == Sponsors == === Champion === * Olivier Lamy (ol...@apache.org) === Nominated Mentors === * Olivier Lamy (ol...@apache.org) * Henri Gomez (hgo...@apache.org) * Jean-Baptiste Onofré (jbono...@apache.org) * Tammo van Lessen (va...@apache.org) *
Re: [ANNOUNCE] Christian Müller joins the IPMC
Thanks for the warm welcome. Because I'm a newbie here, be aware of stupid questions... ;-) Best, Christian Am 03.10.2013 08:02 schrieb Romain Manni-Bucau rmannibu...@gmail.com: Congrats! *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/3 Jean-Louis MONTEIRO jeano...@gmail.com Congrats Christian. Jean Louis Le 3 oct. 2013 01:20, Marvin Humphrey mar...@rectangular.com a écrit : Apache Member and Apache Camel PMC Chair Christian Müller has joined the Incubator PMC. Welcome! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] BatchEE as an incubated project
+1 Best, Christian Christian Müller - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, Sep 30, 2013 at 6:52 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Since discussion about the BatchEE seems done, I'd like to call a vote for BatchEE to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/BatchEEProposal Let's keep this vote open for three business days, closing the voting on Thursday 10/03. [ ] +1 Accept BatchEE into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept BatchEE because... = BatchEE, JBatch Implementation = === Abstract === BatchEE will be an ASL-licensed implementation of the JBatch Specification which is defined as JSR-352 (for version 1.0). === Proposal === BatchEE specification is an effort for defining a standard API and way to write batches in Java. It is integrated with JavaEE (JTA, CDI) but works out of the box in a standalone environment. BatchEE Project is responsible for implementing the runtime container contract for the JBatch specification. Besides the implementation, BatchEE 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 will define default reader/processor/writer for jdbc, jpa, xml/json/flat files... === Background === Until today writing batches in java meant using a proprietary framework and link to JavaEE was quite limited (or missing). JBatch defines an API fixing this issue and now developpers need a fix. === Rationale === Current JBatch specificatin is released, and only the reference implementation is available but not really intended to be maintained. Moreover multiple Apache projects (geronimo, TomEE, ...) will need an Apache compatible Jbatch implementation to go ahread and implement JavaEE 7. === Initial Goals === The initial goals of the BatchEE Project are * Fully implement the JSR-352 specification. * Attracts a community around the current code base. * Active relationship with the other dependent projects to further develop some useful batch 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 OpenEJB, OpenWebBeans, Geronimo and TomEE Apache projects. BatchEE project is very related with these projects and in the some cases, it enhances these projects. We are thinking that BatchEE project gets strong community because it complete the needed frameworks of a java developper and unifies the using of these projects. It simplifies the developer effort for building complex enterprise applications batches. === Core Developers === BatchEE project has been developing by the IBM then forked by Romain Manni-Bucau as a sole contributor. === Alignment === BacthEE project will be a candidate for use in Geronimo AS and TomEE as a default JBatch implementation. Other projects could benefit from the BatchEE project as a general purpose component and context management. BatchEE project is closely aligned with the OpenEJB and OpenWebBeans projects perfectly. It depends on these projects to satisfy its requirements (mainly tests). == Known Risks == === Orphaned products === Even if the initial committer of the project has no plan to leave the active development, it must necessary to get other committers for the project. So that it less dependent on the single developer. The source code of the project is well documented and new committers could easily grasp the details. Initial committer continues to support actively this project. === Inexperience with Open Source === Initial developer have worked on open source project before, including OpenEJB/TomEE, OpenWebBeans, XBean... === Homogeneous Developers === Altough the initial committer of the project is single, developer team may be increased within the active project lifecycle from the different locations. === Reliance on Salaried Developers === Project currently has no salaried developers. All the commitment is done by the volunteer developer. === Relationships with Other Apache Products === BatchEE will likely be used in the Geronimo and Apache TomEE. OpenWebBeans could bring added value for tests and integration with CDI. OpenEJB will be great to pass EE tests (JTA is mandatory and CDi a must have