Re: Bluesky calls for a new mentor!
I am not certain on this point, but I believe Jack Cai would be interested in being a mentor. I don't think he is subscribed to this mailing list tho. Jack? Bill On 6/29/11 9:12 PM, Chen Liu wrote: Hi,all, Now, Bluesky project calls for a new mentor to guide us to complete the release work of 4th version. BlueSky is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China (e.g., countryside of Western China). BlueSky is already deployed to 12 + 5 primary/high schools with positive reviews.BlueSky was originally created by Qinghua Zheng and Jun Liu in September 2005. The BlueSky development is being done at XJTU-IBM Open Technology and Application Joint Develop Center, more than 20 developers are involved. And it entered incubation on 2008-01-12. BlueSky is consisted with two subsystems -- RealClass system and MersMp system, both of which contains a set of flexible, extensible applications such as Distance Collaboration System, Collaboration player, Collaboration recording tool, Resources Sharing and Management Platform and Access of mobile terminal, designed by engineers and educators with years of experience in the problem domain, as well as a framework that makes it possible to create new applications that exist with others. Currently,Bluesky project has evolved into the 4th version system with more flexible applications and stabilities. We had developed the core applications of bluesky system with QT to support both Windows and Linux. What's more important, the new version system has the feature of integrated applications, which means that user can record a video during the interactive process and then play it in VOD method.The third advancement is that the 4th version sysytem supports Android platform and we can further advance Blursky in the mobile domain. We propose to move future development of BlueSky to the Apache Software Foundation in order to build a broader user and developer community. We hope to encourage contributions and use of Bluesky by other developing countries with similar education needs. Currently, the new version of BlueSky system is already handy to release.We really need to add an enthusiastic and responsive mentor to help us to complete full cycle of successful release.So we hope that with the help of developers all around the world, the system could become more powerful and functional in education area. We appreciate your attentions to Bluesky project. Best regards. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Bluesky Podling
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. Bill On 6/28/11 1:49 AM, berndf wrote: Hi everyone, this is a vote to retire the Bluesky podling. 3.5 years into incubation, the podling has not made progress in terms of becoming an Apache project. Dev is still done behind closed doors, and developers are changing frequently without notifications on the public lists. Mentors are M.I.A. Reports are often late. No Apache release was every made. There were multiple attempts to reboot the podling (Thanks Luciano!) without much success. So now I'm calling a vote to end Incubation for Bluesky. The vote is open at least until 2011-07-02 12:00 UTC. [] +1, retire Bluesky for the time being [] -0/+0, I'm undecided [] -1, I will step up as a mentor, so let's give it another try Thanks for voting, Bernd - 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 OpenOffice.org for incubation
[X] +1 Accept OpenOffice.org for incubation On 6/10/11 12:02 PM, Sam Ruby wrote: *** Please change your Subject: line for any [DISCUSSION] of this [VOTE] As the discussions on the OpenOfficeProposal threads seem to be winding down, I would like to initiate the vote to accept OpenOffice.org as an Apache Incubator project. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/OpenOfficeProposal?action=recallrev=207 As the proposal discussion threads are numerous, I encourage people to scan and review the archives for this month: http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/browser Please cast your votes: [ ] +1 Accept OpenOffice.org for incubation [ ] +0 Indifferent to OpenOffice.org incubation [ ] -1 Reject OpenOffice.org for incubation This vote will close 72 hours from now. - Sam Ruby = OpenOffice.org - An open productivity environment = == Abstract == !OpenOffice.org is comprised of six personal productivity applications: a word processor (and its web-authoring component), spreadsheet, presentation graphics, drawing, equation editor, and database. !OpenOffice.org is released on Windows, Solaris, Linux and Macintosh operation systems, with more [[http://porting.openoffice.org/|communities]] joining, including a mature [[http://porting.openoffice.org/freebsd/|FreeBSD port]]. !OpenOffice.org is localized, supporting over 110 languages worldwide. == Proposal == Apache !OpenOffice.org will continue the mission pursued by the !OpenOffice.org project while under the sponsorship of Sun and Oracle, namely: To create, as a community, the leading international office suite that will run on all major platforms and provide access to all functionality and data through open-component based APIs and an XML-based file format. In addition to to building the !OpenOffice.org product, as an end-user facing product with many existing individual and corporate users, this project will also be active in supporting end-users via tutorials, user forums, document template repositories, etc. The project will also work to further enable !OpenOffice.org to be used as a programmable module in document automation scenarios. == Background == !OpenOffice.org was launched as an open source project by Sun Microsystems in June 2000. !OpenOffice.org was originally developed under the name of StarOffice by Star Division, a German company, which was acquired by Sun Microsystems in 1999. Sun released this as open source in 2000. !OpenOffice.org is the leading alternative to MS-Office available. Its most recent major version, the 3.x series saw over [[http://www.webmasterpro.de/portal/news/2010/02/05/international-openoffice-market-shares.html|100 million downloads]] in its first year. The [[http://www.webmasterpro.de/portal/news/2010/02/05/international-openoffice-market-shares.html|most recent estimates]] suggest a market share on the order of 8-15%. The !OpenOffice source is written in C++ and delivers language-neutral and scriptable functionality. This source technology introduces the next-stage architecture, allowing use of the suite elements as separate applications or as embedded components in other applications. Numerous other features are also present including XML-based file formats based on the vendor-neutral !OpenDocument Format (ODF) standard from OASIS and other resources. == Rationale == !OpenOffice.org core development would continue at Apache following the contribution by Oracle, in accordance with Apache bylaws and its usual open development processes. Both Oracle and ASF agree that the !OpenOffice.org development community, previously fragmented, would re-unite under ASF to ensure a stable and long term future for OpenOffice.org. ASF would enable corporate, non-profit, and volunteer stakeholders to contribute code in a collaborative fashion. Supporting tooling projects will accompany the !OpenOffice.org contribution, providing APIs for extending and customizing !OpenOffice.org. Both !OpenOffice.org and the related tooling projects support the OASIS Open Document Format, and will attract an ecosystem of developers, ISVs and Systems Integrators. ODF ensures the users of !OpenOffice.org and related solutions will own their document data, and be free to choose the application or solution that best meets their requirements. The !OpenOffice.org implementation will serve as a reference implementation of the Open Document Format standard. = Current Status = == Meritocracy == We understand the intention and value of meritocracy at Apache. We are particularly gratified to learn, during the discussion on this proposal, that there is a strong role for non-coders to participate in this meritocracy and as they demonstrate their sustained commitment and merit, to take on additional community responsibilities. The initial
Re: [VOTE] Retire the Imperius Podling
+1 On 5/10/11 10:39 AM, Kevan Miller wrote: The Imperius podling has voted to retire/suspend/terminate/dormantify the Imperius podling. I'm now bringing the vote to the incubator pmc. The vote was unanimous with 6 +1 votes (kevan miller, david wood, mark carlson, neeraj joshi, david kaminsky, and craig russell). From the original vote thread on imperius-dev: We seem to have a consensus that it is time to retire the Imperius Podling. Although the Apache Imperius project was successful in building an SPL implementation and had a successful release, there is not sufficient community energy to warrant continued development of Imperius at the Apache Software Foundation. I believe it is time to suspend development of the Imperius project at the Apache Incubator. The Incubator status for this state is retired or dormant. Please cast your vote: [ ] +1 to retire the Imperius project [ ] 0 for Don't care [ ] -1 for No, please keep it alive (please provide arguments why) I'll leave this vote open for a minimum of 72 hours. I would like to note that this in no way reflects on the quality of the Imperius software codebase or the past actions of the Imperius community. It is simply an acknowledgement that we do not have sufficient community involvement to keep the Imperius project going. --kevan - 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On 2/23/10 10:57 AM, Donald Woods wrote: Given the lack of response on the proposal and the push from our champion to get moving :-), I'll assume lazy consensus and call a vote. I would like to present for a vote the following proposal to be sponsored by the Incubator PMC for a new Validation podling. The goal is to build a community around delivering a JSR-303 Bean Validation implementation based on a new incoming codebase from Agimatec GmbH. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/ValidationProposal [] +1 to accept Validation into the Incubator [] 0 don't care [] -1 object and reason why. +1 Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Subversion is now an official ASF project!
On 2/17/10 4:16 PM, Greg Stein wrote: Hi all, The ASF Board just voted to approve the graduation of Subversion from the Incubator. We are now an official project of the Apache Software Foundation! Go forth! Be merry! Congrats! Cheers, -g - 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][PROPOSAL] Spatial Information Systems Proposal
On 2/19/10 5:42 PM, Bertrand Delacretaz wrote: On Fri, Feb 19, 2010 at 11:04 PM, Ian Holsmanli...@holsman.net wrote: we now have 3 mentors. should we call a re-vote? or just leave this one running, seeing how no-one '-1'd us so far. As the only objections were about the number of mentors, I suggest going forward with this vote. -Bertrand Agree. Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE][PROPOSAL] Spatial Information Systems Proposal
On 2/16/10 10:15 PM, Ian Holsman wrote: Given the lack of response on the proposal, I'll assume lazy consensus and call a vote. +1 Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: *** Missing Reports
On 2/15/10 11:20 AM, Noel J. Bergman wrote: BlueSky and HISE are missing, and won't be in the February report. --- Noel Bluesky folks are away for Chinese Near Year. Bill - 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: graduating Subversion
On 1/26/10 1:00 AM, Niclas Hedhman wrote: On Tue, Jan 26, 2010 at 4:49 AM, Greg Steingst...@gmail.com wrote: Before calling for a vote to graduate Subversion, I figured it prudent to have a discussion first. I believe Subversion is quite ready (and has been, but the holidays and whatnot kept me from sending this earlier). Any thoughts on why Subversion should NOT graduate now? I want to see a graduation. Motivation; Incubator is about fostering the community, and I don't think that the Incubator can provide anything additional from the Apache folks already present in the Subversion community. Anything else sounds like bureaucracy for the sake of it, to me... Well said. Nothing to add but my support for graduation. Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][VOTE] Subversion
+1 Bill Greg Stein wrote: Subversion is a version control system. You probably know it well as it is the version control system employed by the Apache Software Foundation. The Subversion project would like to join the Apache Software Foundation to remove the overhead of having to run its own corporation. The Subversion project is already run quite like an Apache project, and already counts a number of ASF Members amongst its committers. Work on Subversion was originally started at CollabNet; Karl Fogel was hired in January 2000. Jim Blandy, at RedHat, already had an initial design for the storage system, which was incorporated into the FS design. In February Brian Behlendorf invited Greg Stein to contribute his WebDAV experience to Subversion. Ben Colins-Sussman was hired in April 2000 to work on the project. In that same month the first all hands meeting was held, where a number of interested people came together to talk about the project. Subversion was run as an open source project since the early days. Now, more than nine years later, it retains a healthy community, and has a good number of committers. In the life span of Subversion, several committers have switched employers and have maintained involvement. The committership is diverse, both geographically as well as in terms of employment. The equivalent of the PMC consists of all the full committers to the Subversion project (currently around 55 people). The community uses the voting process also used at the ASF. Releases are signed off by gathering votes/digital signatures of each committer who verified the release candidate. We feel the ASF and Subversion communities are very compatible, witness the cross interest that already exists. There is both a vibrant developer as well as a large and active user community. Technology-wise, Subversion builds on APR, and implements two Apache HTTP Server modules. Note that Subversion has a number of related projects, which are not part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse). More information on Subversion can be found at http://www.subversion.org/ and http://subversion.tigris.org/. The Subversion Corporation has a license to all source code, and has CLAs on file for nearly all it's committers. That is, we have all but one or two full committers, and some percentage of partial committers. We have a number of *user-configurable* dependencies which are not compatible with the AL: - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL. (An alternative HTTP client library, libsvn_ra_serf uses the Serf library under ALv2.) - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is under Academic Free License 2.1 or =GPL-2. (This support is for integration for KDE and GNOME's authentication providers.) - libintl (This library provides translation support for systems without a proper internationalization library.) - BDB (This is used by the libsvn_fs_base system which stores its data in BDB; an alternative repository system called fs_fs does not have this dependency.) --- Required Resources - Mailing lists - dev - issues - users - private - commits - announce - breakage (see http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552) - We will work with the Infrastructure team to transfer the subscriber listings to the new destinations. - Subversion: - We have not made a decision whether we prefer Subversion should be imported into the main ASF Subversion repository or be hosted as a separate repository to enable early testing of the repository code. We intend to discuss this during the Incubation process before the code is imported. It is also understood that ASF infrastructure team may be willing to run custom pre-release Subversion server builds for the entire ASF, so this separate repository option may not be required. - The Subversion source code can be found at: http://svn.collab.net/repos/svn/. - Issue tracking - We haven't made a decision between JIRA or Bugzilla at this time and expect this decision to be made as part of the Incubation process. Our current issue tracking system uses Issuezilla (a fork of Bugzilla) and we have not yet decided whether we want to import our previous issues into the new system and will decide this in the course of the Incubation process. - Our current issue tracker is at http://subversion.tigris.org/issue-tracker.html. - Buildbot - We currently use buildbot across a number of platforms and configurations for automated builds and testing. Over time, we would like to migrate these services to Apache infrastructure where appropriate. - Our current buildbot master is at http://buildbot.subversion.org/buildbot/ Note that we request these resources to be at their final
Re: [VOTE] Accept Aries proposal for incubation
Jeremy Hughes wrote: 2009/9/16 Jim Jagielski j...@jagunet.com: On Sep 16, 2009, at 4:32 AM, Niall Pemberton wrote: ... IMO this is more a graduation issue, rather than something that should prevent entry to the incubator - since thats when destination is decided. There are many possible outcomes from that - perhaps some parts will go to felix and others to a new TLP(s) - but I say lets see how it works out during graduation rather than shooting it down now. I agree that the rubber hits the road when graduation, and when there is a resolution before the board to make this a TLP. However, my thoughts are that without this concern front-and-center from the get-go, the podling runs the risk of hitting this roadblock right at the end, at which point who knows how much impact this may have on it... In other words, if a podling umbrella attempts to graduate into a TLP umbrella, it will likely be shot down. Do we really want to wait until the end to address this once and for all? Just my 2c. PS: BTW, I think it's a great proposal and podling and technically am a big +1 on it. My only concern is lack of directed focus... It is not our intent to create an umbrella TLP - the focus of Aries is specifically on developing the componentry needed to enable an enterprise OSGi application prgramming model. This will include implementing some of the OSGi EEG specs - the initial focus is as described in the sections Initial Goals and Initial Source but the proposal also tries to make it clear that Aries will consume technology from other projects where available: It is the expectation that Aries will therefore not be delivering components such as ... Aries will instead seek to enable the use of such components from other projects. We are starting out largely speaking as a community of people with a heritage in enterprise Java runtimes looking to encouarge the exploitation of OSGi by the applications deployed to enterprise environments. We are not looking to target specific runtimes or to implement *every* spec that comes out of the EEG but we are looking to build coherent componentry needed by enterprise applications when deployed as OSGi bundles to an enterprise runtime. We've described this in the Relationship with Other Apache Projects section. How we evolve from the stated initial goals will largely depend on the community that forms - which I believe is reasonable for a new incubator. To help remove any impression that Aries is looking to become an umbrella TLP we could perhaps reword the first sentence of the proposal from It is a goal of the Aries project to provide a natural home for open source implementations of current and future OSGi EEG specifications, .. to It is a goal of the Aries project to implement OSGi EEG specifications that are part of the enterprise application programming model, to clarify the scope - this remains consistent with the rest of the proposal. Thanks, Jeremy Crickets it's terribly quiet around here.. I am having a really difficult time getting my head around Jim and Niclas' objections that this is an umbrella project. The mother of all umbrella projects was Jakarta... (coded in Java? It should go into Jakarta...); this proposal clearly isn't that. This proposal is concerned with implementing an OSGi application programming model; it relies heavily on specs from the OSGi Alliance Enterprise Expert Group (EEG) and the EEG itself is a small, narrowly scoped part of the OSGi Alliance. The project scope seems pretty darn succinct to me. What am I missing? What I see here is a surprisingly diverse group of developers interested in working on a project and having the freedom to bring the vision to fruition. A lot like Geronimo really, whose mission is to implement the JEE programming model. Geronimo draws heavily on projects from both inside and outside the ASF. If the Geronimo team requires a piece of technology that's not available, they collaborate with other groups to obtain it or do the work themselves at last resort. In other words, Geronimo has operational freedom to control its own destiny. Not a bad thing, imho. It's pretty clear (at least to me :-) that the Aries proposal is more tightly scoped than even Geronimo and Geronimo works reasonably well. The project proposers clearly know -where- they want to go (and have communicated that in the proposal) .. what's understandably less clear is precisely how they are going to get there... that's why a degree of operational freedom is important; attempting to nail the proposers down to a precise path right now is counter productive to the success of the project. Bill - 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
+1 Jeremy Hughes 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 focus specifically on the needs of enterprise applications. The objective of this project is to deliver open source implementations of these application-centric
Re: [VOTE] Mothball/Pause Lokahi
Niclas Hedhman wrote: PMC and others, Lokahi's community has collapsed long time ago and albeit Noel's repeated efforts to create interest around the project, there is no signs of any improvement. I am therefor calling a vote to mothball/pause the project. Please place your votes. [X] +1, go ahead and mothball/pause Lokahi, [ ] -1, don't mothball/pause Lokahi, because... (reason is optional, but appreciated) Cheers - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP clearance and copyright transfer
Sanjiva Weerawarana wrote: I was looking at: http://incubator.apache.org/ip-clearance/ip-clearance-template.html It seems to imply that we require copyright transfer as part of the IP clearance process. Since when do we require copyright transfer?? I thought we only require a license. Sanjiva. Sanjiva, I interpreted the wording exactly as you did. It's confusing. Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What should be the consequences of missing required Incubator Reports?
Bertrand Delacretaz wrote: On Tue, Jan 13, 2009 at 10:49 AM, Niclas Hedhman nic...@hedhman.org wrote: ...On Mon, Jan 12, 2009 at 5:44 PM, Noel J. Bergman n...@devtech.com wrote: I think that it is, unfortunately, time to have a discussion as to the consequences of what happens when a project misses its report. Perhaps not a one-off, but on a becoming regular process To me it sounds that the Mentors are sleeping Totally agree, it is the mentors responsibility to make sure their podlings submit their reports on time. -Bertrand Bill (Bluesky podling mentor) sheepishly agrees. Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: answers to IPMC comments of Bluesky December pmc report
Samul Kevin wrote: http://wiki.apache.org/incubator/December2008 IPMC comments: - jukka: Why the new server and web site? I don't seem to be able to access it (I'm in Switzerland). -Because we can't put source code on our offical website http://incubator.apache.org/bluesky/, and we want people to download the clean version code to help us check whether still there are code violate ASL. That's why we set up website at our school. And this address http://202.117.16.249 is an international address and should be visited from out net. Actually, the most important function of this site is to provide three version source code, anyone who can't access and want the code could write e-mail to me and i will send the source code to him. The http://202.* website is a staging website where we can perform review of bluesky material prior to it being brought into the ASF. The bluesky project originally contained a lot of LGPL/GPL code from various projects. The team has been making (slow and painful) progress reimplementing and refactoring code to resolve the license issues. Congratulations to the team for their work so far... - clr: What does it mean as soon as the code is granted by Apache community? -i mean as soon as legalization of our code is ensured by Apache community. I'm sorry for the inconvenience that my pooor English had caused. I've done an initial review of the Bluesky code to make sure it is 'clean' of legal issues. No problems found so far, but I'm not quite ready to declare it clean. A bit more due diligence is needed. When I am satisfied that the code is clean, I'll direct the Bluesky team to complete the code grant and we'll check the code into the ASF Bluesky repository. We've almost cleared a MAJOR hurdle for bringing the Bluesky project to the ASF. Excising the GPL/LGPL code from Bluesky has been a major, multi month effort and I sense that the effort is nearing completion. My expectation going forward ... after CNY (Chinese New Year), thsi project will begin to look more like a normal ASF project in incubation. Regards Bill (Bluesky Mentor) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Missing reports: BlueSky, JSecurity, Lokahi, WSRP4J, XAP
Jukka Zitting wrote: Hi, We're again missing reports from some incubating projects. I'd be very interested in seeing a report at least from BlueSky. I'll write something up. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache Tuscany Graduation as TLP
+1 Bill ant elder wrote: After 29 months in the incubator, 19 releases, 25 new committers, and tons of emails the Apache Tuscany community (with support from our mentors) again feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://apache.markmail.org/message/lss5jhjxail7m67r We would like the resolution below to be presented to the board for consideration at the next possible board meeting. For additional information, the Tuscany status file is here: https://svn.apache.org/repos/asf/incubator/tuscany/STATUS Thanks in advance for your time and consideration. ...ant X. Establish the Apache Tuscany 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, that simplifies the development, deployment and management of distributed applications built as compositions of service components. These components may be implemented with a range of technologies and connected using a variety of communication protocols. This software will implement relevant open standards including, but not limited to, the Service Component Architecture standard defined by the OASIS OpenCSA member section, and related technologies. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Tuscany Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is responsible for the creation and maintenance of software related to Apache Tuscany; and be it further RESOLVED, that the office of Vice President, Apache Tuscany 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 Tuscany Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Tuscany 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 Tuscany Project: * Adriano Crestani adrianocrestani at apache dot org * ant elder antelder at apache dot org * Brady Johnson bjohnson at apache dot org * Frank Budinsky frankb at apache dot org * Ignacio Silva-Lepe isilval at apache dot org * Jean-Sebastien Delfino jsdelfino at apache dot org * kelvin goodson kelvingoodson at apache dot org * Luciano Resende lresende at apache dot org * Mark Combellack mcombellack at apache dot org * Matthieu Riou mriou at apache dot org * Mike Edwards edwardsmj at apache dot org * Paul Fremantle pzf at apache dot org * Pete Robbins robbinspg at apache dot org * Raymond Feng rfeng at apache dot org * Simon Laws slaws at apache dot org * Simon Nash nash at apache dot org * Venkata Krishnan svkrish at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder be appointed to the office of Vice President, Apache Tuscany, 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 Apache Tuscany Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Tuscany podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Tuscany podling encumbered upon the Apache Incubator Project are hereafter discharged. - 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] NoNameYet - Pluto
William A. Rowe, Jr. wrote: Roland Weber wrote: I think that is a bit oversimplified. IBM has strict rules about open source participation. It is either on private time, such as my involvement at Apache. Then the person is acting as an individual. Or it is on company time. Then the person is doing what he or she is paid for. And if IBM is changing it's priorities, or the line item that required OSS participation is closed, plenty of other work will be dumped on that person, simply leaving no (work) time for OSS participation. Yes, Apache attaches all merits to the individual. But you cannot reasonably expect individuals that got paid for working on an Apache project to continue their involvement at a comparable level on private time, nor judge them for retiring. The ultimate cause of reduced activity here would be the employer's decision, not the individual's. You are absolutely right... Yep, Roland and Bill, I agree. Thanks to the efforts of Ken Coar and others, IBM, the corporate entity, has organizational knowledge (read process) for formally reviewing proposals to contribute code to open source communities. I've personally shutdown more than a few IBM proposals that would have been 'code dumps'. You might be surprised at how I most often do it... I show them how difficult it is to get through the internal review process . When they discover how hard it is to 'dump' code, they quickly lose interest. No one here would waste their time going to the effort to 'dump' code. The word 'dump' is a really bad metaphor. So is the process perfect? Of course not and that's a silly question as there is no such thing as a perfect process in the real world. I'm certain some IBM sponsored projects have not lived up to expectations. Open invitation to anyone reading this... if you detect a pattern of IBM dumping code, let me know. It's certainly possible that our internal process for vetting proposals is not strict as it should be. Convince me there is a problem and I will work to solve it on the IBM side. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve release CXF 2.0.4-incubator
+1 Bill Daniel Kulp wrote: We held a vote on cxf-dev to release a new version of CXF. This version is pretty much just a big bug fix rollup compared to 2.0.3 fixing over 50 JIRA issues reported by users and bugs encountered during some interop testing. For a full list of the issues, see: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312855styleName=HtmlprojectId=12310511Create=Create The vote thread is at: http://www.nabble.com/-VOTE--Release-CXF-2.0.4-incubator-to15025947.html In summary, we have 11 +1 votes, no 0 or -1 votes. Two of the votes are from ASF members (bsnyder and gnodet). I'm not sure if they are binding yet or not. (I think they both sent in requests to join the IPMC, just not sure if that is finished yet). The staging area is at: http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator The distributions are in the dist directory. The m2repo directory contains the stuff that will by pushed to the m2-incubating-repository. This release is tagged at: http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.4-incubator/ We and our users appreciate you taking the time to look over this release! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE Result] Project Bluesky has been accepted for Incubation
I am pleased to announce that project Bluesky has been accepted into the Apache Incubator with 24 votes in favor and no dissenting votes! Congratulations Bluesky team, this was an exceptionally high voter turnout for an incubator proposal! Thanks to everyone who contributed to the proposal, this promises to be a very interesting project. Link to the proposal is here: http://wiki.apache.org/incubator/BlueSky Next Steps: - Open an INFRA Jira to request mailing lists to be setup (Bill S) - Arrange to collect CLAs and user id preference from each project member (Bill) - Work on the CCLA (Bill) Bill Stoddard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Accept Bluesky Project into the Incubator
Thanks to everyone who made contributions to this proposal and special thanks to Niclas and Aaron for stepping up as mentors. The project is documented here: http://wiki.apache.org/incubator/BlueSky Please vote on accepting Bluesky into the Apache Incubator. The vote will run 1 week, beginning now, and will conclude Saturday, January 12, 2008. [ ] +1 Accept BlueSky for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason : Thanks, Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSSION] BlueSky Proposal
Yoav Shapira wrote: On Jan 3, 2008 11:07 PM, Niclas Hedhman [EMAIL PROTECTED] wrote: On Thursday 03 January 2008 07:09, Bill Stoddard wrote: Can the team meet the challenge? I think we should get going, and then resolve and evaluate these issues as part of incubation. Agreed, let's do it. +1 to BlueSky coming into the Incubator. Yoav I will post a vote thread later today! Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSSION] BlueSky Proposal
Thanks for the good comments. Ting Peng, All successful open source projects share one thing in common... they have active and diverse developer communities (and hopefully a growing user community). The word and concept of 'community' is extremely important. A project's development community works together, collaborates, to define the goals of the project, ensure that code is high quality and secure, and create releases for end users. ASF projects cannot exist without community. The Incubator PMC will not allow projects to graduate from Incubation if they fail to establish an active and diverse developer community. This is why Bertrand's comments are extremely important. To be accepted into incubation, the Bluesky team must commit to doing development in an open, public and transparent way. When a project is accepted into Incubation, the project will get a website (or wiki space), an SVN source code repository, and a mailing list to be used by the development team. The bluesky team must: 1. use the developer mailing list, website and wiki to conduct most all of the communication between team members regarding design and development decisions The mailing list archive should almost be a 'design document', where design decisions are discussed openly and team members are given a chance to comment on decisions. 'hallway' and face to face discussion resulting in design decisions should be avoided if possible, and when they do happen, someone must capture the decision in an email sent to the mailing list so the community can see how the project is evolving. 2. In order to grow the community as large as possible, the ASF requires that all development communication be conducted in English. This allows people from all over the world to follow the project, watch it evolve and contribute. It's perfectly okay to provide documentation in other languages, but most discussions about project design and implementation decisions must be conducted in English in a public forum (mailing list, wiki, etc). If the Bluesky project is accepted into Incubation, will the Bluesky team be able to commit to conducting project communications in the public in English? This is a significant challenge to the Chinese developers on the Bluesky team. Can the team meet the challenge? 新年快乐, Happy New Year! Bill Bertrand Delacretaz wrote: On Dec 19, 2007 12:43 AM, Bill Stoddard [EMAIL PROTECTED] wrote: ...I've updated the BlueSky project proposal. Ting Peng and Incubator PMC, please review/update as needed and report back any concerns I have two concerns about http://wiki.apache.org/incubator/BlueSky: ...weekly development summary on this web site: http://www.p12.edu.cn/ (Currently, only available in mainland of China)... I think we need a committment from the BlueSky team that all information and artifacts related to the project will be available worldwide. I know nothing about how things work in China in this respect, but having parts of the project segregated is not acceptable, IMHO. That might make some community members second-class citizens if they don't have access to everything. Currently, we have built official site of BlueSky, which is located at http://202.117.16.176/ . This website is worldwide available. You are welcomed to visit this website. ...Documentation All in Chinese now... In the same vein, we need to make it very clear that all project-related communications have to happen in english on the ASF mailing lists and websites. I don't think the ASF would be able to provide the necessary oversight for anything happening in Chinese, just as we don't support other languages at the moment. Sorry if I sound negative, I agree that the goals of the project are important, but I also see a risk of creating a project that might live on its own island, with very little ties to the rest of the ASF. I'm not saying it's impossible, but IMHO we have to make sure that the necessary agreements are in place before going further. We have already written some documents about project BlueSky. These includes technical structure, source code, compiling instructions and screenshots. All of them are in English. More documents are in preparing. -Bertrand If anyone has any advice about our project BlueSky, please let us know. We do need your help. Merry Christmas and Happy New Year! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Move Project Yoko to Apache Geronimo and Apache CXF
+1 Bill Matt Hogstrom wrote: Below is a proposal that was discussed and brought forward by the Yoko Community. In a nutshell the proposal is to create a Yoko sub-project of Apache Geronimo for the Core ORB and to move the bindings to CXF. Please read the proposal below for all the detail. This proposal was brought forward to the Apache Geronimo and Apache CXF communities. Both communities have voted to accept this proposal. Vote results from Apache Geronimo were 20 +1 votes and no 0 or -1 votes. 17 were binding from the Geronimo PMC. CXF Results on the CF Dev list were 13 +1 votes and 1 0 vote I am now bringing this to the Incubator for final approval so that the code can be moved from Incubator to the respective receiving projects. This proposal was previously sent to the IPMC for comment while the respective communities discussed and voted. During that time there has been no comments that indicated there was an issue so I bring this vote back to the Incubator for finalization: [ ] +1 Approve the below proposal and code migration to Apache Geronimo and CXF respectively [ ] 0 No opinion [ ] -1 Do not approve of the move (please provide rationale If someone wants to comment on this thread please use the Alternate [DISCUSS] thread and not the vote thread. This vote will conclude on Dec 14th at 0900 ET. Original Proposal The members of project yoko have been considering the future of Yoko as a project. There have been several milestones delivered and the project is used by other ASF projects. The project is not as active as other ASF projects and it makes sense to move the code from Yoko to other projects. The Yoko team has the following proposal for your consideration. Proposed Code Donation from Project Yoko to Apache CXF and Apache Geronimo The Yoko community has been successful in delivering several milestones of the ORB implementation while in the Apache Incubator. These milestones are used by other Apache projects (namely Geronimo and Harmony) to support their releases. The WebServices bindings are dependent on CXF. The Yoko community has decided that the Yoko project does not have quite the momentum to carry itself as an independent project but has sufficient value for other projects for them to consider receiving the code and committers for that code-base as sub-projects. Since the code under consideration is used by Apache Geronimo, Apache CXF and Apache Harmony the movement of the code should continue to allow for independent releases so the code can be easily shared with other dependent projects. The proposed division is: yoko-spec-corba - this is the org.omg interface classes. rmi-spec - this is the javax.rmi spec implementation core - This is the actual ORB implementation. rmi-impl - This is the implementation of the RMIIIOP support. These modules are also used by Harmony. In addition to the code we propose that the following committers in Apache Yoko be accepted as committers in Apache Geronimo given their demonstration of delivering code, creating releases and functioning as a community. Those noted with asterisks are already Geronimo committers. Continued involvement with the core: Rick McGuire * David Jencks * Alan Cabrera * Lars Kuhne Alexey Petrenko Darren Middleman The remainder of the modules in Yoko are part of the webservices support and are independent of the underlying ORB implementation. api -- interface classes used for the web services support. bindings -- code to implement the CORBA-Web services bindings. tools -- tools for generation WSDL and IDL for the bindings maven-plugin -- some maven plugins that can use the tools for generating binding-related build artifacts. None of the maven-plugin code is used by the ORB. There is also a distribution directory with some sample applications. One set of samples demonstrates using the core ORB, the other set is for WebServices. We recommend that the distribution directory should move to Apache CXF as the webservices examples use the orb samples to bind them as web services. Since Apache Geronimo's only use of CORBA is for exporting EJBs, these samples are not particularly valuable for Geronimo. The Yoko community did not have any committers that expressed an interest in continuing work on these bindings. As such, only the code would be moving to apache CXF. - 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] Graduate Woden into the WS PMC
Niclas Hedhman wrote: On Monday 03 December 2007 23:09, Paul Fremantle wrote: Here is my +1. Paul +1, With a note that IBM's contribution to the project *seems* to be a worryingly large proportion. I still vote +1 as I am convinced that the WS PMC will be able to deal with that if it becomes a problem. If Woden were seeking TLP, I would probably not vote in favor. Now, get out of here... ;o) Cheers +1 echo'ing Niclas' concerns. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE RESULT] Accept project Imperius into the Incubator
The Imperius Project has been accepted into Apache Incubation with no dissents and the following votes in favor: Yoav Shapira, Niclas Hedhman, Craig Russell, Matthieu Riou, Niall Pemberton, Robert Burrell Donkin Bertrand Delacretaz expressed concern about the number of mentors. Bertrand, thanks for the feedback, I believe your concern has been resolved. Project Mentors: Bill Stoddard, Filip Hanik, Craig Russell, Kevan Miller (non-binding) Link to Project Proposal: http://wiki.apache.org/incubator/ImperiusProposal -//- 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. Congratulations Imperius Project Members! Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE RESULT] Accept project Imperius into the Incubator
Next Steps... David, Mike, Neeraj, Mark and Prashant, you should: 1. Complete and return ICLAs to the ASF http://www.apache.org/licenses/icla.txt (flat text file) http://www.apache.org/licenses/icla.pdf (PDF) You will not be given commit access to the Imperius source code repository until you sign the ICLA. 2. Review material at the the following links: http://www.apache.org/foundation/how-it-works.html http://www.apache.org/licenses/ 3. Ask questions!! David, Review and start working on the software grant: http://www.apache.org/licenses/software-grant.txt I will ask infra to setup the mailing lists. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal Draft]BlueSky-Wish to ADD
Ni Hao, Ting Peng This is an interesting project. I'm happy to be a mentor if the project is accepted for incubation. How familiar is the Bluesky team with open source development at the Apache Software Foundation? I'll be in Beijing the week of 12/3. If you are interested, I can fly to Xi'an on 12/8 and meet with the Bluesky developers at XJTU and talk about open source development at the ASF. I must depart Xi'an on 12/11. Let me know if you are interested, I would really enjoy meeting with you. Regards, Bill Ting Peng wrote: Hello, everyone! Now, we are going to move our project BlueSky (Blue Sky Distance Collaboration System) to Apache Incubator for future development. Its aim is to make people under the sky to communicate and share resources with each other more easily. When, the system is employed, users can communicated via audio/video(computer screen also included) and text at the same time. In other words, Multi-Object Multimedia capable makes the system more vivid and glamorous. Cosmic Resource Share Management System is also included. It provides unique portal for users to share resources(such as multi-object multimedia course ware). It's proposal is at http://wiki.apache.org/incubator/BSDCSProposal The system has been developed for years, more than 20 persons are involved. It is used in distance learning in primary and middle schools in China. More than 40,000 students has benefited from it. Our developing website is http://202.117.16.176/ , source code is also available. All source code of this project is written by ourselves, no third part components are included. Currently, all developers of Blue Sky Distance Collaboration System are not native speaker of English. But we don't have any obstacles to communicate in English on technical topics. We want to share our work with people who is interested in it around the world. We want new volunteers to make our team more diverse, active and creative. For this is our first candidate project to Apache Foundation. We are grateful for your ideas! We are looking forward for your advice! -- Best regards! Ting Peng ([EMAIL PROTECTED]) XJTU-IBM Open Tech. RD Center - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soliciting mentors for Imperius project ... [VOTE] Accept project Imperius into the Incubator
Craig L Russell wrote: Hi, I'm currently mentoring two other projects, so it's not clear how much time I can put in. With that disclaimer, I'm happy to volunteer as a mentor. Craig Thanks Craig! I expect to get the outstanding vote wrapped up by end of this week. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soliciting mentors for Imperius project ... [VOTE] Accept project Imperius into the Incubator
Thanks Filip. Would like one more mentor... anyone? Bill Filip at Apache wrote: I'd be happy to help out and join as a mentor Filip Bill Stoddard wrote: Anyone care to join me mentoring the Imperius project? Thanks, Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Accept project Imperius into the Incubator
of the ASF. We believe that such synergy, along with the shared philosophy, and process and licensing consideration, make the ASF the proper community. Scope --- The scope of the Imperius project at ASF would be to continue the project development, including adding new features and bindings, and improving overall code quality, scalability and performance. Documentation -- The CIM-SPL specification: http://www.dmtf.org/standards/published_documents/DSP0231.pdf Initial Source The initial source, a prototype SPL engine, has been developed. Source and Intellectual Property Submission Plan -- The source comes from IBM. IBM will submit a CCLA if the incubator proposal is accepted. Information about DMTF policies can be found in references [1], [2] and [3]. External Dependencies - None Cryptography -- None implemented in the code. Resources Required (3.1) mailing list(s) -imperius-private (with moderated subscriptions) -imperius-dev -imperius-commits -imperius-user (3.2) Subversion or CVS repositories Imperius would like to use a SVN repository. (3.3) Jira (issue tracking) Since Imperius would have its own release cycle, it should have its own JIRA project -Project Name: Imperius -Project Key: Imperius Initial Committers -Mike Nunez Michael.Nunez at Sun.COM -Neeraj Joshi jneeraj at us.ibm.com -Mark Carlson Mark.Carlson at Sun.COM -Prashant Baliga prabalig at in.ibm.com Sponsors -- Champion -Bill Stoddard([EMAIL PROTECTED]) Nominated Mentors -Bill Stoddard([EMAIL PROTECTED]) Sponsoring Entity - Incubator PMC References [1] http://www.dmtf.org/about/policies [2] http://www.dmtf.org/standards/published_documents/DSP4004.pdf [3] http://www.dmtf.org/about/policies/patent-10-18-01.pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Imperius (was SPL) Incubator Proposal
David L Kaminsky wrote: All, I updated the proposal to include the new proposed project name. Imperius seems to be cleaner than the alternatives. I also added the references to the DMTF's IP policy. Please let me know if there are more questions. (Please CC [EMAIL PROTECTED]) Thanks, David Discussion seems to be wrapping up. Thanks for all the great comments and suggestions. Unless I hear objections, I'll call for a vote to accept Imperius into the incubator later this week. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] JSPWiki
snip JSPWiki is a wiki engine available under the Lesser General Public License. snip The initial goals of the project is to release JSPWiki 2.8 under the Apache license: Successfully executing the license change could prove to be a challenge. All past contributors to the project will need to agree to the license change. Contributions from those who do not agree to the license change (either because they cannot be tracked down or they just simply disagree with the license change) will need to be reverted and reimplemented. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] (repost) Propose OpenEJB for graduation to a TLP
Brett Porter wrote: After the previous discussion, the proposal has been amended to include the new wording. We will restart the vote. Please cast your votes on whether to recommend this proposal. +1 Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Formally retired the Wadi project
Noel J. Bergman wrote: Brian McCallister wrote: I think wadi withdrew from incubation. It seems alive here: http://wadi.codehaus.org/ Correct. +1 to formally retire it. --- Noel +1 Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Publish Yoko M2 Release
Rick McGuire wrote: The Yoko community voted on and has approved a proposal to release Yoko Milestone 2. Pursuant to the Releases section of the Incubation Policy we would now like to request the permission of the Incubator PMC to publish the milestone on the Yoko Download page. +1 Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BouncyCastle IDEA patent
David Jencks wrote: On Feb 21, 2007, at 12:38 PM, Jeremy Boynes wrote: On Feb 21, 2007, at 12:05 PM, Matt Hogstrom wrote: Regarding Bouncy Castle, IIRC they used to include the IDEA algorithm in their distribution and provided a one-off for Geronimo to use to bypass the patent issue. Not sure if that is an issue or not for Tuscany but just a heads up. IIUC RC the resolution to this is that we copied the non-patent-related bouncycastle code into the geronimo-util module because bouncycastle declined to produce an unencumbered release. I'd suggest that if you don't need the patented code you use the geronimo-util jar instead. Yep, that's my recollection as well. thanks david jencks Bill Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Request to release Tuscany C++ M1
Pete Robbins wrote: We have held a vote on tuscany-dev@ws.apache.org to publish a release of the Tuscany C++ implementation. The vote email thread is available here: http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg05134.html http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg05134.html+ In summary we have 4 +1 votes from committers and no 0s or -1s. We would like to request approval from the Incubator PMC to release this version. The candidate distribution is available here: http://people.apache.org/~robbinspg/RC-3b/ Thank you. --- Pete +1 Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pre-proposal] AsyncWeb
Justin Erenkrantz wrote: On 7/15/06, Alex Karasulu [EMAIL PROTECTED] wrote: Everyone else that has been working with Dave is already an ASF committer with a CLA on file at the ASF: Trustin Lee Dan Diephouse Alex Karasulu Yes let's get that software grant and a CLA from you Dave. Considering the constituents of the project at safehaus we might be able to take up Justin's earlier suggestion to possibly import the project: moving the source, doco (confluence) and jira issues all at once to the ASF. I think then a software grant and iCLA/CCLA plus a completed IP Clearance form from an ASF Officer or Member is sufficient (see the IP clearance template for the instructions on submission). Depending upon how substantial the contributions were from the 3 ASFers, we might need Trustin, Dan, and Alex to also sign the software grant too for AsyncWeb. The official policy is that we need software grants signed from all developers - but if you guys just submitted minor patches, that's probably not necessary - but if you developed large chunks of AsyncWeb too, then a grant should be filed too even though you have iCLAs on file. Also note that there are no dependencies except on MINA. Good. Why don't we start the process of importing the project into Directory for now as a MINA protocol example and get the MINA TLP proposal before the board. With the move of MINA (and AsyncWeb) out of Directory, AsyncWeb will be under a MINA TLP. Honestly, I'd recommend flipping it: get MINA to be TLP first and then move in AsyncWeb. There's no reason that AsyncWeb should land in the Directory TLP and then move again in short-order. Ensure that the submitted charter of MINA can incorporate AsyncWeb sufficiently. If you submit the resolution ASAP, it'll make it into this month's Board meeting (which is likely to be Wednesday, but that's not confirmed yet). You can add Dave to the initial MINA PMC roster even though his project isn't in just yet, too. Or, you can add him after the IP paperwork is filed too - whatever works best. Or do you still see incubation as being necessary for AsyncWeb even after getting a Grant and CLA from Dave? I personally don't think so. We're talking about one committer joining an already existing ASF project and that individual has already worked with at least three other ASFers. If the legal paperwork is filed (i.e. grant and iCLA/CCLA), I don't see the point of 'full' Incubation. MINA's getting a chunk of code...the Incubator PMC just needs to ensure that the legal paperwork is received first. +1. Very interesting project BTW. Hope I can find time to participate ;-) Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Request to release (revised) Tuscany M1
Bill Stoddard wrote: Jeremy Boynes wrote: We voted on tuscany-dev on a revised version that addresses the issues Robert raised below and the results can be viewed at http://article.gmane.org/gmane.comp.apache.webservices.tuscany.devel/3403 We would like to request approval from the Incubator PMC to release this new version. The candidate distribution can be found at http://people.apache.org/~jsdelfino/test-incubating-M1/ Thanks -- Jeremy +1 Bill I just noticed this distribution redistributes (unmodified?)the MPL 1.1 licensed Rhino JavaScript engine. MPL 1.1 is significantly more restrictive than the AL 2. Is this a concern? Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubator PMC to approve ActiveMQ 4.0 Release
James Strachan wrote: In accordance with the incubator release procedure (see below) the ActiveMQ community has voted on and approved the 4.0 release binary. We would now like to request the permission of the Incubator PMC to perform the release. +1 Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Request to release (revised) Tuscany M1
Jeremy Boynes wrote: We voted on tuscany-dev on a revised version that addresses the issues Robert raised below and the results can be viewed at http://article.gmane.org/gmane.comp.apache.webservices.tuscany.devel/3403 We would like to request approval from the Incubator PMC to release this new version. The candidate distribution can be found at http://people.apache.org/~jsdelfino/test-incubating-M1/ Thanks -- Jeremy +1 Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Incubator PMC to approve the 4.0-RC2 release of ActiveMQ
James Strachan wrote: Please correct accordingly, as neither appears to be the case currently. Will do; I'll call a 4.0-RC3 vote shortly when we've got a new distro... -- James James, I just reviewed RC3 (placed in the repo 4/13) and it looks good. I'll give it a +1 when your ready to call a vote. Bill --- http://radio.weblogs.com/0112098/ - 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]
