Re: [Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
This still only has 3 committers. How is the project going to function with such a small group? I don't see that there has been a realistic answer to this question. On Fri, Jan 9, 2015 at 10:35 AM, Marko Rodriguez okramma...@gmail.com wrote: Hello everyone, Over the last 2 weeks, TinkerPop's proposal has been worked on with support from: * David Nalley (champion) * Rich Bowen (mentor) * Hadrian Zbarcea (mentor) * Daniel Gruno (mentor) * Marko Rodriguez (submitting on behalf of TinkerPop) We feel it is now in prime shape from submission to vote. Enjoy!. (URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal) A. Abstract TinkerPop http://tinkerpop.com/ is a graph computing framework written in Java. A graph http://en.wikipedia.org/wiki/Graph_%28mathematics%29 is a data structure composed of vertices and edges and is useful for modeling complex domains with arbitrary relations (edges, links, lines) between entities (vertices, objects, dots). TinkerPop https://wiki.apache.org/incubator/TinkerPop provides a core API that graph system vendors can implement. There are various types of graph systems including in-memory graph libraries, OLTP graph databases, and OLAP graph processors (see On Graph Computing http://markorodriguez.com/2013/01/09/on-graph-computing/ for more information). Once the core interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin and processed withTinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled algorithms. For many, TinkerPop https://wiki.apache.org/incubator/TinkerPop is seen as the JDBC http://en.wikipedia.org/wiki/Java_Database_Connectivity of the graph computing community. B. Proposal TinkerPop https://wiki.apache.org/incubator/TinkerPop was formed in 2009 and is currently in the milestone series of 3.0.0. From the start, TinkerPop https://wiki.apache.org/incubator/TinkerPop has provided its software open source and free to use for which ever reason (commercial or otherwise). Initially the license was BSD, but as of TinkerPop3 https://wiki.apache.org/incubator/TinkerPop3, the license was changed to Apache2. The TinkerPop https://wiki.apache.org/incubator/TinkerPop team is composed of developers, evangelists, and representatives from graph system vendors (see TinkerPop Contributors http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors for more information). TinkerPop https://wiki.apache.org/incubator/TinkerPop has done its best to remain vendor agnostic and works closely with all vendors to ensure that the constructs within TinkerPop https://wiki.apache.org/incubator/TinkerPop are able to accommodate the requirements of the underlying graph system. To date, 12 TinkerPop https://wiki.apache.org/incubator/TinkerPop recognized graph system vendors provide TinkerPop https://wiki.apache.org/incubator/TinkerPop implementations. We believe that by joining The Apache Software Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. C. Background TinkerPop https://wiki.apache.org/incubator/TinkerPop has had steady, active development since 2009 when it was founded. Over the years, the Gremlin query language within TinkerPop https://wiki.apache.org/incubator/TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript https://wiki.apache.org/incubator/JavaScript, and the like. In many ways, Gremlin is seen as a traversal style that can be readily adopted within the programming constructs of the developer's native language --- both on and off the JVM. TinkerPop https://wiki.apache.org/incubator/TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop https://wiki.apache.org/incubator/TinkerPop is being used is production graph-based applications around the world and is only getting better with age. D. Rationale The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop https://wiki.apache.org/incubator/TinkerPop was created as a unifying framework for interoperability, language standardization, and data model standardization. This framework makes it simple to plug and play the back-end graph implementation without affecting the developer's code. This is analogous to the way in which the JDBC allows users to swap relational databases while keeping the same programming interface. TinkerPop https://wiki.apache.org/incubator/TinkerPop also brings together OLTP systems (graph databases) and OLAP systems (graph
Re: [Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
On 10 Jan 2015, at 6:18 am, Ted Dunning ted.dunn...@gmail.com wrote: This still only has 3 committers. How is the project going to function with such a small group? I don't see that there has been a realistic answer to this question. It is part of the incubation process to help gain more, and again as a tlp, an ongoing process. Lots of TLPs have more committers, with only one or two actually active. Gav… On Fri, Jan 9, 2015 at 10:35 AM, Marko Rodriguez okramma...@gmail.com mailto:okramma...@gmail.com wrote: Hello everyone, Over the last 2 weeks, TinkerPop's proposal has been worked on with support from: * David Nalley (champion) * Rich Bowen (mentor) * Hadrian Zbarcea (mentor) * Daniel Gruno (mentor) * Marko Rodriguez (submitting on behalf of TinkerPop) We feel it is now in prime shape from submission to vote. Enjoy!. (URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal https://wiki.apache.org/incubator/TinkerPopProposal) A. Abstract TinkerPop http://tinkerpop.com/ is a graph computing framework written in Java. A graph http://en.wikipedia.org/wiki/Graph_%28mathematics%29 is a data structure composed of vertices and edges and is useful for modeling complex domains with arbitrary relations (edges, links, lines) between entities (vertices, objects, dots). TinkerPop https://wiki.apache.org/incubator/TinkerPop provides a core API that graph system vendors can implement. There are various types of graph systems including in-memory graph libraries, OLTP graph databases, and OLAP graph processors (see On Graph Computing http://markorodriguez.com/2013/01/09/on-graph-computing/ for more information). Once the core interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin and processed withTinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled algorithms. For many, TinkerPop https://wiki.apache.org/incubator/TinkerPop is seen as the JDBC http://en.wikipedia.org/wiki/Java_Database_Connectivity of the graph computing community. B. Proposal TinkerPop https://wiki.apache.org/incubator/TinkerPop was formed in 2009 and is currently in the milestone series of 3.0.0. From the start, TinkerPop https://wiki.apache.org/incubator/TinkerPop has provided its software open source and free to use for which ever reason (commercial or otherwise). Initially the license was BSD, but as of TinkerPop3 https://wiki.apache.org/incubator/TinkerPop3, the license was changed to Apache2. The TinkerPop https://wiki.apache.org/incubator/TinkerPop team is composed of developers, evangelists, and representatives from graph system vendors (see TinkerPop Contributors http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors for more information). TinkerPop https://wiki.apache.org/incubator/TinkerPop has done its best to remain vendor agnostic and works closely with all vendors to ensure that the constructs within TinkerPop https://wiki.apache.org/incubator/TinkerPop are able to accommodate the requirements of the underlying graph system. To date, 12 TinkerPop https://wiki.apache.org/incubator/TinkerPop recognized graph system vendors provide TinkerPop https://wiki.apache.org/incubator/TinkerPop implementations. We believe that by joining The Apache Software Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. C. Background TinkerPop https://wiki.apache.org/incubator/TinkerPop has had steady, active development since 2009 when it was founded. Over the years, the Gremlin query language within TinkerPop https://wiki.apache.org/incubator/TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript https://wiki.apache.org/incubator/JavaScript, and the like. In many ways, Gremlin is seen as a traversal style that can be readily adopted within the programming constructs of the developer's native language --- both on and off the JVM. TinkerPop https://wiki.apache.org/incubator/TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop https://wiki.apache.org/incubator/TinkerPop is being used is production graph-based applications around the world and is only getting better with age. D. Rationale The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop https://wiki.apache.org/incubator/TinkerPop was created as a unifying framework for
Re: [VOTE][Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
+1 binding Regards, Alan On Jan 9, 2015, at 8:58 AM, Hadrian Zbarcea hzbar...@gmail.com wrote: +1 From the conversation with Marko, he intended to submit this as a formal vote, but didn't use the regular voting template. Voting will remain open until at least January 15, 2015 18:00 ET. Cheers, Hadrian On 01/09/2015 11:35 AM, Marko Rodriguez wrote: Hello everyone, Over the last 2 weeks, TinkerPop's proposal has been worked on with support from: * David Nalley (champion) * Rich Bowen (mentor) * Hadrian Zbarcea (mentor) * Daniel Gruno (mentor) * Marko Rodriguez (submitting on behalf of TinkerPop) We feel it is now in prime shape from submission to vote. Enjoy!. (URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal) A. Abstract TinkerPop http://tinkerpop.com/ is a graph computing framework written in Java. A graph http://en.wikipedia.org/wiki/Graph_%28mathematics%29 is a data structure composed of vertices and edges and is useful for modeling complex domains with arbitrary relations (edges, links, lines) between entities (vertices, objects, dots). TinkerPop https://wiki.apache.org/incubator/TinkerPop provides a core API that graph system vendors can implement. There are various types of graph systems including in-memory graph libraries, OLTP graph databases, and OLAP graph processors (see On Graph Computing http://markorodriguez.com/2013/01/09/on-graph-computing/ for more information). Once the core interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin and processed withTinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled algorithms. For many, TinkerPop https://wiki.apache.org/incubator/TinkerPop is seen as the JDBC http://en.wikipedia.org/wiki/Java_Database_Connectivity of the graph computing community. B. Proposal TinkerPop https://wiki.apache.org/incubator/TinkerPop was formed in 2009 and is currently in the milestone series of 3.0.0. From the start, TinkerPop https://wiki.apache.org/incubator/TinkerPop has provided its software open source and free to use for which ever reason (commercial or otherwise). Initially the license was BSD, but as of TinkerPop3 https://wiki.apache.org/incubator/TinkerPop3, the license was changed to Apache2. The TinkerPop https://wiki.apache.org/incubator/TinkerPop team is composed of developers, evangelists, and representatives from graph system vendors (see TinkerPop Contributors http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors for more information). TinkerPop https://wiki.apache.org/incubator/TinkerPop has done its best to remain vendor agnostic and works closely with all vendors to ensure that the constructs within TinkerPop https://wiki.apache.org/incubator/TinkerPop are able to accommodate the requirements of the underlying graph system. To date, 12 TinkerPop https://wiki.apache.org/incubator/TinkerPop recognized graph system vendors provide TinkerPop https://wiki.apache.org/incubator/TinkerPop implementations. We believe that by joining The Apache Software Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. C. Background TinkerPop https://wiki.apache.org/incubator/TinkerPop has had steady, active development since 2009 when it was founded. Over the years, the Gremlin query language within TinkerPop https://wiki.apache.org/incubator/TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript https://wiki.apache.org/incubator/JavaScript, and the like. In many ways, Gremlin is seen as a traversal style that can be readily adopted within the programming constructs of the developer's native language --- both on and off the JVM. TinkerPop https://wiki.apache.org/incubator/TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop https://wiki.apache.org/incubator/TinkerPop is being used is production graph-based applications around the world and is only getting better with age. D. Rationale The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop https://wiki.apache.org/incubator/TinkerPop was created as a unifying framework for interoperability, language standardization, and data model standardization. This framework makes it simple to plug and play the back-end graph implementation without affecting the developer's code. This is analogous to the way in which the JDBC allows
Re: [Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
+0 then On Sat, Jan 10, 2015 at 1:18 AM, Gavin McDonald ga...@16degrees.com.au wrote: On 10 Jan 2015, at 6:18 am, Ted Dunning ted.dunn...@gmail.com wrote: This still only has 3 committers. How is the project going to function with such a small group? I don't see that there has been a realistic answer to this question. It is part of the incubation process to help gain more, and again as a tlp, an ongoing process. Lots of TLPs have more committers, with only one or two actually active. Gav… On Fri, Jan 9, 2015 at 10:35 AM, Marko Rodriguez okramma...@gmail.com mailto:okramma...@gmail.com wrote: Hello everyone, Over the last 2 weeks, TinkerPop's proposal has been worked on with support from: * David Nalley (champion) * Rich Bowen (mentor) * Hadrian Zbarcea (mentor) * Daniel Gruno (mentor) * Marko Rodriguez (submitting on behalf of TinkerPop) We feel it is now in prime shape from submission to vote. Enjoy!. (URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal https://wiki.apache.org/incubator/TinkerPopProposal) A. Abstract TinkerPop http://tinkerpop.com/ is a graph computing framework written in Java. A graph http://en.wikipedia.org/wiki/Graph_%28mathematics%29 is a data structure composed of vertices and edges and is useful for modeling complex domains with arbitrary relations (edges, links, lines) between entities (vertices, objects, dots). TinkerPop https://wiki.apache.org/incubator/TinkerPop provides a core API that graph system vendors can implement. There are various types of graph systems including in-memory graph libraries, OLTP graph databases, and OLAP graph processors (see On Graph Computing http://markorodriguez.com/2013/01/09/on-graph-computing/ for more information). Once the core interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin and processed withTinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled algorithms. For many, TinkerPop https://wiki.apache.org/incubator/TinkerPop is seen as the JDBC http://en.wikipedia.org/wiki/Java_Database_Connectivity of the graph computing community. B. Proposal TinkerPop https://wiki.apache.org/incubator/TinkerPop was formed in 2009 and is currently in the milestone series of 3.0.0. From the start, TinkerPop https://wiki.apache.org/incubator/TinkerPop has provided its software open source and free to use for which ever reason (commercial or otherwise). Initially the license was BSD, but as of TinkerPop3 https://wiki.apache.org/incubator/TinkerPop3, the license was changed to Apache2. The TinkerPop https://wiki.apache.org/incubator/TinkerPop team is composed of developers, evangelists, and representatives from graph system vendors (see TinkerPop Contributors http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors for more information). TinkerPop https://wiki.apache.org/incubator/TinkerPop has done its best to remain vendor agnostic and works closely with all vendors to ensure that the constructs within TinkerPop https://wiki.apache.org/incubator/TinkerPop are able to accommodate the requirements of the underlying graph system. To date, 12 TinkerPop https://wiki.apache.org/incubator/TinkerPop recognized graph system vendors provide TinkerPop https://wiki.apache.org/incubator/TinkerPop implementations. We believe that by joining The Apache Software Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. C. Background TinkerPop https://wiki.apache.org/incubator/TinkerPop has had steady, active development since 2009 when it was founded. Over the years, the Gremlin query language within TinkerPop https://wiki.apache.org/incubator/TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript https://wiki.apache.org/incubator/JavaScript, and the like. In many ways, Gremlin is seen as a traversal style that can be readily adopted within the programming constructs of the developer's native language --- both on and off the JVM. TinkerPop https://wiki.apache.org/incubator/TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop https://wiki.apache.org/incubator/TinkerPop is being used is production graph-based applications around the world and is only getting better with age. D. Rationale The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop
Re: What is The Apache Way?
The temperature of this might be reduced by replacing, 'no one knows what the Apache Way is' with 'a lot of us have trouble translate it into practical decisions in a repeatable fashion.' Or not. As reported here, we have performed multiple experiments in which multiple members, directors, and others have derived conflicting _practical_ interpretations from 'the way.' People need to make practical decisions about releases, web sites, brands, and the like. People don't enjoy being told that they have 'trangresssed'. People particularly don't like this when their trangression was an action recommended by someone who is 'supposed to know,' and, in fact, thinks that she or he does know. So, either a lot of us are really stupid, or the Foundation as a whole has a gap between the general principles and their application. No, we can't have a rule book that details every particle of how to run an Apache project, but apparently we could have more concrete guidance. On Fri, Jan 9, 2015 at 10:30 AM, Jim Jagielski j...@jagunet.com wrote: Please tell me where the examples you give diverge or conflict? On Jan 9, 2015, at 10:20 AM, Marvin Humphrey mar...@rectangular.com wrote: On Fri, Jan 9, 2015 at 6:58 AM, Jim Jagielski j...@jagunet.com wrote: And I think that someone who is an ASF member who claims that the Apache Way is completely unknown and nebulous and that there is no clear understanding of what the Apache Way is, well I think that's a big problem as well. We've seen Brane's version of The Apache Way. Here are some others: https://www.apache.org/foundation/how-it-works.html#philosophy While there is not an official list, these six principles have been cited as the core beliefs of philosophy behind the foundation, which is normally referred to as The Apache Way: * collaborative software development * commercial-friendly standard license * consistently high quality software * respectful, honest, technical-based interaction * faithful implementation of standards * security as a mandatory feature http://communityovercode.com/2013/11/apache-governance-projects-first/ These include things like The Apache Way of: volunteer and collaborative led community built software projects; using the permissive Apache license; and having a consistent and stable brand, infrastructure services, and home for all Apache projects. http://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg * Open Development vs. Open Source * Everyone is equal, everyone is a volunteer * All technical decisions about a project are public * She who has the best ideas leads * Until a better idea emerges http://theapacheway.com/ The Apache Way is sort of like Zen. It's something that's difficult to explain, has many interpretations, and the best way to learn it is to do it. The Incubator stands accused, on this list and others, of graduating pudlings who fail to understand the Apache Way. Like me, these podlings have an their own interpretation of the Apache Way. But we don't know, and can't know, every possible interpretation of The Apache Way. If the Board thinks that not knowing The Apache Way is a problem, give us a specific definition -- and then don't hold us accountable for knowledge of any other version. Marvin Humphrey - 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: What is The Apache Way?
Maybe it's about perception. Most organisations have a culture that has at least some degree of interpretation. If you want something clear cut and defined in such a way as to have no scope for interpretation you lose flexibility. Even the law gets interpretation. So perhaps its just a matter of understanding that individuals will have different perceptions of what clear expectations mean. Maybe not such a deep dysfunction as an inevitable one that is common to some degree in all orgs? On 9 January 2015 at 15:01, Jim Jagielski j...@jagunet.com wrote: And fwiw, maybe the reason directors are chosen to represent members is because they *do* understand what the Apache Way is... Personally, I'm shocked, saddened and disappointed that this conversation is even happening, since it really clearly shows the depth of the dysfunction. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ian Ofqual Accredited Qualifications https://theingots.org/community/index.php?q=qualifications Headline points in the 2014, 2015, 2016 school league tables Baseline testing and progress measures https://theingots.org/community/Baseline_testing_info The Learning Machine Limited, Reg Office, Unit 4D Gagarin, Lichfield Road Industrial Estate, Tamworth, Staffordshire, B79 7GN. Reg No: 05560797, Registered in England and Wales. +44 (0)1827 305940
Re: What is The Apache Way?
On Fri, Jan 9, 2015 at 6:58 AM, Jim Jagielski j...@jagunet.com wrote: And I think that someone who is an ASF member who claims that the Apache Way is completely unknown and nebulous and that there is no clear understanding of what the Apache Way is, well I think that's a big problem as well. We've seen Brane's version of The Apache Way. Here are some others: https://www.apache.org/foundation/how-it-works.html#philosophy While there is not an official list, these six principles have been cited as the core beliefs of philosophy behind the foundation, which is normally referred to as The Apache Way: * collaborative software development * commercial-friendly standard license * consistently high quality software * respectful, honest, technical-based interaction * faithful implementation of standards * security as a mandatory feature http://communityovercode.com/2013/11/apache-governance-projects-first/ These include things like The Apache Way of: volunteer and collaborative led community built software projects; using the permissive Apache license; and having a consistent and stable brand, infrastructure services, and home for all Apache projects. http://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg * Open Development vs. Open Source * Everyone is equal, everyone is a volunteer * All technical decisions about a project are public * She who has the best ideas leads * Until a better idea emerges http://theapacheway.com/ The Apache Way is sort of like Zen. It's something that's difficult to explain, has many interpretations, and the best way to learn it is to do it. The Incubator stands accused, on this list and others, of graduating pudlings who fail to understand the Apache Way. Like me, these podlings have an their own interpretation of the Apache Way. But we don't know, and can't know, every possible interpretation of The Apache Way. If the Board thinks that not knowing The Apache Way is a problem, give us a specific definition -- and then don't hold us accountable for knowledge of any other version. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
Please tell me where the examples you give diverge or conflict? On Jan 9, 2015, at 10:20 AM, Marvin Humphrey mar...@rectangular.com wrote: On Fri, Jan 9, 2015 at 6:58 AM, Jim Jagielski j...@jagunet.com wrote: And I think that someone who is an ASF member who claims that the Apache Way is completely unknown and nebulous and that there is no clear understanding of what the Apache Way is, well I think that's a big problem as well. We've seen Brane's version of The Apache Way. Here are some others: https://www.apache.org/foundation/how-it-works.html#philosophy While there is not an official list, these six principles have been cited as the core beliefs of philosophy behind the foundation, which is normally referred to as The Apache Way: * collaborative software development * commercial-friendly standard license * consistently high quality software * respectful, honest, technical-based interaction * faithful implementation of standards * security as a mandatory feature http://communityovercode.com/2013/11/apache-governance-projects-first/ These include things like The Apache Way of: volunteer and collaborative led community built software projects; using the permissive Apache license; and having a consistent and stable brand, infrastructure services, and home for all Apache projects. http://www.slideshare.net/rgardler/the-apache-way-and-openofficeorg * Open Development vs. Open Source * Everyone is equal, everyone is a volunteer * All technical decisions about a project are public * She who has the best ideas leads * Until a better idea emerges http://theapacheway.com/ The Apache Way is sort of like Zen. It's something that's difficult to explain, has many interpretations, and the best way to learn it is to do it. The Incubator stands accused, on this list and others, of graduating pudlings who fail to understand the Apache Way. Like me, these podlings have an their own interpretation of the Apache Way. But we don't know, and can't know, every possible interpretation of The Apache Way. If the Board thinks that not knowing The Apache Way is a problem, give us a specific definition -- and then don't hold us accountable for knowledge of any other version. Marvin Humphrey - 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 Streams 0.1-incubating
-1 (binding) Besides the findings already reported by Justin Mclean in addition I noticed: - binary artifacts, including the -sources and -javadoc jars, do not contain the required DISCLAIMER file alongside the NOTICE and LICENSE files I also encountered build test failures. For the next release candidate I strongly suggest to provide at least a basic getting started either online or with the source because for outsiders it is totally unclear how to use Streams or even what it does ... Regards, Ate For the IPMC: I'm a mentor on Streams but was on holiday when this vote ran on the streams-dev list. On 2014-12-21 23:06, Steve Blackmon wrote: This is the first incubator release for Apache Streams, with the artifacts being versioned as 0.1-incubating. We are requesting at least two additional IPMC member votes, as we have received 1 binding IPMC +1 vote during the release voting on streams-dev. VOTE: http://markmail.org/thread/kbgr73ndhztwybsh RESULT: http://markmail.org/thread/fz53tiiqnadwyagg IPMC member votes from the streams-dev list: Matthew Franklin: +1 Git tag streams-project-0.1-incubating-rc1 (commit 8e561d6) https://git-wip-us.apache.org/repos/asf?p=incubator-streams.git;a=commit;h=8e561d60bae3fb74baad05ed5a0d1be6631ceab1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachestreams-1000 Source release: http://repository.apache.org/content/repositories/orgapachestreams-1000/org/apache/streams/streams-project/0.1-incubating/streams-project-0.1-incubating-source-release.zip Release artifacts are signed with the following key: https://people.apache.org/keys/committer/sblackmon.asc Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Steve Blackmon sblack...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: proposal: mentor re-boot
On Fri, Jan 9, 2015 at 3:31 AM, Dave Fisher dave2w...@comcast.net wrote: ...I think the IPMC is doing almost all of the above better. Everything except for Failed. I think that now we are blaming the mentor. Let's get over it. Not every podling will work That's distinct concerns IMO: some podlings are failing and no mentor can save them, but there are also podlings that would be doing better if they had sufficiently active mentors. Also, from the point of view of oversight, the IPMC needs a way to find out how podlings are doing, and that's delegated to mentors. Failing that, poor IPMC volunteers have to step up and that gets boring over time. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
Enthusiastically +1 to welcome TinkerPop to the Incubator. On 01/09/2015 11:35 AM, Marko Rodriguez wrote: Hello everyone, Over the last 2 weeks, TinkerPop's proposal has been worked on with support from: * David Nalley (champion) * Rich Bowen (mentor) * Hadrian Zbarcea (mentor) * Daniel Gruno (mentor) * Marko Rodriguez (submitting on behalf of TinkerPop) We feel it is now in prime shape from submission to vote. Enjoy!. (URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal) A. Abstract TinkerPop http://tinkerpop.com/ is a graph computing framework written in Java. A graph http://en.wikipedia.org/wiki/Graph_%28mathematics%29 is a data structure composed of vertices and edges and is useful for modeling complex domains with arbitrary relations (edges, links, lines) between entities (vertices, objects, dots). TinkerPop https://wiki.apache.org/incubator/TinkerPop provides a core API that graph system vendors can implement. There are various types of graph systems including in-memory graph libraries, OLTP graph databases, and OLAP graph processors (see On Graph Computing http://markorodriguez.com/2013/01/09/on-graph-computing/ for more information). Once the core interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin and processed withTinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled algorithms. For many, TinkerPop https://wiki.apache.org/incubator/TinkerPop is seen as the JDBC http://en.wikipedia.org/wiki/Java_Database_Connectivity of the graph computing community. B. Proposal TinkerPop https://wiki.apache.org/incubator/TinkerPop was formed in 2009 and is currently in the milestone series of 3.0.0. From the start, TinkerPop https://wiki.apache.org/incubator/TinkerPop has provided its software open source and free to use for which ever reason (commercial or otherwise). Initially the license was BSD, but as of TinkerPop3 https://wiki.apache.org/incubator/TinkerPop3, the license was changed to Apache2. The TinkerPop https://wiki.apache.org/incubator/TinkerPop team is composed of developers, evangelists, and representatives from graph system vendors (see TinkerPop Contributors http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors for more information). TinkerPop https://wiki.apache.org/incubator/TinkerPop has done its best to remain vendor agnostic and works closely with all vendors to ensure that the constructs within TinkerPop https://wiki.apache.org/incubator/TinkerPop are able to accommodate the requirements of the underlying graph system. To date, 12 TinkerPop https://wiki.apache.org/incubator/TinkerPop recognized graph system vendors provide TinkerPop https://wiki.apache.org/incubator/TinkerPop implementations. We believe that by joining The Apache Software Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. C. Background TinkerPop https://wiki.apache.org/incubator/TinkerPop has had steady, active development since 2009 when it was founded. Over the years, the Gremlin query language within TinkerPop https://wiki.apache.org/incubator/TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript https://wiki.apache.org/incubator/JavaScript, and the like. In many ways, Gremlin is seen as a traversal style that can be readily adopted within the programming constructs of the developer's native language --- both on and off the JVM. TinkerPop https://wiki.apache.org/incubator/TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop https://wiki.apache.org/incubator/TinkerPop is being used is production graph-based applications around the world and is only getting better with age. D. Rationale The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop https://wiki.apache.org/incubator/TinkerPop was created as a unifying framework for interoperability, language standardization, and data model standardization. This framework makes it simple to plug and play the back-end graph implementation without affecting the developer's code. This is analogous to the way in which the JDBC allows users to swap relational databases while keeping the same programming interface. TinkerPop https://wiki.apache.org/incubator/TinkerPop also brings together OLTP systems (graph databases) and OLAP systems (graph processors) by providing a single query language (Gremlin) for executing graph algorithms transparently over either type of system. The seamless support of single-machine systems and distributed
Re: What is The Apache Way?
+1 Doug. -Original Message- From: Doug Cutting cutt...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Friday, January 9, 2015 at 9:05 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: What is The Apache Way? On Fri, Jan 9, 2015 at 8:12 AM, Benson Margulies bimargul...@gmail.com wrote: So, either a lot of us are really stupid, or the Foundation as a whole has a gap between the general principles and their application. No, we can't have a rule book that details every particle of how to run an Apache project, but apparently we could have more concrete guidance. The gap definitely exists. What often leads to confusion is when folks think there's no gap, that everything is clear-cut and certain, when it's not. Different Apache projects are permitted to operate differently, and the ill-defined line of what's acceptable moves over time. This is not entirely bad. Fixed practices are hard to change, but the open-source software world changes rapidly. So maintaining some flexibility is important. What we should try to do are document acceptable practices, those ways of operating that are common in many projects and have worked well. There may be multiple acceptable practices in a given area (e.g., CTR RTC). Projects that diverge from these might still be acceptable, but they might also run into problems and should proceed with caution. Some might tell them that they don't get the Apache Way, which is distressing, but, at the end of the day, so long as the board doesn't vote to evict them from the foundation, they're part of the Apache Way. The board doesn't generally act without good notice. Generally things escalate from folks griping, to the board agreeing to monitor and advise a project, to the board giving an ultimatum for a specific practice to stop, to the board finally taking some action. Doug - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
On Fri, Jan 9, 2015 at 9:41 AM, David Nalley da...@gnsa.us wrote: Can a project use an external bug tracker? Can a project use a third-parties CI system? Can a project host their website outside of the ASF? Can a project avoid a users mailing list and move to StackOverflow? Can projects use github? It depends on the details. Many are not recommended practices. A project is likely to get more flak if it takes such paths rather than more standard paths, e.g., folks declaring that it's absolutely not allowed. Some of these may someday be recommended practices if projects persevere and show how they can be done without violating the spirit of Apache-style software development. The board may ask for more details when a project takes uncommon paths in order to gain comfort that Apache needs are met. Doug - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: What is The Apache Way?
+1, I'll repeat one a little my previous mail and say patches welcome (as long as they keep the document simple - remember, it's a signpost document not a discussion or detail document - the discussion/detail documents should be linked from this one). http://community.apache.org/projectIndependence.html this document starts with While not all aspects of the Apache Way are practiced the same way by all projects at the ASF, there are a number of rules and policies that Apache projects are required to follow – things like complying with PMC release voting, legal policy, brand policy, using mailing lists, etc., which are documented in various places. (note the second sentence has 5 links, the rest of the document has some explanatory text and copious links). Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: Doug Cutting [mailto:cutt...@apache.org] Sent: Friday, January 9, 2015 9:05 AM To: general@incubator.apache.org Subject: Re: What is The Apache Way? On Fri, Jan 9, 2015 at 8:12 AM, Benson Margulies bimargul...@gmail.com wrote: So, either a lot of us are really stupid, or the Foundation as a whole has a gap between the general principles and their application. No, we can't have a rule book that details every particle of how to run an Apache project, but apparently we could have more concrete guidance. The gap definitely exists. What often leads to confusion is when folks think there's no gap, that everything is clear-cut and certain, when it's not. Different Apache projects are permitted to operate differently, and the ill-defined line of what's acceptable moves over time. This is not entirely bad. Fixed practices are hard to change, but the open-source software world changes rapidly. So maintaining some flexibility is important. What we should try to do are document acceptable practices, those ways of operating that are common in many projects and have worked well. There may be multiple acceptable practices in a given area (e.g., CTR RTC). Projects that diverge from these might still be acceptable, but they might also run into problems and should proceed with caution. Some might tell them that they don't get the Apache Way, which is distressing, but, at the end of the day, so long as the board doesn't vote to evict them from the foundation, they're part of the Apache Way. The board doesn't generally act without good notice. Generally things escalate from folks griping, to the board agreeing to monitor and advise a project, to the board giving an ultimatum for a specific practice to stop, to the board finally taking some action. Doug - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
On Fri, Jan 9, 2015 at 11:12 AM, Benson Margulies bimargul...@gmail.com wrote: The temperature of this might be reduced by replacing, 'no one knows what the Apache Way is' with 'a lot of us have trouble translate it into practical decisions in a repeatable fashion.' Or not. As reported here, we have performed multiple experiments in which multiple members, directors, and others have derived conflicting _practical_ interpretations from 'the way.' People need to make practical decisions about releases, web sites, brands, and the like. People don't enjoy being told that they have 'trangresssed'. People particularly don't like this when their trangression was an action recommended by someone who is 'supposed to know,' and, in fact, thinks that she or he does know. So, either a lot of us are really stupid, or the Foundation as a whole has a gap between the general principles and their application. No, we can't have a rule book that details every particle of how to run an Apache project, but apparently we could have more concrete guidance. This! Specifically, in the context of the incubator projects coming into the incubator are likely told about the Apache Way, they likely agree with the big picture items, it's the practical application as they migrate their project that causes projects so much confusion; and I'd get away from even the term 'Apache Way' and ask this question in the context of the Incubator: 'What is required of an Apache Project'. Some examples of this: Can a project use an external bug tracker? Can a project use a third-parties CI system? Can a project host their website outside of the ASF? Can a project avoid a users mailing list and move to StackOverflow? Can projects use github? I've seen most (and maybe all) of these get different, conflicting answers from members, directors, and others when asked in the past year or so by projects coming into the incubator. As mentioned on another thread somewhere, one question is at what point does a project become 'in us, but not of us'? If all we are looking for is some reasonable intepretation of the six points here[1], it would seem that lots of the questions above are pointless. I realize that this is culturally known for members. It's ingrained, they don't even have to really think about it. But the outside world has no concept of most of this, or more importantly, it's practical application. --David [1]https://www.apache.org/foundation/how-it-works.html#philosophy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator report sign-off
Thanks Roman. On Thu, Jan 8, 2015 at 10:29 AM, Roman Shaposhnik ro...@shaposhnik.org wrote: On Mon, Jan 5, 2015 at 5:49 PM, Andrew Purtell apurt...@apache.org wrote: One extra thing to note, that while we can *start* this comittee as dedicated to Incubating projects, it will be a very natural extension to get it involved in monitoring all of TLPs, not just pTLPs. What problem exists today where the Board needs such a buffer? Nobody says it does. At least not long term. If the board feels like they can handle the load themselves -- there's no need for the side of the committee that acts that way. However, it feels like a safer bet to try and have it first and then see if the load is light enough so that the board can act directly 100%. Btw, board *does* act directly even today (case in point the thread started by Rich). In what ways could this committee substitute its judgement for PMC of the TLP? Just as the board's job is to tell PMC when something's going wrong ditto with the committee. How would one apply to be on this committee? Would this be a case of some members being more member than others? I see it same way as ComDev (or any other ground like that). There's a voting process, you get nominated and accepted. The only qualification is that you *have* to be an ASF member. What would be the process and expectations for resolving disagreements between the TLP and this committee? Again, since the comittee is just acting as a 'clerk' for the board, the process is still the same as what we have today between the board and the TLPs.
[VOTE][Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION]
+1 From the conversation with Marko, he intended to submit this as a formal vote, but didn't use the regular voting template. Voting will remain open until at least January 15, 2015 18:00 ET. Cheers, Hadrian On 01/09/2015 11:35 AM, Marko Rodriguez wrote: Hello everyone, Over the last 2 weeks, TinkerPop's proposal has been worked on with support from: * David Nalley (champion) * Rich Bowen (mentor) * Hadrian Zbarcea (mentor) * Daniel Gruno (mentor) * Marko Rodriguez (submitting on behalf of TinkerPop) We feel it is now in prime shape from submission to vote. Enjoy!. (URL to wiki version: https://wiki.apache.org/incubator/TinkerPopProposal) A. Abstract TinkerPop http://tinkerpop.com/ is a graph computing framework written in Java. A graph http://en.wikipedia.org/wiki/Graph_%28mathematics%29 is a data structure composed of vertices and edges and is useful for modeling complex domains with arbitrary relations (edges, links, lines) between entities (vertices, objects, dots). TinkerPop https://wiki.apache.org/incubator/TinkerPop provides a core API that graph system vendors can implement. There are various types of graph systems including in-memory graph libraries, OLTP graph databases, and OLAP graph processors (see On Graph Computing http://markorodriguez.com/2013/01/09/on-graph-computing/ for more information). Once the core interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin and processed withTinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled algorithms. For many, TinkerPop https://wiki.apache.org/incubator/TinkerPop is seen as the JDBC http://en.wikipedia.org/wiki/Java_Database_Connectivity of the graph computing community. B. Proposal TinkerPop https://wiki.apache.org/incubator/TinkerPop was formed in 2009 and is currently in the milestone series of 3.0.0. From the start, TinkerPop https://wiki.apache.org/incubator/TinkerPop has provided its software open source and free to use for which ever reason (commercial or otherwise). Initially the license was BSD, but as of TinkerPop3 https://wiki.apache.org/incubator/TinkerPop3, the license was changed to Apache2. The TinkerPop https://wiki.apache.org/incubator/TinkerPop team is composed of developers, evangelists, and representatives from graph system vendors (see TinkerPop Contributors http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors for more information). TinkerPop https://wiki.apache.org/incubator/TinkerPop has done its best to remain vendor agnostic and works closely with all vendors to ensure that the constructs within TinkerPop https://wiki.apache.org/incubator/TinkerPop are able to accommodate the requirements of the underlying graph system. To date, 12 TinkerPop https://wiki.apache.org/incubator/TinkerPop recognized graph system vendors provide TinkerPop https://wiki.apache.org/incubator/TinkerPop implementations. We believe that by joining The Apache Software Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. C. Background TinkerPop https://wiki.apache.org/incubator/TinkerPop has had steady, active development since 2009 when it was founded. Over the years, the Gremlin query language within TinkerPop https://wiki.apache.org/incubator/TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript https://wiki.apache.org/incubator/JavaScript, and the like. In many ways, Gremlin is seen as a traversal style that can be readily adopted within the programming constructs of the developer's native language --- both on and off the JVM. TinkerPop https://wiki.apache.org/incubator/TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop https://wiki.apache.org/incubator/TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop https://wiki.apache.org/incubator/TinkerPop is being used is production graph-based applications around the world and is only getting better with age. D. Rationale The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop https://wiki.apache.org/incubator/TinkerPop was created as a unifying framework for interoperability, language standardization, and data model standardization. This framework makes it simple to plug and play the back-end graph implementation without affecting the developer's code. This is analogous to the way in which the JDBC allows users to swap relational databases while keeping the same programming interface. TinkerPop https://wiki.apache.org/incubator/TinkerPop also brings together OLTP systems (graph
Re: proposal: mentor re-boot
On Jan 9, 2015, at 1:35 AM, Bertrand Delacretaz wrote: On Fri, Jan 9, 2015 at 3:31 AM, Dave Fisher dave2w...@comcast.net wrote: ...I think the IPMC is doing almost all of the above better. Everything except for Failed. I think that now we are blaming the mentor. Let's get over it. Not every podling will work That's distinct concerns IMO: some podlings are failing and no mentor can save them, but there are also podlings that would be doing better if they had sufficiently active mentors. And that depends on mentors who are sufficiently interested with enough time and also the type of mentoring required. Maybe it is community help or it could be release help. Also, from the point of view of oversight, the IPMC needs a way to find out how podlings are doing, and that's delegated to mentors. Failing that, poor IPMC volunteers have to step up and that gets boring over time. So we have Shepherds as delegates from the IPMC to take a look every so often. It is a Role that is more like a scout. We've had Shepherds report Mentor issues, Release issues, Community issues. Regards, Dave -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: What is The Apache Way?
On Fri, Jan 9, 2015 at 8:12 AM, Benson Margulies bimargul...@gmail.com wrote: So, either a lot of us are really stupid, or the Foundation as a whole has a gap between the general principles and their application. No, we can't have a rule book that details every particle of how to run an Apache project, but apparently we could have more concrete guidance. The gap definitely exists. What often leads to confusion is when folks think there's no gap, that everything is clear-cut and certain, when it's not. Different Apache projects are permitted to operate differently, and the ill-defined line of what's acceptable moves over time. This is not entirely bad. Fixed practices are hard to change, but the open-source software world changes rapidly. So maintaining some flexibility is important. What we should try to do are document acceptable practices, those ways of operating that are common in many projects and have worked well. There may be multiple acceptable practices in a given area (e.g., CTR RTC). Projects that diverge from these might still be acceptable, but they might also run into problems and should proceed with caution. Some might tell them that they don't get the Apache Way, which is distressing, but, at the end of the day, so long as the board doesn't vote to evict them from the foundation, they're part of the Apache Way. The board doesn't generally act without good notice. Generally things escalate from folks griping, to the board agreeing to monitor and advise a project, to the board giving an ultimatum for a specific practice to stop, to the board finally taking some action. Doug - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
As mention in a previous thread, all the particulars of what encompasses the Apache Way was learned from years of experience, based on learning what works and what doesn't, usually after some painful semi-disasters. They don't exist because we love process nor are they something a bunch of old-timers pulled out of our arses. Without going into a history lesson, look at what bootstrapped the ASF (well, we were the Apache Group then): an open source project, which many of us depended on, was dropped, and so the effort was picked up again by us to ensure that such a thing would never again happen to us, or anyone else. We wanted to ensure that no matter who came or went within that community, the project and the community survived. This was the start of our focus on community and rewarding individual merit. We wanted new blood to always feel welcome. And since most of us were doing this as volunteers, we wanted to make it easier for us, and others, who were doing this in our spare time, and as a combined work of passion and necessity. So what is it that volunteers lack? An over-abundance of free time to work on the code. So as volunteer cycles ebb and flow, we wanted to make it as easy as possible for people to help when then can and return when they can, hence the idea that merit doesn't expire. Hence the idea that all development must be done on mailing lists (so decisions are archived and asynchronous). Hence the need for voting and consensus and that vetoes can be cast at any time, and must be honored. Hence the several days before significant changes are made, Hence etc etc etc. And finally, we wanted it to be fun, and where we could enjoy hacking and stuff and be protected from legal action. So all those questions you ask are related to the Apache Way, but only in so far as how they help, or hinder, how the project abides by, and *fosters* that sense. And, of course, there are legal and IP provenance issues as well which must be abided by, which also factor into such things as where-they-code-is and what-is-a-release and where-are-releases-done,... Another way to look at the Apache Way is as a musical composition. Sure, it was written for a specific arrangement, but sometimes it's played as a jazz piece, other-times as a classical, or maybe with a blues flavor. But it is always (or *should be*) recognizable. If you *don't* recognize it, then you've taken the interpretation too far, if you get my meaning. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
On Jan 9, 2015, at 3:01 PM, Rich Bowen rbo...@rcbowen.com wrote: On 01/09/2015 02:03 PM, Jim Jagielski wrote: Another way to look at the Apache Way is as a musical composition. Sure, it was written for a specific arrangement, but sometimes it's played as a jazz piece, other-times as a classical, or maybe with a blues flavor. But it is always (or*should be*) recognizable. If you*don't* recognize it, then you've taken the interpretation too far, if you get my meaning. What a delightful analogy. Of course, you're always going to get people who say that a disco rendition is fine, and others who say it's blasphemous. https://www.youtube.com/watch?v=0ouMaLRth-s blasphemous? Maybe. Recognizable? Yeah (fortunately or not) :) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
Sent from my iPhone On Jan 9, 2015, at 12:20 PM, Jim Jagielski j...@jagunet.com wrote: On Jan 9, 2015, at 3:01 PM, Rich Bowen rbo...@rcbowen.com wrote: On 01/09/2015 02:03 PM, Jim Jagielski wrote: Another way to look at the Apache Way is as a musical composition. Sure, it was written for a specific arrangement, but sometimes it's played as a jazz piece, other-times as a classical, or maybe with a blues flavor. But it is always (or*should be*) recognizable. If you*don't* recognize it, then you've taken the interpretation too far, if you get my meaning. What a delightful analogy. Of course, you're always going to get people who say that a disco rendition is fine, and others who say it's blasphemous. https://www.youtube.com/watch?v=0ouMaLRth-s blasphemous? Maybe. Recognizable? Yeah (fortunately or not) :) - 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: What is The Apache Way?
On 01/09/2015 02:03 PM, Jim Jagielski wrote: Another way to look at the Apache Way is as a musical composition. Sure, it was written for a specific arrangement, but sometimes it's played as a jazz piece, other-times as a classical, or maybe with a blues flavor. But it is always (or*should be*) recognizable. If you*don't* recognize it, then you've taken the interpretation too far, if you get my meaning. What a delightful analogy. Of course, you're always going to get people who say that a disco rendition is fine, and others who say it's blasphemous. -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[NOTICE] Corinthia mentors += Dave Fisher
Hi. Dave has volunteered to help mentoring our project, the PPMC was all in favor for accepting the offer. rgds jan i
[VOTE] Release Apache Johnzon 0.5-incubating
The Apache Johnzon PPMC has voted to release Apache Johnzon 0.5-incubating based on the release candidate described below. Now it is the IPMC's turn to vote. Git commit for the release is [a88f797] https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=a88f79789c0ca288217d90d509633b566c0ac692 Maven staging repo: https://repository.apache.org/content/repositories/orgapachejohnzon-1002 Source releases (zip/tar.gz): https://repository.apache.org/content/repositories/orgapachejohnzon-1002/org/apache/johnzon/johnzon/0.5-incubating/johnzon-0.5-incubating-src.zip https://repository.apache.org/content/repositories/orgapachejohnzon-1002/org/apache/johnzon/johnzon/0.5-incubating/johnzon-0.5-incubating-src.tar.gz Site is here: http://people.apache.org/~salyh/johnzon-0.5-incubating-site/ PGP release keys (signed using 22D7F6EC): https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS Project vote passes with 3 binding +1 votes, one non-binding +1 vote and no -1 votes: http://markmail.org/thread/ovuhl6uqaowopuwh This release fixes a few bugs and introduce some new features like comments parsing and mapper enhancements. It also improves performance. The vote will be open for at least 72 hours. [ ] +1 approve [ ] -1 disapprove (and reason why) Thanks Hendrik -- Hendrik Saly (salyh, hendrikdev22) @hendrikdev22 PGP: 0x22D7F6EC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
What is The Apache Way? No one can say. There is no bounded set of expectations that an Apache project must fulfill. Where do Apache's official policies begin and end? Which best practices must be mastered? What will be enforced, what will be ignored? Every last podling graduates without a clear understanding of The Apache Way, because it is impossible to attain a clear understanding of The Apache Way. Really? Are you serious? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
On Fri, Jan 9, 2015 at 5:22 AM, Jim Jagielski j...@jagunet.com wrote: What is The Apache Way? No one can say. There is no bounded set of expectations that an Apache project must fulfill. Where do Apache's official policies begin and end? Which best practices must be mastered? What will be enforced, what will be ignored? Every last podling graduates without a clear understanding of The Apache Way, because it is impossible to attain a clear understanding of The Apache Way. Really? Are you serious? Absolutely. And if anyone who represents us on the Board doesn't think that a lack of clear expectations is a problem, I think that's a big problem. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
On Jan 9, 2015, at 9:51 AM, Marvin Humphrey mar...@rectangular.com wrote: On Fri, Jan 9, 2015 at 5:22 AM, Jim Jagielski j...@jagunet.com wrote: What is The Apache Way? No one can say. There is no bounded set of expectations that an Apache project must fulfill. Where do Apache's official policies begin and end? Which best practices must be mastered? What will be enforced, what will be ignored? Every last podling graduates without a clear understanding of The Apache Way, because it is impossible to attain a clear understanding of The Apache Way. Really? Are you serious? Absolutely. And if anyone who represents us on the Board doesn't think that a lack of clear expectations is a problem, I think that's a big problem. And I think that someone who is an ASF member who claims that the Apache Way is completely unknown and nebulous and that there is no clear understanding of what the Apache Way is, well I think that's a big problem as well. Even bigger. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: What is The Apache Way?
And fwiw, maybe the reason directors are chosen to represent members is because they *do* understand what the Apache Way is... Personally, I'm shocked, saddened and disappointed that this conversation is even happening, since it really clearly shows the depth of the dysfunction. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
