Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) Looks great D. On Wed, Oct 12, 2011 at 4:55 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: +1, binding, awesome guys, good luck! Cheers, Chris On Oct 11, 2011, at 2:09 PM, Jukka Zitting wrote: Hi, As discussed, the PhoneGap project would like to enter the Incubator under the Apache Callback name (potential alternative names to be discussed during incubation). The initial proposal has been well received and there are no major open issues, so it's time to vote! Thus I'm now calling a formal VOTE on the Apache Callback proposal as included below. The proposal is also available at http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal on the PhoneGap wiki, and I'll place a copy for our archives on the Incubator wiki as soon as it stops giving me internal server errors. Please VOTE: [ ] +1 Accept Apache Callback for incubation [ ] -1 Don't accept Apache Callback for incubation because... This vote is open for the next 72 hours. Everyone is welcome to participate, but only votes from the Incubator PMC members are binding. Thanks! My vote is +1. Best regards, Jukka Zitting Apache Callback Proposal Abstract Apache Callback is a platform for building native mobile applications using HTML, CSS and JavaScript. Proposal Apache Callback allows web developers to natively target Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian and Samsung Bada with a single codebase. The Callback APIs are based on open web standards. The Callback bridge technology enables access to native device capabilities. Utilizing the Callback bridge native plugins allow for any type of native access from the embedded webview. Background -- Apache Callback is the free software evolution of the popular PhoneGap project. PhoneGap evolved from a hack that enabled a FFI (Foreign Function Interface) to an embedded WebView on iOS to a complete suite of tools for tackling parity across many mobile device and desktop platforms. PhoneGap has always focused on two complementary goals. Our first goal, is to see the web as a first class development platform. Not a sandbox without a filesystem but a real first class platform that includes access to the local system apis, sensors and data, in addition to first class tooling such as system debuggers. The second goal of PhoneGap is for the project to cease to exist. This is not a nihilistic sentiment, rather we at the PhoneGap project are providing a reference implementation for web browsers to assist and guide the standardization process of browser APIs. The name and trademark of PhoneGap will become the commercial entity for the project. The source, code, documentation and related assets will all be contributed to the Apache Foundation as Callback. The Callback name comes from the event of the same name that is fired when the FFI bridge is established. Rationale - The dominate window to the web is quickly becoming devices, mostly phones. The manufacturers of devices, creators of mobile operating systems, and authors of web browsers are consolidating. (In many cases these are all already the same company.) Those stakeholders may see a future for the web but their bottom line is not necessarily motivated to participate in an open web. It is especially clear that while many of these platforms have been seeing some level of strategic neglect in favor of enhanced experiences at the price locking developers into their respective platforms. The Callback project exists to bring the focus back to an open and accessible web. Initial Goals - * License all PhoneGap source code and documentation to the Apache Software Foundation. (We already name the Apache license in our CLA.) * Setup and standardize the open governance of the Callback project. * Rename all assets from PhoneGap to Callback in project src, docs, tests and related infrastructure. Current Status -- Callback is a mature software project recently shipping 1.0 on July 29, 2011. Meritocracy --- Callback has always been a project driven by merit and, in a sense, our solution is brute force requiring many collaborating developers to solve our goals. It would be far easier, and perhaps more correct, for the Callback project to port a single web browser codebase, and API bindings, across platforms but our executable size would be appreciably larger, unacceptably so for mobile, and our target abstraction would be only tertiary to maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The
Re: [VOTE] Kafka to join the Incubator
+1 (Binding) By the way, it is great to see another Scala-based project coming to Apache. Dick VP Apache ESME On Wed, Jun 29, 2011 at 12:35 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: +1 (binding) Tommaso 2011/6/28 Jun Rao jun...@gmail.com Hi all, Since the discussion on the thread of the Kafka incubator proposal is winding down, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/KafkaProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg29594.html Please cast your votes: [ ] +1 Accept Kafka for incubation [ ] +0 Indifferent to Kafka incubation [ ] -1 Reject Kafka for incubation This vote will close 72 hours from now. Thanks, Jun == Abstract == Kafka is a distributed publish-subscribe system for processing large amounts of streaming data. == Proposal == Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing. == Background == Kafka was developed at LinkedIn to process the large amounts of events generated by that company's website and provide a common repository for many types of consumers to access and process those events. Kafka has been used in production at LinkedIn scale to handle dozens of types of events including page views, searches and social network activity. Kafka clusters at LinkedIn currently process more than two billion events per day. Kafka fills the gap between messaging systems such as Apache ActiveMQ, which provide low latency message delivery but don't focus on throughput, and log processing systems such as Scribe and Flume, which do not provide adequate latency for our diverse set of consumers. Kafka can also be inserted into traditional log-processing systems, acting as an intermediate step before further processing. Kafka focuses relentlessly on performance and throughput by not introspecting into message content, nor indexing them on the broker. We also achieve high performance by depending on Java's sendFile/transferTo capabilities to minimize intermediate buffer copies and relying on the OS's pagecache to efficiently serve up message contents to consumers. Kafka is also designed to be scalable and it depends on Apache ZooKeeper for coordination amongst its producers, brokers and consumers. Kafka is written in Scala. It was developed internally at LinkedIn to meet our particular use cases, but will be useful to many organizations facing a similar need to reliably process large amounts of streaming data. Therefore, we would like to share it the ASF and begin developing a community of developers and users within Apache. == Rationale == Many organizations can benefit from a reliable stream processing system such as Kafka. While our use case of processing events from a very large website like LinkedIn has driven the design of Kafka, its uses are varied and we expect many new use cases to emerge. Kafka provides a natural bridge between near real-time event processing and offline batch processing and will appeal to many users. == Current Status == === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Kafka following the Apache meritocracy model. Since Kafka was open sourced we have solicited contributions via the website and presentations given to user groups and technical audiences. We have had positive responses to these and have received several contributions and clients for other languages. We plan to continue this support for new contributors and work with those who contribute significantly to the project to make them committers. === Community === Kafka is currently being used by developed by engineers within LinkedIn and used in production in that company. Additionally, we have active users in or have received contributions from a diverse set of companies including MediaSift, SocialTwist, Clearspring and Urban Airship. Recent public presentations of Kafka and its goals garnered much interest from potential contributors. We hope to extend our contributor base significantly and invite all those who are interested in building high-throughput distributed systems to participate. We have begun receiving contributions from outside of LinkedIn, including clients for several languages including Ruby, PHP, Clojure, .NET and Python. To further this goal, we use GitHub issue tracking and branching facilities, as well as maintaining a public mailing list via Google Groups. === Core Developers === Kafka is currently being
Re: [VOTE] Accept OpenOffice.org for incubation
+1 (binding) Dick On Sat, Jun 11, 2011 at 10:06 PM, donald_harbi...@us.ibm.com wrote: +1 (non-binding) - Don Harbison Sam Ruby ru...@intertwingly.net wrote on 06/10/2011 12:02:44 PM: Please cast your votes: [ X] +1 Accept OpenOffice.org for incubation [ ] +0 Indifferent to OpenOffice.org incubation [ ] -1 Reject OpenOffice.org for incubation This vote will close 72 hours from now. - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] ESME Graduation to TLP
Hi IPMC'ers and the rest of the Incubator community, The ESME community has been discussing graduation to TLP [1] and we just concluded a vote on the subject [2]. There is overwhelming consensus in the community (all +1 VOTEs including those from our mentors) that we've achieved what's required here in the Incubator, and so we'd like to put forth the following board resolution for the next Board meeting to promote ESME to an Apache TLP and graduate from the Incubator. Please VOTE on the below resolution for promoting ESME to an Apache TLP and graduating from the Incubator. The VOTE is open for 72 hrs. [ ] +1 Accept ESME's graduation from the Incubator [ ] +0 Don't care. [ ] -1 Don't accept ESME's graduation from the Incubator because... = Establish the Apache ESME Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to collaborative messaging systems 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 ESME Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache ESME Project be and hereby is responsible for the creation and maintenance of software related to collaborative messaging systems; and be it further RESOLVED, that the office of Vice President, Apache ESME 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 ESME Project, and to have primary responsibility for management of the project within the scope of responsibility of the Apache ESME 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 ESME Project: * Anne Kathrine Petteroeakpe...@apache.org * Darren Hague dha...@apache.org * Ethan Jewettesje...@apache.org * Mrinal Wadhwamri...@apache.org * Richard Hirsch rhir...@apache.org * Vassil Dichev vdic...@apache.org * Imtiaz Ahmed H Eimt...@apache.org * Bertrand Delacretazbdel...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Hirsch be appointed to the office of Vice President, Apache ESME, 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 ESME 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 ESME Project; and be it further RESOLVED, that the Apache ESME Project be and hereby is tasked with the migration and rationalization of the Apache Incubator ESME podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator ESME podling encumbered upon the Apache Incubator Project are hereafter discharged. = Here's my +1 (binding). Regards, Dick [1] http://markmail.org/thread/gv5msai5acgfwjz4 [2] http://markmail.org/thread/krf7nwf7swsde2ys - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [RESULT] Approve the release of apache-esme-incubating-1.1
Thanks for the information I'll copy the files this evening D. On Fri, Oct 8, 2010 at 9:48 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Fri, Oct 8, 2010 at 5:52 AM, Richard Hirsch hirsch.d...@gmail.com wrote: ...I'll proceed with distribution [2]. As a IPMC member, do I have access to www.apache.org/dist? Do I just copy the material from http://people.apache.org/~rhirsch/esme/ directly into http://www.apache.org/dist/incubator/esme/ and replace the old KEYS file with the new one?... AFAIK you should copy to /x1/www/www.apache.org/dist/incubator/esme on people.apache.org, that's replicated a few times a day to http://www.apache.org/dist/incubator/esme/ Looks like your rights are good to copy there. -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
[VOTE] [RESULT] Approve the release of apache-esme-incubating-1.1
Hi all, after more than 72 hours, this vote has started and together with those received on the podling list [1], we have now received sufficient IPMC binding votes to proceed with the release of ESME 1.1. We got 3 binding IPMC +1 votes and no 0 or -1 votes as listed below: +1 Dick Hirsch +1 Daniel Kulp +1 Bertrand Delacretaz I'll proceed with distribution [2]. As a IPMC member, do I have access to www.apache.org/dist? Do I just copy the material from http://people.apache.org/~rhirsch/esme/ directly into http://www.apache.org/dist/incubator/esme/ and replace the old KEYS file with the new one? Thanks D. [1] http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/201010.mbox/%3caanlktim_jhcbvzao6ou-dt_adicgyhsi7+pj-a+9y...@mail.gmail.com%3e - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] Re: [VOTE] experimental delegation of new committer votes to PPMC
Was there a particular reason why the three podlings were selected (thrift, sis, and esme). D. On Mon, Aug 23, 2010 at 11:04 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sun, Aug 22, 2010 at 12:38 AM, Joe Schaefer joe_schae...@yahoo.com wrote: The vote has closed and here is the tally:... I was offline and missed the vote but here's my late +1 for support! -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: Compatibility of code written in Scala with Apache License
Hi Sandro, you may be interested to know that is already a Scala-based Apache incubator project: http://incubator.apache.org/esme/ Regards, Dick On Tue, Apr 20, 2010 at 3:51 PM, Sandro Martini sandro.mart...@gmail.comwrote: Hi Bertrand, thank you very much for the Help. I find Scala very (complex but) exciting, so start some experiments in Apache with Scala could be really a good thing, for both communities. Bye, Sandro 2010/4/16, Bertrand Delacretaz bdelacre...@apache.org: Hi, On Fri, Apr 16, 2010 at 12:51 AM, Sandro Martini sandro.mart...@gmail.com wrote: ...a quick question (I hope this is the right place for this question, if not excuse me):... The best place for such questions is legal-disc...@apache.org, but I think this case is simple enough to be answered here. I have some code created in Scala, and I'd like (if accepted by other team members, but in any case this is an interesting thing to know) in the future to publish it into SVN here (I'm one of Apache Pivot Developers), but I'd like a confirm that this will be compatible with the Apache license. The main dependency it has is to Scala, and then also with other related Scala libraries mainly for tests (but this could be drop in case of problems) You should look at each library's license individually, and check http://apache.org/legal/resolved.html or ask legal-discuss if unclear. Scala is licensed in a similar way of BSD ( http://www.scala-lang.org/node/146 , http://www.scala-lang.org/node/249 ) ... so there shouldn't be problems, right ? Those licenses look good to me, and IIUC they require the copyright notice to be added to your project's NOTICE file. ...Thanks you very much for the help... You're welcome - anything that comes out of epfl is a Good Thing (my office is just 2km from that ;-) -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
[VOTE RESULT] Approve the release of apache-esme-1.0-RC1-incubating
The vote is now closed. The vote results are: +1 votes: 4 (Bertrand Delacretaz, Gianugo Rabellino, Sylvain Wallez, Daniel Kulp) 0 votes: 0 -1 votes: 0 The vote therefore passes. Many thanks to those who voted. Regards, Dick On Tue, Mar 2, 2010 at 1:53 AM, Daniel Kulp dk...@apache.org wrote: +1 IPMC Binding. Nice job! Dan On Thu February 25 2010 11:42:55 pm Richard Hirsch wrote: The ESME community has voted on and approved the release of apache-esme-1.0-RC1-incubating. We would now like to request the approval of the Incubator PMC for this release. Details of the ESME community vote can be found here: http://www.mail-archive.com/esme-...@incubator.apache.org/msg03120.html The candidate can be found at http://people.apache.org/~rhirsch/esme/ See the CHANGES.txt file for details on release contents. The release candidate is a tar archive of the sources in https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-RC1-in cubating/ The MD5 checksum of the apache-esme-1.0-RC1-incubating.src.tar.gz release package is 35 72 D0 B3 49 3C C3 BA D5 4F 57 E8 EA 1D 9D 54 Please vote on releasing this package as Apache ESME 1.0-incubating. Please vote to publish this release by Monday, March 1 05:41 CET, please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the ESME mailing list. The link to the vote result is here: http://www.mail-archive.com/esme-...@incubator.apache.org/msg03156.html Thanks Dick Hello All, Voting on the ESME apache-esme-1.0-RC1-incubating has concluded Results: 5 binding +1 vote Dick Hirsch +1 Ethan Jewett +1 Anne Kathrine Petteroe +1 Gianugo Rabellino +1 Bertrand Delacretaz +1 2 non-binding +1 votes Daniel Koller +1 Uday Subbarayan +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Approve the release of apache-esme-1.0-RC1-incubating
The ESME community has voted on and approved the release of apache-esme-1.0-RC1-incubating. We would now like to request the approval of the Incubator PMC for this release. Details of the ESME community vote can be found here: http://www.mail-archive.com/esme-...@incubator.apache.org/msg03120.html The candidate can be found at http://people.apache.org/~rhirsch/esme/ See the CHANGES.txt file for details on release contents. The release candidate is a tar archive of the sources in https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-RC1-incubating/ The MD5 checksum of the apache-esme-1.0-RC1-incubating.src.tar.gz release package is 35 72 D0 B3 49 3C C3 BA D5 4F 57 E8 EA 1D 9D 54 Please vote on releasing this package as Apache ESME 1.0-incubating. Please vote to publish this release by Monday, March 1 05:41 CET, please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the ESME mailing list. The link to the vote result is here: http://www.mail-archive.com/esme-...@incubator.apache.org/msg03156.html Thanks Dick Hello All, Voting on the ESME apache-esme-1.0-RC1-incubating has concluded Results: 5 binding +1 vote Dick Hirsch +1 Ethan Jewett +1 Anne Kathrine Petteroe +1 Gianugo Rabellino +1 Bertrand Delacretaz +1 2 non-binding +1 votes Daniel Koller +1 Uday Subbarayan +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: [VOTE] Approve the release of apache-esme-incubating-1.0
-- Forwarded message -- From: Richard Hirsch hirsch.d...@gmail.com Date: Tue, Feb 16, 2010 at 4:17 PM Subject: Re: [VOTE] Approve the release of apache-esme-incubating-1.0 To: Daniel Kulp dk...@apache.org On Tue, Feb 16, 2010 at 3:57 PM, Daniel Kulp dk...@apache.org wrote: +1 (mentor and IPMC binding) Some thoughts, but nothing that I would consider a show stopper since this is a source only release (aka: not providing a prebuilt war type thing or deploying it to Maven central): 1) The README mentions a Collective work: Copyright 2007, but the NOTICE starts the copyright at 2008. That said, I'd just remove the License section from the README entirely. Done. 2) The tar unpacks into a trunk directory. That really should unpack into a apache-esme-1.0 directory or similar. I'll change this for the next release. 3) The version number in the pom is still 0.3.0-SNAPSHOT. Thus, if you build it, you get a snapshot war.Not a huge deal if we're not providing a binary war, but a bit unusual and unexpected. What would be better in the pom.xml: versionapache-esme-1.0/version? 4) Snapshot dependencies. It has dependencies on snapshots from Lift. Not good for a release as the release isn't really reproducible. Do you mean: lift.version1.1-SNAPSHOT/lift.version? I'll remember it for the next release. 5) Very minor suggestion: if you are Java 6 only, you could exclude things like activation.jar, xml-apis, and most likely xerces to make the war a little bit smaller.. We are hoping to be JDK 1.5 buildable again in the future (crossing our fingers...), so I wanted to leave these files in the release As far as the legal bits go, looks ok for a source release, so +1. Dan Thanks On Mon February 15 2010 10:05:43 am Richard Hirsch wrote: The ESME community has voted on and approved the release of ESME 1.0. We would now like to request the approval of the Incubator PMC for this release. Details of the ESME community vote can be found here: http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/201002.mbox/%3C fa2d9f451002120649u54cdd8b5red151033d655b...@mail.gmail.com%3e The candidate can be found at: http://people.apache.org/~rhirsch/esme/http://people.apache.org/%7Erhirsch/esme/ See the CHANGES.txt file for details on release contents. The release candidate is a tar archive of the sources in https://svn.apache.org/repos/asf/incubator/esme/tags/esme-1.0-incubating/ The MD5 checksum of the apache-esme-incubating-1.0- src.tar.gz release package is A4 9B 04 07 47 66 41 0C FE 01 2D 8B 5C 23 33 18 Please vote on releasing this package as Apache ESME 1.0-incubating. Please vote to publish this release by Thursday, Feb 18 16:03 CET, please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the ESME mailing list Thanks Dick --- Sender-time Sent at 4:00 PM (GMT+01:00). Current time there: 4:04 PM. ✆ toesme-...@incubator.apache.org date Mon, Feb 15, 2010 at 4:00 PM subject [VOTE][RESULT] ESME 1.0 mailed-by gmail.com Hello All, Voting on the ESME 1.0 candidate release has concluded Results: 6 binding +1 vote Dick Hirsch +1 Mrinal Wadhwa +1 Vassil Dichev +1 Ethan Jewett +1 Anne Kathrine Petteroe +1 Darren Hague +1 1 non-binding +1 votes Daniel Koller +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: [VOTE] Approve the release of apache-esme-incubating-1.0
Like I said - I'm seeing this first release as a learning experience (grin, grin) On Tue, Feb 16, 2010 at 5:28 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Mon, Feb 15, 2010 at 4:05 PM, Richard Hirsch hirsch.d...@gmail.com wrote: ...The candidate can be found at: http://people.apache.org/~rhirsch/esme/http://people.apache.org/%7Erhirsch/esme/ Unfortunately I'm -1 on the release, I have a few issues including a GPL dependency. 1) jwebunit dependency is GPL The server module depends on net.sourceforge.jwebunit:jwebunit-htmlunit-plugin:jar:1.4.1:test which according to http://jwebunit.sourceforge.net/license.html is GPL. I didn't check any maven dependencies, because they weren't part of SVN. 2) The sha1 digest does not match, did I do something wrong? $ openssl sha1 apache-esme-incubating-1.0-src.tar.gz SHA1(apache-esme-incubating-1.0-src.tar.gz)= a9ec8d95266d5944d493392a06eb1651c03222f1 $ cat apache-esme-incubating-1.0-src.tar.gz.sha apache-esme-incubating-1.0-src.tar.gz: A53494C8 55474CE3 5AC20516 C2448CB6 64B3B76C 747BA64A FFC9A836 EDAB8D86 4E0735CC AA29ACA9 07767C58 D1C0FEDA CA7E73A3 ADA3944D 464314B2 4BE0E476 I'm assuming I did something wrong. It was my first attempt at signing. I'll take another shot at it. 3) mvn dependency:analyze of the server module shows lots of unused declared dependencies, those should be cleaned up, especially openDMK:jdmkrt:jar which according to https://opendmk.dev.java.net/ is either GPL or CDDL license. Not sure which parts of OpenDMK are which license, but as it's unused better remove it. OK - I'll take a look at it. 4) When trying to build esme-java-client with mvn clean install I get Embedded error: Error while executing the external compiler if JAVA_HOME is not set. How can you deal with this via maven? Is this an ESME problem or a maven problem? 5) apache-esme-incubating-1.0-src.tar.gz contains .svn folders, it should not have that. You could have created the release using svn export of http://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-incubating/ to avoid that. OK. Didn't know that. 6) I couldn't find license information for the com.twitter:stats:jar:1.3:compile dependency, was that checked to be ok? Don't know - I'll have to check. This was from our JMX interface . Sorry that I didn't have time to look at that during the ESME podling vote. Apart from the GPL dependency the release preparation looks mostly ok, rat reports are good, license/notice are provided, etc. -Bertrand
[VOTE] Approve the release of apache-esme-incubating-1.0
The ESME community has voted on and approved the release of ESME 1.0. We would now like to request the approval of the Incubator PMC for this release. Details of the ESME community vote can be found here: http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/201002.mbox/%3cfa2d9f451002120649u54cdd8b5red151033d655b...@mail.gmail.com%3e The candidate can be found at: http://people.apache.org/~rhirsch/esme/ See the CHANGES.txt file for details on release contents. The release candidate is a tar archive of the sources in https://svn.apache.org/repos/asf/incubator/esme/tags/esme-1.0-incubating/ The MD5 checksum of the apache-esme-incubating-1.0- src.tar.gz release package is A4 9B 04 07 47 66 41 0C FE 01 2D 8B 5C 23 33 18 Please vote on releasing this package as Apache ESME 1.0-incubating. Please vote to publish this release by Thursday, Feb 18 16:03 CET, please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the ESME mailing list Thanks Dick --- Sender-time Sent at 4:00 PM (GMT+01:00). Current time there: 4:04 PM. ✆ to esme-...@incubator.apache.org dateMon, Feb 15, 2010 at 4:00 PM subject [VOTE][RESULT] ESME 1.0 mailed-by gmail.com Hello All, Voting on the ESME 1.0 candidate release has concluded Results: 6 binding +1 vote Dick Hirsch +1 Mrinal Wadhwa +1 Vassil Dichev +1 Ethan Jewett +1 Anne Kathrine Petteroe +1 Darren Hague +1 1 non-binding +1 votes Daniel Koller +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve the release of apache-esme-incubating-1.0
@Glen: Thanks for the tip. I've updated the README for the next release. D. On Mon, Feb 15, 2010 at 9:34 PM, Glen Daniels g...@thoughtcraft.com wrote: Seems to work fine, although you should perhaps make super-clear in the next version's README that you require JDK 1.6 (I was on 1.5 and had build problems). +1 from me for the release. Thanks, --Glen On 2/15/2010 10:05 AM, Richard Hirsch wrote: The ESME community has voted on and approved the release of ESME 1.0. We would now like to request the approval of the Incubator PMC for this release. Details of the ESME community vote can be found here: http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/201002.mbox/%3cfa2d9f451002120649u54cdd8b5red151033d655b...@mail.gmail.com%3e The candidate can be found at: http://people.apache.org/~rhirsch/esme/http://people.apache.org/%7Erhirsch/esme/ See the CHANGES.txt file for details on release contents. The release candidate is a tar archive of the sources in https://svn.apache.org/repos/asf/incubator/esme/tags/esme-1.0-incubating/ The MD5 checksum of the apache-esme-incubating-1.0- src.tar.gz release package is A4 9B 04 07 47 66 41 0C FE 01 2D 8B 5C 23 33 18 Please vote on releasing this package as Apache ESME 1.0-incubating. Please vote to publish this release by Thursday, Feb 18 16:03 CET, please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the ESME mailing list Thanks Dick --- Sender-time Sent at 4:00 PM (GMT+01:00). Current time there: 4:04 PM. ✆ toesme-...@incubator.apache.org date Mon, Feb 15, 2010 at 4:00 PM subject [VOTE][RESULT] ESME 1.0 mailed-by gmail.com Hello All, Voting on the ESME 1.0 candidate release has concluded Results: 6 binding +1 vote Dick Hirsch +1 Mrinal Wadhwa +1 Vassil Dichev +1 Ethan Jewett +1 Anne Kathrine Petteroe +1 Darren Hague +1 1 non-binding +1 votes Daniel Koller +1 - 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] Copyright issue (ESME-47)
Check his email from Tue, Jan 19, 2010 at 5:06 PM On Wed, Jan 20, 2010 at 1:02 PM, Santiago Gala santiago.g...@gmail.com wrote: Robert and Gianugo, did you mean to veto this with your -1s, or just express your disagreement with the majority? I might be thick or gmail buggy, but where is Gianugo's -1 ? I can't find it... Regards Santiago - 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
Was there a Confluence Update for Apache wiki
Hi, I just noticed today that some of the ESME content (RSS feeds, license warning for gliffy, etc).in the Apache wiki (http://cwiki.apache.org/confluence/display/ESME/Index) is now broken and was wondering if there has been recent change (new version, etc.). It was working on July 8th when I added a Gliffy diagram and today, I noticed that I'm receiving multiple warnings. Furthermore, the exported site (http://cwiki.apache.org/ESME/) is also broken. The tabs/cards are broken as well. I haven't changed our auto-export template, so I'm assuming that there has been some other external change in the wiki configuration. Thanks, D. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Was there a Confluence Update for Apache wiki
Looked at the test site (http://confluence-test.zones.apache.org:8080/display/ESME/Index) and the tabs are working there. Unfortunately, I couldn't find the exported site to see if the tabs are working there. @Don: Were the old export templates copied into the new configuration? In the old environment, I had to add a line to the template to get it the cards to work. Unfortunately, I didn't save what this code was :-. If possible could you send me a copy of our old export template. Since I don't have admin rights any more for the wiki, some nice admin is going to have to add the code to the new export template. Thanks. Dick On Sat, Jul 11, 2009 at 4:00 PM, Don Browndonald.br...@gmail.com wrote: I also have a full backup, in case one of your templates was lost, for some reason. Even if it wasn't, there are UI changes in this rather large upgrade of Confluence so you'll probably need tweaking regardless. Don On Sat, Jul 11, 2009 at 11:54 PM, Bertrand Delacretazbdelacre...@apache.org wrote: Hi Dick, On Sat, Jul 11, 2009 at 3:47 PM, Richard Hirschhirsch.d...@gmail.com wrote: ...I just noticed today that some of the ESME content (RSS feeds, license warning for gliffy, etc).in the Apache wiki (http://cwiki.apache.org/confluence/display/ESME/Index) is now broken and was wondering if there has been recent change (new version, etc.) Yes, Confluence was just updated, see https://blogs.apache.org/infra/entry/confluence_2_10_migration_for ...the exported site (http://cwiki.apache.org/ESME/) is also broken. The tabs/cards are broken as well. I haven't changed our auto-export template, so I'm assuming that there has been some other external change in the wiki configuration I guess the fix is to recreate the export template based on the new default one. I can hopefully have a look on Monday, unless someone beats me to it. Worst case, the default export template should give decent results. -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
Re: Was there a Confluence Update for Apache wiki
I looked at the old template and we need the following snippet (if I remember correctly...) at the end of the export template !-- Needed for composition plugin -- !-- delay the loading of large javascript files to the end so that they don't interfere with the loading of page content -- SPAN style=display: none SCRIPT type=text/javascript language=JavaScript src=http://cwiki.apache.org/confluence/labels-javascript;/SCRIPT /SPAN /body /html On Sat, Jul 11, 2009 at 4:27 PM, Don Browndonald.br...@gmail.com wrote: On Sun, Jul 12, 2009 at 12:18 AM, Richard Hirschhirsch.d...@gmail.com wrote: Looked at the test site (http://confluence-test.zones.apache.org:8080/display/ESME/Index) and the tabs are working there. Unfortunately, I couldn't find the exported site to see if the tabs are working there. The exported page is http://confluence-test.zones.apache.org:8080/export/ESME/index.html although it doesn't seem to be working. @Don: Were the old export templates copied into the new configuration? In the old environment, I had to add a line to the template to get it the cards to work. Unfortunately, I didn't save what this code was :-. If possible could you send me a copy of our old export template. I put all the old autoexport templates here: http://cwiki.apache.org/autoexport-2.2.9-templates/ Let me know if you need any more files. I'm heading to bed, but if you don't get a response on a wiki admin, try the infra list, irc channel, or general harassment of the incubator PMC :) Don Since I don't have admin rights any more for the wiki, some nice admin is going to have to add the code to the new export template. Thanks. Dick On Sat, Jul 11, 2009 at 4:00 PM, Don Browndonald.br...@gmail.com wrote: I also have a full backup, in case one of your templates was lost, for some reason. Even if it wasn't, there are UI changes in this rather large upgrade of Confluence so you'll probably need tweaking regardless. Don On Sat, Jul 11, 2009 at 11:54 PM, Bertrand Delacretazbdelacre...@apache.org wrote: Hi Dick, On Sat, Jul 11, 2009 at 3:47 PM, Richard Hirschhirsch.d...@gmail.com wrote: ...I just noticed today that some of the ESME content (RSS feeds, license warning for gliffy, etc).in the Apache wiki (http://cwiki.apache.org/confluence/display/ESME/Index) is now broken and was wondering if there has been recent change (new version, etc.) Yes, Confluence was just updated, see https://blogs.apache.org/infra/entry/confluence_2_10_migration_for ...the exported site (http://cwiki.apache.org/ESME/) is also broken. The tabs/cards are broken as well. I haven't changed our auto-export template, so I'm assuming that there has been some other external change in the wiki configuration I guess the fix is to recreate the export template based on the new default one. I can hopefully have a look on Monday, unless someone beats me to it. Worst case, the default export template should give decent results. -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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Was there a Confluence Update for Apache wiki
OK. I looked at our auto-export script and this snippet is still there. The problem still exists in our export and I'm assuming in other sites that use cards (such as OpenEJB) as well. Should I post a JIRA item? D. On Sat, Jul 11, 2009 at 5:00 PM, Richard Hirschhirsch.d...@gmail.com wrote: I looked at the old template and we need the following snippet (if I remember correctly...) at the end of the export template !-- Needed for composition plugin -- !-- delay the loading of large javascript files to the end so that they don't interfere with the loading of page content -- SPAN style=display: none SCRIPT type=text/javascript language=JavaScript src=http://cwiki.apache.org/confluence/labels-javascript;/SCRIPT /SPAN /body /html On Sat, Jul 11, 2009 at 4:27 PM, Don Browndonald.br...@gmail.com wrote: On Sun, Jul 12, 2009 at 12:18 AM, Richard Hirschhirsch.d...@gmail.com wrote: Looked at the test site (http://confluence-test.zones.apache.org:8080/display/ESME/Index) and the tabs are working there. Unfortunately, I couldn't find the exported site to see if the tabs are working there. The exported page is http://confluence-test.zones.apache.org:8080/export/ESME/index.html although it doesn't seem to be working. @Don: Were the old export templates copied into the new configuration? In the old environment, I had to add a line to the template to get it the cards to work. Unfortunately, I didn't save what this code was :-. If possible could you send me a copy of our old export template. I put all the old autoexport templates here: http://cwiki.apache.org/autoexport-2.2.9-templates/ Let me know if you need any more files. I'm heading to bed, but if you don't get a response on a wiki admin, try the infra list, irc channel, or general harassment of the incubator PMC :) Don Since I don't have admin rights any more for the wiki, some nice admin is going to have to add the code to the new export template. Thanks. Dick On Sat, Jul 11, 2009 at 4:00 PM, Don Browndonald.br...@gmail.com wrote: I also have a full backup, in case one of your templates was lost, for some reason. Even if it wasn't, there are UI changes in this rather large upgrade of Confluence so you'll probably need tweaking regardless. Don On Sat, Jul 11, 2009 at 11:54 PM, Bertrand Delacretazbdelacre...@apache.org wrote: Hi Dick, On Sat, Jul 11, 2009 at 3:47 PM, Richard Hirschhirsch.d...@gmail.com wrote: ...I just noticed today that some of the ESME content (RSS feeds, license warning for gliffy, etc).in the Apache wiki (http://cwiki.apache.org/confluence/display/ESME/Index) is now broken and was wondering if there has been recent change (new version, etc.) Yes, Confluence was just updated, see https://blogs.apache.org/infra/entry/confluence_2_10_migration_for ...the exported site (http://cwiki.apache.org/ESME/) is also broken. The tabs/cards are broken as well. I haven't changed our auto-export template, so I'm assuming that there has been some other external change in the wiki configuration I guess the fix is to recreate the export template based on the new default one. I can hopefully have a look on Monday, unless someone beats me to it. Worst case, the default export template should give decent results. -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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Suggestion regarding improvement of iCLA submission process
I like the idea of using JIRA to track the iCLA status. It is already possible to submit attachments with Jira items, so that would deal with submissions by email. For mailed and faxed submissions, I could imagine volunteers scanning these items, adding them to Jira and then mailing the submitter the link to Jira item. I'll move the discussion to legal-discuss and see what happens. D. On Thu, Apr 23, 2009 at 8:39 AM, Robert Burrell Donkin robertburrelldon...@gmail.com wrote: On Thu, Apr 23, 2009 at 7:16 AM, Richard Hirsch hirsch.d...@gmail.com wrote: The current CLA submission process is described here: http://www.apache.org/dev/committers.html#cla-registration I'd like to make a suggestion that emails be sent to people to submitting iCLAs so that they have idea of the status of their submission. I'd suggest sending emails when an iCLA has been received, when it has been acknowledged and finally when it has been registered. This would improve the process and avoid emails in the podling mailing lists asking about the status of individual iCLA submissions. I've just submitted an iCLA via email and I have no way to check its status besides looking at the Committers' page ( http://people.apache.org/~jim/committers.html) on a daily basis. Thanks. don't be so quick to thanks us ;-) the price of submitting ideas is being willing to actively help to make it happen :-) IMO asking the secretary to send more mails would just add more strain to our key volunteer infrastructure. so, the some means of automation would be needed. IMHO this means using JIRA to record and track these documents and the associated workflow. the easiest way to do this would be by finding a way to allow contributors to submit an iCLA via JIRA. AIUI the requirement for submission by fax, email or mail is a legal one, so the first step you need to take is to subscribe to legal-discuss and ask what steps apache needs to take to allow submission of iCLAs via JIRA. - robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Suggestion regarding improvement of iCLA submission process
I just posted the question to legal-discuss. Let's see what they say. D. On Thu, Apr 23, 2009 at 9:03 AM, Upayavira u...@odoko.co.uk wrote: I personally would just ask the secretary what he thinks - mail secret...@. He's responsible for managing this stuff, and it might be easy for him to automate sending mails. Dunno. Upayavira On Thu, 2009-04-23 at 08:56 +0200, Richard Hirsch wrote: I like the idea of using JIRA to track the iCLA status. It is already possible to submit attachments with Jira items, so that would deal with submissions by email. For mailed and faxed submissions, I could imagine volunteers scanning these items, adding them to Jira and then mailing the submitter the link to Jira item. I'll move the discussion to legal-discuss and see what happens. D. On Thu, Apr 23, 2009 at 8:39 AM, Robert Burrell Donkin robertburrelldon...@gmail.com wrote: On Thu, Apr 23, 2009 at 7:16 AM, Richard Hirsch hirsch.d...@gmail.com wrote: The current CLA submission process is described here: http://www.apache.org/dev/committers.html#cla-registration I'd like to make a suggestion that emails be sent to people to submitting iCLAs so that they have idea of the status of their submission. I'd suggest sending emails when an iCLA has been received, when it has been acknowledged and finally when it has been registered. This would improve the process and avoid emails in the podling mailing lists asking about the status of individual iCLA submissions. I've just submitted an iCLA via email and I have no way to check its status besides looking at the Committers' page ( http://people.apache.org/~jim/committers.html) on a daily basis. Thanks. don't be so quick to thanks us ;-) the price of submitting ideas is being willing to actively help to make it happen :-) IMO asking the secretary to send more mails would just add more strain to our key volunteer infrastructure. so, the some means of automation would be needed. IMHO this means using JIRA to record and track these documents and the associated workflow. the easiest way to do this would be by finding a way to allow contributors to submit an iCLA via JIRA. AIUI the requirement for submission by fax, email or mail is a legal one, so the first step you need to take is to subscribe to legal-discuss and ask what steps apache needs to take to allow submission of iCLAs via JIRA. - robert - 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
