Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 non-binding Cheers, Andreas --- Andrei Savu: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. === Relationships with Other Apache Products === Provisionr is closely integrated with CloudStack, Karaf, CXF, BigTop in a numerous ways. We look forward to collaborating with those
Re: [VOTE] - Apache Clerezza Graduation Resolution
+1 (non-binding) Cheers, Andreas --- Tommaso Teofili: ... Here's the resolution updated as per Suresh's suggestion. X. Establish the Apache Clerezza Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an OSGi-based modular application and set of components for building RESTFul Semantic Web applications and services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Clerezza Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Clerezza Project be and hereby is responsible for the creation and maintenance of software related to an OSGi-based modular application and set of components for building RESTFul Semantic Web applications and services; and be it further RESOLVED, that the office of Vice President, Apache Clerezza be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Clerezza Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Clerezza Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Clerezza Project: * Reto Bachmann-Gmuer r...@apache.org * Tsuyoshi Ito i...@apache.org * Hasan Hasan ha...@apache.org * Tommaso Teofili tomm...@apache.org * Bertrand Delacretaz bdelacre...@apache.org * Florent André flor...@apache.org * Rupert Westenthaler rwes...@apache.org * Daniel Spicar dspi...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan be appointed to the office of Vice President, Apache Clerezza, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Clerezza PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Clerezza Project; and be it further RESOLVED, that the Apache Clerezza Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Clerezza podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Clerezza podling encumbered upon the Apache Incubator Project are hereafter discharged. Regards, Tommaso p.s.: keep voting :-) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Apache Stanbol Re: DOAP
Recently there had been a brief discussion on the Apache Stanbol mailing list about processing DOAP with Stanbol for something. Suggestions are welcome. Cheers, Andreas --- Shane Curcuru: DOAP files are required for all TLPs, per the Branding policy: http://www.apache.org/foundation/marks/pmcs DOAP files are used to autogenerate the projects listing site: http://projects.apache.org/indexes.html DOAP files are the best way we have currently to ensure we have a single, simple and machine-parseable list of all software projects available at the ASF. We currently under-utilize this: it would be nice if projects had more detailed DOAPs that we could entice people to create interesting visualizations of all Apache projects. It should also be linked to more, so that newcomers to the ASF have an easier way to find all the different software technologies that Apache projects have to offer to the world. From the brand perspective, DOAPs are required so the ASF can track all formal TLP projects and major software products that our projects ship (among other reasons, so we can one day auto-generate our list of trademarks). DOAPs should also have sufficient information about software downloads available so that if someone does write a crawler to inspect software products, they'll get useful information. It would be nice if projects kept DOAPs up to date with all new releases, etc., but I personally don't have the effort available in the near future to push on that area. What's more important is ensuring all TLPs have at least a basic DOAP that's checked in and reflected at projects.a.o We really need to explain this more clearly in the incubator docs, and make it clear that having a DOAP checked in is part of the branding checklist that is required to complete before graduation. I.e., we should ensure that podlings meet the Project Branding Requirements before they go to graduate. - Shane On 1/2/2013 5:08 AM, Christian Grobmeier wrote: Hi, Onami is not listed below, but we have a Doap file (which needs some maintenance :-) http://svn.apache.org/repos/asf/incubator/onami/committers/doap_Onami.rdf Three questions, because I am not so familiar with Doap files. 1) do we have to add them manually to: https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml 2) On onami we maintain several independent components. Should we maintain different doap files (one for each component), like it seems to be done by Commons? 3) Should the doap file become part of the release? thanks! Christian On Wed, Jan 2, 2013 at 1:09 AM, Benson Margulies bimargul...@gmail.com wrote: Hi there. In the process of cleaning up photark, I noticed that very few incubating projects have DOAP files. That is, I looked at https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml. If that page is stale and DOAP-i-ness happens elsewhere, someone please fill me in and excuse this noise. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Marmotta into the incubator
+1 non-binding Andy Seaborne: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and community-driven implementation of a Linked Data Platform and related Semantic Web standards, LDP 1.0 Draft and SPARQL 1.1 mainly * Move the existing LMF source from the current Google Code page to the Apache infrastructure * Remove LMF extensions that are not relevant for a core Linked Data
Re: [PROPOSAL] Apache Linda
+1 (non-binding) as a first comment. Cheers, Andreas Sebastian Schaffert: Dear all, we would like to propose a new project called Apache Linda as a Linked Data Platform implementation to the incubator. Andy Seaborne was so kind as to volunteer as a champion for the project. The proposal is available at http://wiki.apache.org/incubator/LindaProposal The goal of Apache Linda is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. Linda will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Linda aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). We are looking forward to your feedback and suggestions on how to improve the proposal and idea! Sergio, Thomas, Jakob and Sebastian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Stanbol to graduate from the incubator
+1 (non-binding) This vote started on 2012-09-05. How long will it be open? Normal time seems to be 72 hours. Cheers, Andreas --- Fabian Christ: Hi, the Stanbol podling has discussed [1] that we are ready for graduation. The project has created two releases during incubation and created an active community around the topic of semantic content management. The PPMC internal vote for a resolution to establish the project got positive feedback [2]. We are now asking the IPMC to vote on the resolution to establish Stanbol and to recommend the resolution to the board. The resolution to vote on is also available online [3]. [1] http://markmail.org/thread/6shesliws7naqgit [2] http://markmail.org/thread/ml3pfnz3ttmmpe5g [3] http://incubator.apache.org/stanbol/graduation-resolution.html === X. Establish the Apache Stanbol Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a set of reusable components for semantic content management for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Stanbol Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Stanbol Project be and hereby is responsible for the creation and maintenance of software related to a set of reusable components for semantic content management; and be it further RESOLVED, that the office of Vice President, Apache Stanbol be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Stanbol Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Stanbol Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Stanbol Project: * Alessandro Adamoualex...@apache.org * Andrea Nuzzolese anuzzol...@apache.org * Andreas Gruber agru...@apache.org * Andreas Kuckartz a...@apache.org * Benjamin Nagel bna...@apache.org * Bertrand Delacretaz bdelacre...@apache.org * Cihan Cimen ci...@apache.org * Concetto Bonafedeconcel...@apache.org * Enrico Daga enrid...@apache.org * Fabian Christfchr...@apache.org * Florent Andréflor...@apache.org * Olivier Grisel ogri...@apache.org * Ozgur Kilic oz...@apache.org * Reto Bachmann-Gmür r...@apache.org * Rupert Westenthaler rup...@apache.org * Suat Gonul s...@apache.org * Szaby Grünwald sza...@apache.org * Tommaso Teofili tomm...@apache.org * Valentina Presutti v...@apache.org * Walter Kasperwkas...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Fabian Christ be appointed to the office of Vice President, Apache Stanbol, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Stanbol PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Stanbol Project; and be it further RESOLVED, that the Apache Stanbol Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Stanbol podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Stanbol podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Stanbol to graduate from the incubator
+1 (non-binding) Fabian Christ: Hi, the Stanbol podling has discussed [1] that we are ready for graduation. The project has created two releases during incubation and created an active community around the topic of semantic content management. The PPMC internal vote for a resolution to establish the project got positive feedback [2]. We are now asking the IPMC to vote on the resolution to establish Stanbol and to recommend the resolution to the board. The resolution to vote on is also available online [3]. [1] http://markmail.org/thread/6shesliws7naqgit [2] http://markmail.org/thread/ml3pfnz3ttmmpe5g [3] http://incubator.apache.org/stanbol/graduation-resolution.html === X. Establish the Apache Stanbol Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a set of reusable components for semantic content management for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Stanbol Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Stanbol Project be and hereby is responsible for the creation and maintenance of software related to a set of reusable components for semantic content management; and be it further RESOLVED, that the office of Vice President, Apache Stanbol be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Stanbol Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Stanbol Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Stanbol Project: * Alessandro Adamoualex...@apache.org * Andrea Nuzzolese anuzzol...@apache.org * Andreas Gruber agru...@apache.org * Andreas Kuckartz a...@apache.org * Benjamin Nagel bna...@apache.org * Bertrand Delacretaz bdelacre...@apache.org * Cihan Cimen ci...@apache.org * Concetto Bonafedeconcel...@apache.org * Enrico Daga enrid...@apache.org * Fabian Christfchr...@apache.org * Florent Andréflor...@apache.org * Olivier Grisel ogri...@apache.org * Ozgur Kilic oz...@apache.org * Reto Bachmann-Gmür r...@apache.org * Rupert Westenthaler rup...@apache.org * Suat Gonul s...@apache.org * Szaby Grünwald sza...@apache.org * Tommaso Teofili tomm...@apache.org * Valentina Presutti v...@apache.org * Walter Kasperwkas...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Fabian Christ be appointed to the office of Vice President, Apache Stanbol, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Stanbol PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Stanbol Project; and be it further RESOLVED, that the Apache Stanbol Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Stanbol podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Stanbol podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Stanbol to graduate from the incubator
Good catch. The first one obviously was omitted by mistake. Likely cause of this omission: He was not added to this list when he became a committer and a PPMC member: http://incubator.apache.org/stanbol/team.html That Ali Anil Sinaci became a committer was one of the results of the incubation process ! Cheers, Andreas --- Niall Pemberton: I see from the discussion threads that you decided to remove people who had never been active - but were the following people omitted from the resolution by mistake or on purpose? Ali Anil Sinaci (70 commits, last in May voted on graduation resolution): http://stanbol.markmail.org/search/?q=from%3Asinaci Wernher Behrendt (3 commits, all in June) http://stanbol.markmail.org/search/?q=from%3Awernher Stefane Fermigier http://stanbol.markmail.org/search/?q=from%3Afermigier Niall - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
end-user operating systems Re: [VOTE] Apache OpenOffice Community Graduation Vote
Rob Weir: You probably don't see this on the server yet, but end-user operating systems, both desktop and devices, both at OS level as well as in browsers and with antivirus software, are shifting over to excluding non-signed executable by default. This is equally true of software distributed on CD's, via downloads, or listed in OS-vendor stores. That is the direction that the industry is going. Any desktop application that ignores this trend will become unusable by most users. Instead of detached digital signatures that Apache releases already carry, the OS vendors expect integrated signatures via code signing. Sorry for extending this thread, but I am curious: Which OS vendors and end-user operating systems are you talking about? The end-user operating system Debian does not require integrated signatures: http://wiki.debian.org/SecureApt Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Convenience signatures Re: [VOTE] Apache OpenOffice Community Graduation Vote
Benson Margulies: In the mean time, AOO releases can continue to have 'convenience binaries', sans signatures. If they can have 'convenience binaries' they should also be able to provide 'convenience signatures. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Stanbol 0.9.0-incubating
+1 non-binding On 02.05.2012 11:28, Fabian Christ wrote: Hi, this is the first Apache Stanbol (incubating) release. Please vote for releasing *Apache Stanbol 0.9.0-incubating* The RC7 for this release has passed our PPMC vote and we already have three binding +1 votes from IPMC members. The PPMC vote thread can be found here http://markmail.org/thread/irzmcr6iekjjzuje The source release is available for download at: http://people.apache.org/~fchrist/apache-stanbol-0.9.0-incubating-RC7/ The required -deps package is available for download at: http://www.apache.org/dist/incubator/stanbol/apache-stanbol-0.9.0-incubating-deps/ Keys are at: http://www.apache.org/dist/incubator/stanbol/KEYS Release tag is: https://svn.apache.org/repos/asf/incubator/stanbol/tags/0.9.0-incubating This release covers 408 resolved issues marked in JIRA as fixed for 0.9.0-incubating. https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hiderequestId=12319391 This vote is open for at least 72 hours. Best, - Fabian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
+1 non-binding Cheers, Andreas On 10.04.2012 03:32, Kevin Kluge wrote: Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. The proposal is available at [1] and I have also included it below. Please vote with: +1: accept CloudStack into Incubator +0: don't care -1: do not accept CloudStack into Incubator (please explain the objection) The vote is open for at least 72 hours from now (until at least 19:00 US-PST on April 12, 2012). Thanks for the consideration. -kevin [1] http://wiki.apache.org/incubator/CloudStackProposal Abstract CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration platform. Proposal CloudStack provides control plane software that can be used to create an IaaS cloud. It includes an HTTP-based API for user and administrator functions and a web UI for user and administrator access. Administrators can provision physical infrastructure (e.g., servers, network elements, storage) into an instance of CloudStack, while end users can use the CloudStack self-service API and UI for the provisioning and management of virtual machines, virtual disks, and virtual networks. Citrix Systems, Inc. submits this proposal to donate the CloudStack source code, documentation, websites, and trademarks to the Apache Software Foundation (ASF). Background Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual machines to end users. CloudStack additionally provides baremetal OS installation to end users via a self-service interface. The management of physical resources to provide the larger goal of cloud service delivery is known as orchestration. IaaS clouds are usually described as elastic -- an elastic service is one that allows its user to rapidly scale up or down their need for resources. A number of open source projects and companies have been created to implement IaaS clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General Public License version 3 (GPL v3) in 2010. Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache License v2 in April, 2012. Rationale IaaS clouds provide the ability to implement datacenter operations in a programmable fashion. This functionality is tremendously powerful and benefits the community by providing: - More efficient use of datacenter personnel - More efficient use of datacenter hardware - Better responsiveness to user requests - Better uptime/availability through automation While there are several open source IaaS efforts today, none are governed by an independent foundation such as ASF. Vendor influence and/or proprietary implementations may limit the community's ability to choose the hardware and software for use in the datacenter. The community at large will benefit from the ability to enhance the orchestration layer as needed for particular hardware or software support, and to implement algorithms and features that may reduce cost or increase user satisfaction for specific use cases. In this respect the independent nature of the ASF is key to the long term health and success of the project. Initial Goals The CloudStack project has two initial goals after the proposal is accepted and the incubation has begun. The Cloudstack Project's first goal is to ensure that the CloudStack source includes only third party code that is licensed under the Apache License or open source licenses that are approved by the ASF for use in ASF projects. The CloudStack Project has begun the process of removing third party code that is not licensed under an ASF approved license. This is an ongoing process that will continue into the incubation period. Third party code contributed to CloudStack under the CloudStack contribution agreement was assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack project has begun the process of amending the previous CloudStack contribution agreements to obtain consent from existing contributors to change the CloudStack project's license. In the event that an existing contributor does not consent to this change, the project is prepared to remove that contributor's code. Additionally, there are binary dependencies on redistributed libraries that are not provided with an ASF-approved license. Finally, the CloudStack has source files incorporated from third parties that were not provided with an ASF-approved license. We have begun the process of re-writing this software. This is an ongoing process that will extend into the incubation period. These issues are discussed in more detail later in the proposal. Although CloudStack is open source, many design documents and discussions that should have been publicly available and accessible were not publicized. The Project's second goal will be to fix this lack of
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
These touch up changes pretty much complete the proposal and we're ready to kick off a [VOTE] thread. Thoughts? +1 Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: CloudStack Incubation proposal
On 03.04.2012 19:09, Jim Jagielski wrote: Now let's see who complains and says we're fragmenting the cloud community or whatever... Where's Simon? :) Please, as far as I know the community situation regarding CloudStack seems to be very different from the one concerning LibreOffice and OpenOffice.org Maybe you never understood what the discussion was about? Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: CloudStack Incubation proposal
On 03.04.2012 20:10, Jim Jagielski wrote: Oh come on... 1st of all, it's a joke. One I do not find funny at all. And 2ndly, people could complain that we should refuse the donation and force them to put all their code/energies into OpenStack... CloudStack and OpenStack seem to be complementary and they use the same license. I expect collaboration between these projects to increase not decrease. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project
+1 non-binding Cheers, Andreas On 02.04.2012 11:10, Andy Seaborne wrote: This is a call for vote to graduate the Apache Jena podling from Apache Incubator to be a top level project. Jena entered incubation in November 2010. The project has added two new committers and PPMC members, made several releases and has a diverse committer base. The user and development communities are active. The PPMC has indicated [1,2,3] that it believes the project is ready to graduate as a top-level project with the resolution draft below. We ask that the IPMC approve this graduation request though this VOTE. [1] Vote: http://s.apache.org/jena-graduation-vote [2] Result: http://s.apache.org/jena-graduation [3] Request for comments: http://mail-archives.apache.org/mod_mbox/incubator-general/201203.mbox/%3C5C4A33CB-B122-43A8-B082-CBD63B526DE7%40cray.com%3E On behalf of the Apache Jena PPMC, Andy - [ ] +1 Recommend to the ASF Board that Apache Jena Proposal is ready to graduate to being a top level project. [ ] 0 [ ] -1 Do not graduate Apache Jena because ... The vote will be tallied no earlier than: Thursday April 5th, at 23:59 UTC. - X. Establish the Apache Jena Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to accessing, storing, querying, publishing and reasoning with semantic web data while adhering to relevant W3C and community standards. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Jena Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Jena Project be and hereby is responsible for the creation and maintenance of software related to accessing, storing, querying, publishing and reasoning with semantic web data while adhering to relevant W3C and community standards; and be it further RESOLVED, that the office of Vice President, Apache Jena be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Jena Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Jena Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Jena Project: * Andy Seaborne (andy) * Benson Marguilies (bimargulies) * Chris Dollin (chrisdollin) * Damian Steer (damian) * Dave Reynolds (der) * Ian Dickinson (ijd) * Paolo Castagna (castagna) * Rob Vesse (rvesse) * Stephen Allen (sallen) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andy Seaborne be appointed to the office of Vice President, Apache Jena, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Jena PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Jena Project; and be it further RESOLVED, that the Apache Jena Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Jena podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Jena podling encumbered upon the Apache Incubator Project are hereafter discharged. - 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] Release Apache Rave 0.7-incubating
+1 (non-binding) Cheers, Andreas On 23.01.2012 16:17, Franklin, Matthew B. wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGELOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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] DeviceMap to join the Apache incubator
+1 (non-binding) Cheers, Andreas Am 29.12.2011 17:05, schrieb Bertrand Delacretaz: Hi Incubator PMC members (*), I've just reviewed the [PROPOSAL] Apache DeviceMap... thread and I think all relevant issues have been adressed now. Let's cast your votes to accept DeviceMap as an incubating project, proposal is at http://wiki.apache.org/incubator/DeviceMapProposal and copied below as well: [ ] +1 approve DeviceMap as an incubating project. [ ] -1 reject (explaining why) [ ] +/- 0 don't care. This majority vote is open for at least 72 hours. Here's my +1. -Bertrand (*) although only votes from Incubator PMC members are binding, anybody is welcome to cast a vote *** DeviceMap proposal *** == Abstract == Apache DeviceMap is a data repository containing device information, images and other relevant information for all sorts of mobile devices, e.g. smartphones and tablets. While the focus is initially on that data, APIs will also be created to use and manage it. == Proposal == Apache DeviceMap allows users to access a wide array of technical specifications, images and other artifacts related to mobile devices. Typical mobile devices include smartphones and tablets, such as: * Android devices from multiple vendors * Apple’s iPhone and iPad family of devices * !BlackBerry devices * Windows Phone devices from multiple vendors * Symbian devices * Devices with a small marketshare running Bada, Tizen, WebOS etc. The list of Apache DeviceMap devices remains open to other device types, as the mobile sector is a highly dynamic marketplace and new device forms may surface which may not too well fit into a smartphone / tablet matrix, e.g. ChromeOS Devices. == Repository Data == The exact structure of the repository data will be defined as the project progresses. At the moment we envision storing user agent strings and/or regular expressions, properties similar to CSS Media Queries, images of the actual devices, other attributes similar to what’s in UAPROF (http://en.wikipedia.org/wiki/UAProf) for example, per-country market share data, etc. Modern mobile applications often do not need very detailed device data, so we will concentrate, at least initially, on basic device features as used in html5 websites. The W3C’s Mobile Web Initiative specs (http://www.w3.org/2005/MWI/DDWG/) will also be evaluated for use in DeviceMap. == Background == The initial motivation for Apache DeviceMap is to provide an open repository of mobile device data, available to the general public according to the Apache License. == Rationale == We propose an open and community driven repository containing mobile device data, thereby allowing for analysis of device capabilities and feature sets. This is beneficial on several fronts, be it for software developers, stakeholders/decision makers or analysts. == Initial Goals == * Define what form of data is valuable/required to setup a good working repository * Define what image sets are valuable/required * Define a data retention policy, meaning when should data be purged * Collect existing data and setup simple procedures for users to contribute and validate such data. == Current Status == Proposal has been [[http://mail-archives.apache.org/mod_mbox/incubator-general/201112.mbox/%3CCAEWfVJkuv5qmb%2B8JXuF%3D3Zx4dsUNXoMMRKLWpZu4Eh%3D9-vJESg%40mail.gmail.com%3E|discussed]] on the Incubator general list, vote is ongoing there now (TODO add link). == Community == This project will form a new community, driven by the initial committers listed below. We hope and feel that Apache DeviceMap will draw interest and its community will broaden. == Known Risks == For device images and other data, we’ll need to define acceptance criteria and traceability rules similar to what Apache uses for code, to avoid any legal issues. Gathering data of any sort is a potential sensitive area and may require good public communication or even public relation activities. == Initial Source == The [[http://OpenDDR.org|OpenDDR.org]] team will donate their existing source code to the DeviceMap podling. == Initial Committers == * Philip Jespersen - philip.jespersen (at) terria (dot) com * Bertrand Delacretaz - bdelacretaz (at) apache (dot) org * Christian Stocker - chregu (at) liip.ch * Scott Wilson - scottbw (at) apache (dot) org * Sylvain Wallez - sylvain (at) apache (dot) org * Andrew Savory - asavory (at) apache (dot) org * Nils Dehl - nils.dehl (at) dkd (dot) de * Brian !LeRoux - brian (at) apache (dot) org * Stefano Andreani - s.andreani (at) opentecheng (dot) com * Alessandro Bellucci - a.bellucci (at) opentecheng (dot) com * Werner Keil - werner (at) openddr (dot) org * Tim Fernando - info (at) timfernando (dot) com == Required Resources == === Mailing lists === * devicemap-dev @ incubator.apache.org * devicemap-commits @ incubator.apache.org * devicemap-private @
Re: OpenNLP IP clearance question
Am 13.09.2011 21:38, schrieb Jörn Kottmann: The contributor told me that he worked on it also during his day job and cannot reach his VP to sign a software grant and CCLA from him. Therefore he decided to proceed as an individual and he did send an ICLA and SGA to the secretary. Can we now proceed, accept his contribution and go through the IP clearance? He worked on it during his day job and nobody legally representing the company(?) did sign a software grant or indicate agreement with the contribution otherwise, correct? Can there be any other answer to your question than no? Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Bluesky cleanup? (was: [RESULT][VOTE] Retire Bluesky Podling)
Am 19.07.2011 11:10, schrieb Chen Liu: Can we continue to release work? Sure, but *not* within the Apache Incubator. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Bluesky Podling
The vote does not need to be suspended. It perhaps would be enough to leave the vote open for a month. If there is at least one -1 by then the podling might continue to exist, otherwise it is retired. My non-binding vote on retirement: +1 Cheers, Andreas --- Am 01.07.2011 23:28, schrieb Upayavira: I would support a one month wait. No more. They've had a long time. One month is long enough to show seriousness. With no movement in that time, a swift vote can close the project down. Upayavira On Fri, 01 Jul 2011 09:36 -0400, Noel J. Bergman n...@devtech.com wrote: Bill Stoddard wrote: I would like to see this vote suspended until we can get some feedback from Jack Cai re whether he is willing to be a mentor. I concur that we should suspend this vote pending the outcome of the project's attempt to reboot. --- Noel - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Accept OpenOffice.org for incubation
Am 12.06.2011 01:20, schrieb Henri Yandell: It is a large project; but so what? I thought Harmony had no chance of being coded and that went very quickly, showing how well maximum openness can walk the path between corporate, startup and hobby needs. You think Apache Harmony is a comparable project? That went really well ... it is almost dead now. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenOffice.org for incubation
+0 (non-binding) I would likely have voted +1 if there were no existing Open Source community behind LibreOffice. The alleged(!) necessity to remove/replace LGPL libraries not covered by the Oracle grant will not result in an improved free office suite but only in delays and further incompatibilities with LibreOffice. Cheers, Andreas --- [ ] +1 Accept OpenOffice.org for incubation [ ] +0 Indifferent to OpenOffice.org incubation [ ] -1 Reject OpenOffice.org for incubation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Remediation ...
Am 09.06.2011 19:13, schrieb Noel J. Bergman: Please stop using the meme that software patents make Americans happy. + 1 from Germany Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
Am 07.06.2011 19:58, schrieb robert_w...@us.ibm.com: and charge $0.99 for the download, the cost of an iPhone app. That is over $30 million/year. Heck, I might just do that myself and retire! No, you can not retire: I will only charge $0.49 or a part of a bitcoin ;-) Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Legal concern: Are we getting to close ot a division of markets conversation?
Am 06.06.2011 03:56, schrieb robert_w...@us.ibm.com: There are limits to what competitors can do to divide markets among themselves. IANL, of course, but this smells very bad, and I suggest we don't broach the topic again, unless cleared by ASF Legal Affairs. I myself will withdraw from this list if the topic comes up again, pending review by IBM Legal. In that case maybe it would be a good idea to ask IBM Legal now and let those know about the result who will vote about the incubation proposal, because your mail suggests that people working for IBM will potentially sabotage reasonable collaboration with TDF / LO during incubation. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Legal concern: Are we getting to close ot a division of markets conversation?
Am 06.06.2011 08:22, schrieb Greg Stein: This is just not a concern. Please end this thread. There is no problem, so this is just noise. I disagree. The issue is not if there is a legal problem but if people working for IBM state that it might be one. That might have a potentially severe effect on the podling. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Legal concern: Are we getting to close ot a division of markets conversation?
Am 06.06.2011 09:25, schrieb Greg Stein: Hey. Feel free to spin your theories. Thanks. It just isn't possible to divide markets around ALv2 code. Great if that is so. But if true or not: it is not even an answer to the question raised by Rob. I think that you completely misunderstand how this thread started. One of the main topics of the whole discussion regarding the OpenOffice.org incubation proposal was and is collaboration with TDF / LO. And now the first initial committer from IBM in the proposal states that some ways of collaborating with TDF /LO might be illegal and should not even be discussed. Sorry, but I think describing that as noise and asking people to move along and not to worry is inappropriate. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Legal concern: Are we getting to close ot a division of markets conversation?
Am 06.06.2011 03:08, schrieb robert_w...@us.ibm.com: But I am very very very concerned that this conversation is starting to cross over into a division of market conversation, which has stiff penalties under US and international competition law. Open source work, like standards, is work done voluntarily among competitors in the market. There are some things we must not talk about, especially things where competitors may be seen as arranging to reduce competition. We need to steer the conversation far from this. The discussion is not about reducing competition but about a reasonable potential division of labor between Open Source projects to avoid duplicate work. For some it might also be about eliminating an existing monopoly regarding office applications. To some extent this requires joining forces, not dividing them. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
OpenOffice.org: Question to IBM regarding license of Lotus Symphony
I am involved in both copyleft and non-copyleft projects and write this as a member of the Open Source community in the broad sense. Some people wrote that the only option to make OpenOffice.org / LibreOffice code legally usable within IBM Lotus Symphony is to use a non-copyleft license such as ASL2. That does not seem to be true: I suppose IBM could make Lotus Symphony source code available under a license which is compatible with LGPL3. I also notice that IBM currently does not sell Lotus Symphony but makes binaries available for free: http://www.ibm.com/software/lotus/symphony So my question to IBM is: Are you willing to consider open-sourcing IBM Lotus Symphony (even if only parts of it) ? If yes: which licenses would IBM be willing to consider ? If those questions have already been answered than forgive me, there are a lot of mails to read regarding the OpenOffice.org / Apache Incubator proposal ;-) Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org: Question to IBM regarding license of Lotus Symphony
The reason for my questions is that I hope that answers might in some way potentially help to avoid separate code bases for OpenOffice.org / LibreOffice or at least make it possible to avoid that for parts of the code. Some kind of reasonable relation between Lotus Symphony and Openoffice.org / LibreOffice obviously is needed. *** My opinion is that some kind of copyleft license might be better suited for this type of software than a non-copyleft license. The difference between libraries, frameworks etc. which are mostly used by developers and end user applications might be decisive. I am aware of great existing proprietary products usable by end users built using software produced in ASF projects but I can not point to any ASF application which is easily usable by non-developer end users (I would be glad to be corrected ;-). Maybe that has something to do with the license. At the same time I think that a strong community around a project is (regularly) more important than the license used by it. In other words: perhaps there are parts of OpenOffice.org for which the Apache License 2 is more appropriate than it is for other parts. Cheers, Andreas --- Am 04.06.2011 13:35, schrieb Sam Ruby: On Sat, Jun 4, 2011 at 6:24 AM, Andreas Kuckartz a.kucka...@ping.de wrote: If yes: which licenses would IBM be willing to consider ? Is there any reason to believe that the Apache License, Version 2.0 is not an appropriate choice in this situation? Am 04.06.2011 13:35, schrieb Sam Ruby: On Sat, Jun 4, 2011 at 6:24 AM, Andreas Kuckartz a.kucka...@ping.de wrote: So my question to IBM is: Are you willing to consider open-sourcing IBM Lotus Symphony (even if only parts of it) ? While I work for IBM, I don't work for that part of IBM. That being said, I do believe that we already have an answer to that question. IBM has indicated that they are willing to contribute to a project made available under the Apache License, Version 2.0, which is a recognized Open Source license. Some of these contributions will be derived from the current IBM Lotus Symphony offering. As you are undoubtedly aware, IBM contributes to a number of projects, including Linux. Contributions to each project are made consistent with the license terms of that project. If yes: which licenses would IBM be willing to consider ? Is there any reason to believe that the Apache License, Version 2.0 is not an appropriate choice in this situation? - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org: Question to IBM regarding license of Lotus Symphony
Another possible consequence of that option would be that both die. Cheers, Andreas --- Am 04.06.2011 15:10, schrieb Ian Lynch: 1. TDF and LO goes its own way completely separate from Apache/OOo. ... Possible consequences of Option 1. ApacheOOo gets insufficient support and stagnates, TDF LO carry on developing what becomes the main used code base. Or ApacheOOo attracts developers from TDF and it thrives and TDF dies. Or both thrive as two separate projects in their own right. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org: Question to IBM regarding license of Lotus Symphony
Am 04.06.2011 16:00, schrieb Sam Ruby: While other choices may make sense depending on the specific circumstances, a necessary consequence of making a choice that does not cast the widest possible net is fragmentation. I do not know if that is a valid perspective or not, but I think that the categorical statement (necessary consequence) contained in it is false. The license used for the Linux kernel certainly does not cast the widest possible net but I do not see significant fragmentation, quite the contrary. There is essentially one and the same kernel used by (almost) all Linux distributions (with rather small modifications). (Generally: When a net is to wide it can get teared up.) Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
opportunity to reunite the related communities Re: OpenOffice.org Apache Incubator Proposal: Splitting the Community?
Am 02.06.2011 18:09, schrieb Jukka Zitting: I wouldn't be too quick to throw away this opportunity to reunite the related communities. If the differences truly are insurmountable, I'd like to see that explained in the proposal before we vote on it. +1 (not binding) Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Wave into the incubator
+1 non-binding Cheers, Andreas Please vote on the acceptance of Wave into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/WaveProposal (for your convenience, a snapshot is also copied below) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenNLP Project
http://wiki.apache.org/incubator/OpenNLPProposal Out of curiosity: Are there noteworthy relations to these projects? Apache Stanbol Apache Jena Apache Clerezza Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Jena into the incubator
+1 (non-binding) Cheers, Andreas --- Am 17.11.2010 14:10, schrieb Ross Gardler: Please vote on the acceptance of JENA into the incubator. The proposal can be found at http://wiki.apache.org/incubator/JenaProposal and is copied below. [ ] +1 Accept Jena for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for at least 72 hours. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: FOO proposal and Clerezza
I think that Clerezza and Foo can work together in one top-level project. I have seen that the Jena project also decided to take Jena into the incubator: http://sourceforge.net/mailarchive/message.php?msg_name=4CD0127C.8090105%40epimorphics.com Maybe the time is ripe for a united Apache Semantic Technologies project. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Twitter widget on Apache project website.
Which widget exactly? I would not be happy if an inclusion of a widget would enable a company to track visitors of apache.org. Cheers, Andreas Am 26.10.2010 04:02, schrieb Edward J. Yoon: Hello, We'd like to add twitter widget to apachehama website for display recent tweets about #apachehama on Twitter as below: https://issues.apache.org/jira/secure/attachment/12458027/screenshot.PNG I just wonder whether there is a problem with ASF policy. Thanks! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator Board Report February 2010
What happened to Socialsite? It was still mentioned in January 2010. Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: SocialSite Podling status ?
Dave wrote on August 12, 2009: I hope to have another update very soon, I just wrote to my ol' buddy Jonathan and my favorite Sun VP ;-) Any news ? (It would be sad if Oracle and/or Sun prevent this software to survive ...) Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Move Apache Lenya to Successfully Incubated
I do not see those changes on the website... Andreas - Original Message - From: Gregor J. Rothfuss [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 9:50 PM Subject: Re: Move Apache Lenya to Successfully Incubated Andreas Kuckartz wrote: Apache Lenya is still listed as Currently Incubating on this page http://incubator.apache.org/projects/index.html Lenya has successfully exited the incubator. Please move the entry to Successfully Incubated and change the link to http://lenya.apache.org/ Thanks, Andreas BTW: there is a small typo on the page: Succesfully - Successfully both fixed -- Gregor J. Rothfuss COO, Wyona Content Management Solutionshttp://wyona.com Apache Lenya http://lenya.apache.org [EMAIL PROTECTED] [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: Move Apache Lenya to Successfully Incubated
I have forwarded your mail to the Lenya developers list. Cheers, Andreas - Original Message - From: Niclas Hedhman [EMAIL PROTECTED] To: Andreas Kuckartz [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, November 17, 2004 6:14 PM Subject: Re: Move Apache Lenya to Successfully Incubated On Wednesday 17 November 2004 22:04, Andreas Kuckartz wrote: I do not see those changes on the website... We (at Gump) could use a little bit of help figuring out what it takes to build Lenya. Does any of the following ring a bell? http://brutus.apache.org/gump/public/lenya/lenya/gump_work/build_lenya_lenya.htm l Cheers Niclas -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ - 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: Mentor(s) required for a search engine project
I am no potential sponsor but would like to see a comparison to Apache Jakarta Lucene (http://jakarta.apache.org/lucene/docs/index.html) which is implemented in Java. Andreas - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 4:04 PM Subject: Mentor(s) required for a search engine project Hello, I am looking for a Mentor(s) for the following project. We are developing a new open source search engine provisionally named Locust and are looking for an open source organization to host this project. The main features of Locust are: * High performance - about one million documents per day on a Dell PowerEdge 2500 server, index size of up to ten million documents with fast search is successfully used. * Integration of full-text search with directory assisted search (Yahoo style) is built in. * A multi-threaded Linux application written in C++ with STL. Locust is based on complete rewriting of another open search engine ASPseek (http://www.aspseek.org/). The reason for rewriting was a dismal state of ASPseek code that made it impossible to develop it further. Whoever wrote it made a very good job on general architecture and features, but had no idea about software engineering. New code is reasonably clean and modular. Although it generally mimics the functionality of ASPseek (plus added integration with directories and better document set selection), it is possible now, due to its modular structure, to develop the code in many interesting direction, such as indexing document from different sources (in addition to the Web), creating distributed search services where many Locust based search engines cooperate via TCP/IP, etc. I would be glad to provide more information to potential Mentors. Gregory Kozlovsky Project Manager for Information Systems Tel: +41 (0)1 632 63 70 International Relations and Security Network (ISN) Fax: +41 (0)1 632 14 13 Center for Security Studies Email: [EMAIL PROTECTED] ETH Zürich (Swiss Federal Institute of Technology Zurich) http://www.isn.ch/ Leonhardshalde 21, ETH-Zentrum / LEH CH-8092 Zürich, Switzerland - 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]
LGPL / Apache (Re: Proposition: Twister WS-BPEL engine and Apache Agila)
I noticed that Twister is licensed under the LGPL. Is it possible to merge that code with Apache Agila ? Andreas - Original Message - From: Matthieu Riou [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, October 20, 2004 2:52 PM Subject: Proposition: Twister WS-BPEL engine and Apache Agila Hello, I'm the project leader of Twister, an open source WS-BPEL engine. More can be found about Twister here: http://www.smartcomps.org/twister I'm sending this e-mail to suggest a donation of Twister to the Apache Group and a merge with the incubated Apache Agila project. I believe that Twister and the Gluecode engine could be assembled to a better solution, using the strengths of both implementations. This would also be beneficial for the BPM Open Source community and would bring more users and contributors to Agila. Regards, Matthieu Riou - 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: Apache Agila : BPM engine
Sounds interesting. Is a more detailed description availiable somewhere ? Andreas - Original Message - From: Geir Magnusson Jr. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Jakarta General List [EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 8:27 PM Subject: Apache Agila : BPM engine All, The Jakarta PMC has voted to accept in Jakarta the contribution of a BPM engine from Gluecode, my employer, and I am starting the basic work of getting it into [and out of] incubation. Currently called Apache Agila, it is a small, lightweight BPM engine that we have developed as the core of our BPM product. BPM is an important part of the Java server-side stack, and we feel that this contribution will be a great 'seed' for a full-fledged BPM project at Apache. At the ASF, you can find a fairly rich set of parts for an enterprise application stack, such as Geronimo, Tomcat, Derby, Jetspeed, Pluto et al, and now there's the addition of BPM. The engine has no dependencies upon platform (like J2EE), and I'm guessing that it's easy to embed this engine into the popular framworks and platforms, such as hivemind, spring, struts, pico, etc. Agila will arrive with simple HTML GUI via a servlet, and JDBC-based persistence, but these are services that can be replaced with other implementations. For example, the Gluecode product does a JSR-168 portals and J2EE-based implementation of the services. Anyway, this is a notice of what's happening, and an invitation to all to come and participate in the project. I've CC-ed [EMAIL PROTECTED], but lets keep the conversation about it here in the incubator for now. I'll be setting up the mail-lists first, and will note when that happens so we can switch . Thanks geir -- Geir Magnusson Jr +1-203-665-6437 [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: DB PMC has voted to sponsor Derby
For those who are interested in Derby / Cloudscape: IBM Donates Cloudscape to Apache Foundation MS's Patent Purpose http://www.groklaw.net/article.php?story=20040803025804265 It seems to be big: IBM estimated the value of its contribution to be about $85 million Andreas - Original Message - From: John McNally [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 2:03 AM Subject: DB PMC has voted to sponsor Derby IBM has submitted a proposal to the Apache DB project for a Java-based package to be called 'Derby'. The DB project has voted to sponsor Derby through the incubator, so the incubator can go ahead and start setting up the infrastructure to accommodate the mailing lists, codebase, and other aspects. The attached proposal asks that a [EMAIL PROTECTED] list and cvs module incubator-derby be created. I would suggest [EMAIL PROTECTED], unless that conflicts with current incubator policy. There is also some discussion indicating Derby may wish to use subversion instead of cvs. Since cvs module setup is sometimes delegated to the sponsoring PMC, I will make sure this is clarified before that step is taken. But please proceed with the preparations for Derby's incubation. Ken Coar [EMAIL PROTECTED] will be the podling mentor. Thank you, John McNally DB PMC Chair - 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] Lenya exiting incubation
Steven Noels wrote: I'm +1 on Lenya exiting incubation, withdrawing earlier reservations in the sense that I feel the current community is much more diverse, goal-oriented and less marketing-eager than what we have seen in the past. I am still marketing-eager... (I hope you do not withdraw your withdrawal now ;-) Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Personal attacks and respect
This is my last mail regarding Stephen McConnell. His mails are now automatically deleted from my inbox. I do not have time for such debates (?)with no visible content. Andreas - Original Message - From: Stephen McConnell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 08, 2004 8:58 PM Subject: Re: Personal attacks and respect Noel J. Bergman wrote: I'm quite confident that a good portion of the inhabitants of this list doesn't care much about who is going to win this flamefest. +1 There is a sense in which a general discussion on community building techniques and communication skills is worthwhile. I've suggested to Nicola Ken that he start work on a web page to cover ideals, techniques and scenarios. -1 Sorry but Nicola Ken is not qualified. I'm sorry Nicola but you instigated this and only you can fix it. Stephen. -- |---| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---| - 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: [Summary ]Re: [TEST+VOTE] Lenya 1.2 Release
Noel J. Bergman wrote: why is there an urgent need for release? And why release first, exit later? Why not get cleaned up, exit and then have a real release? Personally, I suspect that the ability to do the aforementioned releases has been a factor underlying the lack of impetus within Lenya to get clean and exit. Those who have followed the debate on lenya-dev list know that the developers want to release the code to be able to strengthen the community. If there are any objections to the release of Lenya 1.2 based on the code quality or based on legal reasons etc. then please state them now. I think that it should be the task of the Apache Incubator to help exiting the incubator. It should not try to artificially block releases. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Official Name for Geronimo Project
I'm changing my vote, not because I don't believe in my earlier thoughts, but becausewe are wasting so much time and energy on something that should be much simpler. This gets my vote for the most unprincipled vote in this whole thread. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: We want to donate a XML / Cocoon / EJB / WebStart - based CMS
Because of ongoing server problems you can test the Application under: http://213.252.141.109/admin/ To get access to the Admin Tool try following: User: BT Passwd: test I tried that but when I tried to log in using the Java application I got an error message saying null. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Login problems (Re: AW: AW: We want to donate a XML / Cocoon / EJB / WebStart - based CMS)
This doesn't work for me at all, I get It was no possible to get config file or words to that effect. Ideas? Do you're using a proxy server? No, but I am behind a firewall - which should not matter but who knows. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: updating bugzilla (was: policy question)
Any idea what it would take to update bugzilla? Is it just a replace-the-script operation, or is it more involved? Details for the latest released version (2.16.3) are documented here: http://www.bugzilla.org/docs216/html/upgrading.html Conflicting Perl library versions are one potential problem which comes to mind. I therefore would not encourage to upgrade without having some experience with Perl, CPAN and MySQL available in case something does not work as it should. Maybe an appeal to the AxKit and mod_perl people could help to find such experience (and people willing to help) within the Apache community. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: policy question
bugzilla seems to be the one tool that is driving projects to use foreign tools [...] One reason might be that this problem with the installation on nagoya is not fixed - which could be done by upgrading to a current version of Bugzilla: query.cgi javascript is as slow as molasses http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18747 Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Invitation to participate in Apache J2EE efforts
Apache Geronimo has been launched within the Apache Incubator. Interesting. I have not seen a single mail on [EMAIL PROTECTED] mentioning such a project before. The exception is a mail containing a proposal sent by Geir Magnusson Jr. which arrived 9 minutes earlier. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Marc Fleury reacts (Fw: [JBoss-dev] July 2003 news)
FYI. Other strange things are happening as well such as blocked JBoss cvs accounts and blocked mails to JBoss mailing lists. This is really becoming ugly. Cheers, Andreas - Original Message - From: marc fleury [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 6:33 AM Subject: [JBoss-dev] July 2003 news [...] Apache J2EE effort. First a bit of history. I offered EJBoss when it was 4 month old to Apache. The guys at Jakarta vote OK unanimously and their vote was overridden by Brian Behlendorf. The reason from behlendorf was that they 'were not the dust bin of open source projects'. I heard the Apache crowd got offended for me calling them a bunch of fat ladies drinking tea at a later date when they were running around telling us how to run our project. We had reports that this was the non-official reason for this challenge. Challenge accepted. More seriously as we overtake them in corporate penetration and business model, I guess they are finally looking beyond the HTTPD C codebase and imitation is the sincerest form of flattery. We are the real thing, all we have so far is talk and announcement, announcements are a dime a dozen. Apache code on this project has yet to be released and then production reached and then maturity bla bla bla. I have little comment on the project except to say that JBOSS IS NOT A PART OF IT. In a misleading announcement Apache chairman's Greg Stein implied JBoss was participating and that JBOSS CODE WAS PART OF THE PROJECT. No current JBoss developers are participating in the Apache J2EE project and since JBoss is LGPL only full copyright holders can offer JBoss code under other licenses. Bottom line? JBoss can't be forked by apache. As our customers know, we are a business, a serious one and we seriously believe in and defend professional open source. That includes legal protection of IP. Make no mistakes, JBoss will AGGRESIVELY defend its copyright and LGPL license. [...] Marcf x Marc Fleury, Ph.D Founder JBoss Group, LLC x --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bad link: Contributor's Agreement (PDF)
This link to the Contributor's Agreement (PDF) does not work: http://incubator.apache.org/forms/ASF_Contributor_License_2_form.pdf missing-file C:\ApacheUPD2\incubator-site\build\site\forms\ASF_Contributor_License_2_form .pdf Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
