[this interview is available online at https://s.apache.org/InsideInfra-Greg ] The third "Inside Infra" interview is with ASF Infrastructure Administrator Greg Stein, who shares his experience with Sally Khudairi, ASF VP Marketing & Publicity. --- "We've got about 200 different machines and each one runs something different" --- - What is your name --how is it pronounced? Greg Stein. "Gregg St-eye-n" - When people need to find you, are you at gstein@? Has that always been your handle for everything? Ever since high school, actually. I was gjs@ for a bit in college, but went back to gstein@. I started at Google early April 2004, and Gmail launched on April 1, so I was able to get my work email ID, gstein@gmail. So it’s great, but also rather annoying, because there are a lot of Gary Steins and Gertrude Steins and George Steins, and I get all of their email ... I get plane tickets, hotel reservations ... I got a proposal from the Gates Foundation once. I had some crazy bitter angry lady yelling at her husband as they were getting divorced, and she could rant. I mean, wow: that lady had a pirate's mouth. - But she didn't have his email address. Apparently not. - When and how did you get involved with the ASF? I left Microsoft in 1998, and the product group I was working in was building WebDAV into various Microsoft products. I thought the concept of WebDAV was very cool, and wanted the Open Source world to have it. That meant writing a module for the Apache Web Server. I think it was September 1998 when I started posting to the Apache mailing list and looking at how to plug in a WebDAV module. That was Apache 1.3 at the time. I developed a module called mod_dav for Apache 1.3, And when we started Apache 2.0 in 2000, I donated the module to Apache, and it became a standard module in Apache 2.0. - I remember that: I did the press release for that way back when. I knew you were connected with mod_dav, but didn't realize the path as to how you got there. It's very interesting. That's what brought me to Apache, when they started putting together the foundation: it was in the Spring of '99. I remember asking Roy if I could be one of the first members of the foundation, and Roy's answer was basically like, "We already had the set of people locked in. You'll probably get nominated and voted in at our first member meeting," which occurred in September 1999. So yes, I was in that first batch of new members rather than the original membership. - You've been a member of the ASF much longer than you've been involved with ASF Infra. What were the previous hats you were wearing at the ASF? You've been here for a while, and have had a lot of different configurations. This is true. So I'm a committer on HTTPd (Apache HTTP Server) and then a PMC Member, an ASF Member. I helped start the APR (Apache Portable Runtime) project with some of the other Web server committers, we pulled that out of HTTPd and created APR, and we used that for 2.0. We used APR, whereas Apache 1.3 was essentially the combination of the two, one big code base. Then Justin Erenkrantz and I started Apache Serf, and that was a high performance C-based client library for HTTP. But we didn't have three people in the community, so it couldn't really be an Apache project. So we took it out of Apache and started working on it on our own, and then eventually Subversion started to use Serf, and so we got more committers on Serf, and the community kind of built up around it because of Subversion. So we ran Serf externally, but just like it was an Apache community, it was Apache licensed and so on. Eventually we wanted to move it back into Apache, and I don't recall off hand, but we went straight to a TLP from our external project back to Apache Serf. Early 2000, it was January or February, (ASF co-Founder) Brian Behlendorf approached me about helping with the network protocol for this new version control system they were starting at CollabNet, because he knew my background in HTTP and WebDAV. That “V” stands for versioning. I got involved with the Subversion project that Spring. That was also run as a very egalitarian Open Source project, very similar to how we run stuff at Apache. I was really the only Apache person, but Karl Fogel just knows how to run a great community, and so all those values that we cherish in communities at Apache were part of Subversion from day one, but was run by CollabNet. I was hired in 2001 to manage their development team. Eventually, CollabNet wanted to turn it into a vendor-neutral thing that wasn't only CollabNet, so they started a small LLC called the Subversion Corporation. Once the IP was transferred to the Subversion Corporation, people said, "Okay, let's move to Apache," because nobody wanted to deal with the overhead of the Subversion Corporation. We approached Apache at the end of 2009, and Subversion became Apache Subversion. I was the first VP for
The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit 2.20.1. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release: Release Notes -- Apache Jackrabbit -- Version 2.20.1 Introduction This is Apache Jackrabbit(TM) 2.20.1, a fully compliant implementation of the Content Repository for Java(TM) Technology API, version 2.0 (JCR 2.0) as specified in the Java Specification Request 283 (JSR 283). Apache Jackrabbit 2.20.1 is an incremental feature release based on and compatible with earlier stable Jackrabbit 2.x releases. Jackrabbit 2.20.x releases are considered stable and targeted for production use. The minimum Java version for this release is Java 8. See http://jackrabbit.apache.org/jcr/downloads.html for maintenance versions that support earlier Java versions. Changes in Jackrabbit 2.20.1 Bug [JCR-3942] - Content-Length header field may be set twice [JCR-4549] - backup with RepositoryCopier.copy() fails on second method call [JCR-4551] - Use the normalized MediaType to check if the given MediaType should be indexed Improvement [JCR-4541] - reduce classpath lookups for SaxParserFactory Task [JCR-4519] - Update httpcore dependency to 4.4.13 [JCR-4520] - Update Jackrabbit trunk and 2.20 to Oak 1.22.0 [JCR-4522] - Update httpclient/mime dependencies to 4.5.11 [JCR-4525] - Update Jackrabbit trunk and 2.20 to Oak 1.24.0 [JCR-4529] - Update tomcat dependency to 8.5.50 [JCR-4530] - jackrabbit-core: avoid use of deprecated commons-collections Buffers [JCR-4531] - Update tomcat dependency to 8.5.51/7.0.100 [JCR-4539] - Update Jackrabbit trunk and 2.20 to Oak 1.26.0 [JCR-4543] - Update Tika dependency to 1.24 [JCR-4544] - Update slf4j dependency to 1.7.30 [JCR-4545] - Update httpclient/mime dependencies to 4.5.12 [JCR-4546] - Update aws java sdk version to 1.11.700 (consistent with Oak) [JCR-4547] - Update tomcat dependency to 8.5.53/7.0.103 [JCR-4548] - update javadoc-plugin dependency to 3.2.0 [JCR-4554] - Update Tika dependency to 1.24.1 [JCR-4555] - Update mockito dependency to 3.3.3 [JCR-4556] - Update tomcat dependency to 8.5.54 [JCR-4557] - update junit dependency to 4.13 [JCR-4558] - update Apache parent pom to version 23 [JCR-4559] - Update commons file-upload dependency to 1.4 [JCR-4560] - Update h2db dependency to 1.4.200 [JCR-4561] - webapp: update htmlunit dependency to 2.40.0 [JCR-4562] - Remove workaround for FELIX-2492 [JCR-4563] - test OSGi bundles [JCR-4564] - jackrabbit-jcr-server: remove obsolete workaround for scr-plugin [JCR-4575] - Update tomcat dependency to 8.5.55/7.0.104 For more detailed information about all the changes in this and other Jackrabbit releases, please see the Jackrabbit issue tracker at https://issues.apache.org/jira/browse/JCR Release Contents This release consists of a single source archive packaged as a zip file. The archive can be unpacked with the jar tool from your JDK installation. See the README.txt file for instructions on how to build this release. The source archive is accompanied by an SHA512 checksum and a PGP signature that you can use to verify the authenticity of your download. The public key used for the PGP signature can be found at https://www.apache.org/dist/jackrabbit/KEYS. About Apache Jackrabbit --- Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR). A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more. For more information, visit http://jackrabbit.apache.org/ About The Apache Software Foundation Established in 1999, The Apache Software Foundation provides organizational, legal, and financial support for more than 140 freely-available, collaboratively-developed Open Source projects. The pragmatic Apache License enables individual and commercial users to easily deploy Apache software; the Foundation's intellectual property framework limits the legal exposure of its 3,800+ contributors. For more information, visit http://www.apache.org/ Trademarks -- Apache Jackrabbit, Jackrabbit, Apache, the Apache feather logo, and the Apache Jackrabbit project logo are trademarks of The Apache Software Foundation.
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid JMS 0.52.0. This is the latest release of our newer JMS client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid Proton protocol engine and implementing the AMQP JMS Mapping as it evolves at OASIS. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via Maven Central: http://qpid.apache.org/maven.html Release notes can be found at: http://qpid.apache.org/releases/qpid-jms-0.52.0/release-notes.html Thanks to all involved, Robbie