Re: [PROPOSAL] Tashi

2008-07-23 Thread Doug Cutting
William A. Rowe, Jr. wrote: This looks like a very interesting technology, and when proposed as a collaboration by actual persons A, B, and C (who happen to work for X, Y, and Z) we will have something to discuss. Great, because that's what I think we have. It so happens that persons D, E and

Re: [PROPOSAL] Tashi

2008-07-23 Thread Jason van Zyl
On 23-Jul-08, at 6:12 PM, Niall Pemberton wrote: I really don't see what the problem is here, there are two named committers in the proposal. Whatever the interests of the companies they work for, Tashi will have to create a healthy community to graduate and I don't think corporate backing shou

Re: [PROPOSAL] Tashi

2008-07-23 Thread Michael Stroucken
[EMAIL PROTECTED]> Subject: Re: [PROPOSAL] Tashi Hi, I've read the messages from Henning and William, and I'd like to address some of the concerns voiced by them. I'm Michael Stroucken, and I'm a senior systems programmer at CMU. That means I am staff, and my interests in the Tashi project are

Re: [PROPOSAL] Tashi

2008-07-23 Thread Justin Erenkrantz
On Wed, Jul 23, 2008 at 3:12 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > I really don't see what the problem is here, there are two named > committers in the proposal. Whatever the interests of the companies > they work for, Tashi will have to create a healthy community to > graduate and I don

Re: [PROPOSAL] Tashi

2008-07-23 Thread Niclas Hedhman
On Thursday 24 July 2008 05:23, William A. Rowe, Jr. wrote: > In other words, I'll vote -1 on any Proposal for non-person entities > X, Y, and Z to form an incubator podling, and I know several other PMC > members who will do likewise. I disagree. IMHO, wording in the proposal is irrelevant. If th

Re: [PROPOSAL] Tashi

2008-07-23 Thread Niall Pemberton
On Wed, Jul 23, 2008 at 10:23 PM, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: > Doug Cutting wrote: >> >> There's no conspiracy here to steal Apacheness. Rather, Yahoo!, Intel and >> CMU would like to collaborate on open source software. Intel and CMU have a >> prototype, and Yahoo! is intere

Re: [PROPOSAL] Tashi

2008-07-23 Thread William A. Rowe, Jr.
Doug Cutting wrote: There's no conspiracy here to steal Apacheness. Rather, Yahoo!, Intel and CMU would like to collaborate on open source software. Intel and CMU have a prototype, and Yahoo! is interested in helping to develop this further. All three believe that other parties will also b

Re: [PROPOSAL] Tashi

2008-07-23 Thread Doug Cutting
Henning Schmiedehausen wrote: - Are the proposed committers, people "assigned to work on the project" or are they genuinely interested in this software. Those are not necessarily disjoint sets. Folks who are "assigned" are frequently also "genuinely interested", and vice versa. IAW, will

Re: [PROPOSAL] Tashi

2008-07-23 Thread Henning Schmiedehausen
Hi, a number of questions: - Are the proposed committers, people "assigned to work on the project" or are they genuinely interested in this software. IAW, will they stick around or leave as soon as they are reassigned to other projects or their grants run out? The wording for the Yahoo! "slot"

Re: [PROPOSAL] Tashi

2008-07-23 Thread David O'Hallaron
No worries. I've removed the entry on the wiki version of the proposal at http://wiki.apache.org/incubator/TashiProposal. It now reads simply: Initially, there will be one committer each from Carnegie Mellon and Intel Research: * Michael Stroucken ([EMAIL PROTECTED]) * Michael Ryan ([EMAIL PROTE

Re: [VOTE]: Buildr 1.3.2 release

2008-07-23 Thread ant elder
On Wed, Jul 23, 2008 at 8:14 AM, Assaf Arkin <[EMAIL PROTECTED]> wrote: > On Tue, Jul 22, 2008 at 6:18 AM, ant elder <[EMAIL PROTECTED]> wrote: > > Looks ok to me so +1. > > > > Would be helpful to include a RAT report with the request, but I ran it > > myself and it didn't highlight any issues. >

Re: [VOTE]: Buildr 1.3.2 release

2008-07-23 Thread Assaf Arkin
On Tue, Jul 22, 2008 at 6:18 AM, ant elder <[EMAIL PROTECTED]> wrote: > Looks ok to me so +1. > > Would be helpful to include a RAT report with the request, but I ran it > myself and it didn't highlight any issues. > > If the doc pdf is going to be distributed separately it should probably > includ