I tend to agree that we are rushing this a bit. I would have thought that
critical bug fixes to enable a JMS transport would be relatively few and
could be handled by sending patches to axis-dev. This will quickly build
confidence in the submitters of these patches who can then be proposed as
committers.
The JMS transport itself could presumably be developed in a separate cvs
and built strictly on top of the Axis jars. The Sonic guys can change it to
their hearts' content and then contribute a version into the proposals
directory.
If and when we adopt the proposal, we could at that point propose new
committers.
Glyn
Richard
Sitze/Austin/IBM@ To: [EMAIL PROTECTED]
IBMUS cc:
Subject: Re: user id request
09/17/02 10:09 PM
Please respond to
axis-dev
Nothing personal Dave.
I'm usually the last to vote for bureaucracy. Process must be balanced by
common sense.
On the one hand, the process is (generally) that you make yourself
familiar to the community by submitting patches. You gain experience in
the process/style/discussion of the community - then you (we prefer rather
quickly) become a commiter. In this case 'quickly' was VERY quickly. . .
Note that I didn't vote against you.
On the other hand, you & your team are working on items incidental to the
main work of the team. There may or may not be a problem, and from your
comments its sounds like the possibility is low.
Normally I wouldn't take a hard-line stance on this (I can say that since
it didn't happen that way :-). However, on top of the above issues, there
is an impending 1.0 release. I, myself, am trying to stay out of the way
of the core group working on TCK & interop issues. I'm probably the worst
for rocking the boat at this point. . . [having tests back on-line will be
helpful :-]
The last thing anyone wants at this point in the game is to rock the boat
more than it needs to be. I'm not so much voting AGAINST new committers,
but rather that I'm trying to balance the issues by voting for stability,
flexibility (dave or ? becomes committer) AND process for new committers.
Let 1.0 out the door [primary goal being to pass TCK], and we should be
able to resolve this to everyones satisfaction.
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
David Chappell <[EMAIL PROTECTED]>
09/17/2002 03:08 PM
Please respond to axis-dev
To: [EMAIL PROTECTED]
cc:
Subject: Re: user id request
David Chappell wrote:
...
>
> I can assure you that we will not be disruptive to 1.0.
> Dave
Meaning, the only thing we might possibly check into the 1.0 tree from
here on would be some documentation and some critical bug fixes should
that need arise.
Dave
>
> James M Snell wrote:
> >
> > Nah, all three of 'em will do active.
> >
> > - James Snell
> > IBM Emerging Technologies
> > [EMAIL PROTECTED]
> > (559) 587-1233 (office)
> > (700) 544-9035 (t/l)
> > Programming Web Services With SOAP
> > O'Reilly & Associates, ISBN 0596000952
> >
> > Have I not commanded you? Be strong and courageous.
> > Do not be terrified, do not be discouraged, for the Lord your
> > God will be with you whereever you go. - Joshua 1:9
> >
> > Richard Sitze/Austin/IBM@IBMUS wrote on 09/17/2002 11:24:12 AM:
> >
> > > >I'm fine with that, but if we go that route the
> > > >committer should be whoever is going to do the
> > > >most work on the code (would that be Jaime?)...
> >
> > > +1
> >
> > >
> > > *******************************************
> > > Richard A. Sitze
> > > IBM WebSphere WebServices Development
> >
> > >
> > > Glen Daniels <[EMAIL PROTECTED]>
> > > 09/17/2002 12:57 PM
> > > Please respond to axis-dev
> >
> > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > > cc:
> > > Subject: RE: user id request
> > >
> > > I'm fine with that, but if we go that route the committer should be
> > > whoever is going to do the most work on the code (would that be
> > Jaime?)...
> >
> > > --Glen
> >
> > > > -----Original Message-----
> > > > From: Richard Sitze [mailto:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, September 17, 2002 1:53 PM
> > > > To: [EMAIL PROTECTED]
> > > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > > Subject: Re: user id request
> > > >
> > > >
> > > > WHOA WHOA...
> > > >
> > > > There WAS a vote called for ONE committer, David Chappell.
> > > >
> > > > There WAS NOT a vote for any others.
> > > >
> > > > I was silent on David (personally, I'd like to see patches
submitted
> > > > first), but I'm going to -1 anyone else. Seems like we've
> > > > got someone to
> > > > represent the work, and I think we need time to get to know
> > > > them before we
> > > > call for more submitters without history. Until 1.0 ships,
> > > > this should
> > > > have only MINIMAL impact on AXIS. Taking this slow is the
> > > > right thing to
> > > > do.
> > > >
> > > > <ras>
> > > >
> > > > *******************************************
> > > > Richard A. Sitze
> > > > IBM WebSphere WebServices Development
> > > >
>
> --
> Sonic Software - Backbone of the Extended Enterprise
> --
> David Chappell <[EMAIL PROTECTED]> Office: (781)999-7099
> Mobile: (617)510-6566
> Vice President and Chief Technology Evangelist, Sonic Software
> co-author,"Java Web Services", (O'Reilly 2002)
> "The Java Message Service", (O'Reilly 2000)
> "Professional ebXML Foundations", (Wrox 2001)
> --
--
Sonic Software - Backbone of the Extended Enterprise
--
David Chappell <[EMAIL PROTECTED]> Office: (781)999-7099
Mobile: (617)510-6566
Vice President and Chief Technology Evangelist, Sonic Software
co-author,"Java Web Services", (O'Reilly 2002)
"The Java Message Service", (O'Reilly 2000)
"Professional ebXML Foundations", (Wrox 2001)
--
#### chappell.vcf has been removed from this note on September 17 2002 by
Richard Sitze
