Re: Abdera 0.3.0
On Sep 17, 2007, at 11:45 AM, James M Snell wrote: The Apache Abdera project is ready to let loose it's 0.3.0-incubating release. The 0.3.0 branch was created a couple of weeks ago and has since undergone a solid review by both committers and users. A number of issues were identified and fixed. The current candidate zips have received the requisite number of +1's to release. The 0.3.0-incubating release candidate zips are available for download at http://people.apache.org/~jmsnell/abdera/0.3.0 The one issue that might hold us up is the fact that we are shipping the bouncy castle jar. As I've mentioned on a couple of other notes, it would not be difficult for us to soften the dependency on that jar and not ship it. Hi James, IMO, I think we've gotten a pretty clear message -- you can't include the BouncyCastle jar, unless you obtain an Apache-compatible license for the IDEA implementation. I doubt that will happen. So, I recommend you switch to a soft dependency... --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Abdera 0.3.0
Ok, I've got no problem with this. cc'ing the abdera-dev list: I'll make the change a bit later today and will re-roll the zips. - James Kevan Miller wrote: On Sep 17, 2007, at 11:45 AM, James M Snell wrote: The Apache Abdera project is ready to let loose it's 0.3.0-incubating release. The 0.3.0 branch was created a couple of weeks ago and has since undergone a solid review by both committers and users. A number of issues were identified and fixed. The current candidate zips have received the requisite number of +1's to release. The 0.3.0-incubating release candidate zips are available for download at http://people.apache.org/~jmsnell/abdera/0.3.0 The one issue that might hold us up is the fact that we are shipping the bouncy castle jar. As I've mentioned on a couple of other notes, it would not be difficult for us to soften the dependency on that jar and not ship it. Hi James, IMO, I think we've gotten a pretty clear message -- you can't include the BouncyCastle jar, unless you obtain an Apache-compatible license for the IDEA implementation. I doubt that will happen. So, I recommend you switch to a soft dependency... --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira closure and resolution user and date tracking
FYI: I've filed an INFRA request to reindex Jira to populate the Resolved custom field for existing issues: http://issues.apache.org/jira/browse/INFRA-1366 Martin Martin Sebor wrote: Marshall Schor wrote: To search for issues resolved or closed between given dates, you can come close by searching for issues with the filter set to resolved or closed, and then use the updated fields to specify the date range. Maybe this doesn't quite do what you want though - or does it? Thanks. You're right, it doesn't do quite what we need because of the potential for false positives. We also tried using the custom Resolved field but as has just been pointed out to me on the Jira forum, the database (most likely) needs to be reindexed before the field can be used to query existing records. Perhaps we should start by requesting that first. Martin -Marshall Martin Sebor wrote: In an effort to improve our scheduling processes stdcxx is trying to find a better way to manage our issues. One feature that I think would help us is the ability to search for issues resolved and/or closed between given dates. Our Jira doesn't seem to provide the feature out of the box, although there is a plugin that apparently makes this possible. Before I request that INFRA install this plugin I'm curious if other projects have a similar need and if so, how they manage without it. The pugin is here: http://confluence.atlassian.com/pages/viewpage.action?pageId=195827 Thanks Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Jira-closure-and-resolution-user-and-date-tracking-tf4430953.html#a12760880 Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: SPL
Noel J. Bergman wrote: We proposed to develop a policy-based management infrastructure that automates administrative tasks by executing policies Sounds good. I will be curious to see the reaction from the HTTP Server folks, but this sort of thing is very much needed in real-world deployments of app servers. The initial goals are to develop an SPL evaluation engine and bindings to the APIs for [...] What about Tomcat? I'd be happy to help out with this piece, should the vote to incubation go through Filip Nominated Mentors -Bill Stoddard([EMAIL PROTECTED]) Glad to see that Bill will have cycles for this. :-) Would you please take a look at lokahi (http://incubator.apache.org/lokahi) and comment on any synergies that you see? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Incubator Proposal: Pig
Hi, Yahoo! research and development teams have developed a proposal below. The proposal is also available on wiki at http://wiki.apache.org/incubator/PigProposal http://wiki.apache.org/incubator/PigProposal. We would like to ask that the ASF consider forming a podling according to the proposal. Thanks, Olga Natkovich mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] - = Pig Open Source Proposal = == Abstract == Pig is a platform for analyzing large data sets. == Proposal == The Pig project consists of high-level languages for expressing data analysis programs, coupled with infrastructure for evaluating these programs. The salient property of Pig programs is that their structure is amenable to substantial parallelization, which in turns enables them to handle very large data sets. At the present time, Pig's infrastructure layer consists of a compiler that produces sequences of Map-Reduce programs, for which large-scale parallel implementations already exist (e.g., the Hadoop subproject). Pig's language layer currently consists of a textual language called Pig Latin, which has the following key properties: 1. ''Ease of programming''. It is trivial to achieve parallel execution of simple, embarrassingly parallel data analysis tasks. Complex tasks comprised of multiple interrelated data transformations are explicitly encoded as data flow sequences, making them easy to write, understand, and maintain. 2. ''Optimization opportunities''. The way in which tasks are encoded permits the system to optimize their execution automatically, allowing the user to focus on semantics rather than efficiency. 3. ''Extensibility''. Users can create their own functions to do special-purpose processing. == Background == Pig started as a research project at Yahoo! in May of 2006 to combine ideas in parallel databases and distributed computing. The first internal release took place in July 2006. The first release was a simple front-end to the Hadoop Map/Reduce framework. The following releases added new features and evolved the language based on user feedback. In July 2007, pig was taken over by a development team and the first production version is due to be released on 9/28/07. Since its inception, we had observed a steady growth of the user community within Yahoo!. In April 2007, Pig was released under a BSD-type license. Several external parties are using this version and have expressed interest in collaborating on its development. == Rationale == In an information-centric world, innovation is driven by ad-hoc analysis of large data sets. For example, search engine companies routinely deploy and refine services based on analyzing the recorded behavior of users, publishers, and advertisers. The rate of innovation depends on the efficiency with which data can be analyzed. To analyze large data sets efficiently, one needs parallelism. The cheapest and most scalable form of parallelism is cluster computing. Unfortunately, programming for a cluster computing environment is difficult and time-consuming. Pig makes it easy to harness the power of cluster computing for ad-hoc data analysis. While other language exist that try to achieve the same goals, we believe that Pig provides more flexibility and gives more control to the end user. SQL typically requires (1) importing data from a user's preferred format into a database system's internal format (2) well-structured, normalized data with a declared schema, and (3) programs expressed in declarative SELECT-FROM-WHERE blocks. In contrast, Pig Latin facilitates (1) interoperability, i.e. data may be read/written in a format accepted by other applications such as text editors or graph generators (2) flexibility, i.e. data may be loosely structured or have structure that is defined operationally, and (3) adoption by programmers who find procedural programming more natural than declarative programming. Sawzall is a scripting language used at Google on top of Map-Reduce. A sawzall program has a fairly rigid structure consisting of a filtering phase (the map step) followed by an aggregation phase (the reduce step). Furthermore, only the filtering phase can be written by the user, and only a pre-built set of aggregations are available (new ones are non-trivial to add). While Pig Latin has similar higher level primitives like filtering and aggregation, an arbitrary number of them can be flexibly chained together in a Pig Latin program, and all primitives can use user-defined functions with equal ease. Further, Pig Latin has additional primitives such as cogrouping, that allow operations such as joins (which require multiple programs in Sawzall) to be written in a single line in Pig Latin. Further, Pig Latin is designed to be embedded into other languages, and can use functions written in other languages. Thus, in contrast to Sawzall, it directly caters to a large community of developers
Re: Incubator Proposal: Pig
Hey, On 9/18/07, Olga Natkovich [EMAIL PROTECTED] wrote: Yahoo! research and development teams have developed a proposal below. The proposal is also available on wiki at http://wiki.apache.org/incubator/PigProposal Looks very cool to me. +1 to accepting Pig as an Incubator project. I'll also gladly volunteer as a mentor. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
Garrett Rooney wrote: Is there any particular reason you want this podling to be sponsored by the Incubator PMC (which is generally done for projects that intend to turn into their own top level project) rather than having it sponsored by the Lucene PMC (where Hadoop currently resides)? It seems to me that the close relationship between Pig and Hadoop implies that they very well might best be served under the same roof. The existing contributor base is largely disjoint from the Hadoop contributor base, and they expect that to mostly remain the case. Nigel, Owen I, Hadoop committers, will mostly just help the Pig crew out with Apache ways, and don't expect to become significant contributors to Pig. Pig builds on Hadoop, and the communities may overlap a bit, but, to the primary folks involved, it feels like a separate community and they'd prefer to aim for a TLP. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
Hey, On 9/18/07, Doug Cutting [EMAIL PROTECTED] wrote: overlap a bit, but, to the primary folks involved, it feels like a separate community and they'd prefer to aim for a TLP. It should be clear to everyone involved, though, that part of the goal of incubation is to diversify the project's community so that it's not disjoint from everyone else. I hope to have a bunch of non-Yahoo people contributing to the project. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
Is there any particular reason you want this podling to be sponsored by the Incubator PMC (which is generally done for projects that intend to turn into their own top level project) Is this true? I thought all new projects had to go through the incubator. Woden [1] is an incubator project that plans to graduate and join the WS PMC. [1] http://incubator.apache.org/woden/ Lawrence Garrett Rooney [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/18/2007 04:02 PM Please respond to general@incubator.apache.org To general@incubator.apache.org cc Subject Re: Incubator Proposal: Pig On 9/18/07, Olga Natkovich [EMAIL PROTECTED] wrote: Hi, Yahoo! research and development teams have developed a proposal below. The proposal is also available on wiki at http://wiki.apache.org/incubator/PigProposal http://wiki.apache.org/incubator/PigProposal. We would like to ask that the ASF consider forming a podling according to the proposal. Is there any particular reason you want this podling to be sponsored by the Incubator PMC (which is generally done for projects that intend to turn into their own top level project) rather than having it sponsored by the Lucene PMC (where Hadoop currently resides)? It seems to me that the close relationship between Pig and Hadoop implies that they very well might best be served under the same roof. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
On 9/18/07, Lawrence Mandel [EMAIL PROTECTED] wrote: Is there any particular reason you want this podling to be sponsored by the Incubator PMC (which is generally done for projects that intend to turn into their own top level project) Is this true? I thought all new projects had to go through the incubator. Woden [1] is an incubator project that plans to graduate and join the WS PMC. [1] http://incubator.apache.org/woden/ All projects need to go through the incubation process, but not all are sponsored by the incubator PMC, many are sponsored by an existing PMC outside the incubator. I don't recall for sure, but I'd expect that woden entered the incubator after being sponsored by the WS PMC (at least, that's how things tend to work today if I understand correctly, it's quite possible that woden predates that practice, I'm really not sure). -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
On 9/18/07, Olga Natkovich [EMAIL PROTECTED] wrote: Hi, Yahoo! research and development teams have developed a proposal below. The proposal is also available on wiki at http://wiki.apache.org/incubator/PigProposal http://wiki.apache.org/incubator/PigProposal. We would like to ask that the ASF consider forming a podling according to the proposal. Is there any particular reason you want this podling to be sponsored by the Incubator PMC (which is generally done for projects that intend to turn into their own top level project) rather than having it sponsored by the Lucene PMC (where Hadoop currently resides)? It seems to me that the close relationship between Pig and Hadoop implies that they very well might best be served under the same roof. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: SPL
Hi all, Over at Directory we have an initial attempt at an identity solution in place called Triplesec. It does the usual AAA with some additional things like mobile keyfobs however it's authorization policy management features might benefit from this project or there may be some overlap. Here's a link btw for some additional information on tsec: http://directory.apache.org/triplesec Specifically the following information refers to the authorization policy store and an API to access the information therein which can be stored in LDAP or in an LDIF file (exported from LDAP). http://directory.apache.org/triplesec/guardian-api-users-guide.html http://directory.apache.org/triplesec/authorization-using-guardian-api.html http://directory.apache.org/triplesec/administration-tool-users-guide.html So the big question is there much overlap here? An initial glance tells me there might not be but I may be wrong. Thoughts? Alex On 9/17/07, Filip at Apache [EMAIL PROTECTED] wrote: Noel J. Bergman wrote: We proposed to develop a policy-based management infrastructure that automates administrative tasks by executing policies Sounds good. I will be curious to see the reaction from the HTTP Server folks, but this sort of thing is very much needed in real-world deployments of app servers. The initial goals are to develop an SPL evaluation engine and bindings to the APIs for [...] What about Tomcat? I'd be happy to help out with this piece, should the vote to incubation go through Filip Nominated Mentors -Bill Stoddard([EMAIL PROTECTED]) Glad to see that Bill will have cycles for this. :-) Would you please take a look at lokahi ( http://incubator.apache.org/lokahi) and comment on any synergies that you see? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
+1 as well. I would be happy to help with code contributions and user testing. Yoav Shapira-2 wrote: Hey, On 9/18/07, Olga Natkovich [EMAIL PROTECTED] wrote: Yahoo! research and development teams have developed a proposal below. The proposal is also available on wiki at http://wiki.apache.org/incubator/PigProposal Looks very cool to me. +1 to accepting Pig as an Incubator project. I'll also gladly volunteer as a mentor. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Incubator-Proposal%3A-Pig-tf4476730.html#a12766208 Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
On 9/18/07, Doug Cutting [EMAIL PROTECTED] wrote: Garrett Rooney wrote: Is there any particular reason you want this podling to be sponsored by the Incubator PMC (which is generally done for projects that intend to turn into their own top level project) rather than having it sponsored by the Lucene PMC (where Hadoop currently resides)? It seems to me that the close relationship between Pig and Hadoop implies that they very well might best be served under the same roof. The existing contributor base is largely disjoint from the Hadoop contributor base, and they expect that to mostly remain the case. Nigel, Owen I, Hadoop committers, will mostly just help the Pig crew out with Apache ways, and don't expect to become significant contributors to Pig. Pig builds on Hadoop, and the communities may overlap a bit, but, to the primary folks involved, it feels like a separate community and they'd prefer to aim for a TLP. Well, it seems a little odd to me (if anything it seems like a new TLP associated with hadoop and generic distributed computing tools like pig that are built on top of hadoop seems like it would make more sense than just a pig TLP), but if that's what the people involved want I don't see anything wrong with it. I mean it's not like a decision on a final home for the project has to happen now anyway. In any event, +1 from me, this is a neat project and I'd be happy to see it here. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
Garrett Rooney wrote: (if anything it seems like a new TLP associated with hadoop and generic distributed computing tools like pig that are built on top of hadoop seems like it would make more sense than just a pig TLP), Yes, I agree. But that's not happened yet, and the Pig folks are ready to enter the incubator now. but if that's what the people involved want I don't see anything wrong with it. I mean it's not like a decision on a final home for the project has to happen now anyway. Exactly. If, when Pig is ready to graduate, there is a more Hadoop-specific TLP, then it may make sense to have Pig join that as a sub-project, or it may not. But, for now, the folks involved have elected to aim for TLP rather than Lucene sub-project (the available options). Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
Yoav Shapira wrote: It should be clear to everyone involved, though, that part of the goal of incubation is to diversify the project's community so that it's not disjoint from everyone else. I hope to have a bunch of non-Yahoo people contributing to the project. Indeed. That's the primary reason to move this to Apache: to be able to collaborate with others outside Y!. If Y! didn't want to diversify the community it could just keep posting code dumps under BSD as it does today. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Proposal: Pig
On Sep 18, 2007, at 2:45 PM, Doug Cutting wrote: Garrett Rooney wrote: (if anything it seems like a new TLP associated with hadoop and generic distributed computing tools like pig that are built on top of hadoop seems like it would make more sense than just a pig TLP), Yes, I agree. But that's not happened yet, and the Pig folks are ready to enter the incubator now. but if that's what the people involved want I don't see anything wrong with it. I mean it's not like a decision on a final home for the project has to happen now anyway. Exactly. If, when Pig is ready to graduate, there is a more Hadoop- specific TLP, then it may make sense to have Pig join that as a sub- project, or it may not. I agree. One of the objectives of incubation is to decide exactly where in Apache a project (or sub-project) belongs. Let's get it into incubation and see what kind of community/synergy Pig can build with other projects. Craig But, for now, the folks involved have elected to aim for TLP rather than Lucene sub-project (the available options). Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
