Re: [VOTE] Accept Groovy into the Apache Incubator
+1 On Mar 19, 2015, at 9:55 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/KWE I would like to call a VOTE for accepting Groovy as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/GroovyProposal and is also included at the bottom of this email. Vote is open until at least Saturday, 21st March 2015, 23:59:00 PST [ ] +1 accept Groovy in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == Groovy is an object-oriented programming language for the Java platform. It is a language with features similar to those of Python, Ruby, Java, Perl, and Smalltalk. Groovy, if accepted by Incubator, will be a first major programming language developed under the umbrella of Apache Software Foundation. == Proposal == Groovy is a programming language for the Java platform. It is a primarily dynamic language with features similar to those of Python, Ruby, Perl, and Smalltalk. It also has optional static type checking and static compilation facilities. It can be used as a scripting language for the Java Platform or to write complete applications, is compiled to Java Virtual Machine (JVM) bytecode, and interoperates with other Java code and libraries. Groovy uses a Java-like curly-bracket syntax. Most Java code is also syntactically valid Groovy, although semantics may be different. Groovy has long been developed under an Apache License v2.0 under an open governance community management process. However, so far Groovy has been a project mostly sponsored by a single company. This proposal aims at bringing Groovy community under the umbrella of the Apache Software Foundation. It must be explicitly noted, that a few sister projects such as Groovy Eclipse and others (some of them hosted under https://github.com/groovy and listed at http://groovy-lang.org/ecosystem.html) are not covered by this proposal. It is possible that these other projects will be joining ASF either independently or as sub-projects of Apache Groovy in the future. For now, we are only proposing groovy-core. == Background == Groovy 1.0 was released on January 2, 2007, and Groovy 2.0 in July, 2012. Groovy 2.5 is planned for release in 2015. Groovy 3.0 is planned for release in 2016, with support for a new Meta Object Protocol. Since version 2, Groovy can also be compiled statically, offering type inference and performance very close to that of Java. Groovy 2.4 will be the last major release under Pivotal Software's sponsorship, which is scheduled to end on March 31, 2015. == Rationale == Groovy is a pretty mature language. After 12 years of development, it has grown from being primarily a dynamic scripting language on the JVM to an optionally statically compiled language allowing the same performance level as Java applications. With the release of Groovy 2.4, the language targets the largest pool of mobile developers with native Android support. Groovy has been integrated in a large number of applications, including well known open-source projects like Jenkins, Gradle, ElasticSearch, Spring and more. There are multiple alternative languages on the JVM: Scala, Clojure, Ceylon, Kotlin, JRuby, Golo and others but Groovy is the only one which has proved to be very easy to integrate with Java in both ways: Groovy code using Java code, but also Java code using Groovy code. Groovy even provides a joint compiler which allows interdependent Java and Groovy classes to compile together. Groovy also supports dynamic code generation, that is to say classes at runtime, making it a perfect fit for scripting. With a very lightweight and malleable syntax, it is also easy to build internal Domain Specific Languages (DSLs) which integrate smoothly within applications. Groovy provides a number of unique features, like builders (Java 8 has lambdas but still has syntactic overhead and no notion of delegate), AST transformations (compile-time metaprogramming) or type checking extensions (which allows the developer to bring the compiler to levels of type checking and type inference that go far beyond what other languages do). Groovy also provides powerful integration options and customizations which set it apart from other languages. Groovy is also unique in the way it allows the developer to choose between various paradigms without compromise: functional vs object-oriented, statically compiled vs dynamic, scripting vs applications, etc. Despite all those advantages, and the fact that Groovy is widely adopted (4.5 million downloads in 2014 for Groovy alone), only a few Apache projects include Groovy and not a lot of them leverage its full power. Some developers tend to choose Scala for example to build DSLs without even knowing that the learning curve is much easier with Groovy, or that they can leverage powerful type inference in their own DSLs.
Re: [VOTE] Graduate OpenMeetings from Incubator
+1 On Dec 2, 2012 6:51 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubation members, During incubation, OpenMeetings has : * Produced 1 Release * Added 5 new Committer/PPMC members and shows constant community activities * Cleared IP on all code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that Given these accomplishments, I propose that we submit the following graduation resolution to the incubator PMC. We organized already a community vote: http://markmail.org/thread/wnxvkvukdqgdddpn The vote received: 1x +1 Yegor IPMC 5x +1 solomax, aaf, sebawagner, greenes PMC 1x +1 Irina Please VOTE over the next 72 hours on the resolution below: [ ] +1 Graduate OpenMeetings from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate OpenMeetings from the Incubator because: = Charter here: https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter and copied below: X. Establish the Apache OpenMeetings 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 OpenMeetings Web-Conferencing tool. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache OpenMeetings Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is responsible for the creation and maintenance of software related to the OpenMeetings Web-Conferencing tool; and be it further RESOLVED, that the office of Vice President, Apache OpenMeetings 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 OpenMeetings Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenMeetings 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 OpenMeetings Project: * Alexei Fedotova...@apache.org * Sebastian Wagner sebawag...@apache.org * Maxim Solodovnik solo...@apache.org * Oliver Becherer smoe...@apache.org * Rodion Volkovrc...@apache.org * Eugen Schwert eschw...@apache.org * German Grekhovggrek...@apache.org * Timur Tleukenov ti...@apache.org * Alvaro Bustos Ruiz al...@apache.org * George Kirkham gkirk...@apache.org * Stephen Cotthammegatroni...@apache.org * Sascha Xander sxan...@apache.org * Evgeny Rovinskyrovin...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner be appointed to the office of Vice President, Apache OpenMeetings, 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 OpenMeetings 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 OpenMeetings Project; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenMeetings podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenMeetings 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] Graduate Syncope podling from Apache Incubator
+1 Looking forward to actually using Syncope soon. On Nov 2, 2012, at 1:43 PM, Emmanuel Lécharny elecha...@gmail.com wrote: a big +1 ! Excellent work, guys ! Le 11/2/12 10:00 AM, Francesco Chicchiriccò a écrit : Hi all, this is a call for vote to graduate the Syncope podling from Apache Incubator. Syncope entered the Incubator in Feb 2012. Since then it has added two new committers and PPMC members, picked up a couple of new contributors, and made some releases following the ASF policies and guidelines. The community of Syncope is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. The Syncope community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Syncope podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Syncope podling [ ] -1 Reject graduation of Syncope podling from Apache Incubator because ... This vote will be open for at least 72 hours. Please find the proposed board resolution below. [1] http://s.apache.org/up [2] http://s.apache.org/A8u Regards. Resolution: X. Establish the Apache Syncope 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 managing digital identities in enterprise environments. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Syncope Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Syncope Project be and hereby is responsible for the creation and maintenance of software related to the Identity Management and be it further RESOLVED, that the office of Vice President, Apache Syncope 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 Syncope Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Syncope 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 Syncope Project: * Colm O Heigeartaigh cohei...@apache.org * Emmanuel Lécharny elecha...@apache.org * Fabio Martelli fmarte...@apache.org * Francesco Chicchiriccò ilgro...@apache.org * Jan Bernhardt jbernha...@apache.org * Jean-Baptiste Onofré jbono...@apache.org * Massimiliano Perrone ma...@apache.org * Marco Di Sabatino Di Diodoro mdisabat...@apache.org * Simone Tripodi simonetrip...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Francesco Chicchiriccò be appointed to the office of Vice President, Apache Syncope 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 Syncope Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Amber podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Amber podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com - 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] [IP clearance] OpenDDR resources file donation to DeviceMap podling
Ok, fair enough. My goal was to make everyone aware of the nastiness surrounding wurfl.xml, and that goal is hereby achieved :) Now let's concentrate on the IP evaluation process. Here is my +1 for this vote. Andrus On Sep 28, 2012, at 9:25 PM, Benson Margulies bimargul...@gmail.com wrote: On Fri, Sep 28, 2012 at 2:06 PM, Andrus Adamchik and...@objectstyle.org wrote: Hi Bertrand, OpenDDR combining forces with DeviceMap is great news! And having the resource file will make it very useful immediately. Regarding this vote.. While the original wurfl.xml was clearly open source, and I am going to cast a positive vote to accept it in DeviceMap, I am fairly certain that once we do that and start releasing it, we'll hear from Scientiamobile trolls. So is Incubator PMC an appropriate body to decide on this risk? Should the Board get involved? I don't think that the IPMC or the board is interested in a troll analysis. What we need here, as always, is a grant that satisfies both the legal grant of a license and the Foundation's requirement for a clear, voluntary, grant. (You are a Board member yourself of course :)) Andrus On Sep 28, 2012, at 6:21 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, IP clearance usually works by lazy consensus, but in this case I'd like an explicit vote, as the donation described at [0] includes data that when hosted on Github has caused a DMCA takedown request [1] to which OpenDDR responded [2]. I guess from our point of view the decision is whether the donation of that data can be considered voluntary, as the ownership of the original data is somewhat unclear. The header of the original data file [2] states that the information listed here has been collected by many different people from many different countries, but in [1] a copyright on that data is asserted. The code parts of the OpenDDR donation are not affected, so I'd like Incubator PMC members to vote as follows: [ ] +1, accept the OpenDDR donation including the OpenDDR-Resources_1.0.0.10.zip data [ ] -1, do not accept the OpenDDR-Resources_1.0.0.10.zip (but the other parts are ok) IMO the alternative, if we don't accept the resources part of the donation, is to ask OpenDDR to come up with a resources file that contains only their own original work. The vote is open for at least 72 hours (will leave it open a bit more due to TGIF). -Bertrand (DeviceMap mentor) [0] http://incubator.apache.org/ip-clearance/devicemap-openddr.html [1] https://github.com/github/dmca/blob/master/2012-01-04-scientiamobile.markdown [2] http://openddr.org/takedown.html (looks down right now, Google cache at http://s.apache.org/openddr_cache just in case) - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [IP clearance] OpenDDR resources file donation to DeviceMap podling
Ok, fair enough. My goal was to make everyone aware of the nastiness surrounding wurfl.xml, and that goal is hereby achieved :) Now let's concentrate on the IP evaluation process. Here is my +1 for this vote. Andrus On Sep 28, 2012, at 9:25 PM, Benson Margulies bimargul...@gmail.com wrote: On Fri, Sep 28, 2012 at 2:06 PM, Andrus Adamchik and...@objectstyle.org wrote: Hi Bertrand, OpenDDR combining forces with DeviceMap is great news! And having the resource file will make it very useful immediately. Regarding this vote.. While the original wurfl.xml was clearly open source, and I am going to cast a positive vote to accept it in DeviceMap, I am fairly certain that once we do that and start releasing it, we'll hear from Scientiamobile trolls. So is Incubator PMC an appropriate body to decide on this risk? Should the Board get involved? I don't think that the IPMC or the board is interested in a troll analysis. What we need here, as always, is a grant that satisfies both the legal grant of a license and the Foundation's requirement for a clear, voluntary, grant. (You are a Board member yourself of course :)) Andrus On Sep 28, 2012, at 6:21 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, IP clearance usually works by lazy consensus, but in this case I'd like an explicit vote, as the donation described at [0] includes data that when hosted on Github has caused a DMCA takedown request [1] to which OpenDDR responded [2]. I guess from our point of view the decision is whether the donation of that data can be considered voluntary, as the ownership of the original data is somewhat unclear. The header of the original data file [2] states that the information listed here has been collected by many different people from many different countries, but in [1] a copyright on that data is asserted. The code parts of the OpenDDR donation are not affected, so I'd like Incubator PMC members to vote as follows: [ ] +1, accept the OpenDDR donation including the OpenDDR-Resources_1.0.0.10.zip data [ ] -1, do not accept the OpenDDR-Resources_1.0.0.10.zip (but the other parts are ok) IMO the alternative, if we don't accept the resources part of the donation, is to ask OpenDDR to come up with a resources file that contains only their own original work. The vote is open for at least 72 hours (will leave it open a bit more due to TGIF). -Bertrand (DeviceMap mentor) [0] http://incubator.apache.org/ip-clearance/devicemap-openddr.html [1] https://github.com/github/dmca/blob/master/2012-01-04-scientiamobile.markdown [2] http://openddr.org/takedown.html (looks down right now, Google cache at http://s.apache.org/openddr_cache just in case) - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [IP clearance] OpenDDR resources file donation to DeviceMap podling
Hi Bertrand, OpenDDR combining forces with DeviceMap is great news! And having the resource file will make it very useful immediately. Regarding this vote.. While the original wurfl.xml was clearly open source, and I am going to cast a positive vote to accept it in DeviceMap, I am fairly certain that once we do that and start releasing it, we'll hear from Scientiamobile trolls. So is Incubator PMC an appropriate body to decide on this risk? Should the Board get involved? (You are a Board member yourself of course :)) Andrus On Sep 28, 2012, at 6:21 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, IP clearance usually works by lazy consensus, but in this case I'd like an explicit vote, as the donation described at [0] includes data that when hosted on Github has caused a DMCA takedown request [1] to which OpenDDR responded [2]. I guess from our point of view the decision is whether the donation of that data can be considered voluntary, as the ownership of the original data is somewhat unclear. The header of the original data file [2] states that the information listed here has been collected by many different people from many different countries, but in [1] a copyright on that data is asserted. The code parts of the OpenDDR donation are not affected, so I'd like Incubator PMC members to vote as follows: [ ] +1, accept the OpenDDR donation including the OpenDDR-Resources_1.0.0.10.zip data [ ] -1, do not accept the OpenDDR-Resources_1.0.0.10.zip (but the other parts are ok) IMO the alternative, if we don't accept the resources part of the donation, is to ask OpenDDR to come up with a resources file that contains only their own original work. The vote is open for at least 72 hours (will leave it open a bit more due to TGIF). -Bertrand (DeviceMap mentor) [0] http://incubator.apache.org/ip-clearance/devicemap-openddr.html [1] https://github.com/github/dmca/blob/master/2012-01-04-scientiamobile.markdown [2] http://openddr.org/takedown.html (looks down right now, Google cache at http://s.apache.org/openddr_cache just in case) - 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: Your vote is casting Was: Openmeetings release approval by Incubator PMC Was: Incubation state transitions and stuck projects (Was: February report review)
BTW, most current people's memberships across apache cane be checked here: http://people.apache.org/committer-index.html On Jul 24, 2012, at 2:12 PM, Alexei Fedotov wrote: Andrus, thanks! We also have a shepherd. Matt, aren't you, by chance, IPMC? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Mon, Jul 23, 2012 at 5:33 PM, Andrus Adamchik and...@objectstyle.org wrote: Hi Alexei, I am listed as a mentor in error at http://incubator.apache.org/projects/openmeetings.html . I was the champion on the proposal. But even though I like the project, I knew I wouldn't be able to lead you through incubator and give all needed attention due to other commitments. So I indicated back then that I am stepping down after incubator entry. So I guess we should take my name from the mentor list. Having said that, I'll be happy to lend a hand on this occasion and I am still an IPMC member. Just give me some time to evaluate the release. One more note - you actually need 2 more votes. Only Egor's (yegor) vote is binding. You are listed as a mentor, but you don't appear to be an IPMC member. This means we'll need help from Ross and/or Jim. And maybe we can enroll new mentors. Anyone? Andrus On Jul 23, 2012, at 7:50 AM, Alexei Fedotov wrote: Jukka, thanks for explaining. Ross, Andrus, would you please consider voting for the Openmeetings release? We are stuck with insufficient number of votes. Thanks! Incubator folks, Don't allow another little cute kitten and fluffy puppy die by missing Apache Openmeetings (Incubating) release: http://demo.openmeetings.de/openmeetings/ http://demo.dataved.ru/openmeetings/ You are mostly welcome to support our release here http://markmail.org/message/azenwwlcfhnxmysf -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The release vote have successfully passed and forwarded to general@ list [1]. What should be our next step? Have we got Incubator PMC approval? Can we proceed with wider distribution? See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases for the Incubator policy on releases. You're almost done, just an extra approval vote on general@ is still needed (and since you already have two mentor +1s, you only need one more IPMC member to vote for the release). BR, Jukka Zitting - 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] Approve Openmeetings (Incubating) release
+1 (binding) I notice you've done lots of ASF compliance-related work recently, going through 4 release candidates. Really appreciate your patience and resolve to get things right. Using Rat and scanning through the distro I couldn't find any new holes in the current iteration. Also just noticed that Red5 is ASF licensed now, which I am sure makes everyone in OM community happy :) Andrus On Jul 23, 2012, at 1:03 PM, Alexei Fedotov wrote: The Openmeetings community voted on and has approved a proposal to release Openmeetings 2.0. Pursuant to the Releases section of the Incubation Policy and with the endorsement of two of our mentors we would now like to request the permission of the Incubator PMC to publish the release on the Download page. Please vote by 26 July 10 AM GMT Thanks, Alexei Proposal: http://markmail.org/message/aahmijcb5dsjlxiv Vote result: http://markmail.org/message/azenwwlcfhnxmysf Download page: http://www.apache.org/dist/incubator/openmeetings Releases section of the Incubation Policy: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Demos Kittens http://markmail.org/message/oqj3eko732rx2cgy On Mon, Jul 23, 2012 at 11:50 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Jukka, thanks for explaining. Ross, Andrus, would you please consider voting for the Openmeetings release? We are stuck with insufficient number of votes. Thanks! Incubator folks, Don't allow another little cute kitten and fluffy puppy die by missing Apache Openmeetings (Incubating) release: http://demo.openmeetings.de/openmeetings/ http://demo.dataved.ru/openmeetings/ You are mostly welcome to support our release here http://markmail.org/message/azenwwlcfhnxmysf -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The release vote have successfully passed and forwarded to general@ list [1]. What should be our next step? Have we got Incubator PMC approval? Can we proceed with wider distribution? See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases for the Incubator policy on releases. You're almost done, just an extra approval vote on general@ is still needed (and since you already have two mentor +1s, you only need one more IPMC member to vote for the release). BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Your vote is casting Was: Openmeetings release approval by Incubator PMC Was: Incubation state transitions and stuck projects (Was: February report review)
Hi Alexei, I am listed as a mentor in error at http://incubator.apache.org/projects/openmeetings.html . I was the champion on the proposal. But even though I like the project, I knew I wouldn't be able to lead you through incubator and give all needed attention due to other commitments. So I indicated back then that I am stepping down after incubator entry. So I guess we should take my name from the mentor list. Having said that, I'll be happy to lend a hand on this occasion and I am still an IPMC member. Just give me some time to evaluate the release. One more note - you actually need 2 more votes. Only Egor's (yegor) vote is binding. You are listed as a mentor, but you don't appear to be an IPMC member. This means we'll need help from Ross and/or Jim. And maybe we can enroll new mentors. Anyone? Andrus On Jul 23, 2012, at 7:50 AM, Alexei Fedotov wrote: Jukka, thanks for explaining. Ross, Andrus, would you please consider voting for the Openmeetings release? We are stuck with insufficient number of votes. Thanks! Incubator folks, Don't allow another little cute kitten and fluffy puppy die by missing Apache Openmeetings (Incubating) release: http://demo.openmeetings.de/openmeetings/ http://demo.dataved.ru/openmeetings/ You are mostly welcome to support our release here http://markmail.org/message/azenwwlcfhnxmysf -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Sat, Jul 21, 2012 at 1:02 AM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, Jul 19, 2012 at 2:45 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The release vote have successfully passed and forwarded to general@ list [1]. What should be our next step? Have we got Incubator PMC approval? Can we proceed with wider distribution? See http://incubator.apache.org/incubation/Incubation_Policy.html#Releases for the Incubator policy on releases. You're almost done, just an extra approval vote on general@ is still needed (and since you already have two mentor +1s, you only need one more IPMC member to vote for the release). BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)
With Noel's email, this vote makes sense now. +1 to Jukka (binding) Cheers, Andrus On Feb 9, 2012, at 6:16 PM, Mattmann, Chris A (388J) wrote: Hi Folks, OK there has been enough discussion here. It's time to VOTE for a new IPMC chair and it looks like the remaining folks (including me) that were in the running have aligned beyond the following nominee: Jukka Zitting. Suffice to say, he was *my first choice* :) In the interest of moving the current discussion matters forward, please VOTE on this recommendation to the board by the IPMC. I'll leave the VOTE open for at least the next 72 hours: [ ] +1 Recommend Jukka Zitting for the IPMC chair position. [ ] +0 Don't care. [ ] -1 Don't recommend Jukka Zitting for the IPMC chair position because... Note that only VOTEs from the Incubator PMC members are binding, but all are welcome to voice their opinion and it will be recorded in the final tallies. Finally, just to note, these VOTEs on personnel are normally the only thing in Apache that is discussed in private (human/social issues), but in the interest of openness and transparency that has been demonstrated here during these discussions, I will hold this VOTE on the public list. Thanks! Cheers, Chris P.S. Here's my +1. Thanks buddy. On Feb 8, 2012, at 3:11 PM, Benson Margulies wrote: I am happy to step out of the way for Jukka. He was clever enough to stay out of the email s*** storm, and that alone, in my mind, renders him most qualified. On Wed, Feb 8, 2012 at 6:02 PM, Christian Grobmeier grobme...@gmail.com wrote: I already mentioned that I would have nominated you, and so I am delighted to read your message. It will be very difficult to choose between all these strong candidates. Cheers On Wed, Feb 8, 2012 at 11:49 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, After consideration and some convincing (thanks!), I've decided to throw also my hat into the ring as a candidate to be the next chairman of the IPMC. I believe in that role I could be more effective in focusing more of our collective attention at where I think it would do most good - at the actual podlings we're here to help. That said, the current incubation process clearly has problems and I very much support efforts to improve the way we work (even if the result is to replace the Incubator with something better). However, I'd like to leave the leadership on these efforts to others and, as mentioned elsewhere, rather try to act as a balancing force that helps achieve consensus where possible. Should I be elected, I'd resign as the chairman of the Jackrabbit PMC. In fact I think it's in any case high time for Jackrabbit to be rotating that role. Finally, if elected (and assuming the IPMC still exists), I'd serve for at most two years before calling for a re-election, or possibly much less if I don't find enough free cycles to perform the duty as well as it should. BR, Jukka Zitting ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - 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 On Dec 29, 2011, at 7:05 PM, Bertrand Delacretaz wrote: 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: [PROPOSAL] Apache DeviceMap, a data repository and APIs for mobile device information
Big +1. With WURFL demise and disgraceful behavior of its founders, we certainly need a truly open source alternative. So what is the origin of OpenDDR database and how does it compare to WURFL? Cheers, Andrus On Dec 23, 2011, at 9:32 AM, Bertrand Delacretaz wrote: Hi Incubator PMC, The proposal at http://wiki.apache.org/incubator/DeviceMapProposal (copied below) is open for discussion, I'm planning to start the vote to accept it sometime next week. -Bertrand *** Apache 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 is being discussed on the Incubator general list (TODO add link to that). 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 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 - savs (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 @ incubator.apache.org Subversion Directory http://svn.apache.org/repos/incubator/devicemap Issue Tracking DMAP project in JIRA. Sponsors Champion Bertrand Delacretaz Nominated Mentors Sylvain Wallez Kevan Miller Bertrand Delacretaz Sponsoring Entity Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache DeviceMap, a data repository and APIs for mobile device information
The question is essentially about any existing assets the project is planning to bring to Apache. While any answer to that is unlikely to disqualify the proposal, it may lead to licensing questions, process questions, etc. So while this is curiosity of sorts, I think it is an important thing to understand. Andrus On Dec 23, 2011, at 12:04 PM, Bertrand Delacretaz wrote: On Fri, Dec 23, 2011 at 4:08 PM, Andrus Adamchik and...@objectstyle.org wrote: On Dec 23, 2011, at 9:57 AM, Bertrand Delacretaz wrote: Note that the proposal mentions OpenDDR donating their *source code* only - as mentioned in the proposal, the details of the repository data will be discussed once the podling starts. The repository is the most valuable piece here. So I think it is important to discuss this aspect here now. Appreciate the proposal authors commenting on it I agree that the format and contents of the DeviceMap data repository require serious discussions: which sources of data to use, which format(s) to use to store and to publish the data, how to trace data provenance where needed, etc. However, all this is IMO out of scope of the do we agree for DeviceMap podling to enter incubation discussion that we're having now. So, if you're asking out of curiosity I'm fine, but if you think the acceptance of the podling should be based on this discussion about the data repository details, I disagree. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache DeviceMap, a data repository and APIs for mobile device information
Thanks. That answers it actually :-) On Dec 23, 2011, at 12:36 PM, Bertrand Delacretaz wrote: On Fri, Dec 23, 2011 at 6:14 PM, Andrus Adamchik and...@objectstyle.org wrote: The question is essentially about any existing assets the project is planning to bring to Apache. While any answer to that is unlikely to disqualify the proposal, it may lead to licensing questions, process questions, etc. So while this is curiosity of sorts, I think it is an important thing to understand. Ok, I see your point and agree - but keep in mind that we're not intially planning to adopt any OpenDDR *data* - as I said, doing that or not requires more discussion once the podling starts. -Bertrand On Dec 23, 2011, at 12:04 PM, Bertrand Delacretaz wrote: On Fri, Dec 23, 2011 at 4:08 PM, Andrus Adamchik and...@objectstyle.org wrote: On Dec 23, 2011, at 9:57 AM, Bertrand Delacretaz wrote: Note that the proposal mentions OpenDDR donating their *source code* only - as mentioned in the proposal, the details of the repository data will be discussed once the podling starts. The repository is the most valuable piece here. So I think it is important to discuss this aspect here now. Appreciate the proposal authors commenting on it I agree that the format and contents of the DeviceMap data repository require serious discussions: which sources of data to use, which format(s) to use to store and to publish the data, how to trace data provenance where needed, etc. However, all this is IMO out of scope of the do we agree for DeviceMap podling to enter incubation discussion that we're having now. So, if you're asking out of curiosity I'm fine, but if you think the acceptance of the podling should be based on this discussion about the data repository details, I disagree. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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
[VOTE CLOSED] Accept Openmeetings to Apache Incubator
I am officially closing the vote. We have 27 +1's and no other votes. Of those 11 are from the Incubator PMC members. So the proposal passes and Openmeetings is officially a part of the Apache Incubator now. Congratulations! Below is the vote summary: [Incubator PMC] Ross Gardler +1 Davanum Srinivas +1 Ate Douma +1 Jean-Baptiste Onofré +1 Deepal Jayasinghe +1 Andrus Adamchik +1 Yegor Kozlov +1 Olivier Lamy +1 Mohammad Nour El-Din +1 Alan D. Cabrera +1 Jim Jagielski +1 [Wider community] Francis De Brabandere +1 Raffaele P. Guidi +1 Kalle Korhonen +1 Alexei Fedotov +1 Daniel Haischt +1 enterdv +1 Bruno F. Souza +1 oigl +1 dkandrov +1 Jomar Silva +1 Mikhail Fursov +1 solomax +1 German Grekhov +1 timtl +1 Maurizio Cucchiara +1 Matthew B. Franklin +1 --- Andrus Adamchik Apache Cayenne ORM: http://cayenne.apache.org/ Twitter: http://twitter.com/andrus_a On Nov 8, 2011, at 9:53 AM, Andrus Adamchik wrote: Opemeetings proposal has been discussed a few times here before. The group of developers behind it worked hard (and succeeded) to address all potential obstacles to the Incubator acceptance and to the following incubation. They even went an extra mile and collected all ICLAs in adbvance. So now I am starting the vote to accept Openmeetings to Apache Incubator. The proposal is also available at: http://wiki.apache.org/incubator/OpenmeetingsProposal Please cast your votes: [ ] +1 Accept Openmeetings for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Andrus --- Andrus Adamchik Apache Cayenne ORM: http://cayenne.apache.org/ Twitter: http://twitter.com/andrus_a --- == OpenMeetings Project Proposal == == Abstract == Openmeetings is a web conferencing solution. == Proposal == Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming. == Background == Openmeetings was developed since 2007 by Sebastian Wagner and willing developers. The project ships a release approximately once per quarter. It was developed using LGPL license, and developers are currently thinking of re-licensing it under Apache License 2.0. The project started as module by Sebastian Wagner for an ELearning platform (Dokeos) and was then split into a separated project. That is the reason why there is a strong relation to educational institutions that are using OpenMeetings and there are integrations for platforms like Moodle, ATutor, Sakai, STudIP or ILias available (http://code.google.com/p/openmeetings/wiki/MoodlePlugins). The relation to educational institutions also subsequently lead to some projects funded by the EU where OpenMeetings was involved, for example by the Swedish/Finnish Centre of Open-Source !OpenKarken (Case-Study about the EU project at OSOR.eu: http://www.osor.eu/studies/finland-and-sweden-collaborate-using-oss ) The integration and internationalization of the project was a primary focus right from the start of the project. Since Version 0.5 there is a Language-Editor (http://code.google.com/p/openmeetings/wiki/LanguageEditor) to edit labels, export and import them as XML and you can use those XML files for future installations (or contribute it to the community). There are currently around 30 languages available. Since version 0.5.1 there is also a SOAP API to integrate !OpenMeetings. We constantly improve this SOAP/REST API (http://code.google.com/p/openmeetings/wiki/SoapMethods) with new functionality with a strong focus on security and usability. The auth-mechnism is quite similar to OAuth, you create some token and then assign rights to the token. (Documentation for Single Sign On: http://code.google.com/p/openmeetings/wiki/DirectLoginSoapGeneralFlow) The project name !OpenMeetings and logos are inspired by Ludovic Gasc who has been the project manager at Dokeos at the time Sebastian split !OpenMeetings as separated project. Red5 Server provides an Edge-Orion-Clustering (http://trac.red5.org/wiki/Documentation/Tutorials/EdgeOriginClusteringConfiguration). We hope to extend this clustering solution with support for rtmpt and rtmps and integrate that into our application as native clustering option. == Rationale == Last year most major vendors started commercial web conferencing solutions. This is an important part of software ecosystem, and there is an urge to consolidate open source development efforts in this direction. According to several studies demand for synchronous Communication, in opposite to asynchronous Communication like wiki's or email, will raise the upcoming years. For example Gartner promises that 2011 the market will grow 20% according to their Magic Quadrant report 2010 ( http://www.gartner.com/DisplayDocument?doc_cd
Re: [VOTE] Accept Openmeetings to Apache Incubator
On Nov 8, 2011, at 9:53 AM, Andrus Adamchik wrote: [X] +1 Accept Openmeetings for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Openmeetings to Apache Incubator
Opemeetings proposal has been discussed a few times here before. The group of developers behind it worked hard (and succeeded) to address all potential obstacles to the Incubator acceptance and to the following incubation. They even went an extra mile and collected all ICLAs in adbvance. So now I am starting the vote to accept Openmeetings to Apache Incubator. The proposal is also available at: http://wiki.apache.org/incubator/OpenmeetingsProposal Please cast your votes: [ ] +1 Accept Openmeetings for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Andrus --- Andrus Adamchik Apache Cayenne ORM: http://cayenne.apache.org/ Twitter: http://twitter.com/andrus_a --- == OpenMeetings Project Proposal == == Abstract == Openmeetings is a web conferencing solution. == Proposal == Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming. == Background == Openmeetings was developed since 2007 by Sebastian Wagner and willing developers. The project ships a release approximately once per quarter. It was developed using LGPL license, and developers are currently thinking of re-licensing it under Apache License 2.0. The project started as module by Sebastian Wagner for an ELearning platform (Dokeos) and was then split into a separated project. That is the reason why there is a strong relation to educational institutions that are using OpenMeetings and there are integrations for platforms like Moodle, ATutor, Sakai, STudIP or ILias available (http://code.google.com/p/openmeetings/wiki/MoodlePlugins). The relation to educational institutions also subsequently lead to some projects funded by the EU where OpenMeetings was involved, for example by the Swedish/Finnish Centre of Open-Source !OpenKarken (Case-Study about the EU project at OSOR.eu: http://www.osor.eu/studies/finland-and-sweden-collaborate-using-oss ) The integration and internationalization of the project was a primary focus right from the start of the project. Since Version 0.5 there is a Language-Editor (http://code.google.com/p/openmeetings/wiki/LanguageEditor) to edit labels, export and import them as XML and you can use those XML files for future installations (or contribute it to the community). There are currently around 30 languages available. Since version 0.5.1 there is also a SOAP API to integrate !OpenMeetings. We constantly improve this SOAP/REST API (http://code.google.com/p/openmeetings/wiki/SoapMethods) with new functionality with a strong focus on security and usability. The auth-mechnism is quite similar to OAuth, you create some token and then assign rights to the token. (Documentation for Single Sign On: http://code.google.com/p/openmeetings/wiki/DirectLoginSoapGeneralFlow) The project name !OpenMeetings and logos are inspired by Ludovic Gasc who has been the project manager at Dokeos at the time Sebastian split !OpenMeetings as separated project. Red5 Server provides an Edge-Orion-Clustering (http://trac.red5.org/wiki/Documentation/Tutorials/EdgeOriginClusteringConfiguration). We hope to extend this clustering solution with support for rtmpt and rtmps and integrate that into our application as native clustering option. == Rationale == Last year most major vendors started commercial web conferencing solutions. This is an important part of software ecosystem, and there is an urge to consolidate open source development efforts in this direction. According to several studies demand for synchronous Communication, in opposite to asynchronous Communication like wiki's or email, will raise the upcoming years. For example Gartner promises that 2011 the market will grow 20% according to their Magic Quadrant report 2010 ( http://www.gartner.com/DisplayDocument?doc_cd=205941 ). Openmeetings is a unique solution in terms of patent purity and potentially can grow into solution built on top of the fully open source stack. That is why it is a good candidate for consolidating web conferencing community efforts. == Initial Goals == Each of project committers has their own set of goals, but we all share the following. * Move to Apache. * Become popular. To become popular we plan to do the following. * Improve ecosystem around the project. * Improve release process. * Improve project testing and stability. * Apply modular architecture/SOA for better integration with other projects. == Current Status == We have agreed on applying for the Apache Foundation and preparing our proposal for the vote. Technical status of the project is: Current stable tree is 1.8.x, Trunk is 1.9. === Meritocracy === Developers community is successfully driven by consensus now. If there are more developers on board, consensus may turn into meritocracy. === Community === The developer
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
I've been in touch with Sebastian and Alexei and I am willing to champion the proposal. Just added myself to the corresponding section on the Wiki. I think we may still need to refine / update the proposal a bit before we can start the vote. But IMO we are very close to this point. The technology has been developed in the open from the start, so I see no problems with the community aspect or a single company controlling the project. Potential licensing issues have been identified, and the project members are working towards a compatible resolution. So I think the project is a perfect fit for Apache. In the meantime, if there are more willing mentors, please sign up. Also if somebody has more comments on the proposal, speak up now. Thanks, Andrus On Aug 16, 2011, at 11:56 AM, Ross Gardler wrote: 2011/8/11 seba.wag...@gmail.com seba.wag...@gmail.com: Great, I have updated the Proposal to be more clear on the external dependencies and possibilities to move away from them: http://wiki.apache.org/incubator/OpenmeetingsProposal#External_Dependencies Thanks for addressing these concerns and signposting potential solutions, both short and long term. I have signed up as a mentor, but we still need a champion. Unfortunately I don't really have the time right now to do the heavy lifting in the early stages of the project and thus don't feel comfortable stepping in as champion right now. In around 6 weeks I will have some more time and can dedicate that to mentoring. Ross Sebastian 2011/8/11 Jim Jagielski j...@jagunet.com I've signed up for Mentor, in case we go ahead... On Jul 29, 2011, at 5:46 AM, dsh wrote: Sebastian and Alexei, your are welcome! Btw, here is my +1 On Fri, Jul 29, 2011 at 9:47 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Daniel, Thank you for an excellent report! -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jul 28, 2011 at 10:20 PM, dsh daniel.hais...@googlemail.com wrote: Hi, please find my feedback below: OS X Lion: * tested with: ** Firefox 5.0.1 and Adobe Flash Player 10.3 ** Safari 5.1 and Adobe Flash Player 10.3 * Observations: ** Openmeetings did not work with Firefox/Safari if using a webcam/mic cause on the adobe flash player settings dialog it was not possible to click allow nor deny ** In Safari clicking the share/record screen button N times did open the screen sharing app N times (maybe you want to check whether an instance of the app is already running) ** I understand if sharing screens everybody has control over your screen. you may consider adding a view only mode too. ** you might check while signing up whether popup blockers are active. if yes you could prompt the user to disable popup blockers first before signing in. ** pressing the share/record screen button opens a new, blank window just to download the JNLP app. maybe you want to change that to not open a separate window that needs to be closed after starting the JNLP app ** It looks like after stopping screen sharing the shared screen still remains on each participants screen. Maybe it would make sense to provide a message to each participant that the host stopped sharing its screen. OS X Snow Leopard: * tested with: ** Firefox 5.0.1 and Adobe Flash Player 10.3 ** Safari 5.1 and Adobe Flash Player 10.3 * Observations: ** Openmeetings did not work with Firefox cause the initial screen did not load after signing up ** In Safari clicking the share/record screen button N times did open the screen sharing app N times (maybe you want to check whether an instance of the app is already running) ** I understand if sharing screens everybody has control over your screen. you may consider adding a view only mode too. ** you might check while signing up whether popup blockers are active. if yes you could prompt the user to disable popup blockers first before signing in. ** pressing the share/record screen button opens a new, blank window just to download the JNLP app. maybe you want to change that to not open a separate window that needs to be closed after starting the JNLP app ** It looks like after stopping screen sharing the shared screen still remains on each participants screen. Maybe it would make sense to provide a message to each participant that the host stopped sharing its screen. Windows 7 Ultimate: * tested with: ** Firefox 4.0.1 and Adobe Flash Player 10.3 ** Firefox 5.0.1 and Adobe Flash Player 10.3 ** Safari 5.1 and Adobe Flash Player 10.3 * Observations: ** In Firefox clicking the share/record screen button N times did open the screen sharing app N times (maybe you want to check whether an instance of the app is already running) ** I understand if sharing screens everybody has control over your screen. you may consider adding a view only mode too. ** you might check while signing up
Re: Project Proposal Question
Hi Erich, There are no formal limitations on what an Apache software can do. While there is some historical bias towards certain types of projects and technologies here, it is not set in stone or anything. The area of use can be as broad or as specific as its creators decide. The only practical limitations are: * Apache software distribution should not bundle dependencies with incompatible licenses. * The community behind the project must be diverse enough to ensure no single employer controls the project. So please prepare the proposal and present it here. Good luck, Andrus On Jun 21, 2011, at 9:46 PM, HOCHMUTH, ERICH [AG/1000] wrote: Does the Apache Software Foundation accept project proposals that are industry domain focused? I'd like to begin the process of proposing a new Hadoop based project like Mahout for Machine Learning but Hadoop for Genomic Analysis. There appears to be a lot of momentum in the enterprise and academia in applying Hadoop and MapReduce to genomic datasets. To foster development and potentially ensure that algorithms are working from a set of standard datasets and common tools it could be valuable to consolidate efforts into a single project. Thanks, Erich This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. The information contained in this email may be subject to the export control laws and regulations of the United States, potentially including but not limited to the Export Administration Regulations (EAR) and sanctions regulations issued by the U.S. Department of Treasury, Office of Foreign Asset Controls (OFAC). As a recipient of this information you are obligated to comply with all applicable U.S. export laws and regulations. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Wave] editing incubator documents
Per Feb 2 message from Upayavira on wave-dev (1296637259.12852.1418516...@webmail.messagingengine.com), SVN auth grants are setup for all Wave committers. Not sure if the permissions are extended to the Incubator site? Andrus On Feb 4, 2011, at 10:31 AM, Michael MacFadden wrote: David, Thanks for the heads up. I have been trying to follow said process, however it seems like the wave committers have not yet been given that ability to commit changes to the incubator SVN. I have some pending changes to the wave project page I have been waiting to check in. ~Michael On Feb 3, 2011, at 10:02 PM, David Crossley wrote: When publishing some Incubator docs (doing 'svn up' on the server) i see that someone has made some hard-coded changes to the generated html doc for the Wave status page. You need to follow this process to make the changes in the SVN source files instead, then re-generate, etc. http://incubator.apache.org/guides/website.html (That is the system until the Incubator switches over to use the new CMS.) -David - 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: Account requests: Wave (Incubating) initial committers
Hi root, thanks for creating the new Wave accounts. There's one remaining account for James Purser that still needs to be setup. I contacted secretary about missing CLA, and it turned out that his CLA was recorded two weeks ago, but due to some SVN issue didn't make it to iclas.txt. This is fixed now, and we can proceed with this account. Also I noticed that I had a typo in email address in my original account request, so here is the correct info on this account: purserj, jpurser: James Purser, jamesrpur...@gmail.com Thanks, Andrus On Dec 16, 2010, at 1:00 PM, Andrus Adamchik wrote: Hi root! As a Wave project incubator mentor I am requesting to create Apache accounts for the following list of Wave committers. This list is a subset of the people on the Wave incubator proposal [1] for those individuals who submitted their CLAs. 1. Groups: I assume they should be the members of the following UNIX groups (?): apcvs, apsite, wave. 'wave' group needs to be created. 2. Accounts If more than one UNIX account name specified for a given person, they are sorted in the order of decreasing preference) : anorth, alexn: Alexander North, a...@alex.id.au [2] awatkins, antwatkins: Anthony LaMarr Watkins, awatkin...@gmail.com danield or danilatos Dan Danilatos, danila...@google.com purserj, jpurser: James Purser, jamesrpur...@gmai.com [2] michael, mmacfadden: Michael MacFadden, mich...@macfadden.org soren, sorenlassen Soren Lassen, so...@google.com tad, tglines: Tad Glines, tad.gli...@gmail.com ohler: Christian Ohler, oh...@google.com weis, torben.weis, weistn: Torben Weis, torben.w...@gmail.com zdwang, zedavidwang: David Wang [3] [1] http://incubator.apache.org/projects/wave.html [2] as of now CLA is not yet recorded, but I have an electronic copy and shared in with the secretary [3] CLA submitted as Zheng Wang Thanks, Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Account requests: Wave (Incubating) initial committers
On Jan 2, 2011, at 11:13 AM, Andrus Adamchik wrote: Hi root, Sorry meant to send it to priv...@i.a.o, not general. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wave Incubator Next Steps
I can't see why not forwarding it to Incubator PMC would hold root@ from creating the accounts (I mean, if it is such a big deal, root@ can always forward this message themselves and/or contact me to do it). Anyways, I just forwarded the original request. BTW, the original request was sent to root on 12.16, which was only a week ago :) Andrus On Dec 23, 2010, at 1:41 AM, David Crossley wrote: I wondered why the Wave initial committer accounts were not yet set up. The wave-dev list indicates that it seems to be stalled. (Please come to general@ and ask if ever there is a holdup.) Yes Infra does do it in batches. However, one reason might be that the request for accounts might not have been done properly. The relevant PMC needs to be Cc too. I don't see any on the Incubator PMC private. That is because the ASF needs to be a good corporation, follow its procedures and notify the responsible committee. Hope that helps. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wave Incubator Next Steps
Actually those were there before I started the process of gathering committer ids. None of the last week CLAs are recorded yet. Andrus On Dec 13, 2010, at 2:09 AM, David Crossley wrote: Upayavira wrote: At the same time, folks that don't have ICLAs recorded yet should send them in. I am not on the Wave dev mail list, but i can read that Andrus was waiting on the first batch of CLAs being recorded. The bottom of this page shows that some have now: http://people.apache.org/committer-index.html -David - 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
On Nov 30, 2010, at 8:52 AM, Dan Peterson wrote: [X] +1 Accept Wave for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Accept Wave for incubation
On Nov 26, 2010, at 1:07 PM, Bernd Fondermann wrote: I wouldn't stop the proposal, though. This can be identified as an issue to be solved in Incubation - either by changing the name away from 'Wave' or by transferring marks or even by determining that none of both is required. Exactly, this is an exit requirement, not an entry one. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Accept Wave for incubation
Sounds good :-) On Nov 24, 2010, at 8:09 PM, Dan Peterson wrote: Hi Andrus, Thanks for your support. I think this'll be a good home for Wave to grow and mature. I've taken the liberty of adding you on the mentor list. :) Cheers, -Dan On Wed, Nov 24, 2010 at 1:20 AM, Andrus Adamchik and...@objectstyle.orgwrote: +1 I am so happy that after all considerations and suggestions that were floated in the Wave community, you guys picked Apache as the place to develop Wave community and WIAB. Good luck and let me know if you need extra mentors (you already have 4, so I figured you are covered and didn't add myself to the list). Cheers, Andrus On Nov 23, 2010, at 10:16 PM, Dan Peterson wrote: Hello all, We'd like to propose Wave for entry into the ASF incubator. The draft proposal is available at: http://wiki.apache.org/incubator/WaveProposal (for your convenience, a snapshot is also copied below) A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave in a Box (WIAB) is the name of the main product at the moment, which is a server that hosts and federates waves, supports extensive APIs, and provides a rich web client. This project also includes an implementation of the Wave Federation protocol, to enable federated collaboration systems (such as multiple interoperable Wave In a Box instances). As a result of the recent Wave Summit, beyond growing a few new committers, we've put together the following proposal for migrating the community into the ASF incubator. More details on the summit Wave in a Box progress in this blogpost: http://googlewavedev.blogspot.com/2010/11/this-weeks-wave-protocol-summit-updates.html We are looking forward to your feedback and suggestions. By the way, if you're looking to learn more about the technology related to wave, you can see the videos and presentations from the recent Wave Summit in: https://wave.google.com/wave/waveref/googlewave.com/w+rwFyiw47A Kind regards, -Dan, on behalf of the Wave Community P.S. For those on the wave-protocol Google Group (that aren't yet on general@incubator.apache.org), please participate in this discussion by sending a message to general-subscribe at incubator dot apache dot org Apache Wave Proposal (Apache Incubator) = Abstract = Apache Wave is the project where wave technology is developed at Apache. Wave in a Box (WIAB) is the name of the main product at the moment, which is a server that hosts and federates waves, supports extensive APIs, and provides a rich web client. This project also includes an implementation of the Wave Federation protocol, to enable federated collaboration systems (such as multiple interoperable Wave In a Box instances). = Proposal = A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. WIAB is a server that hosts waves. The best analogy for this is a mail server with a web client. WIAB is comprised of a few high-level components: the client and the server. They have the following major functionality (though this is not an exhaustive list): * Client *A dynamic web client for users to create, edit, and search waves. Users can access this client by directly visiting the server in a browser. * Gadgets provide the ability to insert, view, and modify the UI -- exposing the Wave Gadgets API ( http://code.google.com/apis/wave/extensions/gadgets/guide.html) * A console client that can create and edit waves via a command-line-like interface. * Server * Hosts and stores waves. WIAB comes with a default storage mechanism. The administrators of the server may configure it to use alternative storage mechanisms. * Indexing, allowing for searching the waves a user has access to. * Basic authentication, configurable to delegate to other systems. * Federation, allowing separate Wave in a Box servers to communicate with each other using the Wave Federation Protocol ( http://www.waveprotocol.org/federation). * Robots, using the Wave Robots API, ( http://code.google.com/apis/wave/extensions/robots/) may interact with waves on a WIAB instance. = Background = Wave expresses a new metaphor for communication: hosted conversations. This was created by Lars and Jens Rasmussen after observation of people's use of many separate forms of communication to get something done, e.g, email, chat, docs, blogs, twitter, etc. The vision has always been to better the way people communicate and collaborate. Building open protocols and sharing code available in an open and free way is a critical part of that vision. Anyone should be able to bring up their own wave server and communicate with others (much like SMTP). We hope this project will allow everyone to easily gain the benefits of Wave with a standard implementation of Wave – in a box. = Rationale
Re: [PROPOSAL] Accept Wave for incubation
+1 I am so happy that after all considerations and suggestions that were floated in the Wave community, you guys picked Apache as the place to develop Wave community and WIAB. Good luck and let me know if you need extra mentors (you already have 4, so I figured you are covered and didn't add myself to the list). Cheers, Andrus On Nov 23, 2010, at 10:16 PM, Dan Peterson wrote: Hello all, We'd like to propose Wave for entry into the ASF incubator. The draft proposal is available at: http://wiki.apache.org/incubator/WaveProposal (for your convenience, a snapshot is also copied below) A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. Wave in a Box (WIAB) is the name of the main product at the moment, which is a server that hosts and federates waves, supports extensive APIs, and provides a rich web client. This project also includes an implementation of the Wave Federation protocol, to enable federated collaboration systems (such as multiple interoperable Wave In a Box instances). As a result of the recent Wave Summit, beyond growing a few new committers, we've put together the following proposal for migrating the community into the ASF incubator. More details on the summit Wave in a Box progress in this blogpost: http://googlewavedev.blogspot.com/2010/11/this-weeks-wave-protocol-summit-updates.html We are looking forward to your feedback and suggestions. By the way, if you're looking to learn more about the technology related to wave, you can see the videos and presentations from the recent Wave Summit in: https://wave.google.com/wave/waveref/googlewave.com/w+rwFyiw47A Kind regards, -Dan, on behalf of the Wave Community P.S. For those on the wave-protocol Google Group (that aren't yet on general@incubator.apache.org), please participate in this discussion by sending a message to general-subscribe at incubator dot apache dot org Apache Wave Proposal (Apache Incubator) = Abstract = Apache Wave is the project where wave technology is developed at Apache. Wave in a Box (WIAB) is the name of the main product at the moment, which is a server that hosts and federates waves, supports extensive APIs, and provides a rich web client. This project also includes an implementation of the Wave Federation protocol, to enable federated collaboration systems (such as multiple interoperable Wave In a Box instances). = Proposal = A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. WIAB is a server that hosts waves. The best analogy for this is a mail server with a web client. WIAB is comprised of a few high-level components: the client and the server. They have the following major functionality (though this is not an exhaustive list): * Client *A dynamic web client for users to create, edit, and search waves. Users can access this client by directly visiting the server in a browser. * Gadgets provide the ability to insert, view, and modify the UI -- exposing the Wave Gadgets API ( http://code.google.com/apis/wave/extensions/gadgets/guide.html) * A console client that can create and edit waves via a command-line-like interface. * Server * Hosts and stores waves. WIAB comes with a default storage mechanism. The administrators of the server may configure it to use alternative storage mechanisms. * Indexing, allowing for searching the waves a user has access to. * Basic authentication, configurable to delegate to other systems. * Federation, allowing separate Wave in a Box servers to communicate with each other using the Wave Federation Protocol ( http://www.waveprotocol.org/federation). * Robots, using the Wave Robots API, ( http://code.google.com/apis/wave/extensions/robots/) may interact with waves on a WIAB instance. = Background = Wave expresses a new metaphor for communication: hosted conversations. This was created by Lars and Jens Rasmussen after observation of people's use of many separate forms of communication to get something done, e.g, email, chat, docs, blogs, twitter, etc. The vision has always been to better the way people communicate and collaborate. Building open protocols and sharing code available in an open and free way is a critical part of that vision. Anyone should be able to bring up their own wave server and communicate with others (much like SMTP). We hope this project will allow everyone to easily gain the benefits of Wave with a standard implementation of Wave – in a box. = Rationale = Wave has shown it excels at small group collaboration when hosted by Google. Although Wave will not continue as a standalone Google product, there is a lot of interest from many organizations in both running Wave and building upon the technology for new products. We are confident that with the community-centric development environment
Re: Future of RAT
While I second that in general, and I have argued (unsuccessfully) on the incubator list against arbitrary size constraints for graduating podlings, still in theory a PMC min size comes from the need to have a sustainable quorum to vote on releases. If it can get at least 3 people to vote, it should be fine. Otherwise +1 - one size does not fit all and Apache should (and does) accommodate different size projects. Andrus On Aug 10, 2010, at 8:20 PM, Greg Stein wrote: Let me repeat: where does it say a TLP must be at least THIS size ? Answer: nowhere. Small projects are just fine. We're looking at the overall community and the people to shepherd that community. Those are the RAT developers and users. Not the Apache Commons or Apache Maven people. They have other concerns and focus points. TLPs are not expensive, so they don't have to have a minimum size to justify their existence. Cheers, -g - 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!
Congrats to Subversion. Glad to see you guys here. Ah, the good memories of the day when I discovered SVN and source control stopped being a pain. Keep up the good work! Andrus On Feb 17, 2010, at 11: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! Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: document translation infrastructure?
Many projects are using cwiki.apache.org/confluence to maintain documentation. Confluence has version tracking with visual diff display. Probably also possible to setup an RSS feed to watch the pages that changed. So that should be all you need. Andrus On Nov 24, 2009, at 8:20 PM, Miles Libbey wrote: Hi folks- We have a volunteer to translate our documentation from English into Korean. Any recommendations for translation management/ infrastructure? That is-- as the english documentation changes, is there any software that can help to find out of date or new strings/ sections? thanks, miles libbey - 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 VCL 2.1
On Nov 23, 2009, at 5:49 PM, sebb wrote: There is only a bz2 archive. Normally projects release archives in zip andr tar.gz format which are more commonly supported. IMO, this is a release blocker Just curious why you think this is a blocker? Each project knows better what formats are common and acceptable in the target user community. There's no single distribution format and this is not a blocker IMO. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hibernate migration strategy Was: [PROPOSAL][VOTE] OpenMeetings
If you are going to do a rewrite, yet another option is to use Apache Cayenne, which has all the features of a modern ORM (plus a few more) and is also rather friendly to beginners: http://cayenne.apache.org/ Then maybe we can collaborate with OpenMeetings to make sure Cayenne works on Google App Engine ;-) Cheers, Andrus On Nov 19, 2009, at 6:17 PM, Alexei Fedotov wrote: Hello, As for migrating from Hibernate, I see several alternatives for persistence. Enterprise Java experts, please, could you comment on this? 1. stackoverflow.com suggested using Spring as a persistence technology. My friend said that it requires coding, but you get manageable, clear and transparent application. We already use Spring as a dependency. 2. Using JPA from Java 6 JPA allows using less libraries and being more compatible with Google App Engine. The latter may help general users to host the web application. 3. Does OpenJPA suggested by Niclas offer any benefits compared to JPA? Synergy is good, but there may be other benefits I cannot see. Sorry for my ignorance. Thanks. P.S. Ross, it would be really nice to get you as a mentor. On Wed, Nov 18, 2009 at 6:56 PM, Ross Gardler rgard...@apache.org wrote: 2009/11/18 Sebastian Wagner seba.wag...@gmail.com: we would like to propose Openmeetings project to join the incubator. Full Proposal: http://wiki.apache.org/incubator/OpenmeetingsProposal Calling a vote is premature. Therefore my vote is -1. Your proposal does not yet have a confirmed champion and you don't have sufficient mentors yet. I'm still toying with the idea of mentoring, but I'm still unclear with respect to the legal situation. I've not seen a clear consensus that it will ever be possible to produce a cleanly licensed application that does not require the use of LGPL/GPL code. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://harmony.apache.org/ http://www.expressaas.com/ http://openmeetings.googlecode.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hibernate migration strategy Was: [PROPOSAL][VOTE] OpenMeetings
No. We froze the JPA compatibility effort started some time ago. Cayenne uses its own persistence API. Cheers, Andrus On Nov 19, 2009, at 7:08 PM, jean-frederic clere wrote: On 11/19/2009 05:49 PM, Andrus Adamchik wrote: If you are going to do a rewrite, yet another option is to use Apache Cayenne, which has all the features of a modern ORM (plus a few more) and is also rather friendly to beginners: http://cayenne.apache.org/ So cayenne is JPA-enabled? Cheers Jean-Frederic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Insanity. Apache Incubator should be about education (was: [PROPOSAL][VOTE] Subversion)
Hi Greg, I am not on either side of the debate here, but Martijn is correct in pointing that the formal standard was applied to *all* podlings to date. There's more than a few projects in the ASF that were originally developed in the open, with strong communities. And in those cases that I am aware of, no amount of reasoning from those projects would convince the IPMC to give them a break and just let them in. You'd have to sit in limbo forever until you are done with the checklist. So I am fine if SVN incubation would result in reasonable changes in those incubator policies. Unless whoever was behind those policies in the first place will step in and object? Andrus On Nov 9, 2009, at 4:49 PM, Greg Stein wrote: On Mon, Nov 9, 2009 at 09:27, Martijn Dashorst martijn.dasho...@gmail.com wrote: Yes, *AND* ensuring legal dots are put on the i's and j's. This is done through checking the release and ensuring that it is in adherence to our policies which you and others have crafted. *All* podlings have to ensure they have the correct licensing headers, notices and other bits in place before they can graduate. We certainly have no intent to bring Bad Code into the ASF! In fact, we already know of a couple key points that we're bringing to legal-discuss. i.e. we're already ahead of the game by doing a review. We've already got all the IP collected. We've applied standard headers. We're using ALv2. AFAIK releases done by podlings are legally more sound than established projects at Apache. Do you consider that a bad thing? We have no release planned for the timeframe that I believe we will be within the Incubator. To force one does not make sense, as I've stated. What strikes me is that because the SVN project has many old boys network guys on board, somehow the policy to what all podlings are subjected to is no longer valid? That is just an unfair and unfounded accusation. Have an incubator release? (nah, we are better at releasing because we have long standing members) Frankly: yeah. You can read my rationale when I ask for a vote. Feel free to vote against if you feel our waiver is unwarranted, but I do feel that we're quite well-experienced. I prefer Leo's hey, have you checked the RAT output for svn? than you must make a release kind of arguments. He's providing a helpful pointer to a tool, rather than directing us into senseless work. Migrate all subscribers to the mailinglists from one legal organization to another? (afaik this is legally forbidden) Where did you ever see that we would do that? Since you're already making false accusations, how about I just clarify for you: this has *already been discussed*. Our plan is to set up new lists and invite old list members to subscribe to the new one. Hosting non-Apache released artifacts at Apache hardware? If you're referring to the older releases of Subversion? You bet. They are all with a compatible license. Have you ever noticed all those .jar files we host here at Apache? Those aren't released by us. Or how about the PCRE software embedded into httpd? Or that copy of Expat down in apr-util? We have already conferred with Infrastructure, and they saw no problem with hosting old releases on archive.apache.org. And all that said, since you're in an argumentative mood here... sure. I think that is a fair topic for consideration, and possibly for guidance from legal-discuss. But given license compat, I'm laying odds that Legal will have zero problem with it. These things are/were off-limits to podlings that were established and functioning outside Apache just fine. Wicket's incubation was rather painful due to not being able to transfer subscribers and hosting old releases and websites at Apache. I'm fine with short circuiting all the red tape associated with the incubator, but be warned: this will open up doors for other podlings as well. When the next established open source project comes along they expect (rightfully so) the same treatment as Subversion. Absolutely agreed. That is *precisely* why Subversion is going through Incubation rather than directly approaching the Board for TLP status. (which was discussed by the Board and by SVN) Myself and others felt it would set a bad precedent, so here we are. Any deviation from the standard process, I intend to be asking for a specific waiver (much like I did before we even got here!). If somebody else wants to take shortcuts in the future, then they better have solid requests for waiving an item. But I believe that is quite acceptable: if there is a explainable rationale/reason for that waiver for any podling, then why shouldn't it be made? I do not intend to progress quickly by virtue of the old boys network you accuse me and the other svn people of, but simply that we already conform to ASF principles already. There isn't much adjustment needed. I'm looking at the checklist as right. need to talk to infra about that. okay. need to talk to
Re: Insanity. Apache Incubator should be about education (was: [PROPOSAL][VOTE] Subversion)
On Nov 9, 2009, at 5:23 PM, Greg Stein wrote: I mean, really... how many other projects that are 9.5 years old(*) do we expect to see arriving here? And of those, how many *started* with the ideas and precepts of the Apache Software Foundation? I suspect it will be zero, so wasting a lot of time documenting (rather than recognizing) exceptions might not be very useful. There were a few mature projects. Not as large as SVN, but still pretty old (say 5 years of track record) and with established community and market position. Essentially in the same category (maybe sans the ubiquity of SVN). But I say as appropriate. Sometimes it just doesn't make sense to document every possible exception. But simply to note *they can exist*. Agreed. Just that nobody else was able to get a waiver to date, and this was likely because people coming in were intimidated into thinking they have no other way, but follow the procedure. So unfortunately there is (and likely will be) a difference in treatment. I guess that's a social issue, not a procedural one (i.e. insider vs. outsider perception). Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Click as an Apache TLP
+1 On Oct 18, 2009, at 4:39 AM, Bob Schellink wrote: Hi all, The Apache Click community has voted to request graduation from the Incubator as a new TLP [1][2]. I would like to start a vote to recommend the graduation of Apache Click as a Top Level Project to the Board. Please cast your vote: [ ] +1 to recommend Click's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, because ... The vote will be open for 72 hours until Wednesday 2:00 am (UCT). The following IPMC members have already voted in favor of graduation on the Click dev list: Henning Schmiedehausen Will Glass-Husain Andrus Adamchik The proposed board resolution is included below. Kind regards Bob [1]: http://markmail.org/thread/nhhocnq3xufm3lkt [2]: http://markmail.org/message/pwgo2duk6oens7v6 --- Begin Proposed Board Resolution --- 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 framework for creating page and component oriented web applications, 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 Click PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Click PMC be and hereby is responsible for the creation and maintenance of software related to the Click Web Framework and tools, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Click 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 Click PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Click PMC; 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 Click PMC: Henning Schmiedehausen (henn...@apache.org) Will Glass-Husain (wgl...@apache.org) Malcolm Edgar (med...@apache.org) Bob Schellink (sa...@apache.org) Naoki Takezoe (take...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Malcolm Edgar be and hereby is appointed to the office of Vice President, Apache Click, 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 Click PMC be and hereby is tasked with the migration and rationalization of the incubating Apache Click project; and be it further RESOLVED, that all responsibility pertaining to the incubating Apache Click project encumbered upon the incubator PMC be hereafter discharged. --- End Proposed Board Resolution --- - 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: [PROPOSAL] Apache Click graduation
Additional concern, it does not appear that the mentors are planning to be on the PMC. Why not? Why is this a concern? Mentors volunteer to do mentoring to ensure the project is viable and understands the Apache way, not necessarily to develop code. If you trace the existing Apache projects back to the incubator, I'd suspect 70% of them will not have their original mentors on the PMC. Andrus Apache Click Mentor On Apr 24, 2009, at 1:28 AM, Upayavira wrote: On Thu, 2009-04-23 at 23:25 +0100, Niall Pemberton wrote: Comparing the original proposal to the graduation resolution it seems that click entered incubation with 4 committers and proposes to leave with 3. IMO a PMC of three is not enough - one person disappears and you can't get the three votes required to do anything. Additional concern, it does not appear that the mentors are planning to be on the PMC. Why not? Upayavira - 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: [PROPOSAL] Apache Click graduation
3 is the minimal number that is needed for a formal acceptance. So I see no problem with it. Click has been a successful open source project done the Apache way before entering Apache, so I think it is definitely ready to graduate now. While a possibility of a vote deadlock exists, it does exist for any other Apache project as well. Interesting aspect of this though... say a PMC member X goes AWOL. Will it be valid for the 2 remaining members to vote another person in the PMC? I'd say yes, but definitely a non-standard situation... Andrus On Apr 24, 2009, at 1:25 AM, Niall Pemberton wrote: Comparing the original proposal to the graduation resolution it seems that click entered incubation with 4 committers and proposes to leave with 3. IMO a PMC of three is not enough - one person disappears and you can't get the three votes required to do anything. Niall On Thu, Apr 23, 2009 at 8:10 PM, Bob Schellink sa...@apache.org wrote: Hi all, The Apache Click PPMC would like to have feedback on the following graduation proposal before asking for a vote. The Click community already votes in favor of graduation which is recorded here: http://www.mail-archive.com/click-...@incubator.apache.org/msg00574.html Click status page: http://incubator.apache.org/projects/click.html Kind regards Bob --- Begin Proposed Board Resolution --- 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 framework for creating page and component oriented web applications, 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 Click Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Click Project be and hereby is responsible for the creation and maintenance of a page and component oriented web framework and related tools; and be it further RESOLVED, that the office of Vice President, Apache Click 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 Click Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Click 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 Click Project: * Malcolm Edgar (med...@...) * Bob Schellink (sa...@...) * Naoki Takezoe (take...@...) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Malcolm Edgar be and hereby is appointed to the office of Vice President, Apache Click, 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 Click Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Click podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Click podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution --- - 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: [PROPOSAL] Apache Click graduation
Hmm.. 3 PMC members was always ok. Did it change recently? I agree on a tangential point though (and accept some blame myself as a mentor) that the project should've done more active recruiting of committers with the potential to join the PMC. In fact there seem to be good candidates, and this is being discussed in Click right now. So I suggest that we come back to this discussion later if some mentors agree to stay on the PMC until there are more committers, that might work. Speaking for myself, I'd like to stay, as I like the project. Just that I won't be able to contribute in any meaningful way due to the lack of time. So I didn't want to simply pad the proposal with my name to make it look better, and then go AWOL. I am sure they can find great candidates from the existing user community. Andrus On Apr 24, 2009, at 12:57 PM, Bertrand Delacretaz wrote: On Fri, Apr 24, 2009 at 12:25 AM, Niall Pemberton niall.pember...@gmail.com wrote: Comparing the original proposal to the graduation resolution it seems that click entered incubation with 4 committers and proposes to leave with 3. IMO a PMC of three is not enough - one person disappears and you can't get the three votes required to do anything Agree with that - if some mentors agree to stay on the PMC until there are more committers, that might work. But voting in more committers before graduating (assuming there are contributors who deserve that) would be way better. I'm -1 on graduating with only 3 PMC members, the risk is too big for the project to become stuck and unable of voting. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Click graduation
On Apr 24, 2009, at 2:36 PM, Martijn Dashorst wrote: On Fri, Apr 24, 2009 at 1:27 PM, Andrus Adamchik and...@objectstyle.org wrote: As I said already, the bigger point is valid: the opportunities to expand the committer/PMC base were missed, and this should be corrected now if possible. But let's not jump to some strange conclusions from that. The project *is* mature and *is* community driven from day one. This is the fact that can be easily confirmed by going through the list archives. How do you think the original author found 2 other PMC members, who work for different companies and live in different countries. But adding 2 committers over the course of 4 years might suggest that there's a (B)DFL instead of a Meritocratic community. Might, but it is simply not the case. You are making an abstract argument. As a mentor and the Incubator PMC member I am telling what I saw over the years watching this specific project. If you have proof otherwise, please share. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Click graduation
On Apr 24, 2009, at 3:25 PM, Martijn Dashorst wrote: On Fri, Apr 24, 2009 at 2:01 PM, Andrus Adamchik and...@objectstyle.org wrote: If you have proof otherwise, please share. How about that in those four years, no new committers were admitted to the project? A project with a scope and as successful as Click could easily have attracted 4-8 great committers over the course of 4 years. To ask a counter question: why haven't these contributors been considered as committers until just *now*? Isn't that a sign of community immaturity? Martijn I disagree. First of all there was another committer, who dropped off for health reasons. So the original author had no problem accepting at least 3 more people on board. Saying how many committers they should have after X years sounds like a business plan. It doesn't work this way in open source. Then there are different types of contributions. Some warrant a committership, others show that a given person should not be given SVN write access under no circumstances. Then there is a pace issue (which I think is at play here, and this is being reevaluated now), where you need to see a person become a community member before allowing SVN access. This has nothing to do with maturity, just common sense. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Click graduation
Yeah, looks like I missed at least 3 more people. The immaturity argument is really artificial here. Andrus On Apr 24, 2009, at 3:34 PM, Malcolm Edgar wrote: There has been a fair turn over of comitters over the life of the project. Previous committers have included: * Phil Barnes, * Ahmed Mohombe, * Christian Essl, * Stephen Haberman Often these committers have used Click on commercial projects and have become involved, then after a period of time the move on. I don't see this as a sign of immaturity. If we need more committers, we can recruit. regards Malcolm Edgar On Fri, Apr 24, 2009 at 10:25 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Fri, Apr 24, 2009 at 2:01 PM, Andrus Adamchik and...@objectstyle.org wrote: If you have proof otherwise, please share. How about that in those four years, no new committers were admitted to the project? A project with a scope and as successful as Click could easily have attracted 4-8 great committers over the course of 4 years. To ask a counter question: why haven't these contributors been considered as committers until just *now*? Isn't that a sign of community immaturity? Martijn - 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: [PROPOSAL] Apache Click graduation
On Apr 24, 2009, at 4:00 PM, Niclas Hedhman wrote: Does any of the Mentors have any stake (user, contributor, whatever) in the project? Preferably depending on the project on some commercial project... ;-) Can't speak for Henning and Will, but I am not tied to the project at the moment, and this is why I said I won't be on the PMC, and won't pretend to be there to pad the numbers. A 11th hour, 59th minute alarm isn't that good either... This is a mentor's failure - we did miss this aspect, as things in Click have been working smoothly, as always. So the project is fine, but should take a break with graduation to reevaluate its ranks and recruit willing and deserving individuals, and come back here maybe in 2-3 months if this endeavor is successful. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: If you're not interested in Java and MySQL Cluster, you can stop reading now...
Interesting. This is the first time I see a high-level Java design
that is a diversion from DB independence. So how much performance
improvement do you see by nixing JDBC?
Andrus
On Mar 19, 2009, at 2:53 AM, Craig L Russell wrote:
I'm working (day job!) on a Java interface to the MySQL Cluster
database (a.k.a. NDB). NDB is a high performance, high availability
database used mostly in telecommunications applications. It can be
the backing store for a MySQL server (accessed via any of the MySQL
client APIs such as ODBC, JDBC) or can be used directly via
primitive C++ or Java APIs.
What I've been developing is a high performance, easy-to-use Java
interface to NDB that bypasses the MySQL Server and instead goes
directly to the native NDB API. I've used a Domain Object Model
similar to Hibernate, JDO, and JPA.
I'd like to work on this in Apache and would like to discuss the
opportunities with folks at ApacheCon. If this looks interesting,
please let me know. I'll post a proposal to the incubator wiki if
there is positive feedback.
All work is done through a Session instance, which is the primary
application interface between the user and the database.
The user acquires a Session instance from a SessionFactory, which in
turn is obtained via Services lookup. The factory is configured via
Properties, such as:
com.mysql.clusterj.connectstring=127.0.0.1:9311
com.mysql.clusterj.mysqld=localhost
com.mysql.clusterj.username=root
com.mysql.clusterj.password=
com.mysql.clusterj.testDatabase=test
The Session interface provides methods for insert, delete, query,
and update.
A separate Transaction interface provides methods for transaction
completion. The Transaction provides isActive(), begin(), commit(),
rollback(), setRollbackOnly(), and getRollbackOnly() methods.
Two modes of operation are implemented: autocommit on/off.
• With autocommit off:
• when a mutating operation is invoked on the Session, the
Transaction must be active, or an exception is thrown; and
• when a non-mutating operation is invoked when a Transaction is
not active, a transaction is begun and committed for the purpose of
executing the operation.
• With autocommit on:
• when a mutating operation is invoked on the Session, the
Transaction is begun and committed for the operation; and
• when a non-mutating operation is invoked, a transaction is begun
and committed for the purpose of executing the operation.
Deferred operation is proposed. By setting the flag
com.mysql.clusterj.defer.changes, mutating operations are deferred
until the Transaction is committed or the state is flushed via
Session.flush(). With defer changes, find() operations return a
proxy instance whose persistent properties are not initialized until
the user asks for one of them. Inserted instances are not actually
sent to the back end until the session is flushed. Deleted instances
are not deleted until the session is flushed. Queries return a
Results instance that is not instantiated until the user asks for a
property of an instance.
For ease of use, users can define JavaBeans-pattern interfaces to
represent data, with annotations to declare database metadata:
@PersistenceCapable(table=t_basic)
interface Employee {
@PrimaryKey
int getId();
void setId(int id);
String getName();
void setName(String name);
}
The Session.newInstance(Class cls) is a factory for instances that
implement the user interface as well as a high-performance data
access path for the implementation. For JPA/JDO StorageManager, the
high-performance data access path is used.
// Sample code to create a SessionFactory from a properties instance
protected void createSessionFactory() {
loadProperties();
if (sessionFactory == null) {
sessionFactory = ClusterJHelper.getSessionFactory(props);
}
loadSchema();
}
// Sample code to delete and create instances
public void localSetUp() {
createSessionFactory();
session = sessionFactory.getSession();
createEmployeeInstances(NUMBER_TO_INSERT);
tx = session.currentTransaction();
int count = 0;
for (int i = 0; i NUMBER_TO_INSERT; ++i) {
tx.begin();
session.deletePersistent(employees.get(i));
try {
tx.commit();
++count;
} catch (Exception ex) {
// ignore exceptions -- might not be any instances to
delete
}
}
addTearDownClasses(Employee.class);
//System.out.println(Deleted + count + instances.);
}
public void testInsert() {
tx = session.currentTransaction();
tx.begin();
for (int i = 0; i NUMBER_TO_INSERT; ++i) {
// must be done with an active transaction
session.makePersistent(employees.get(i));
}
tx.commit();
}
}
// Sample query code
public void primaryKeyGreaterThanQuery() {
Re: [VOTE] Approve the 2.0.1 release of Apache Click - third try
+1 On Feb 10, 2009, at 6:02 PM, Bob Schellink wrote: New snapshots are available with the following changes: # build.properties has new property to switch off the hibernate dependency # build.xml will only build the hibernate package if hibernate is available on the build path # The ConcurrentReaderHashMap source has been removed from the distribution. Only the binary class is included. The NOTICE has been amended to point to the ConcurrentReaderHashMap source file # NOTICE has been updated to explicitly mention third-party licenses New distribution is available here: http://people.apache.org/~sabob/click/click/2.0.1/dist/ New Maven artifacts are here: http://people.apache.org/~sabob/click/click/2.0.1/maven2/ Thanks Bob - 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] Approve the 2.0.1 release of Apache Click
On Feb 11, 2009, at 1:00 AM, Bob Schellink wrote: Can we get fired for trying to release so many times? Hehe , no :-) Thanks Henning for catching those things. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve the 2.0.1 release of Apache Click
Anybody else from the Incubator PMC can check the release? Henning? Will? Thanks, Andrus On Feb 3, 2009, at 10:10 PM, Bob Schellink wrote: Hi all, The Click community has approved the first release of Apache Click. All IP issues have been resolved and incompatible license dependencies replaced. We would now like to request the approval of the Incubator PMC for this release. The vote on the click-dev mailing list resulted in 5 +1 votes (4 binding) and no other votes: Andrus Adamchik +1 Bob Schellink +1 Naoki Takezoe +1 Malcolm Edgar +1 Ricardo Lecheta +1 Vote thread: http://click.markmail.org/search/#query:+page:1+mid:3t5lfsusnizffj4t+state:results Distribution can be found here: http://people.apache.org/~sabob/click/click/2.0.1/dist/ Maven artifacts can be found here: http://people.apache.org/~sabob/click/click/2.0.1/maven2/ Project home: http://incubator.apache.org/click/ Incubation status: http://incubator.apache.org/projects/click.html Thanks Bob - 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] Approve the 2.0.1 release of Apache Click
+1. On Feb 4, 2009, at 5:00 PM, Bob Schellink wrote: New snapshots are available and contains the incubation disclaimer. Thanks to Kevan for picking this up. The disclaimer can be found in the distribution root while for maven artifacts the disclaimer can be found under META-INF. New distribution is available here: http://people.apache.org/~sabob/click/click/2.0.1/dist/ New Maven artifacts are here: http://people.apache.org/~sabob/click/click/2.0.1/maven2/ Thanks Bob Kevan Miller wrote: On Feb 4, 2009, at 12:23 AM, Bob Schellink wrote: Kevan Miller wrote: Perhaps I missed it, but I don't see an incubator DISCLAIMER as required by http://incubator.apache.org/guides/releasemanagement.html Thanks Kevan you're right, will fix and republish. Have you run RAT against your source? Some files don't have Apache source license headers and looks like they should (e.g. examples/src/cayenne.xml, etc). Nods, cayenneXXX.xml are generated files, my understanding is we don't add headers to those. Other source files without headers are template/*. These files are used to generate a quick-start project, thus have no Apache headers. Is this OK? Yep, that's fine. Thanks for the explanation. --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: [Kalumet] Preparing source code
Hi JB, Procedural things can get really slow here at times due to the volunteer nature of the ASF. Don't get discouraged by that... For now you'll need to ping people to look at the proposal, and find two more mentors. I'd love to be one of them, but I am afraid I will be AWOL most of the time. I am barely catching up with another project I am mentoring now. I can sign up as a backup mentor I guess, but you'll need at least one more person who is ready to be more active for the incubation period. After you get the mentors on board, you'll start a vote on the proposal on this list, and after the vote Kalumet will be formally accepted in the Incubator. There was sufficient interest in the idea, so I am hopeful you will find the missing mentors. Just give it some time and keep nudging the community. Migrating the package names is a bit premature. If you are planning to make releases in the nearest future, you may want to keep the old package names, as releasing the code as org.apache.* when you are not in Apache yet is a bad idea. Andrus On Feb 3, 2009, at 8:16 PM, j...@nanthrax.net wrote: Hi, I have begin to prepare the AutoDeploy subversion repository source code renaming the packaging and project's poms. I have commited this on the trunk : http://buildprocess.svn.sourceforge.net/viewvc/buildprocess/AutoDeploy/trunk/ I have delete current AutoDeploy sources, nevertheless you can access the current production release on the 0.5 branch : http://buildprocess.svn.sourceforge.net/viewvc/buildprocess/AutoDeploy/branches/0.5/ Regards JB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve the 2.0.1 release of Apache Click
The vote quoted below is an internal vote inside the project PPMC - a prerequisite for the gene...@i.a.o vote, which was started now. You are absolutely right about 3 Incubator PMC votes requirement for the vote in THIS thread tho. Andrus On Feb 3, 2009, at 10:47 PM, Martijn Dashorst wrote: Just a point of order: I think you have just one binding vote (only Incubator PMC members' votes are binding): Andrus Adamchik's vote. You'll need at least 2 more to let the vote pass. Martijn On Tue, Feb 3, 2009 at 9:10 PM, Bob Schellink sab...@gmail.com wrote: Hi all, The Click community has approved the first release of Apache Click. All IP issues have been resolved and incompatible license dependencies replaced. We would now like to request the approval of the Incubator PMC for this release. The vote on the click-dev mailing list resulted in 5 +1 votes (4 binding) and no other votes: Andrus Adamchik +1 Bob Schellink +1 Naoki Takezoe +1 Malcolm Edgar +1 Ricardo Lecheta +1 Vote thread: http://click.markmail.org/search/#query:+page:1+mid:3t5lfsusnizffj4t+state:results Distribution can be found here: http://people.apache.org/~sabob/click/click/2.0.1/dist/ Maven artifacts can be found here: http://people.apache.org/~sabob/click/click/2.0.1/maven2/ Project home: http://incubator.apache.org/click/ Incubation status: http://incubator.apache.org/projects/click.html Thanks Bob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - 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: [PROPOSAL] Apache Maestro
On Dec 24, 2008, at 1:02 PM, Niclas Hedhman wrote: What have happened to previous tradition of coming up with good obscure names?? SpretFlinter (zero hits) Crentacto (one hit) Bristasse (116 hits) Not to make JB's job any harder, but IMO these examples are just silly. BTW, what tradition are you referring to? How hard can it be? It is hard. Random letter combinations do not sound that good. BTW, what was wrong with AutoDeploy? Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Scrum
Hi JB, A very interesting problem you are addressing with AutoDeploy. JEE deployment tools that I've seen to date don't scale too well, so this area can use lots of improvement. I've developed a similar system for a big site of one of our customers, with the main goal to manage a mid- size cluster (10-100 app server nodes) running Jetty. The main idea is the same - write an XML descriptor to describe the cluster layout and app destinations, and then write the tools around that descriptor (deployment, monitoring and what not). But of course the tools is where YMMV, and I am happy to see someone else building such tools :-) I downloaded AutoDeploy-0.5.3 (BTW, noticed that the jar files are all duplicated under lib/ and target/ increasing the size of the download to 140MB. Poking around the code now. In the meantime a few questions - do you have a demo system somewhere that would allow to play with the UI without deploying the app? Also are there any diagrams on the deployment flow implemented in AutoDeploy? Thanks, Andrus On Dec 17, 2008, at 11:01 PM, Jean-Baptiste Onofré wrote: Hi, I would like to introduce my Apache Scrum proposal. Abstract Apache Scrum is a complete environment manager and deployer including JEE applications and resources. It's a perfect complement to continuous integration by adding continuous deployment. The whole software factory chain is cover and the JEE administrator managed all environments is a secure and safe way, whatever the underlying application server is. Proposal Apache Scrum provides two components : - Apache Scrum agent are installed localy on the application server server - Apache Scrum console controls and manages agents, allowing the JEE administrator to update all environments from a central web tool. Background Currently, Apache Scrum is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net ). The development has begun 4 years ago and several release have been already provided. AutoDeploy is used in several companies like Fimasys (http://www.fimasys.com ), Vodacom South Africa (http://www.vodacom.com), Mayo Clinic USA (http:// www.mayocinic.com), etc. Rationale The JEE environments administration is heavy cost task with a high level on human action. It suffers : - a different set of script or actions dependning of the application server used (JBoss, Websphere, Weblogic, etc) - a high level of risk due to human action (for exemple, an administrator can forget to deploy a JDBC datasource, or forget to change an application specific configuration file) - the upgrade process can be long (depending of the applications complexity) - most of resources are stored localy to the application server, not in a central repository Apache Scrum securise the environment deployment and cover the whole JEE scope (EAR/WAR archives, JDBC datasources, JMS queues, JMS topics, classloader policy, etc) in a uniq way whatever the underlying application server (it heavely uses JMX to interact with compatible middlewares). Initial Goals When I have begun AutoDeploy, my first goal was to provide several application server JMX plugins. But quickly, I have seen that multi-application servers support was only a small part of the JEE administration need. That's why I have extended AutoDeploy to provide agents and a central console. Using the console, several JEE administrators can use a central tools to manage all environments in a collaborative and secure way. Current Status Currently, AutoDeploy provides two branches : - the 0.5.x branch (with the 0.5.4 lastest release) is the current stable branche - the 0.6.x branch is target to become Apache Scrum Community Currently the project contains two contributors and around 50 users. Thanks to the popularity of ASF, the purpose is increase the number of contributors to improve the functionnality cover of Apache Scrum. Core Developers AutoDeploy/Apache Scrum was founded by Jean-Baptiste Onofré in 2004. Mike Duffy, Vodacom JEE architect, contributes since 2005. Several contributors have provided patches on the project. Open Source Since the beginning, AutoDeploy was a Open Source project using GPL license. Apache Scrum will use the Apache 2 license. Relationships with Other Apache Products AutoDeploy/Apache Scrum heavely uses Apache products such as : - lot of jakarta commons (espcailly VFS) - maven/continuum for build/continuous integration - xerces/xalan for XML manipulation - etc ... I hope that Apache Scrum provide a kind of interest to you :) and really hope that the ASF approve this project. I think that the core product is efficient due to the number of users on the current stable version. Joining ASF will increase the visibility of Scrum and increase the number of contributors, for sure. If you have need more informations, or if you have
Re: [PROPOSAL] Apache Scrum
On Dec 18, 2008, at 12:22 PM, Jean-Baptiste Onofré wrote: Currently, there is not a lot of documentation (I need to produce one) but, anyway, quickly :), the deployment flow is : Step 0 : init VFS file manipulator ... So does it have some cluster deploy strategy (e.g. minimizing downtime by restarting nodes one by one, the next one restarted, when the previous one has finished its startup), or does it rely on the target server tools to handle cluster nodes management? For a live demo, you can try : http://autodeploy.j2ee.fimasys.fr using user : demo pass : demo It's not really a demo : you have a read only access to a small part of an AutoDeploy production environment (that manages around 130 JEE environments using JBoss, Weblogic, Websphere). I hope you didn't expose any sensitive information with this, as this URL is now archived in a dozen mailing list archive sites. Anyways, the URL above redirects me to http://www.fimasys.com/ , so I don't see a login screen. Andrus - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Scrum
Yeah, I am curious how practical it is to use Puppet to deploy JEE apps? Maybe for managing the server config files, but the actual app deployment??? (sorry, that's getting a bit OT, but I think this discussion is still useful in mapping the AutoDeploy problem domain, and hence explaining the proposal to potential mentors). Andrus On Dec 18, 2008, at 5:13 PM, Jean-Baptiste Onofré wrote: Hi David, Puppet is interesting but the scope is not exactly the same : AutoDeploy is mainly focus on JEE environments (supporting all JEE resources). Nevertheless, AutoDeploy and Puppet can be complementary tool. Regards JB -- Jean-Baptiste Onofré j...@nanthrax.net BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net On Thu 18/12/08 15:56, David Pollak feeder.of.the.be...@gmail.com wrote: On Wed, Dec 17, 2008 at 9:47 PM, Jean-Baptiste Onofré wrote: Pizzazz (Yoav's proposition) and DeployX looks nice :) What do you think of Apache Prop ? My 2 cents... have you seen Puppet? http://reductivelabs.com/trac/puppet [1] It's a Ruby-land tool that does many of the same things that your project does. It's being used at some notable and large scale Rails powered sites with success. Borrowing some of Puppet's excellent ideas or even working with the Puppet folks (Luke Kanies is a very cool guy) might lead to an even better tool. Thanks, David Regards JB On Thursday 18 December 2008 - 01:11, Ali Ok wrote: Currently the project is named AutoDeploy which is a little bit confusing too. Apache Scrum is just a name proposition, I'm open to all other name :) How about DeployX :) I tried checking from nameprotect.com, but I couldnt. 2008/12/18 Noel J. Bergman As with Yoav, I am in favor of this project. It resonates with what I do for a living. Also as with Yoav, I'd suggest a different name. And I am personally hoping that more names with be at least marginally reflective of what the project does. I would ask that you take a look at Lokahi (http://incubator.apache.org/lokahi/). [2] And we should engage projects like Tomcat, Geronimo, Ode, Tuscany, et al, with the goal of being able to centrally install, manage and deploy with as many of them as possible. Do you use ssh to jumpstart, e.g., to install the agent remotely? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Jean-Baptiste Onofré (Nanthrax) BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net j...@nanthrax.net PGP : 17D4F086 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Lift, the simply functional web framework http://liftweb.net [4] Collaborative Task Management http://much4.us [5] Follow me: http://twitter.com/dpp [6] Git some: http://github.com/dpp [7] Links: -- [1] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Freductivelabs.c om%2Ftrac%2Fpuppet[2] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fincubator.apach e.org%2Flokahi%2F%29.[3] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fbuildprocess.so urceforge.net%0D%3C%2Ffont[4] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fliftweb.net [5] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fmuch4.us [6] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Ftwitter.com%2Fd pp[7] http://webmail.nanthrax.net/parse.php?redirect=http%3A%2F%2Fgithub.com%2Fdp p - 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: Multiple concerns reviewing BlueSky podling website
On Jul 31, 2008, at 4:18 PM, Luciano Resende wrote: - The BlueSky podling website have a download page, that is pointing to non-apache bluesky released artifacts. I think this is at least very confusing, as it can allude users to think this is a endorsed ASF release. Is this OK ? I don't see a problem with links to pre-ASF releases. BlueSky is not unique in this respect. There are a number of Apache projects with long pre-ASF history. So including links to such releases is totally appropriate. However a clear indication on the page that those are the releases made outside Apache is a good idea. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Click Incubation - Status
On Jul 30, 2008, at 10:32 AM, Henning Schmiedehausen wrote: My personal understanding here is, that Ahmed (and any other contributor) contributed that code to a project that is already under AL2. So there is no need to track down the contributors and/or rewrite code where the contributor can not be tracked down. The AL allows relicensing under AL2 ( :-) ), so the code in the repository is fine. The policy may have changed, but the above was NOT true when Cayenne was incubating. What I suspect is happening is that there is no *policy* as such, and instead we have a range of opinions. What you (and Roy) are saying makes sense to me, but it goes against everything I know about the practiced IP clearance process at Apache. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Click Incubation - Status
Let's take this to legal-discuss and see what comes out. After all, that is where the lawyers lurk. Good idea. Also keep in mind that the problem scope is not limited to the projects coming to the incubator. It also affects contributions to the existing projects by new people. Currently anything beyond a trivial patch (submitted via Jira with include in ASF product radio button), requires an ICLA. We specifically tell people to sign an ICLA. With Roy's interpretation, we should be telling them post this code on the web somewhere, adding a BSD license header, and we'll use it. Andrus On Jul 30, 2008, at 10:46 AM, Henning Schmiedehausen wrote: I feel your pain and I know that Cayenne was in a bad spot because of this. But if we can ease the process for others, why not? Let's take this to legal-discuss and see what comes out. After all, that is where the lawyers lurk. Ciao Henning On Wed, 2008-07-30 at 10:42 -0400, Andrus Adamchik wrote: On Jul 30, 2008, at 10:32 AM, Henning Schmiedehausen wrote: My personal understanding here is, that Ahmed (and any other contributor) contributed that code to a project that is already under AL2. So there is no need to track down the contributors and/or rewrite code where the contributor can not be tracked down. The AL allows relicensing under AL2 ( :-) ), so the code in the repository is fine. The policy may have changed, but the above was NOT true when Cayenne was incubating. What I suspect is happening is that there is no *policy* as such, and instead we have a range of opinions. What you (and Roy) are saying makes sense to me, but it goes against everything I know about the practiced IP clearance process at Apache. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | JEE, Linux, Unix 91054 Buckenhof, Germany -- +49 9131 506540 | Apache Java Software Open Source Consulting, Development, Design| INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen char name_buf[257]; /* max unix filename is 256, right? */ - 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: Click Incubation - Status
Correct me if I am wrong, but what you are saying is that there should be a record somewhere (such as a Click prior email archive?) where a person states his intent to donate the code? What if this person was a committer, and stated his intent by quietly committing the code? In any case, rewriting this code does not have any impact on copyright. Nobody can change the copyright on a work by copying it, even when the copy is from distant memory (think music for comparisons). I guess there are different theories about that. I am not ready to argue in depth about that. But when I wrote a few Cayenne DB adapters that had been written by other people before, I am pretty sure I didn't steal anyone's original work. Andrus On Jul 28, 2008, at 1:26 AM, Roy T. Fielding wrote: On Jul 27, 2008, at 9:22 AM, Andrus Adamchik wrote: Is there existing code in Click written by Ahmed? As getting an ICLA or rewriting this code will be required as a part of the IP clearance process. That isn't quite true. The ASF requires documentation that the original author has licensed the code to the ASF or to someone who can license it to the ASF. If, for example, the code was published by that author under the Apache License, BSD license, or any similar non-copyleft open source license, then the ASF can redistribute that code. We may need to retain some original license headers, but we do not need everyone who isn't going to participate to sign an ICLA. Likewise, an email message sent from the author saying that we can redistribute their code under the Apache License is a legitimate form of license -- just save the message in its original (raw) form. In any case, rewriting this code does not have any impact on copyright. Nobody can change the copyright on a work by copying it, even when the copy is from distant memory (think music for comparisons). The ideal outcome would be for Ahmed to send an ICLA, regardless of his future participation plans, but that's of course up to him to decide. Yes, that is the most sensible thing. He can send it via email if that helps. Because the iCLA is not a copyright assignment (just a non-exclusive license), we can rely on any written communication that can be reasonably determined to be from the author. Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Click Incubation - Status
Hi Malcolm, Is there existing code in Click written by Ahmed? As getting an ICLA or rewriting this code will be required as a part of the IP clearance process. The ideal outcome would be for Ahmed to send an ICLA, regardless of his future participation plans, but that's of course up to him to decide. Thanks, Andrus On Jul 27, 2008, at 8:56 AM, Malcolm Edgar wrote: Hi, Thanks for the update on the ICLA's. Ahmed unfortunately wont be able to join the project initially for personal health reasons and won't be providing an ICLA. You should have also received an ICLA from Phil Barne an early committer to the Click project. I will still try and obtain ICLA's from previous contributors. regards Malcolm Edgar On Sun, Jul 27, 2008 at 9:25 PM, Henning Schmiedehausen [EMAIL PROTECTED] wrote: Hi, this is the current status for the Click incubation: - ICLAs for Malcolm, Bob and Naoki have been received. ICLA for Ahmed is still missing. As soon as this shows up, I will request accounts for Click - Mentors need to prepare a status page for the click incubation, as described at http://incubator.apache.org/guides/ mentor.html#Initialize +Podling+Status+Page - Infra Tickets have been opened at INFRA-1689 and sub-tickets. If you want to be added as a moderator for the click mailing lists, please add yourself to the INFRA-1690 ticket Ciao Henning - 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: [RESULT] Re: [VOTE] Accept Click for Incubation
On Jul 21, 2008, at 12:42 PM, Henning Schmiedehausen wrote: Note: Andrus and Will have requested to join the Incubator PMC but were no IPMC members at the time when they voted. I can vote one more time with my IPMC member hat on ;-) Not that we don't have enough votes. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Click for Incubation
On Jul 18, 2008, at 8:59 PM, William A. Rowe, Jr. wrote: There are no project leads at the ASF. All committers who become a member of the PMC shall have an equal say in the project. This can cause a great amount of friction when the project is perceived to be owned by a small subset of the pmc members. Explosions within such projects happen at least once a year, sometimes for the better and often for the worse. I would have hoped that under Meritocracy, something about the transition from benevolent dictator to project management committee would be said. I would like to know, for example, if every committer will become a PPMC member, or if this is a PPMC of two (Malcolm and Bob). While I agree with the general point, I should add, that no project leads does not mean that you should add random people to the PMC, just because they posted a few times on the mailing list or submitted a trivial patch. Meritocracy means just that - give and elevate karma of people who make the project happen. I thought it is important to underscore this point, as there is often a fear of a project being hijacked. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Click for Incubation
+1 On Jul 14, 2008, at 2:14 PM, Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-dev * click-private == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project called CLICK for the Click framework * Migrate the current JIRA issue tracker from http://www.avoka.com/jira/ == Other Resources == Need to create a new Confluence Wiki * CLICK == Initial Committers == The initial committers for the project should include: * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe * Henning Schmiedehausen * Will Glass-Husain * Ted Husted * Andrus Adamchik == Sponsors == === Champion === * Henning Schmiedehausen === Nominated Mentors === * Will Glass-Husain * Ted Husted * Andrus Adamchik === Sponsoring Entity === * Velocity
Re: [DISCUSS] Do we really need an incubator?
Hi Jim, It's no surprise that Maven chomps at the bit quite a bit regarding ASF policies, but values the Apache brand enough to tow the line. Did you mean Maven as Maven repo deployed @Apache or Maven the PMC? As Noel was talking specifically about the PMC. We can certainly ban Maven repo use until better security, etc. is implemented, but I don't think ASF policies apply to the architecture decisions (good or bad) and development direction of any given project. Andrus On Jul 11, 2008, at 4:23 PM, Jim Jagielski wrote: On Jul 9, 2008, at 12:16 PM, Noel J. Bergman wrote: I am forced to agree with Roy on these points. Until the Maven PMC stops abrogating its responsibility and addresses the issues, there does not appear to be anything that we can do about Maven's flaws short of banning use of the public Maven repositories entirely. Given that I consider promoting Maven's insecurre, uncontrolled, and unmanaged repositories to be at the height of irresponsibility, I would vote in favor of such a ban -- ASF-wide, not limited to the Incubator -- until Maven's flaws were addressed, but unfortunately, I doubt that there is a consensus to do so. At least not until there is an actual exploit in the wild, at which point the Maven PMC might finally open its eyes in panic. And I am forced to agree as well... To be honest, I still at times question exactly the relationship between the ASF and Maven is. It's no surprise that Maven chomps at the bit quite a bit regarding ASF policies, but values the Apache brand enough to tow the line. But IMO it is time for the ASF to see how this is increasing the risk and potential for trouble with the whole foundation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] Do we really need an incubator?
The two are different things. I agree about the technical problem (and can add a dozen of other Maven-related things that drive me crazy as a user). I don't agree that ignoring this problem by the Maven folks constitutes a violation of some Apache policy. So let's approach it in an open source way - try to persuade Maven committers to pay attention and/or contribute the code to fix the problem. I guess that's what we are doing already in this thread, but I just wanted to steer clear from the notion that Maven PMC has an obligation to the ASF to fix it. Andrus On Jul 11, 2008, at 4:53 PM, Jim Jagielski wrote: On Jul 11, 2008, at 9:40 AM, Andrus Adamchik wrote: Hi Jim, It's no surprise that Maven chomps at the bit quite a bit regarding ASF policies, but values the Apache brand enough to tow the line. Did you mean Maven as Maven repo deployed @Apache or Maven the PMC? As Noel was talking specifically about the PMC. We can certainly ban Maven repo use until better security, etc. is implemented, but I don't think ASF policies apply to the architecture decisions (good or bad) and development direction of any given project. Quite simply, if Maven the PMC (or any PMC) or Maven the repo deployed at the ASF (or any infra @ASF) is increasing the risks or exposure of the ASF to security or other related concerns, then we all should be concerned. To be more clear: the Maven repo is a *huge* benefit to the ASF and the entire community. Unless it is done right, it also has the potential of exposing the ASF to high risk. That is the concern that Roy, Noel and Paul appeared to be noting and one that I am also starting to listen to... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] Do we really need an incubator?
On Jul 11, 2008, at 5:04 PM, Jim Jagielski wrote: but I don't think ASF policies apply to the architecture decisions (good or bad) and development direction of any given project. They don't. Sorry if that wasn't clear :) Yep. That's where I was getting. You can ignore my last message then (The two are different things), as it was making the same point. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Click
+1. In a crowded web frameworks space, I very much like Click's philosophy of trading off deeper abstractions for simplicity. Last time I used it, the impression was nice and clean. Haven't used it lately (except for maintaining older projects). I hope it preserved that simplicity as the framework matured and grew up in scope (not an easy task I should say). Let me also sign up as a mentor. I may not be able to dedicate lots of time to that, but still I hope to be helpful every now and then. Andrus On Jul 2, 2008, at 10:29 PM, Henning Schmiedehausen wrote: Please see also http://wiki.apache.org/incubator/ClickProposal Comments until July 9th, if nothing blocking comes up, I'll CfV on July 10th. --- cut --- = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-private * click-dev * click-user == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project called CLICK for the Click framework * Migrate the current JIRA issue tracker from http://www.avoka.com/jira/ == Other Resources == Need to create a new Confluence Wiki *
Re: JEUT Champion Recruitment
Hi Alexis, Sorry, was on the road and unable to reply earlier. If you want to discuss where that might fit with Cayenne, I'd suggest to subscribe to Cayenne dev list and start a discussion there. Andrus On May 16, 2008, at 11:05 PM, Alexis Willemyns wrote: What a good idea! I am really interested by the persistence layer. It would be a great pleasure to work on the Cayenne project. If you desire, we can speak about that by private email. Contact me at [EMAIL PROTECTED] 2008/5/16 Andrus Adamchik [EMAIL PROTECTED]: BTW, if that turns to be the case, you can still collaborate with OpenJPA and Cayenne projects @Apache to provide similar functionality. Andrus On May 16, 2008, at 9:30 AM, Alexis Willemyns wrote: So, with the solution of hibernate.hbm2ddl.auto=validate, you don't need to write a unit test? If it's the case, the JEUT framework doesn't have any sense. I will test this solution! 2008/5/16, James Carman [EMAIL PROTECTED]: This sort of thing should be built into the ORM vendor's implementation. It is with Hibernate. If you set hibernate.hbm2ddl.auto=verify, it will make sure the database is set up correctly based on the mapping settings your application specifies. On Fri, May 16, 2008 at 7:22 AM, Alexis Willemyns [EMAIL PROTECTED] wrote: No I don't think it. The goal is not to test the implementation (Hibernate, Toplink, or another one...) of the JPA specification! Imagine the next case. You have a database engineer, who is for example a Oracle specialist, and you have a backend developper. The db engineer has the responsability to create manually the the db and the associated tables. On another side, the backend developper is responsible of the devolpment of entities (pojos) and he must use the JPA specification. So he will add annotations like @Entity, @Id, @Column, etc... Now the backend developer wants to check that his mapping matches with the work of the db engineer. For example, if he defined a column 'name', he want to ensure that there is a column 'name' defined by the db engineer, that the length is the same, that the unique and nullable factors are the same, and so on... If he want to do that, he must write a unit test, and in this test, persist an instance of the entity, and see if there is an error reported by the JPA implementation. JEUT does the job for you. When you said that it will be good that the framework makes sure that the class has the @Entity annotation, etc,... all these errors will be throwed by the JPA implementation. The goal is not to have an integration test, or to test the JPA implementation, but it's to check the synchonization between the Java pojos (entities) and the physical tables. If the 'name' column is defined as nullable=false via an JPA annotation, we want to be sure that in the table defined by the db engineer, the column is defined with null=false. So for this, in the automated tests of JEUT, an entity with the 'name' field value set to null is persisted and an exception is expected. If there is catched exception (throwed by the persistence implementation), the test is a real success. But if there is no catched exception, it means that the db engineer didn't define the column with null=false, and the test fails! Here is another example. In JPA, you can create date, time and timestamp via @Temporal annotation. If the backend developer defines a column with temporal type as date and the db engineer defines the column with time type, all the information about the day, the month and the year are lost. So JEUT tests the matching for the dates, and will find the previous error of mapping. JEUT is compatible all db server, the framework will use the META-INF/persistence.xml defined in the test source folder in the application of the user. So the user can test with the oracle db, hsqldb, derby, mysql,... It's not easy to explain! Is it more clear? Alexis 2008/5/16, James Carman [EMAIL PROTECTED]: At that point, aren't you just testing that the ORM implementation works? Wouldn't it be better to make unit tests that test the values of the annotations at runtime? Stuff like: 1. Make sure class X has the @Entity annotation. 2. Make sure its id property has the @Id annotation. 3. Make sure the getter for property foo has the @Basic annotation marking it as required. 4. Make sure the getter for property foo has the @Column annotation making it saved in the FOO column with length 255 If you want to test that the data is actually getting to the database, I'd argue that isn't really a unit test, but an integration test. Now to test queries you write, you'd probably want to use something like HSQLDB to make sure you're getting back the correct data (load some known test data before running tests of course). On Fri, May 16, 2008 at 6:27 AM, Alexis Willemyns
Re: JEUT Champion Recruitment
Hi Alexis, Thanks for clarifying. It matches my earlier understanding - it is a model regression testing tool. I am not saying it is not useful, just wanted to define the terms so that we have an understanding of what JEUT is. Andrus On May 16, 2008, at 6:27 AM, Alexis Willemyns wrote: On a technical note, the best solution is to explain you an example. As for every layer in an application, unit tests are welcome. This is too true for the entities mapped via JPA. So if you want to test an entity, you will create an unit test class (for example with JUnit). In this class, you will add some tests. For example, you will write a test that create an instance of the entity, set values, persist the entity, retrieve the entity, and check if the retrieved object is exactly the same as the persisted entity. It allows you to control that your annotations are matching the definition of the real table in the database. You can do extra tests: check the nullable attribute, the length attribute, the unique constraints, and so on... But if you want to test every aspect of your entity, you will write a big piece of code for each entity! If you have a model with 10, 20 or more entities, you see directly the quantity of work. JEUT is designed to automate for you the testing of an entity. You have just to create a test class that extends a specific JEUT test class and all the work is done for you. The framework uses the annotations discovered via reflection API or the XML files (orm.xml). Do you understand the goal of JEUT? 2008/5/15, Andrus Adamchik [EMAIL PROTECTED]: Hi Alexis, I think it would really help if you started developing in the open using one of the free open source sites. This would provide the project history to a potential Champion, including access to the source code and general feel of whether you are really interested in building community around your code. On a technical note, what exactly does this framework test? Is this regression testing (i.e. checking that the ORM schema matches the actual DB schema), or is there a value beyond that? We had a similar framework submitted to the Cayenne project some time back, and I could never understand what exactly is being tested. Andrus On May 15, 2008, at 9:57 AM, Alexis Willemyns wrote: Hello all, I was a little bit hesitant before posting this project proposition. But let's go! I hope that this attempt will be a success. JEUT stands for JPA Entity Unit Test and is currently in development. So there is no public website and the code is ended up to 70%. JEUT is a testing framework for JPA entities and its main goal is to automate the test of entities without the need to write long and boring home tests. The mission is to provide a framework which is able to test the matching between entities using annotations and/or xml descriptors and the real database. A framework 100% compliant with all the existing annotations in JPA, for the current version 1 (and the future version 2... in the future). JEUT analyzes all the annotations and creates instances of entites with random values. It tries to persist these instances via the entity manager and reports the problems if existing. JEUT can be used as an extension of JUnit or TestNG, or maybe all others test frameworks. For the moment, the team is only composed with me, and I have discussed with my self about what is means to become an Apacha project. I am aware what are the conditions, responsabilities and impacts to become an Apache project. I am looking a Champion to go in the proposal phase (if the proposal makes sense) and to build a community around JEUT. Thank you for any feedback and recommendations (and sorry for my english coming from Belgium). I look forward to your responses. Regards, Alexis Willemyns JEUT project founder - 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: JEUT Champion Recruitment
annotations are matching the definition of the real table in the database. You can do extra tests: check the nullable attribute, the length attribute, the unique constraints, and so on... But if you want to test every aspect of your entity, you will write a big piece of code for each entity! If you have a model with 10, 20 or more entities, you see directly the quantity of work. JEUT is designed to automate for you the testing of an entity. You have just to create a test class that extends a specific JEUT test class and all the work is done for you. The framework uses the annotations discovered via reflection API or the XML files (orm.xml). Do you understand the goal of JEUT? 2008/5/15, Andrus Adamchik [EMAIL PROTECTED]: Hi Alexis, I think it would really help if you started developing in the open using one of the free open source sites. This would provide the project history to a potential Champion, including access to the source code and general feel of whether you are really interested in building community around your code. On a technical note, what exactly does this framework test? Is this regression testing (i.e. checking that the ORM schema matches the actual DB schema), or is there a value beyond that? We had a similar framework submitted to the Cayenne project some time back, and I could never understand what exactly is being tested. Andrus On May 15, 2008, at 9:57 AM, Alexis Willemyns wrote: Hello all, I was a little bit hesitant before posting this project proposition. But let's go! I hope that this attempt will be a success. JEUT stands for JPA Entity Unit Test and is currently in development. So there is no public website and the code is ended up to 70%. JEUT is a testing framework for JPA entities and its main goal is to automate the test of entities without the need to write long and boring home tests. The mission is to provide a framework which is able to test the matching between entities using annotations and/or xml descriptors and the real database. A framework 100% compliant with all the existing annotations in JPA, for the current version 1 (and the future version 2... in the future). JEUT analyzes all the annotations and creates instances of entites with random values. It tries to persist these instances via the entity manager and reports the problems if existing. JEUT can be used as an extension of JUnit or TestNG, or maybe all others test frameworks. For the moment, the team is only composed with me, and I have discussed with my self about what is means to become an Apacha project. I am aware what are the conditions, responsabilities and impacts to become an Apache project. I am looking a Champion to go in the proposal phase (if the proposal makes sense) and to build a community around JEUT. Thank you for any feedback and recommendations (and sorry for my english coming from Belgium). I look forward to your responses. Regards, Alexis Willemyns JEUT project founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: general- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JEUT Champion Recruitment
Hi Alexis, I think it would really help if you started developing in the open using one of the free open source sites. This would provide the project history to a potential Champion, including access to the source code and general feel of whether you are really interested in building community around your code. On a technical note, what exactly does this framework test? Is this regression testing (i.e. checking that the ORM schema matches the actual DB schema), or is there a value beyond that? We had a similar framework submitted to the Cayenne project some time back, and I could never understand what exactly is being tested. Andrus On May 15, 2008, at 9:57 AM, Alexis Willemyns wrote: Hello all, I was a little bit hesitant before posting this project proposition. But let's go! I hope that this attempt will be a success. JEUT stands for JPA Entity Unit Test and is currently in development. So there is no public website and the code is ended up to 70%. JEUT is a testing framework for JPA entities and its main goal is to automate the test of entities without the need to write long and boring home tests. The mission is to provide a framework which is able to test the matching between entities using annotations and/or xml descriptors and the real database. A framework 100% compliant with all the existing annotations in JPA, for the current version 1 (and the future version 2... in the future). JEUT analyzes all the annotations and creates instances of entites with random values. It tries to persist these instances via the entity manager and reports the problems if existing. JEUT can be used as an extension of JUnit or TestNG, or maybe all others test frameworks. For the moment, the team is only composed with me, and I have discussed with my self about what is means to become an Apacha project. I am aware what are the conditions, responsabilities and impacts to become an Apache project. I am looking a Champion to go in the proposal phase (if the proposal makes sense) and to build a community around JEUT. Thank you for any feedback and recommendations (and sorry for my english coming from Belgium). I look forward to your responses. Regards, Alexis Willemyns JEUT project founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Duties of the PMC members
On May 6, 2008, at 7:42 PM, Roland Weber wrote: I believe that bylaws are required. At least the creation of bylaws is mentioned in the TLP resolutions I have read last year. I think that's obsolete. Cayenne graduated 1.5 years ago and has no bylaws. Of course I've also seen both terms being used interchangeably :-) My email was an example of that :-) Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Duties of the PMC members
Hi Dims, This looks good, so let me comment specifically on things that IMO need clarification. On May 5, 2008, at 11:29 PM, Davanum Srinivas wrote: #2: Create and maintain a charter that governs the PMC/project(s) That's probably obsolete. I recall seeing some TLP's having a charter, but I don't think that's an ongoing practice. All projects are part of a single org (ASF) after all. #4: Focus efforts more on community building rather than on code. [...] #11: Be active and be a hands on contributor whether it is commits or JIRA's or answering questions on user or dev mailing list. Community comes before code maybe a general ASF philosophy, but relative time and prioritization of code vs. community building is up to an individual to decide. Some people may code like crazy and never show up on a mailing list except for an occasional release vote; others may spend time on the lists, interacting with the users and fellow developers and never commit anything. Either activity is not a duty. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: guidance needed: looking into writing a proposal
Also even if some other proposals got canned, this doesn't this one won't get accepted. The best thing to do is to submit a proposal following one of the existing templates and let the people on this list comment on it, and see if you can find mentors here. Andrus On Apr 14, 2008, at 5:21 PM, Thilo Goetz wrote: Angela Cymbalak wrote: Hi, I am looking into the possibility of writing a proposal to have some code included as a podling within the Incubator project. I have been reading the Incubator Web site and I believe that I have a pretty good idea of what I would need to do if I wanted to contribute my code. The code that I have written is a photo gallery along the lines of Flickr. Instead of being written in PHP, it was written in Java. Currently, I am the only person who has worked on the code. I was looking for an area of the Incubator Web site that would list rejected proposals. It occurs to me that a project like this may have been discussed previously and voted against. I did not see a project like this among any of the existing Apache projects; although, I did see a few suggestions for projects such as Roller to include a gallery. Did you look at the incubator wiki? There's list of proposals there, most of which got accepted though: http://wiki.apache.org/incubator/ I don't remember a project like yours being proposed in the past. --Thilo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Thrift
Sorry, you are right. I just doublechecked Cayenne incubator release history, and we did clear all our IP issues before posting the first release. Anyways, throwing away the code just to *enter* the Incubator is neither required nor seems like a good approach. Andrus On Feb 4, 2008, at 2:47 PM, Martijn Dashorst wrote: On 2/4/08, Andrus Adamchik [EMAIL PROTECTED] wrote: As long as you remember that you can't release or graduate without properly audited code with a paper trail to the original author of the code. You can release from the incubator before all IP is cleared. No you can't: from the policy [1]: Podlings in Incubation SHALL NOT perform any releases of software without the explicit approval of the Incubator PMC. Such approval SHALL be given only after the Incubator PMC has followed the process detailed in these guidelines, and SHALL NOT occur until all source has been legally transferred to the ASF. Martijn [1] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Thrift
On Feb 4, 2008, at 1:15 PM, Martijn Dashorst wrote: And to be quite frank, it feels very counterproductive to me to remove code from the project with full a priori intention of putting it back in. Are you sure you will get the appropriate ICLA's from all the authors that have contributed to the whole code base? I am with Mark - it is counterproductive to throw away code now. Go in to the incubator with all your existing code base, and work on getting all missing CLA's. That's what incubation is for. At the end, even if you fail to clear some pieces, you'll have a hopefully much smaller scope of the code to rewrite/replace. As long as you remember that you can't release or graduate without properly audited code with a paper trail to the original author of the code. You can release from the incubator before all IP is cleared. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Bluesky Project into the Incubator
On Jan 5, 2008, at 9:27 PM, Bill Stoddard wrote: [x] +1 Accept BlueSky for incubation Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Shindig, an OpenSocial Container
+1 I have no explanation why the social networks are experiencing such growth these days, but it is certainly another fun area for developers :-) Andrus Brian McCallister wrote: Shindig Proposal -- = Abstract = Shindig will develop the container and backend server components for hosting OpenSocial applications. = Proposal = Shindig will develop a JavaScript container and implementations of the backend APIs and proxy required for hosting OpenSocial applications. = Background = OpenSocial provides a common set of APIs for social applications across multiple websites. With standard JavaScript and HTML, developers can create social applications that use a social network's friends and update feeds. A social application, in this context, is an application run by a third party provider and embedded in a web page, or web application, which consumes services provided by the container and by the application host. This is very similar to Portal/Portlet technology, but is based on client-side compositing, rather than server. More information can be found about OpenSocial at http://code.google.com/apis/opensocial/ == Rationale == Shindig is an implementation of an emerging set of APIs for client- side composited web applications. The Apache Software Foundation has proven to have developed a strong system and set of mores for building community-centric, open standards based systems with a wide variety of participants. A robust, community-developed implementation of these APIs will encourage compatibility between service providers, ensure an excellent implementation is available to everyone, and enable faster and easier application development for users. The Apache Software Foundation has proven it is the best place for this type of open development. = Current Status = This is a new project. = Meritocracy = The initial developers are very familiar with meritocratic open source development, both at Apache and elsewhere. Apache was chosen specifically because the initial developers want to encourage this style of development for the project. === Community === Shindig seeks to develop developer and user communities during incubation. = Core Developers = The initial core developers are all Ning employees. We hope to expand this very quickly. = Alignment = The developers of Shindig want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and server components. = Known Risks = == Orphaned products == Shindig is new development of an emerging set of APIs. == Inexperience with Open Source == The initial developers include long-time open source developers, including Apache Members. == Homogenous Developers == The initial group of developers is quite homogenous. Remedying this is a large part of why we want to bring the project to Apache. == Reliance on Salaried Developers == The initial group of developers are employed by a potential consumer of the project. Remedying this is a large part of why we want to bring the project to Apache. == Relationships with Other Apache Products == None in particular, except that Apache HTTPD is the best place to run PHP, which the server-side components Ning intends to donate have been implemented in. == A Excessive Fascination with the Apache Brand == We believe in the processes, systems, and framework Apache has put in place. The brand is nice, but is not why we wish to come to Apache. = Documentation = Google's OpenSocial Documentation: http://code.google.com/apis/opensocial/ Ning's OpenSocial Documentation: http://tinyurl.com/3y5ckx = Initial Source = Ning, Inc. intends to donate code based on their implementation of OpenSocial. The backend systems will be replaced with more generic equivalents in order to not bind the implementation to specifics of the Ning platform. This code will be extracted from Ning's internal development, and has not been expanded on past the extraction. It will be provided primarily as a starting place for a much more robust, community- developed implementation. = External Dependencies = The initial codebase relies on a library created by Google, Inc., and licensed under the Apache Software License, Version 2.0. = Required Resources = Developer and user mailing lists A subversion repository A JIRA issue tracker = Initial Committers = Thomas Baker[EMAIL PROTECTED] Tim Williamson [EMAIL PROTECTED] Brian McCallister [EMAIL PROTECTED] Thomas Dudziak [EMAIL PROTECTED] Martin Traverso [EMAIL PROTECTED] = Sponsors = == Champion == Brian McCallister [EMAIL PROTECTED] == Nominated Mentors == Brian McCallister [EMAIL PROTECTED] Thomas Dudziak [EMAIL PROTECTED] Santiago Gala [EMAIL PROTECTED] Upayavira [EMAIL PROTECTED] == Sponsoring Entity == The Apache Incubator. -
Re: Incubator Proposal: Pig
On Sep 24, 2007, at 8:22 PM, Craig L Russell wrote: Speaking just for myself, I find the name unusual but not offensive or even provocative. The fact that you wouldn't eat an animal doesn't mean you deny its existence... +1 I find it a fun name, and the one unlikely to infringe on the existing software trademarks. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] JSPWiki
On Sep 6, 2007, at 11:52 AM, Bertrand Delacretaz wrote: On 9/6/07, Janne Jalkanen [EMAIL PROTECTED] wrote: ...So, any advice on this matter?... In my (totally non-lawyer) opinion, the cleanest way to change the JSPWiki code to the Apache License might be for the project to release an Apache License version of their code, before coming to the Incubator, using their existing release channels. This would mean that the existing community has agreed on this, with the release being a very public notice of the agreement. -Bertrand IMO this would not mean much and the code would still require IP clearance in the Incubator. E.g. the Cayenne project was under Apache license, and we still had to contact all contributors and collect all the CLA's. So no simplification of the procedure at all. Cheers, Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Blue Sky Distance Collaboration System_Proposal Draft
Thanks! This certainly makes things more clear. While most of the people on this list are programming geeks, this is still somewhat outside of the mainstream area of expertise here, so expect to explain what BSDCS is over and over :-) In literature, this kind of application is called /Multi-object Multimedia Applications(MMAs)/. BTW I haven't found much usage of this term via Google, except for the BSDCS site. A few more questions if I may: * The proposal mentions that BSDCS is currently an open source [..] project. Is there currently a place where people outside your team can access the source code? Among other things, providing access to source code may help you to find interested developers at Apache. * This maybe redundant considering the previous question, but what license are you using at the moment? And also if you rely on any third-party open source packages, what license those packages require? Thanks Andrus On Aug 29, 2007, at 4:06 AM, t.peng.dev wrote: When we launched /Blue Sky Distance Collaboration system / development, we according to some reasons like these: 1. When we are discussing with somebody about a CAD drawing, if we can only watch video and hear voice of him/her, it's not enough. If we can are discuss how to use computer, it's much better if his/her computer screen is available. When we are having a lesson, it will be much vivid if teacher's slides, voice,video are available at the same time. When we are watching a football match in remote city, if we can watch it from various view point simultaneously, it becomes a much better enjoyment. This idea is use multiple scenes in distance communication, it is more than conference in which comprises only one video and its affiliated audio. So we use Collaboration instead(message communication is implement, file share and distribution is scheduled, towarding a flexible Collaboration platform ). In literature, this kind of application is called /Multi-object Multimedia Applications(MMAs)/. In our project, MMAs is used as basic component of visual and acoustic communication. 2. For MMAs is used in our system, our player and recorder should have the capability to handle it. So, we developed a customed player(XPlayer for GNU/Linux, CWPlayer for Win32) and MMA capable recorder. In this document(url is below) , there is also screenshot of our players: http://docs.google.com/View?docid=dcj48f88_09k567f Andrus Adamchik wrote: Hi there, I have a few high level technical questions about the scope of the system. I am just trying to understand what it is. * There is a quote 'BSDCS [...] changes the model from the conference to collaboration'. So is that video conferencing software that also allows playback of prerecorded content, or am I missing some other collaboration aspects? * Why a custom player? I mean there's nothing wrong with it, but would it be possible to use the existing players, such as VLC (http://www.videolan.org/)? Cheers, Andrus On Aug 24, 2007, at 1:30 PM, Ting Peng wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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: Blue Sky Distance Collaboration System_Proposal Draft
Hi there, I have a few high level technical questions about the scope of the system. I am just trying to understand what it is. * There is a quote 'BSDCS [...] changes the model from the conference to collaboration'. So is that video conferencing software that also allows playback of prerecorded content, or am I missing some other collaboration aspects? * Why a custom player? I mean there's nothing wrong with it, but would it be possible to use the existing players, such as VLC (http:// www.videolan.org/)? Cheers, Andrus On Aug 24, 2007, at 1:30 PM, Ting Peng wrote: Hello, everyone! Now, we are going to move our project 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 Mutlimedia 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 courseware). 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 benefit from it. It's portal is www.p12.edu.cn, but it is only accessible in mainland of China currently and only Chinese pages provided. We are making our web site available globally and English pages will be provided in near future. Currently, all developers of Blue Sky Distance Collaboration System are not native speaker of English. But we don't have 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 and more active. Project Overview and Features is at herehttp://docs.google.com/View?docid=dcj48f88_09k567f . For this is our first candidate project to Apache Foundation. We are grateful for your ideas! We are looking forward to 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: http://people.apache.org/
On Feb 26, 2007, at 3:49 PM, George Aroush wrote: My question is now, how do I create my folder so that http://people.apache.org/~aroush/ will show up? Your personal web root corresponds to the /home/aroush/public_html/ folder. So you'd ssh to the box and put the files you want to be visible on the web in this folder. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems creating a ftp server: java.net.BindException: Permission denied
Hi Miguel, This is a general incubator list that deals with internal procedures of various incubating Apache projects. Each one of those projects (including FtpServer), have their own mailing lists dedicated to the project specific technical issues. For FtpServer that would likely be ftpserver-dev@incubator.apache.org: http://incubator.apache.org/ftpserver/mail-lists.html Frankly, this is not your fault for mixing the lists. I am looking at the page above and indeed it seems to imply that [EMAIL PROTECTED] is a project list, which is not the case. Andrus On Feb 13, 2007, at 2:34 PM, Miguel Yepes Moyano wrote: Hello. I'm newbie in the list, and I have subscribed on it because i have got a problem: I have created a daemon program using Apache Common Daemons and launched with jsvc utility, and this one implements a Apache ftp server. When I launch it using the port 21 i've the following problem: [...] WARN FtpGenerator start - exception thrown java.net.BindException: Permission denied at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.init(ServerSocket.java:185) at java.net.ServerSocket.init(ServerSocket.java:141) at org.apache.ftpserver.socketfactory.FtpSocketFactory.createServerSocket (FtpSocketFactory.java:92) at org.apache.ftpserver.FtpServer.start(FtpServer.java:59) at com.aplicatec.alarmserver.ftpgenerator.FtpGenerator.start (FtpGenerator.java:137) at com.aplicatec.alarmserver.server.AlarmServer.start(AlarmServer.java: 138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.daemon.support.DaemonLoader.start (DaemonLoader.java:177) java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.daemon.support.DaemonLoader.start (DaemonLoader.java:177) Caused by: com.aplicatec.alarmserver.exception.AlarmServerException: Exception thrown while starting at com.aplicatec.alarmserver.ftpgenerator.FtpGenerator.start (FtpGenerator.java:142) at com.aplicatec.alarmserver.server.AlarmServer.start(AlarmServer.java: 138) ... 5 more Caused by: java.net.BindException: Permission denied at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.init(ServerSocket.java:185) at java.net.ServerSocket.init(ServerSocket.java:141) at org.apache.ftpserver.socketfactory.FtpSocketFactory.createServerSocket (FtpSocketFactory.java:92) at org.apache.ftpserver.FtpServer.start(FtpServer.java:59) at com.aplicatec.alarmserver.ftpgenerator.FtpGenerator.start (FtpGenerator.java:137) ... 6 more 13/02/2007 19:27:57 26344 jsvc.exec error: Cannot start daemon 13/02/2007 19:27:57 26343 jsvc.exec error: Service exit with a return value of 5 This problem does not always appear, it occurs only when daemon is launching using port 21 on Linux (both Ubuntu and Gentoo distribution). Using ports above 1024, there's no problem. Finally, it runs correctly on Ms Windows. I strongly need to launch the daemon with the port configuration option set to the value 21 (of course, when I launch the daemon I'm a root user). Can anybody help me? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Cayenne Becomes a Top Level Apache Project
/A bit of a late announcement and old news to cayenne-dev subscribers, but here is goes/ I am glad to announce that during its December meeting, Apache Board accepted a resolution officially establishing Cayenne as a top level Apache project. This is great (if not unexpected) news for us. ASF is built on principles of meritocracy, inclusiveness and self-governance - same principles that we were following along the road. I am delighted to see ASF as a permanent home for Cayenne (and I am sure I am not alone in that feeling). When we decided to dive into the incubation process, we had a vague idea that joining ASF would be good for growing Cayenne community. What I came to realize now is that the Apache brand is not the only reason why this happens. The other important factor, collaboration within the foundation, is real. We are now a part of a much bigger open source club where new ideas will have a much better chance of finding a receptive audience. It is up to us now to participate and take advantage of that. I'd like to thank the Incubator community and especially our mentors (Jean, Jim, Bill and Brian) for helping us with accommodation at the ASF. And also pat ourselves (Cayenne committers) on the back - we've done a huge amount of work to make the graduation happen. Finally, a note about immediate Cayenne plans: * We will be migrating the site and the mailing lists to the new locations. * We are working on the site facelift. * 2.0.2 (and 1.2.2) releases are almost ready to go. * The first 3.0 milestone (alpha) will follow immediately after that. Cheers, Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TLP Resolution Template
On Dec 7, 2006, at 12:46 AM, Jean T. Anderson wrote: There was a question raised by Greg Stein about a better template for board resolution, but since no alternative template has been made available, we are sticking with what we have. I suggest you change all Apache Cayenne PMC references to Apache Cayenne Project in that resolution (and maybe it will help the next podling). Well, I didn't want to make a change during the vote as this is not as simple as search and replace. It looks like this is something that will require more consideration going forward. In fact the way it is worded, most references to the PMC are correct. E.g. members of the PMC or Apache Cayenne PMC [..] is tasked with the migration [...] of the incubating Apache Cayenne project. Actually I think the only place where the change might make sense is in the second paragraph that now states something like: NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Cayenne PMC, be and hereby is established pursuant to Bylaws of the Foundation. But even here, instead of replacing PMC with Project, I think we simply need to add a sentence about establishing a project (as PMC also has be established). Comments? Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Cayenne to TLP status (pending board approval)
I guess we can close the vote - it's been running for 96 hours already. We've got 5 plus one votes, of which 4 are from the Incubator PMC members, and no other votes. Here is a breakdown: Bill Dudney Jean T. Anderson (Incubator PMC) Leo Simons (Incubator PMC) Robert Burrell Donkin (Incubator PMC) Brian McCallister (Incubator PMC) There was a question raised by Greg Stein about a better template for board resolution, but since no alternative template has been made available, we are sticking with what we have. So now that our graduation has been officially approved by the Incubator, one last thing remains - the vote by the ASF Board. Is this something that is going to happen during the December board meeting? Thanks Andrus On Dec 1, 2006, at 5:24 PM, Andrus Adamchik wrote: Apache Cayenne community just voted to request graduation from the Incubator as a TLP [1]. The text of the proposed board resolution (adopted from iBatis graduation resolution) is included below. Other project related links are also shown below - [2], [3]. The following people cast +1 votes: Andrus Adamchik (PPMC) Craig Russell Malcolm Edgar (committer) Matt Kerr Tore Halset (PPMC) Ari Maniatis Bill Dudney (PPMC) Michael Gentry (PPMC) Mike Kienenberger (PPMC) Jean T. Anderson (PPMC / Incubator PMC) Kevin Menard (committer) Jason Dwyer I am asking for a vote of the Incubator PMC on graduation of Cayenne that is conditional on the board's approval of a TLP for that purpose. Please cast your votes. [1] http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200612.mbox/[EMAIL PROTECTED] [2] http://incubator.apache.org/cayenne/ [3] http://incubator.apache.org/projects/cayenne.html Andrus - Apache Cayenne developers have voted to request the ASF Board to establish Cayenne as a Top Level Project at the ASF. Here is the text of the suggested resolution: 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 object-relational mapping (ORM) and remoting services, 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 Cayenne PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Cayenne PMC be and hereby is responsible for the creation and maintenance of software related to the Cayenne Object Relational Framework and tools, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Cayenne 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 Cayenne PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Cayenne PMC; 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 Cayenne PMC: Andrus Adamchik ([EMAIL PROTECTED]) Bill Dudney ([EMAIL PROTECTED]) Michael Gentry ([EMAIL PROTECTED]) Tore Halset ([EMAIL PROTECTED]) Mike Kienenberger ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrus Adamchik be and hereby is appointed to the office of Vice President, Apache Cayenne, 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 Cayenne PMC be and hereby is tasked with the migration and rationalization of the incubating Apache Cayenne project; and be it further RESOLVED, that all responsibility pertaining to the incubating Apache Cayenne project encumbered upon the incubator PMC be hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Cayenne to TLP status (pending board approval)
Hmm... we took it from the board minutes: http://www.apache.org/foundation/records/minutes/2005/ board_minutes_2005_05_18.txt Anybody can point to a better template? Thanks Andrus On Dec 2, 2006, at 4:51 AM, Greg Stein wrote: The name would be Apache Cayenne Project. Please fix before submitting to the Board. There is some stupid virus of a template showing these as Apache Foo PMC which has to stop. People should really look at actual resolutions that the Board approves, not what gets sent in. We sometimes tweak them. Cheers, -g On 12/1/06, Andrus Adamchik [EMAIL PROTECTED] wrote: Apache Cayenne community just voted to request graduation from the Incubator as a TLP [1]. The text of the proposed board resolution (adopted from iBatis graduation resolution) is included below. Other project related links are also shown below - [2], [3]. The following people cast +1 votes: Andrus Adamchik (PPMC) Craig Russell Malcolm Edgar (committer) Matt Kerr Tore Halset (PPMC) Ari Maniatis Bill Dudney (PPMC) Michael Gentry (PPMC) Mike Kienenberger (PPMC) Jean T. Anderson (PPMC / Incubator PMC) Kevin Menard (committer) Jason Dwyer I am asking for a vote of the Incubator PMC on graduation of Cayenne that is conditional on the board's approval of a TLP for that purpose. Please cast your votes. [1] http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200612.mbox/[EMAIL PROTECTED] %3e [2] http://incubator.apache.org/cayenne/ [3] http://incubator.apache.org/projects/cayenne.html Andrus - Apache Cayenne developers have voted to request the ASF Board to establish Cayenne as a Top Level Project at the ASF. Here is the text of the suggested resolution: 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 object-relational mapping (ORM) and remoting services, 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 Cayenne PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Cayenne PMC be and hereby is responsible for the creation and maintenance of software related to the Cayenne Object Relational Framework and tools, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Cayenne 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 Cayenne PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Cayenne PMC; 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 Cayenne PMC: Andrus Adamchik ([EMAIL PROTECTED]) Bill Dudney ([EMAIL PROTECTED]) Michael Gentry ([EMAIL PROTECTED]) Tore Halset ([EMAIL PROTECTED]) Mike Kienenberger ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrus Adamchik be and hereby is appointed to the office of Vice President, Apache Cayenne, 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 Cayenne PMC be and hereby is tasked with the migration and rationalization of the incubating Apache Cayenne project; and be it further RESOLVED, that all responsibility pertaining to the incubating Apache Cayenne project encumbered upon the incubator PMC be hereafter discharged. -- [EMAIL PROTECTED] ... ASF Chairman ... http://www.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]
[VOTE] Graduate Cayenne to TLP status (pending board approval)
Apache Cayenne community just voted to request graduation from the Incubator as a TLP [1]. The text of the proposed board resolution (adopted from iBatis graduation resolution) is included below. Other project related links are also shown below - [2], [3]. The following people cast +1 votes: Andrus Adamchik (PPMC) Craig Russell Malcolm Edgar (committer) Matt Kerr Tore Halset (PPMC) Ari Maniatis Bill Dudney (PPMC) Michael Gentry (PPMC) Mike Kienenberger (PPMC) Jean T. Anderson (PPMC / Incubator PMC) Kevin Menard (committer) Jason Dwyer I am asking for a vote of the Incubator PMC on graduation of Cayenne that is conditional on the board's approval of a TLP for that purpose. Please cast your votes. [1] http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200612.mbox/[EMAIL PROTECTED] [2] http://incubator.apache.org/cayenne/ [3] http://incubator.apache.org/projects/cayenne.html Andrus - Apache Cayenne developers have voted to request the ASF Board to establish Cayenne as a Top Level Project at the ASF. Here is the text of the suggested resolution: 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 object-relational mapping (ORM) and remoting services, 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 Cayenne PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Cayenne PMC be and hereby is responsible for the creation and maintenance of software related to the Cayenne Object Relational Framework and tools, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Cayenne 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 Cayenne PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Cayenne PMC; 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 Cayenne PMC: Andrus Adamchik ([EMAIL PROTECTED]) Bill Dudney ([EMAIL PROTECTED]) Michael Gentry ([EMAIL PROTECTED]) Tore Halset ([EMAIL PROTECTED]) Mike Kienenberger ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrus Adamchik be and hereby is appointed to the office of Vice President, Apache Cayenne, 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 Cayenne PMC be and hereby is tasked with the migration and rationalization of the incubating Apache Cayenne project; and be it further RESOLVED, that all responsibility pertaining to the incubating Apache Cayenne project encumbered upon the incubator PMC be hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Cayenne to TLP status (pending board approval)
Actually TLP was the plan from the beginning, the main reason being that Cayenne was an existing open source project with a working meritocratic self-management since the inception in 2001. In the ASF structure this maps best to a TLP with its own PMC. Also while we have a great working relationship with some folks from DB community, there is no committer overlap at the moment. So that will make it a pure umbrella project just because Cayenne also happens to deal with DB access. Andrus P.S. This reminds me of something that I should've put in my original email - I'd like to thank DB PMC (and especially Jean) for all the work helping us with various incubation aspects :-) On Dec 1, 2006, at 6:26 PM, Yoav Shapira wrote: Hi, Cool. Can you please refresh my memory on why Cayenne wants to be a TLP now, as opposed to a project under the DB PMC (its original sponsor)? Yoav On 12/1/06, Andrus Adamchik [EMAIL PROTECTED] wrote: Apache Cayenne community just voted to request graduation from the Incubator as a TLP [1]. The text of the proposed board resolution (adopted from iBatis graduation resolution) is included below. Other project related links are also shown below - [2], [3]. The following people cast +1 votes: Andrus Adamchik (PPMC) Craig Russell Malcolm Edgar (committer) Matt Kerr Tore Halset (PPMC) Ari Maniatis Bill Dudney (PPMC) Michael Gentry (PPMC) Mike Kienenberger (PPMC) Jean T. Anderson (PPMC / Incubator PMC) Kevin Menard (committer) Jason Dwyer I am asking for a vote of the Incubator PMC on graduation of Cayenne that is conditional on the board's approval of a TLP for that purpose. Please cast your votes. [1] http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200612.mbox/[EMAIL PROTECTED] %3e [2] http://incubator.apache.org/cayenne/ [3] http://incubator.apache.org/projects/cayenne.html Andrus - Apache Cayenne developers have voted to request the ASF Board to establish Cayenne as a Top Level Project at the ASF. Here is the text of the suggested resolution: 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 object-relational mapping (ORM) and remoting services, 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 Cayenne PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Cayenne PMC be and hereby is responsible for the creation and maintenance of software related to the Cayenne Object Relational Framework and tools, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Cayenne 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 Cayenne PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Cayenne PMC; 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 Cayenne PMC: Andrus Adamchik ([EMAIL PROTECTED]) Bill Dudney ([EMAIL PROTECTED]) Michael Gentry ([EMAIL PROTECTED]) Tore Halset ([EMAIL PROTECTED]) Mike Kienenberger ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrus Adamchik be and hereby is appointed to the office of Vice President, Apache Cayenne, 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 Cayenne PMC be and hereby is tasked with the migration and rationalization of the incubating Apache Cayenne project; and be it further RESOLVED, that all responsibility pertaining to the incubating Apache Cayenne project encumbered upon the incubator PMC be 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: [doc] How to add a PPMC member
On Oct 10, 2006, at 4:20 PM, robert burrell donkin wrote: in practice i think that the PPMC will become the PMC. Sans the mentors who signed up to help with incubation, but no intent to participate in project development. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
We need one more vote from an Incubator PMC member... Or do we? Jim Jagielski voted +1 on the release already during the vote on cayenne-dev. Does that count? Andrus On Oct 1, 2006, at 4:41 PM, Andrus Adamchik wrote: I just posted the new release snapshots here: http://people.apache.org/~aadamchik/release/2.0.1/ The changes from the first attempt are: * Added license headers to the .dtd and .css files in the documentation. * Added license headers to the tutorial Java files that are changeable by users. * Added a note in the LICENSE file referring readers to the NOTICE file for explanation on third-party licenses. Many thanks to Robert for helping to straighten this up. Andrus On Sep 30, 2006, at 12:09 PM, Andrus Adamchik wrote: Cayenne community has voted and approved 2.0.1 release of Cayenne. This release marks a major milestone in Cayenne incubation as we've fully resolved all IP issues and got rid of incompatible license dependencies. Now we would like to request the approval of the Incubator PMC to perform the release. There were 6 +1 votes (including 3 from PPMC members) and no other votes: Andrus Adamchik +1 Michael Gentry +1 Tore Halset +1 Mike Kienenberger +1 Kevin Menard +1 Jim Jagielski +1 (cast on the PPMC list) Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200609.mbox/[EMAIL PROTECTED] %3e Release artifacts can be found here: http://people.apache.org/~aadamchik/release/2.0.1/ And here is my +1 (non-binding) Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
Cayenne 2.0.1 release has been officially approved by the Incubator PMC (voting thread can be found here - [1]). We got 6 +1 votes (of which 3 were binding), and no other votes: Jean T. Anderson +1 Bill Dudney +1 Robert Burrell Donkin +1 Craig L Russell +1 Jim Jagielski +1 Andrus Adamchik +1 Now a practical question - what's involved in distributing the release? Anything beyond placing a copy to people.apache.org:/www/ people.apache.org/dist/incubator/cayenne/ ??? Andrus [1] http://mail-archives.apache.org/mod_mbox/incubator-general/ 200610.mbox/[EMAIL PROTECTED] On Sep 30, 2006, at 12:09 PM, Andrus Adamchik wrote: Cayenne community has voted and approved 2.0.1 release of Cayenne. This release marks a major milestone in Cayenne incubation as we've fully resolved all IP issues and got rid of incompatible license dependencies. Now we would like to request the approval of the Incubator PMC to perform the release. There were 6 +1 votes (including 3 from PPMC members) and no other votes: Andrus Adamchik +1 Michael Gentry +1 Tore Halset +1 Mike Kienenberger +1 Kevin Menard +1 Jim Jagielski +1 (cast on the PPMC list) Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200609.mbox/[EMAIL PROTECTED] Release artifacts can be found here: http://people.apache.org/~aadamchik/release/2.0.1/ And here is my +1 (non-binding) Andrus - 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] Approve the 2.0.1 release of Cayenne
Brian McCallister's vote just came in, so it makes it 7 +1, with 4 binding. Andrus On Oct 5, 2006, at 4:18 PM, Andrus Adamchik wrote: Cayenne 2.0.1 release has been officially approved by the Incubator PMC (voting thread can be found here - [1]). We got 6 +1 votes (of which 3 were binding), and no other votes: Jean T. Anderson +1 Bill Dudney +1 Robert Burrell Donkin +1 Craig L Russell +1 Jim Jagielski +1 Andrus Adamchik +1 Now a practical question - what's involved in distributing the release? Anything beyond placing a copy to people.apache.org:/www/ people.apache.org/dist/incubator/cayenne/ ??? Andrus [1] http://mail-archives.apache.org/mod_mbox/incubator-general/ 200610.mbox/[EMAIL PROTECTED] On Sep 30, 2006, at 12:09 PM, Andrus Adamchik wrote: Cayenne community has voted and approved 2.0.1 release of Cayenne. This release marks a major milestone in Cayenne incubation as we've fully resolved all IP issues and got rid of incompatible license dependencies. Now we would like to request the approval of the Incubator PMC to perform the release. There were 6 +1 votes (including 3 from PPMC members) and no other votes: Andrus Adamchik +1 Michael Gentry +1 Tore Halset +1 Mike Kienenberger +1 Kevin Menard +1 Jim Jagielski +1 (cast on the PPMC list) Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200609.mbox/[EMAIL PROTECTED] %3e Release artifacts can be found here: http://people.apache.org/~aadamchik/release/2.0.1/ And here is my +1 (non-binding) Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
On Oct 3, 2006, at 5:32 PM, robert burrell donkin wrote: (cayenne-2.0.1-incubating/doc/api/cayenne/apache-javadoc.css i think was missed) Oops - fixed that on the 2.0 branch and trunk. Thanks Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
I can swear I did it before, but I posted it again a few minutes ago. Seems to be there now: http://pgp.mit.edu:11371/pks/lookup?search=Andrus+Adamchikop=index Andrus On Oct 3, 2006, at 11:20 AM, Craig L Russell wrote: Hi Andrus, Congratulations on your release candidate. I was unable to retrieve your key B8AF90BF from the public key server pgp.mit.edu, which you used to sign the release. Have you had your key signed and uploaded it to a public server? Craig On Sep 30, 2006, at 9:09 AM, Andrus Adamchik wrote: Cayenne community has voted and approved 2.0.1 release of Cayenne. This release marks a major milestone in Cayenne incubation as we've fully resolved all IP issues and got rid of incompatible license dependencies. Now we would like to request the approval of the Incubator PMC to perform the release. There were 6 +1 votes (including 3 from PPMC members) and no other votes: Andrus Adamchik +1 Michael Gentry +1 Tore Halset +1 Mike Kienenberger +1 Kevin Menard +1 Jim Jagielski +1 (cast on the PPMC list) Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200609.mbox/[EMAIL PROTECTED] %3e Release artifacts can be found here: http://people.apache.org/~aadamchik/release/2.0.1/ And here is my +1 (non-binding) Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
Hi Robert, On Oct 1, 2006, at 12:57 PM, robert burrell donkin wrote: oh yes: the LICENSE and NOTICE files are ok but the LICENSE file could be improved by including an indication about to which artifact or source file the particular license applies. I guess then it would duplicate NOTICE file (not that it is bad, just more chance for the two to get out of sync in the future). NOTICE does it in a way already, so I think of it as an index for the more verbose LICENSE. On Oct 1, 2006, at 12:35 PM, robert burrell donkin wrote: a RAT run turned up a few issues: *IMPORTANT* not under open source license: http://svn.apache.org/repos/asf/incubator/cayenne/main/tags/2.0.1/ cayenne/cayenne-other/wiki-docs/Documentation/User%20Guide/ Introduction/Guide%20to%201.1%20Features/cayenne-data-map-1_2.dtd Everything except for DTD's are generated files. We'll will fix the DTD's shortly. interesting that this is a(nother) binary-with-source distribution. this looks like it's been constructed by a build process rather than a direct svn snapshot. True - this was a conscious decision made a few years ago with the goal to make the release artifacts user-friendly. Looking at some projects that post releases as SVN snapshots can be a nightmare - it is organized for development, not for end-user consumption. It will be a nightmare for Cayenne too, as Cayenne trunk (targeting 3.0 release) is switched to Maven, and there is no one-to- one correspondence between final release jars and Maven artifacts because of multiple JDK versions support, lightweight stripped down jars for remote clients, etc. i hope that cayenne will also be made available as a source distribution. I'd like to hear arguments why this would be a good thing? I can think of two: * Smaller download. IMO this is addressed by clean SVN tagging (users can always build a given version if they want); widespread use of broadband (not only in the West); and much more user-friendly release (you get binaries, source and tools in one place and in place where you expect to find it). * Binaries are not cross-platform. Aside from the tool launchers, everything is Java. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
On Oct 1, 2006, at 2:42 PM, robert burrell donkin wrote: for example http://svn.apache.org/repos/asf/incubator/cayenne/main/ tags/2.0.1/cayenne/tutorials/quick-start/cayenne-tutorial/src/ cayenne/tutorial/Artist.java looked to me like an example of a hand-crafted subclass. This one was generated, but then customized by hand. We do need a license on it - I will clean this up. preferences files didn't look like it was generated to me either: http://svn.apache.org/repos/asf/incubator/cayenne/main/tags/2.0.1/ cayenne/cayenne-java/src/modeler/resources/pref/ ModelerPreferences.map.xml. though perhaps i was fooled... This one is generated by the Modeler tool to map preferences database for itself. one good practice often adopted by projects which make extensive use of generated source is to ensure that it's clear (either by including notes in the documents or by creating them in directories with clear names) which documents are generated and which are not. it would make it a lot easier and quicker to audit cayenne releases if this practice were adopted. Good point - I am +1. In the future releases we'll need to make our templates more explicit in this respect. Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve the 2.0.1 release of Cayenne
I just posted the new release snapshots here: http://people.apache.org/~aadamchik/release/2.0.1/ The changes from the first attempt are: * Added license headers to the .dtd and .css files in the documentation. * Added license headers to the tutorial Java files that are changeable by users. * Added a note in the LICENSE file referring readers to the NOTICE file for explanation on third-party licenses. Many thanks to Robert for helping to straighten this up. Andrus On Sep 30, 2006, at 12:09 PM, Andrus Adamchik wrote: Cayenne community has voted and approved 2.0.1 release of Cayenne. This release marks a major milestone in Cayenne incubation as we've fully resolved all IP issues and got rid of incompatible license dependencies. Now we would like to request the approval of the Incubator PMC to perform the release. There were 6 +1 votes (including 3 from PPMC members) and no other votes: Andrus Adamchik +1 Michael Gentry +1 Tore Halset +1 Mike Kienenberger +1 Kevin Menard +1 Jim Jagielski +1 (cast on the PPMC list) Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200609.mbox/[EMAIL PROTECTED] Release artifacts can be found here: http://people.apache.org/~aadamchik/release/2.0.1/ And here is my +1 (non-binding) Andrus - 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]
[VOTE] Approve the 2.0.1 release of Cayenne
Cayenne community has voted and approved 2.0.1 release of Cayenne. This release marks a major milestone in Cayenne incubation as we've fully resolved all IP issues and got rid of incompatible license dependencies. Now we would like to request the approval of the Incubator PMC to perform the release. There were 6 +1 votes (including 3 from PPMC members) and no other votes: Andrus Adamchik +1 Michael Gentry +1 Tore Halset +1 Mike Kienenberger +1 Kevin Menard +1 Jim Jagielski +1 (cast on the PPMC list) Vote thread: http://mail-archives.apache.org/mod_mbox/incubator-cayenne-dev/ 200609.mbox/[EMAIL PROTECTED] Release artifacts can be found here: http://people.apache.org/~aadamchik/release/2.0.1/ And here is my +1 (non-binding) Andrus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
