Re: Call for mentors: Zeta Components
On Sat, May 1, 2010 at 12:43 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, May 1, 2010 at 12:27 PM, Kore Nordmann m...@kore-nordmann.de wrote: On 01/05/10 12:11, Bertrand Delacretaz wrote: ... If you check the current roster of mentors you'll see that several of us are serial mentors already busy with several podlings each. So that doesn't mean that the project is not interesting, that's more a general lack of available mentors, IMO. What does that mean for us as a project (zeta)? Just wait, until some mentors are available again? Is there anything we can do do to help to resolve this situation?... If you know any ASF members [1], the best might be to contact them and ask if they'd agree to be your mentors - not all members are subscribed to this list. And if you don't have enough mentors in say a week, please ask again here. -Bertrand [1] http://people.apache.org/~jim/committers.html Btw, in the first place you confused me a bit using the term member but pointing to the committers list :) ASF members are called out here - http://www.apache.org/foundation/members.html ASF committers are called out here - http://people.apache.org/committers.html Can every committer become a mentor of a podling? From the roles responsibilities document I read this All Mentors must be members of the Incubator PMC. Cheers Daniel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
actually blogs are done using apache roller as you may figure from the below URL. On Wed, Apr 21, 2010 at 12:40 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Apr 21, 2010 at 12:38 PM, Tobias Schlitt tob...@schlitt.info wrote: ...I read on the infra pages, that our website is required to be generated static HTML content. This is fine for us, since the desired systems does basically do this. But I wounder how really dynamic stuff is handeled here? E.g. having a blog is possible with static HTML, but what about comment functionality?... Projects can have blogs with comments under http://blogs.apache.org/ For other dynamic stuff, projects can use zones: http://www.apache.org/dev/solaris-zones.html -Bertrand - 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: [VOTE] Accept Aries proposal for incubation
[x] +1 Accept Aries for incubation Cheers Daniel On Tue, Sep 15, 2009 at 5:54 PM, Jeremy Hughes hugh...@apache.org wrote: The Aries proposal thread has now gone quiet and we would like to call a vote to accept Aries into the Incubator. There has been some good discussion with a few changes to the proposal including the addition of initial committers, increasing the diversity of committers from the start. The proposal is included below and is also at: http://wiki.apache.org/incubator/AriesProposal Please cast your votes: [ ] +1 Accept Aries for incubation [ ] +0 Indifferent to Aries incubation [ ] -1 Reject Aries for incubation (please help us understand why) Thank you. -- Apache Aries Abstract The Aries project will deliver 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. Proposal It is a goal of the Aries project to provide a natural home for open source implementations of current and future OSGi EEG specifications, including the opportunity for the collaborative development of compliance tests, and an environment to demonstrate the composition of these technologies and to explore areas where EEG specifications lack coverage. A further goal of this project is to leverage experience gained from it to inform contributions to OSGi EEG requirements and specification documents. Aries will offer an enterprise OSGi application programming model that enables applications to leverage Java EE and other enterprise technologies and to benefit from the modularity, dynamism and versioning capabilities of OSGi. A significant feature of Aries will be a container for OSGi Blueprint components - an implementation of the new OSGi v4.2 Blueprint component model that defines a standard dependency injection mechanism for Java components, which is derived from the Spring framework and extended for OSGi to declaratively register component interfaces as services in the OSGi service registry. In addition, the Aries project will develop a model for assembling an application/subsystem into a deployable unit, consisting of multiple bundles, as an archive which may include metadata that describes the version and external location of the application's constituent bundles or which may contain the bundles directly. The Aries project will deliver run-time componentry that supports applications, running in an OSGi framework, exploiting enterprise Java technologies common in web applications and integration scenarios including web application bundles, remote services integration and JPA. The project is not expected to deliver a complete application or integration server runtime but will instead deliver enterprise application componentry that can be integrated into such runtimes. The project will develop extensions that go beyond the OSGi EEG specifications to provide a more complete integration of OSGi modularity with Java enterprise technologies, in particular delivering support that includes but is not restricted to: * isolated enterprise applications composed of multiple, versioned bundles with dynamic lifecycle. * declarative transactions and security for Blueprint components * Container-managed JPA for Blueprint components * Message-driven Blueprint components * Configuration of resource references in module blueprints. * Annotation-based Blueprint configuration * Federation of lookup mechanisms between local JNDI and the OSGi service registry. * Fully declarative application metadata to enable reflection of an SCA component type definition. In order to maximise the potential scope of Aries adoption it is anticipated the project will remain agnostic of a number of complementary technologies and projects. It is the expectation that Aries will therefore not be delivering components such as: an application or integration server runtime kernel; a persistence provider; distribution provider; a deployment provider or a Web container. Aries will instead seek to enable the use of such components from other projects. Background OSGi is a mature and Java modularity technology that is well-used in many environments but, in the enterprise space, has more typically been exploited by the internals of the runtime infrastructure than the applications that run on it. This is primarily because of a lack of a clear enterprise OSGi application programming model and implementation of OSGi-enabled Java technology to support enterprise applications. OSGi specifications are specified and maintained by the OSGi Alliance which recognized this state of affairs several years ago and established the Enterprise Expert Group within the Alliance to
Re: Continuous Build environment?
- http://www.apache.org/dev/ - http://vmbuild.apache.org/continuum/groupSummary.action If Etch has not been already added to Continuum you might need to talk to the infra folks... Cheers Daniel On Sun, Oct 12, 2008 at 11:29 AM, Niclas Hedhman [EMAIL PROTECTED] wrote: Anyone has information about this?? Cheers Niclas -- Forwarded message -- From: James Dixson [EMAIL PROTECTED] Date: Sun, Oct 12, 2008 at 9:48 PM Subject: Continuous Build environment? To: [EMAIL PROTECTED] Does Apache have build-environment resources that we could leverage? Perhaps a shared Atlassian Bamboo or Apache Continuum or similar? We are currently doing Etch builds continuously, but the build server is locked behind our firewall here at Cisco. I would prefer to be able to have the builds manageable by non-Cisco folks. I would like to see us building continuously on Windows and Linux and OSX. -- James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] VCL: Virtual Computing Lab
Hi there, I am kind of interested but my interest goes beyond the provisioning and management of bare metal machines or systems with an installed virtual machine hypervisor. For example I am interested in provisioning and managing router/firewall and Wi-Fi platforms as well ranging from embedded systems to blade centers. Actually I created a proposal called Bennu about a year ago which describes the above use case but the feedback from the ML was as well rather minimal. Cheers Daniel On Thu, Sep 11, 2008 at 8:00 PM, Matt Hogstrom [EMAIL PROTECTED] wrote: Although I would like to think that the proposal for VCL was well worded and totally complete my past experience tells me that this is not likely the case :) I haven't seen any questions or comments on the proposal so does silence imply inadequacy of the proposal or unanimous consent that this is ready to go to a vote? I hope for the comments. Thanks On Sep 6, 2008, at 12:20 AM, Matt Hogstrom wrote: This is a proposal to incubate http://wiki.apache.org/incubator/VCLProposal Posted on the Incubator Wiki is a Proposal that is being bring together a community around further development and expansion of a project started in the academic community a few years ago at NC State. Looking for to comments, questions and and some feedback. Rather than post the contents here the link is provided at the top. We're looking for a couple more mentors. Matt Hogstrom [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubate JSecurity Project
+1 Cheers Alan D. Cabrera wrote: Relevant information can be found in: http://wiki.apache.org/incubator/JSecurityProposal Regards, Alan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subversion vs other source control systems
Seems like people weren't interested in SVK but solely in Git. Otherwise this thread would have come to an end pretty soon without the need of all the FUD cause I suggested/asked to use SVK some days ago already. It doesn't figure why infrastructure stuff needs to be discussed in such a intensity on the incubator list anyway. Just my two cents ... Noah Slater wrote: Sorry for butting in this discussion, but I would like to point out that this is only a problem for the standard Subversion client. As an SVK user (another Subversion client) I regularly make use of off-line commits, local mirroring and smart merges. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept CouchDB for incubation
+1 (non-binding) Cheers Daniel S. Haischt Sam Ruby wrote: We've had an initial discussion, which attracted a number of messages of encouragement, and identified no issues or concerns. Then we proceeded onto a proposal, which attracted three excellent mentors. Now it is time to vote on the proposal which can be found on the Apache Wiki, and reproduced below. I would like to proudly start this off with my +1. - Sam Ruby http://wiki.apache.org/incubator/CouchDBProposal Project Name: CouchDB - == Proposal == The goal is to create either an Apache top level project around the existing CouchDB open source project. Key Features: * a REST API using JSON for data transport, * a JavaScript view engine based on Mozilla Spidermonkey, * a GNU Autotools build system supporting most POSIX systems * a built-in administration interface * experimental fulltext search with Lucene === Rationale === The goals of the project are aligned with the goals of the ASF, namely there is interest in (continuing to) foster a collaborative, consensus based development process, using an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. === Initial goals === * Features for next release * Incremental reduce support, for full map/reduce support. * Document validation model (validate live and replicated changes) * Documentation, Documentation, Documentation * Fulltext Search * Priority feature work * Live compaction * Extensible security model * LDAP authentication * More query capabilities exposed to HTTP, e.g. multi-key view lookups * Future feature work * Server storage partioning * Server failover clustering * Requested Features * hierarchical structure in documents == Current Status == === Meritocracy === The project has recently transformed from being primarily a single person led (and funded) project to one with a number of diverse participants. Development has been coordinated primarily through a mailing list, with some IRC. === Community === The community consists of a set of independent developers, one of which recently joined IBM === Initial Developers === * William Beh * Damien Katz * Jan Lehnardt * Christopher Lenz * Dirk Schalge * Noah Slater === Alignment === A database server with a strong focus on HTTP and REST principles. === Known Risks === * Dependency on Erlang * Including some modifications to the HTTP server stack. The plan is to convert over to [http://code.google.com/p/mochiweb/ MochiWeb] (MIT licenced) * Dependency on Mozilla SpiderMonkey * Including small modifications, to be sent back to Mozilla === Orphaned Products === * This is a new effort, and is far from being orphaned. === Inexperience with Open Source === All participants are active users and contributors to open source. One of them (Christopher Lenz) has experience as committer on other Apache projects. === Homogenous Developers === The exiting committers are spread over a number of countries and employers. === Reliance on Salaried Developers === Only one developer is being paid to work on CouchDB. Read [http://damienkatz.net/2008/01/faq_about_couch.html his views] on the relationship he has with his employer. === Relationships with Other Apache Products === Experimental usage of Lucene === An excessive fascination with the Apache brand === This product started out independent of Apache and under a GPL license. After discussions with a number of people within IBM, Damien Katz agreed to pursue both incubation at the ASF, and employment at IBM == Documentation == === Initial Source === Resides on [http://code.google.com/p/couchdb/ Google Code]. The code has been recently relicensed from GPL to the Apache License, Version 2.0, in anticipation of this submission. === Source and Intellectual Property Submission Plan === The bulk of the core code was written by Damien Katz. Major contributions include: a GNU Autotools build system supporting most POSIX systems contributed by Noah Slater, a built-in administration interface provided by Christopher Lenz, and experimental fulltext search with Lucene by Jan Lehnardt. ICLAs either have been, or are in the process of being, submitted for all code involved in this submission. ICLA's are already on file for: * Jan Lehnardt * Christopher Lenz ICLA's in progress: * William Beh * Damien Katz * Dirk Schalge * Noah Slater There are a few (as in single digit) number of files that we are continuing to sort through the licenses. These include Public Domain, X Consortium, and MITish licenses. === External Dependencies === * [http://www.icu-project.org/ ICU] (MIT) * [http://www.erlang.org/ Erlang] (Erlang Public License) * [http://www.mozilla.org/js/spidermonkey/ SpiderMonkey] (Mozilla Public License) === Cryptography === Not applicable === Required Resources === * Mailing lists: * couchdb-pmc for private PMC discussions (with moderated
Re: [VOTE] Accept Bluesky Project into the Incubator
Bill Stoddard wrote: [x] +1 Accept BlueSky for incubation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Bennu, a Router, Firewall Wi-Fi perimeter
as a follow up ... I did add the following child pages to the Bennu proposal draft in December 2007 as a result of feedback I got from others: * /BennuBackgroundInfo (was part of the initial proposal) * /BennuFaq * /BennuMissionStatement Noel J. Bergman wrote: I spoke with Cliff Skolnick about http://people.apache.org/~dsh/bennu/BENNU_PROPOSAL.txt He is interested and has some comments. Hopefully, he'll have time to comment this week. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Hi, -//- My biggest concern with this project is lack of community diversity. Projects that graduate from Incubation must have a diverse community, with no exceptions. I've asked David Kaminsky and the project members to explicitly consider, plan and document activities designed to promote and build the community. Project mentors, please reinforce this message with the Imperius Project team. I was just reading the Imperius proposal and the CIM-SPL spec. If I am not completely getting it wrong CIM-SPL may be used on a firewall/router system no? I am asking this question because I recently submitted the Bennu project proposal [1] to the incubator ML and I think a CIM-SPL implementation may be re used to abstract for example firewall rules such as iptables or OpenBSD pf rule systems. References: --- [1] Bennu proposal: http://wiki.apache.org/incubator/BennuProposal Cheers Daniel S. Haischt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
