Re: ajax proposal?
On Thu, 2006-01-05 at 14:36 -0500, Jim Jagielski wrote: > On Jan 5, 2006, at 1:38 PM, Sam Ruby wrote: > > Sanjiva and I have experience with Apache SOAP. Two rewrites > > later, and there is a thriving community working on Apache Axis2. > > > > The goal here is not to "crown" anything, but to provide the grain > > of sand that will lead to the production of a pearl. +1; I don't see this as a crowning at all. > I am a big +1 on the ASF getting "involved" with AJAX. Me too. When the time's right, I'll be happy to help sponsor/mentor this project with the idea of heading for an AJAX TLP at some point. Hopefully before graduation we'll get a couple more AJAX projects coming in and getting all married together or co-existing/competing under the same TLP umbrella. Given we have dozens of Webapp frameworks for Java server side, I don't see how the world will end up with less than dozens of AJAX frameworks. First entrant to the new project will not be a guaranteed "winner" as there will be no single "winner." Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FTPServer one more time
Hi Noel Noel J. Bergman wrote: Niklas Gustavsson wrote: I'm not a commiter but I do have my CLA on file "niklas" is already taken for another account. What would be your prefered alternative(s)? Any updates on the progress of setting up the accounts for Sergey and me? /niklas --- Niklas Gustavsson http://www.protocol7.com mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [policy] bring in full code history on incubated project?
On 1/6/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 1/4/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > > Can someone make a definitive statement on whether or not code
> > > history is brought into our repo from elsewhere when a podling
> > > brings code over?
> >
> > It is still being debated, so no. Roy's comments about import from private
> > vs public repositories may be a reasonable approach. Personally, I'm a
> > packrat. I'd keep everything possible. But I am not sure if we quite have
> > a consensus, yet. Close.
>
> I'm swayed. +1 on a policy of importing history whenever possible and
> desired by the incoming proposal.
>
> > I did talk with Garrett Rooney, and we can resolve the authorship namespace
> > problem, so we can take that particular technical issue off the table. The
> > imported author, which is held as a property, could be mangled to something
> > like IMPORTED_${PROJECT}_${AUTHOR} during the import, preventing collisions
> > with existing or future ASF Committers.
>
> +1. Probably not worth the extra work of trying to map to the existing
> committers or new committers.
Well, lets be clear, I said it was possible, not trivial. There'd
still be a need for someone to write some code (a new option to
svndumpfilter or something) to make it happen. Not difficult, but I
don't know of any existing code to do it.
-garrett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [policy] bring in full code history on incubated project?
On 1/4/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > Can someone make a definitive statement on whether or not code
> > history is brought into our repo from elsewhere when a podling
> > brings code over?
>
> It is still being debated, so no. Roy's comments about import from private
> vs public repositories may be a reasonable approach. Personally, I'm a
> packrat. I'd keep everything possible. But I am not sure if we quite have
> a consensus, yet. Close.
I'm swayed. +1 on a policy of importing history whenever possible and
desired by the incoming proposal.
> I did talk with Garrett Rooney, and we can resolve the authorship namespace
> problem, so we can take that particular technical issue off the table. The
> imported author, which is held as a property, could be mangled to something
> like IMPORTED_${PROJECT}_${AUTHOR} during the import, preventing collisions
> with existing or future ASF Committers.
+1. Probably not worth the extra work of trying to map to the existing
committers or new committers.
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
