You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Glen Daniels <gl...@thoughtcraft.com> on 2010/04/15 05:08:17 UTC
What's next for WS@Apache? Discuss.
Hey y'all,
So as per my earlier mail to the dev lists, we need to talk about...
* Which subprojects should be promoted to TLPs?
* Which subprojects should be migrated to the Attic?
* What should the structure look like for what remains?
Here's what we've got to work with.
1. Axiom (commons)
2. Neethi (commons)
3. XmlSchema (commons)
4. Tcpmon (commons)
5. Guththila (commons)
6. JaxMe
7. jUDDI
8. Scout
9. Muse
10.Woden
11.WSIF
12.WSS4J
13.XMLRPC
Let's talk Attic first. It seems WSIF and Muse have been pretty much
inactive for some time now, so I'd propose we get the ball rolling with
proposals to Attic both of those. JaxMe also seems ripe for the Attic.
I think that it's pretty clear jUDDI and Scout should migrate together to a
new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
migrate to Axis.
Is there enough activity on XMLRPC to keep it alive? Jochen?
Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and Tcpmon
as subprojects of WS. I'd like to get rid of the "commons" layer, though,
since I think the "new" WS project should itself be a set of commonly useful
WS components. I know other ideas have been discussed for the commons stuff,
so let's start that discussion and get the various opinions out on the table?
That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for WSS4J,
I'm not sure if it should stay or become a TLP.
So... what do you guys think?
Thanks,
--Glen
P.S. Reminder - please fill out your sections of our board report for this
month if appropriate!
Re: What's next for WS@Apache? Discuss.
Posted by Andreas Veithen <an...@gmail.com>.
What about creating a Wiki page with an initial proposal where people
can indicate their interest in joining as PMC members/committers of
the new TLPs?
Andreas
On Wed, Apr 21, 2010 at 03:28, Daniel Kulp <dk...@apache.org> wrote:
> On Tuesday 20 April 2010 8:49:02 pm Eran Chinthaka Withana wrote:
>> Hi,
>>
>> I'm still confused about this re-org. People started this re-org, saying
>> that the projects inside old-WS project was not manageable and no knows
>> whats going inside all the projects. It was also mentioned that, since
>> project X people also get to have a say in project Y (where X,Y are in WS),
>> it will be a mess.
>> Now why is this theory not applying to Axiom or XmlSchema projects. They
>> are totally independent projects, that can be used beyond Axis2. Also some
>> one concentrating only on XmlSchema or Axiom might not be interested in
>> Axis2 project or its Karma. So why do you wanna put them inside Axis2 or
>> new WS project, once again making the same mistake we had earlier?
>>
>> Axis2 depends on Axiom and XmlSchema, but not the other way round.
>
> Well, Axiom I think has enough going on with it and enough activity that could
> warrant it being a TLP. I really could go either way on that.
>
> If you follow board@ at all (I know, most of you cannot follow it) and the
> board meeting summaries and such, one of the other things that they are not
> liking lately are the repeat "Nothing happened this quarter" reports occuring
> over and over and over from the projects. For some of the smaller, less
> active, projects (like XmlSchema), there would definitely be a danger of
> falling into that path and the board would be concerned about the
> oversight/community of such small projects.
>
> So there needs to be some level of balance between being able to properly
> provide oversight to everything going on in the project along with being able
> to show there is an active and healthy community. The question is how to
> achieve that? If a project like Axiom feels it can go it alone, I would
> definitely support it (providing the new PMC is large enough), but I'd also
> support keeping the smaller ones together until they are "ready" or until the
> technology becomes irrelevant and it goes to the Attic.
>
> Dan
>
>> Dan, if new WS project should not be an umbrella project, then why do you
>> think we should put Axiom/XmlSchema inside it?
>>
>> Thanks,
>> Eran Chinthaka
>>
>> On Tue, Apr 20, 2010 at 8:34 PM, Daniel Kulp <dk...@apache.org> wrote:
>> > On Tuesday 20 April 2010 7:54:27 pm Glen Daniels wrote:
>> > > Hi Sanjiva,
>> > >
>> > > Sorry for the late reply.
>> > >
>> > > On 4/17/2010 3:37 AM, Sanjiva Weerawarana wrote:
>> > > > Glen, your proposal amounts to having gone thru a lot of pain to have
>> > > > simply TLPed Axis. The entire board prerogative was to break up WS
>> > > > wasn't it?
>> > >
>> > > My interpretation was that it was more "WS is too big" than "WS should
>> > > entirely go away". There are plenty of other projects at Apache that
>> >
>> > have
>> >
>> > > a reasonable number of subprojects, with related functions and
>> >
>> > development
>> >
>> > > communities. I'm not yet convinced that there is sufficient community
>> > > around some of the individual subprojects to bootstrap a happy PMC, and
>> > > there also may be good reason to keep some of these things together.
>> > >
>> > > I think reducing WS from >17 subprojects in a two-level container down
>> > > to
>> >
>> > a
>> >
>> > > single-level container for 6 common Web Service related components
>> > > would
>> >
>> > be
>> >
>> > > a pretty good accomplishment... and nothing prevents that from being an
>> > > intermediate step towards spinning off further TLPs down the road.
>> > >
>> > > I'm not saying I'm -1 to more TLPs, by the way, just exploring my
>> > > off-the-cuff impressions.
>> >
>> > Just want to say I completely agree with everything Glen said. Well put.
>> > It's also my understanding that getting WS down to a smaller, more
>> > concentrated project targeting shared WS technologies would be acceptable
>> > and
>> > really would no longer be an "umbrella" project.
>> >
>> > Dan
>> >
>> > > --Glen
>> > >
>> > > > I'd prefer to make a bunch of new TLPs - give people a chance to grow
>> > > > into new roles as well. All the ones you listed as "keep" should be
>> >
>> > TLPs
>> >
>> > > > IMO. There is no "minimum size" required to be a TLP.
>> > > >
>> > > > Sanjiva.
>> > > >
>> > > > On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <glen@thoughtcraft.com
>> > > >
>> > > > <ma...@thoughtcraft.com>> wrote:
>> > > > Hey y'all,
>> > > >
>> > > > So as per my earlier mail to the dev lists, we need to talk
>> >
>> > about...
>> >
>> > > > * Which subprojects should be promoted to TLPs?
>> > > > * Which subprojects should be migrated to the Attic?
>> > > > * What should the structure look like for what remains?
>> > > >
>> > > > Here's what we've got to work with.
>> > > >
>> > > > 1. Axiom (commons)
>> > > > 2. Neethi (commons)
>> > > > 3. XmlSchema (commons)
>> > > > 4. Tcpmon (commons)
>> > > > 5. Guththila (commons)
>> > > > 6. JaxMe
>> > > > 7. jUDDI
>> > > > 8. Scout
>> > > > 9. Muse
>> > > > 10.Woden
>> > > > 11.WSIF
>> > > > 12.WSS4J
>> > > > 13.XMLRPC
>> > > >
>> > > > Let's talk Attic first. It seems WSIF and Muse have been pretty
>> >
>> > much
>> >
>> > > > inactive for some time now, so I'd propose we get the ball
>> > > > rolling with proposals to Attic both of those. JaxMe also seems
>> > > > ripe for the Attic.
>> > > >
>> > > > I think that it's pretty clear jUDDI and Scout should migrate
>> > > > together to a
>> > > > new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>> > > >
>> > > > Does anyone outside of Axis2/C use Guththila? If not, I'd
>> > > > suggest that migrate to Axis.
>> > > >
>> > > > Is there enough activity on XMLRPC to keep it alive? Jochen?
>> > > >
>> > > > Personally, I'd probably prefer to leave Axiom, Neethi,
>> > > > XmlSchema, and Tcpmon
>> > > > as subprojects of WS. I'd like to get rid of the "commons"
>> > > > layer, though,
>> > > > since I think the "new" WS project should itself be a set of
>> > > > commonly useful
>> > > > WS components. I know other ideas have been discussed for the
>> > > > commons stuff,
>> > > > so let's start that discussion and get the various opinions out
>> > > > on the table?
>> > > >
>> > > > That leaves Woden and WSS4J. Maybe Woden should stay in WS? As
>> >
>> > for
>> >
>> > > > WSS4J,
>> > > > I'm not sure if it should stay or become a TLP.
>> > > >
>> > > > So... what do you guys think?
>> > > >
>> > > > Thanks,
>> > > > --Glen
>> > > >
>> > > > P.S. Reminder - please fill out your sections of our board
>> > > > report for this
>> > > > month if appropriate!
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org
>> > http://dankulp.com/blog
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
Re: What's next for WS@Apache? Discuss.
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday 20 April 2010 8:49:02 pm Eran Chinthaka Withana wrote:
> Hi,
>
> I'm still confused about this re-org. People started this re-org, saying
> that the projects inside old-WS project was not manageable and no knows
> whats going inside all the projects. It was also mentioned that, since
> project X people also get to have a say in project Y (where X,Y are in WS),
> it will be a mess.
> Now why is this theory not applying to Axiom or XmlSchema projects. They
> are totally independent projects, that can be used beyond Axis2. Also some
> one concentrating only on XmlSchema or Axiom might not be interested in
> Axis2 project or its Karma. So why do you wanna put them inside Axis2 or
> new WS project, once again making the same mistake we had earlier?
>
> Axis2 depends on Axiom and XmlSchema, but not the other way round.
Well, Axiom I think has enough going on with it and enough activity that could
warrant it being a TLP. I really could go either way on that.
If you follow board@ at all (I know, most of you cannot follow it) and the
board meeting summaries and such, one of the other things that they are not
liking lately are the repeat "Nothing happened this quarter" reports occuring
over and over and over from the projects. For some of the smaller, less
active, projects (like XmlSchema), there would definitely be a danger of
falling into that path and the board would be concerned about the
oversight/community of such small projects.
So there needs to be some level of balance between being able to properly
provide oversight to everything going on in the project along with being able
to show there is an active and healthy community. The question is how to
achieve that? If a project like Axiom feels it can go it alone, I would
definitely support it (providing the new PMC is large enough), but I'd also
support keeping the smaller ones together until they are "ready" or until the
technology becomes irrelevant and it goes to the Attic.
Dan
> Dan, if new WS project should not be an umbrella project, then why do you
> think we should put Axiom/XmlSchema inside it?
>
> Thanks,
> Eran Chinthaka
>
> On Tue, Apr 20, 2010 at 8:34 PM, Daniel Kulp <dk...@apache.org> wrote:
> > On Tuesday 20 April 2010 7:54:27 pm Glen Daniels wrote:
> > > Hi Sanjiva,
> > >
> > > Sorry for the late reply.
> > >
> > > On 4/17/2010 3:37 AM, Sanjiva Weerawarana wrote:
> > > > Glen, your proposal amounts to having gone thru a lot of pain to have
> > > > simply TLPed Axis. The entire board prerogative was to break up WS
> > > > wasn't it?
> > >
> > > My interpretation was that it was more "WS is too big" than "WS should
> > > entirely go away". There are plenty of other projects at Apache that
> >
> > have
> >
> > > a reasonable number of subprojects, with related functions and
> >
> > development
> >
> > > communities. I'm not yet convinced that there is sufficient community
> > > around some of the individual subprojects to bootstrap a happy PMC, and
> > > there also may be good reason to keep some of these things together.
> > >
> > > I think reducing WS from >17 subprojects in a two-level container down
> > > to
> >
> > a
> >
> > > single-level container for 6 common Web Service related components
> > > would
> >
> > be
> >
> > > a pretty good accomplishment... and nothing prevents that from being an
> > > intermediate step towards spinning off further TLPs down the road.
> > >
> > > I'm not saying I'm -1 to more TLPs, by the way, just exploring my
> > > off-the-cuff impressions.
> >
> > Just want to say I completely agree with everything Glen said. Well put.
> > It's also my understanding that getting WS down to a smaller, more
> > concentrated project targeting shared WS technologies would be acceptable
> > and
> > really would no longer be an "umbrella" project.
> >
> > Dan
> >
> > > --Glen
> > >
> > > > I'd prefer to make a bunch of new TLPs - give people a chance to grow
> > > > into new roles as well. All the ones you listed as "keep" should be
> >
> > TLPs
> >
> > > > IMO. There is no "minimum size" required to be a TLP.
> > > >
> > > > Sanjiva.
> > > >
> > > > On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <glen@thoughtcraft.com
> > > >
> > > > <ma...@thoughtcraft.com>> wrote:
> > > > Hey y'all,
> > > >
> > > > So as per my earlier mail to the dev lists, we need to talk
> >
> > about...
> >
> > > > * Which subprojects should be promoted to TLPs?
> > > > * Which subprojects should be migrated to the Attic?
> > > > * What should the structure look like for what remains?
> > > >
> > > > Here's what we've got to work with.
> > > >
> > > > 1. Axiom (commons)
> > > > 2. Neethi (commons)
> > > > 3. XmlSchema (commons)
> > > > 4. Tcpmon (commons)
> > > > 5. Guththila (commons)
> > > > 6. JaxMe
> > > > 7. jUDDI
> > > > 8. Scout
> > > > 9. Muse
> > > > 10.Woden
> > > > 11.WSIF
> > > > 12.WSS4J
> > > > 13.XMLRPC
> > > >
> > > > Let's talk Attic first. It seems WSIF and Muse have been pretty
> >
> > much
> >
> > > > inactive for some time now, so I'd propose we get the ball
> > > > rolling with proposals to Attic both of those. JaxMe also seems
> > > > ripe for the Attic.
> > > >
> > > > I think that it's pretty clear jUDDI and Scout should migrate
> > > > together to a
> > > > new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
> > > >
> > > > Does anyone outside of Axis2/C use Guththila? If not, I'd
> > > > suggest that migrate to Axis.
> > > >
> > > > Is there enough activity on XMLRPC to keep it alive? Jochen?
> > > >
> > > > Personally, I'd probably prefer to leave Axiom, Neethi,
> > > > XmlSchema, and Tcpmon
> > > > as subprojects of WS. I'd like to get rid of the "commons"
> > > > layer, though,
> > > > since I think the "new" WS project should itself be a set of
> > > > commonly useful
> > > > WS components. I know other ideas have been discussed for the
> > > > commons stuff,
> > > > so let's start that discussion and get the various opinions out
> > > > on the table?
> > > >
> > > > That leaves Woden and WSS4J. Maybe Woden should stay in WS? As
> >
> > for
> >
> > > > WSS4J,
> > > > I'm not sure if it should stay or become a TLP.
> > > >
> > > > So... what do you guys think?
> > > >
> > > > Thanks,
> > > > --Glen
> > > >
> > > > P.S. Reminder - please fill out your sections of our board
> > > > report for this
> > > > month if appropriate!
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://dankulp.com/blog
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: What's next for WS@Apache? Discuss.
Posted by Benson Margulies <bi...@gmail.com>.
Instead of debating principle, I would suggest the following procedure.
To turn a sub(sub)project into a TLP, it takes a board resolution. The
standard procedure is for the existing PMC to vote to send recommend the new
TLP resolution to the board.
I, for one, will vote +1 for any plausible proposed TLP resolution, which
(to me) means any resolution with a reasonable critical mass of volunteer
PMC members.
For practical reasons, that mass had better be at least 3, and I'm a little
squeamish if the number is less than 5, and I do wonder what the board
thinks. So, let's find out what the board thinks, and then we'll see what of
the bits and pieces can muster the necessary numbers.
On Tue, Apr 20, 2010 at 8:49 PM, Eran Chinthaka Withana <
eran.chinthaka@gmail.com> wrote:
> Hi,
>
> I'm still confused about this re-org. People started this re-org, saying
> that the projects inside old-WS project was not manageable and no knows
> whats going inside all the projects. It was also mentioned that, since
> project X people also get to have a say in project Y (where X,Y are in WS),
> it will be a mess.
> Now why is this theory not applying to Axiom or XmlSchema projects. They
> are totally independent projects, that can be used beyond Axis2. Also some
> one concentrating only on XmlSchema or Axiom might not be interested in
> Axis2 project or its Karma. So why do you wanna put them inside Axis2 or new
> WS project, once again making the same mistake we had earlier?
>
> Axis2 depends on Axiom and XmlSchema, but not the other way round.
>
> Dan, if new WS project should not be an umbrella project, then why do you
> think we should put Axiom/XmlSchema inside it?
>
> Thanks,
> Eran Chinthaka
>
>
>
> On Tue, Apr 20, 2010 at 8:34 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>> On Tuesday 20 April 2010 7:54:27 pm Glen Daniels wrote:
>> > Hi Sanjiva,
>> >
>> > Sorry for the late reply.
>> >
>> > On 4/17/2010 3:37 AM, Sanjiva Weerawarana wrote:
>> > > Glen, your proposal amounts to having gone thru a lot of pain to have
>> > > simply TLPed Axis. The entire board prerogative was to break up WS
>> > > wasn't it?
>> >
>> > My interpretation was that it was more "WS is too big" than "WS should
>> > entirely go away". There are plenty of other projects at Apache that
>> have
>> > a reasonable number of subprojects, with related functions and
>> development
>> > communities. I'm not yet convinced that there is sufficient community
>> > around some of the individual subprojects to bootstrap a happy PMC, and
>> > there also may be good reason to keep some of these things together.
>> >
>> > I think reducing WS from >17 subprojects in a two-level container down
>> to a
>> > single-level container for 6 common Web Service related components would
>> be
>> > a pretty good accomplishment... and nothing prevents that from being an
>> > intermediate step towards spinning off further TLPs down the road.
>> >
>> > I'm not saying I'm -1 to more TLPs, by the way, just exploring my
>> > off-the-cuff impressions.
>>
>> Just want to say I completely agree with everything Glen said. Well put.
>> It's also my understanding that getting WS down to a smaller, more
>> concentrated project targeting shared WS technologies would be acceptable
>> and
>> really would no longer be an "umbrella" project.
>>
>> Dan
>>
>>
>>
>> > --Glen
>> >
>> > > I'd prefer to make a bunch of new TLPs - give people a chance to grow
>> > > into new roles as well. All the ones you listed as "keep" should be
>> TLPs
>> > > IMO. There is no "minimum size" required to be a TLP.
>> > >
>> > > Sanjiva.
>> > >
>> > > On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <glen@thoughtcraft.com
>> > >
>> > > <ma...@thoughtcraft.com>> wrote:
>> > > Hey y'all,
>> > >
>> > > So as per my earlier mail to the dev lists, we need to talk
>> about...
>> > >
>> > > * Which subprojects should be promoted to TLPs?
>> > > * Which subprojects should be migrated to the Attic?
>> > > * What should the structure look like for what remains?
>> > >
>> > > Here's what we've got to work with.
>> > >
>> > > 1. Axiom (commons)
>> > > 2. Neethi (commons)
>> > > 3. XmlSchema (commons)
>> > > 4. Tcpmon (commons)
>> > > 5. Guththila (commons)
>> > > 6. JaxMe
>> > > 7. jUDDI
>> > > 8. Scout
>> > > 9. Muse
>> > > 10.Woden
>> > > 11.WSIF
>> > > 12.WSS4J
>> > > 13.XMLRPC
>> > >
>> > > Let's talk Attic first. It seems WSIF and Muse have been pretty
>> much
>> > > inactive for some time now, so I'd propose we get the ball rolling
>> > > with proposals to Attic both of those. JaxMe also seems ripe for
>> > > the Attic.
>> > >
>> > > I think that it's pretty clear jUDDI and Scout should migrate
>> > > together to a
>> > > new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>> > >
>> > > Does anyone outside of Axis2/C use Guththila? If not, I'd suggest
>> > > that migrate to Axis.
>> > >
>> > > Is there enough activity on XMLRPC to keep it alive? Jochen?
>> > >
>> > > Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema,
>> > > and Tcpmon
>> > > as subprojects of WS. I'd like to get rid of the "commons" layer,
>> > > though,
>> > > since I think the "new" WS project should itself be a set of
>> > > commonly useful
>> > > WS components. I know other ideas have been discussed for the
>> > > commons stuff,
>> > > so let's start that discussion and get the various opinions out on
>> > > the table?
>> > >
>> > > That leaves Woden and WSS4J. Maybe Woden should stay in WS? As
>> for
>> > > WSS4J,
>> > > I'm not sure if it should stay or become a TLP.
>> > >
>> > > So... what do you guys think?
>> > >
>> > > Thanks,
>> > > --Glen
>> > >
>> > > P.S. Reminder - please fill out your sections of our board report
>> > > for this
>> > > month if appropriate!
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://dankulp.com/blog
>>
>
>
Re: What's next for WS@Apache? Discuss.
Posted by Eran Chinthaka Withana <er...@gmail.com>.
Hi,
I'm still confused about this re-org. People started this re-org, saying
that the projects inside old-WS project was not manageable and no knows
whats going inside all the projects. It was also mentioned that, since
project X people also get to have a say in project Y (where X,Y are in WS),
it will be a mess.
Now why is this theory not applying to Axiom or XmlSchema projects. They are
totally independent projects, that can be used beyond Axis2. Also some one
concentrating only on XmlSchema or Axiom might not be interested in Axis2
project or its Karma. So why do you wanna put them inside Axis2 or new WS
project, once again making the same mistake we had earlier?
Axis2 depends on Axiom and XmlSchema, but not the other way round.
Dan, if new WS project should not be an umbrella project, then why do you
think we should put Axiom/XmlSchema inside it?
Thanks,
Eran Chinthaka
On Tue, Apr 20, 2010 at 8:34 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Tuesday 20 April 2010 7:54:27 pm Glen Daniels wrote:
> > Hi Sanjiva,
> >
> > Sorry for the late reply.
> >
> > On 4/17/2010 3:37 AM, Sanjiva Weerawarana wrote:
> > > Glen, your proposal amounts to having gone thru a lot of pain to have
> > > simply TLPed Axis. The entire board prerogative was to break up WS
> > > wasn't it?
> >
> > My interpretation was that it was more "WS is too big" than "WS should
> > entirely go away". There are plenty of other projects at Apache that
> have
> > a reasonable number of subprojects, with related functions and
> development
> > communities. I'm not yet convinced that there is sufficient community
> > around some of the individual subprojects to bootstrap a happy PMC, and
> > there also may be good reason to keep some of these things together.
> >
> > I think reducing WS from >17 subprojects in a two-level container down to
> a
> > single-level container for 6 common Web Service related components would
> be
> > a pretty good accomplishment... and nothing prevents that from being an
> > intermediate step towards spinning off further TLPs down the road.
> >
> > I'm not saying I'm -1 to more TLPs, by the way, just exploring my
> > off-the-cuff impressions.
>
> Just want to say I completely agree with everything Glen said. Well put.
> It's also my understanding that getting WS down to a smaller, more
> concentrated project targeting shared WS technologies would be acceptable
> and
> really would no longer be an "umbrella" project.
>
> Dan
>
>
>
> > --Glen
> >
> > > I'd prefer to make a bunch of new TLPs - give people a chance to grow
> > > into new roles as well. All the ones you listed as "keep" should be
> TLPs
> > > IMO. There is no "minimum size" required to be a TLP.
> > >
> > > Sanjiva.
> > >
> > > On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <glen@thoughtcraft.com
> > >
> > > <ma...@thoughtcraft.com>> wrote:
> > > Hey y'all,
> > >
> > > So as per my earlier mail to the dev lists, we need to talk
> about...
> > >
> > > * Which subprojects should be promoted to TLPs?
> > > * Which subprojects should be migrated to the Attic?
> > > * What should the structure look like for what remains?
> > >
> > > Here's what we've got to work with.
> > >
> > > 1. Axiom (commons)
> > > 2. Neethi (commons)
> > > 3. XmlSchema (commons)
> > > 4. Tcpmon (commons)
> > > 5. Guththila (commons)
> > > 6. JaxMe
> > > 7. jUDDI
> > > 8. Scout
> > > 9. Muse
> > > 10.Woden
> > > 11.WSIF
> > > 12.WSS4J
> > > 13.XMLRPC
> > >
> > > Let's talk Attic first. It seems WSIF and Muse have been pretty
> much
> > > inactive for some time now, so I'd propose we get the ball rolling
> > > with proposals to Attic both of those. JaxMe also seems ripe for
> > > the Attic.
> > >
> > > I think that it's pretty clear jUDDI and Scout should migrate
> > > together to a
> > > new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
> > >
> > > Does anyone outside of Axis2/C use Guththila? If not, I'd suggest
> > > that migrate to Axis.
> > >
> > > Is there enough activity on XMLRPC to keep it alive? Jochen?
> > >
> > > Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema,
> > > and Tcpmon
> > > as subprojects of WS. I'd like to get rid of the "commons" layer,
> > > though,
> > > since I think the "new" WS project should itself be a set of
> > > commonly useful
> > > WS components. I know other ideas have been discussed for the
> > > commons stuff,
> > > so let's start that discussion and get the various opinions out on
> > > the table?
> > >
> > > That leaves Woden and WSS4J. Maybe Woden should stay in WS? As
> for
> > > WSS4J,
> > > I'm not sure if it should stay or become a TLP.
> > >
> > > So... what do you guys think?
> > >
> > > Thanks,
> > > --Glen
> > >
> > > P.S. Reminder - please fill out your sections of our board report
> > > for this
> > > month if appropriate!
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
Re: What's next for WS@Apache? Discuss.
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday 20 April 2010 7:54:27 pm Glen Daniels wrote:
> Hi Sanjiva,
>
> Sorry for the late reply.
>
> On 4/17/2010 3:37 AM, Sanjiva Weerawarana wrote:
> > Glen, your proposal amounts to having gone thru a lot of pain to have
> > simply TLPed Axis. The entire board prerogative was to break up WS
> > wasn't it?
>
> My interpretation was that it was more "WS is too big" than "WS should
> entirely go away". There are plenty of other projects at Apache that have
> a reasonable number of subprojects, with related functions and development
> communities. I'm not yet convinced that there is sufficient community
> around some of the individual subprojects to bootstrap a happy PMC, and
> there also may be good reason to keep some of these things together.
>
> I think reducing WS from >17 subprojects in a two-level container down to a
> single-level container for 6 common Web Service related components would be
> a pretty good accomplishment... and nothing prevents that from being an
> intermediate step towards spinning off further TLPs down the road.
>
> I'm not saying I'm -1 to more TLPs, by the way, just exploring my
> off-the-cuff impressions.
Just want to say I completely agree with everything Glen said. Well put.
It's also my understanding that getting WS down to a smaller, more
concentrated project targeting shared WS technologies would be acceptable and
really would no longer be an "umbrella" project.
Dan
> --Glen
>
> > I'd prefer to make a bunch of new TLPs - give people a chance to grow
> > into new roles as well. All the ones you listed as "keep" should be TLPs
> > IMO. There is no "minimum size" required to be a TLP.
> >
> > Sanjiva.
> >
> > On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <glen@thoughtcraft.com
> >
> > <ma...@thoughtcraft.com>> wrote:
> > Hey y'all,
> >
> > So as per my earlier mail to the dev lists, we need to talk about...
> >
> > * Which subprojects should be promoted to TLPs?
> > * Which subprojects should be migrated to the Attic?
> > * What should the structure look like for what remains?
> >
> > Here's what we've got to work with.
> >
> > 1. Axiom (commons)
> > 2. Neethi (commons)
> > 3. XmlSchema (commons)
> > 4. Tcpmon (commons)
> > 5. Guththila (commons)
> > 6. JaxMe
> > 7. jUDDI
> > 8. Scout
> > 9. Muse
> > 10.Woden
> > 11.WSIF
> > 12.WSS4J
> > 13.XMLRPC
> >
> > Let's talk Attic first. It seems WSIF and Muse have been pretty much
> > inactive for some time now, so I'd propose we get the ball rolling
> > with proposals to Attic both of those. JaxMe also seems ripe for
> > the Attic.
> >
> > I think that it's pretty clear jUDDI and Scout should migrate
> > together to a
> > new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
> >
> > Does anyone outside of Axis2/C use Guththila? If not, I'd suggest
> > that migrate to Axis.
> >
> > Is there enough activity on XMLRPC to keep it alive? Jochen?
> >
> > Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema,
> > and Tcpmon
> > as subprojects of WS. I'd like to get rid of the "commons" layer,
> > though,
> > since I think the "new" WS project should itself be a set of
> > commonly useful
> > WS components. I know other ideas have been discussed for the
> > commons stuff,
> > so let's start that discussion and get the various opinions out on
> > the table?
> >
> > That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for
> > WSS4J,
> > I'm not sure if it should stay or become a TLP.
> >
> > So... what do you guys think?
> >
> > Thanks,
> > --Glen
> >
> > P.S. Reminder - please fill out your sections of our board report
> > for this
> > month if appropriate!
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: What's next for WS@Apache? Discuss.
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Sanjiva,
Sorry for the late reply.
On 4/17/2010 3:37 AM, Sanjiva Weerawarana wrote:
> Glen, your proposal amounts to having gone thru a lot of pain to have
> simply TLPed Axis. The entire board prerogative was to break up WS
> wasn't it?
My interpretation was that it was more "WS is too big" than "WS should
entirely go away". There are plenty of other projects at Apache that have a
reasonable number of subprojects, with related functions and development
communities. I'm not yet convinced that there is sufficient community around
some of the individual subprojects to bootstrap a happy PMC, and there also
may be good reason to keep some of these things together.
I think reducing WS from >17 subprojects in a two-level container down to a
single-level container for 6 common Web Service related components would be a
pretty good accomplishment... and nothing prevents that from being an
intermediate step towards spinning off further TLPs down the road.
I'm not saying I'm -1 to more TLPs, by the way, just exploring my
off-the-cuff impressions.
--Glen
> I'd prefer to make a bunch of new TLPs - give people a chance to grow
> into new roles as well. All the ones you listed as "keep" should be TLPs
> IMO. There is no "minimum size" required to be a TLP.
>
> Sanjiva.
>
> On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <glen@thoughtcraft.com
> <ma...@thoughtcraft.com>> wrote:
>
> Hey y'all,
>
> So as per my earlier mail to the dev lists, we need to talk about...
>
> * Which subprojects should be promoted to TLPs?
> * Which subprojects should be migrated to the Attic?
> * What should the structure look like for what remains?
>
> Here's what we've got to work with.
>
> 1. Axiom (commons)
> 2. Neethi (commons)
> 3. XmlSchema (commons)
> 4. Tcpmon (commons)
> 5. Guththila (commons)
> 6. JaxMe
> 7. jUDDI
> 8. Scout
> 9. Muse
> 10.Woden
> 11.WSIF
> 12.WSS4J
> 13.XMLRPC
>
> Let's talk Attic first. It seems WSIF and Muse have been pretty much
> inactive for some time now, so I'd propose we get the ball rolling with
> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>
> I think that it's pretty clear jUDDI and Scout should migrate
> together to a
> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>
> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> migrate to Axis.
>
> Is there enough activity on XMLRPC to keep it alive? Jochen?
>
> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema,
> and Tcpmon
> as subprojects of WS. I'd like to get rid of the "commons" layer,
> though,
> since I think the "new" WS project should itself be a set of
> commonly useful
> WS components. I know other ideas have been discussed for the
> commons stuff,
> so let's start that discussion and get the various opinions out on
> the table?
>
> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for
> WSS4J,
> I'm not sure if it should stay or become a TLP.
>
> So... what do you guys think?
>
> Thanks,
> --Glen
>
> P.S. Reminder - please fill out your sections of our board report
> for this
> month if appropriate!
>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Director; Sahana Software Foundation; http://www.sahanafoundation.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
Re: What's next for WS@Apache? Discuss.
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Glen, your proposal amounts to having gone thru a lot of pain to have simply
TLPed Axis. The entire board prerogative was to break up WS wasn't it?
I'd prefer to make a bunch of new TLPs - give people a chance to grow into
new roles as well. All the ones you listed as "keep" should be TLPs IMO.
There is no "minimum size" required to be a TLP.
Sanjiva.
On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hey y'all,
>
> So as per my earlier mail to the dev lists, we need to talk about...
>
> * Which subprojects should be promoted to TLPs?
> * Which subprojects should be migrated to the Attic?
> * What should the structure look like for what remains?
>
> Here's what we've got to work with.
>
> 1. Axiom (commons)
> 2. Neethi (commons)
> 3. XmlSchema (commons)
> 4. Tcpmon (commons)
> 5. Guththila (commons)
> 6. JaxMe
> 7. jUDDI
> 8. Scout
> 9. Muse
> 10.Woden
> 11.WSIF
> 12.WSS4J
> 13.XMLRPC
>
> Let's talk Attic first. It seems WSIF and Muse have been pretty much
> inactive for some time now, so I'd propose we get the ball rolling with
> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>
> I think that it's pretty clear jUDDI and Scout should migrate together to a
> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>
> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> migrate to Axis.
>
> Is there enough activity on XMLRPC to keep it alive? Jochen?
>
> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and
> Tcpmon
> as subprojects of WS. I'd like to get rid of the "commons" layer, though,
> since I think the "new" WS project should itself be a set of commonly
> useful
> WS components. I know other ideas have been discussed for the commons
> stuff,
> so let's start that discussion and get the various opinions out on the
> table?
>
> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for WSS4J,
> I'm not sure if it should stay or become a TLP.
>
> So... what do you guys think?
>
> Thanks,
> --Glen
>
> P.S. Reminder - please fill out your sections of our board report for this
> month if appropriate!
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Director; Sahana Software Foundation; http://www.sahanafoundation.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
Re: What's next for WS@Apache? Discuss.
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Apr 16, 2010 at 9:06 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I don't have a binding vote, but my thoughts.....
>
> (one more thing you MIGHT want to consider is contacting the 100+
> committer/PMC members and finding which could be made emeritus to cut down
> the
> list a little bit)
>
> On Wednesday 14 April 2010 11:08:17 pm Glen Daniels wrote:
> > Hey y'all,
> >
> > So as per my earlier mail to the dev lists, we need to talk about...
> >
> > * Which subprojects should be promoted to TLPs?
> > * Which subprojects should be migrated to the Attic?
> > * What should the structure look like for what remains?
> >
> > Here's what we've got to work with.
> >
> > 1. Axiom (commons)
> > 2. Neethi (commons)
> > 3. XmlSchema (commons)
> > 4. Tcpmon (commons)
> > 5. Guththila (commons)
> > 6. JaxMe
> > 7. jUDDI
> > 8. Scout
> > 9. Muse
> > 10.Woden
> > 11.WSIF
> > 12.WSS4J
> > 13.XMLRPC
> >
> > Let's talk Attic first. It seems WSIF and Muse have been pretty much
> > inactive for some time now, so I'd propose we get the ball rolling with
> > proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>
> That makes sense to me.
>
>
> > I think that it's pretty clear jUDDI and Scout should migrate together to
> a
> > new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>
> +1
>
>
> > Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> > migrate to Axis.
>
> +1
>
>
> > Is there enough activity on XMLRPC to keep it alive? Jochen?
>
> As long as there are people using it that may require some fixes or support
> and someone is willing to support them if required, keeping it in WS for
> now
> is probably OK. There was another project (Excalibur) that recently
> discussed this and came to the same conclusion.
>
> > Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and
> > Tcpmon as subprojects of WS. I'd like to get rid of the "commons" layer,
> > though, since I think the "new" WS project should itself be a set of
> > commonly useful WS components.
>
> +1
>
> > I know other ideas have been discussed for
> > the commons stuff, so let's start that discussion and get the various
> > opinions out on the table?
> >
> > That leaves Woden and WSS4J. Maybe Woden should stay in WS?
>
> +1
>
+ 1 to keep Woden under WS.
Also I think it's time to modify WS PMC after these changes.
Thanks,
>
> > As for WSS4J, I'm not sure if it should stay or become a TLP.
> > So... what do you guys think?
>
> Hmmm... I don't think there really is enough there for TLP. Another
> "idea"
> MAY be to merge it into Santuario with the thought that a closer
> collaboration
> with the lower level libraries may yield some interesting results. That
> said, I don't think the Santuario community is exactly the most healthy at
> this point either so definitely a concern about that as well. I guess
> keeping it in WS makes sense.
>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: What's next for WS@Apache? Discuss.
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday 20 April 2010 12:56:14 am Samisa Abeysinghe wrote:
> On Fri, Apr 16, 2010 at 9:06 PM, Daniel Kulp <dk...@apache.org> wrote:
> > I don't have a binding vote, but my thoughts.....
> >
> > (one more thing you MIGHT want to consider is contacting the 100+
> > committer/PMC members and finding which could be made emeritus to cut
> > down the
> > list a little bit)
>
> I thought in the process of making Axis TLP this happened. Only those
> showed interest was given commit rights.
For the Axis TLP, yes. Only those from WS that were interested were granted
rights on Axis. However, the list for WS remains how it was. What I was
suggesting was to try and get the WS list down a bit.
Dan
>
> Samisa...
>
> --
> blog: http://samisa-abeysinghe.blogspot.com/
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: What's next for WS@Apache? Discuss.
Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Fri, Apr 16, 2010 at 9:06 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I don't have a binding vote, but my thoughts.....
>
> (one more thing you MIGHT want to consider is contacting the 100+
> committer/PMC members and finding which could be made emeritus to cut down
> the
> list a little bit)
>
I thought in the process of making Axis TLP this happened. Only those showed
interest was given commit rights.
Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/
Re: What's next for WS@Apache? Discuss.
Posted by Daniel Kulp <dk...@apache.org>.
I don't have a binding vote, but my thoughts.....
(one more thing you MIGHT want to consider is contacting the 100+
committer/PMC members and finding which could be made emeritus to cut down the
list a little bit)
On Wednesday 14 April 2010 11:08:17 pm Glen Daniels wrote:
> Hey y'all,
>
> So as per my earlier mail to the dev lists, we need to talk about...
>
> * Which subprojects should be promoted to TLPs?
> * Which subprojects should be migrated to the Attic?
> * What should the structure look like for what remains?
>
> Here's what we've got to work with.
>
> 1. Axiom (commons)
> 2. Neethi (commons)
> 3. XmlSchema (commons)
> 4. Tcpmon (commons)
> 5. Guththila (commons)
> 6. JaxMe
> 7. jUDDI
> 8. Scout
> 9. Muse
> 10.Woden
> 11.WSIF
> 12.WSS4J
> 13.XMLRPC
>
> Let's talk Attic first. It seems WSIF and Muse have been pretty much
> inactive for some time now, so I'd propose we get the ball rolling with
> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
That makes sense to me.
> I think that it's pretty clear jUDDI and Scout should migrate together to a
> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
+1
> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> migrate to Axis.
+1
> Is there enough activity on XMLRPC to keep it alive? Jochen?
As long as there are people using it that may require some fixes or support
and someone is willing to support them if required, keeping it in WS for now
is probably OK. There was another project (Excalibur) that recently
discussed this and came to the same conclusion.
> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and
> Tcpmon as subprojects of WS. I'd like to get rid of the "commons" layer,
> though, since I think the "new" WS project should itself be a set of
> commonly useful WS components.
+1
> I know other ideas have been discussed for
> the commons stuff, so let's start that discussion and get the various
> opinions out on the table?
>
> That leaves Woden and WSS4J. Maybe Woden should stay in WS?
+1
> As for WSS4J, I'm not sure if it should stay or become a TLP.
> So... what do you guys think?
Hmmm... I don't think there really is enough there for TLP. Another "idea"
MAY be to merge it into Santuario with the thought that a closer collaboration
with the lower level libraries may yield some interesting results. That
said, I don't think the Santuario community is exactly the most healthy at
this point either so definitely a concern about that as well. I guess
keeping it in WS makes sense.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: What's next for WS@Apache? Discuss.
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Thu, Apr 15, 2010 at 5:08 AM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Is there enough activity on XMLRPC to keep it alive? Jochen?
There is no new development to expect, but I'd consider the mailing list active.
Jochen
--
Germanys national anthem is the most boring in the world - how telling!
Re: What's next for WS@Apache? Discuss.
Posted by Amila Suriarachchi <am...@gmail.com>.
+1 to make both Axiom and XmlSchema as TLPs.
I have been contributing both projects in terms of fixing axis2 related
issues. So I would like to join both.
thanks,
Amila.
On Mon, Apr 19, 2010 at 7:36 PM, Benson Margulies <bi...@gmail.com>wrote:
> At the risk of seeming pedantic, I'm claim that there is a minimum size for
> a TLP. 3. You need three votes to make a release.
>
> XmlSchema is a problem. The board doesn't like umbrellas. There are, AFAIK,
> two of us who are willing to touch it. Yet various things depend on it. The
> one I know best is, of course, CXF.
>
> ASF doesn't have a wonderful structural solution to this situation.
>
> I wonder if we could form a PMC by getting someone from Axis to volunteer
> to join Dan and myself.
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: What's next for WS@Apache? Discuss.
Posted by Benson Margulies <bi...@gmail.com>.
At the risk of seeming pedantic, I'm claim that there is a minimum size for
a TLP. 3. You need three votes to make a release.
XmlSchema is a problem. The board doesn't like umbrellas. There are, AFAIK,
two of us who are willing to touch it. Yet various things depend on it. The
one I know best is, of course, CXF.
ASF doesn't have a wonderful structural solution to this situation.
I wonder if we could form a PMC by getting someone from Axis to volunteer to
join Dan and myself.
Re: What's next for WS@Apache? Discuss.
Posted by Kurt T Stam <ku...@gmail.com>.
Glen Daniels wrote:
> Hm, mostly crickets chirping.
>
> Should we just Attic everything then? :)
>
> --G
>
> On Wed, 14 Apr 2010 23:08:17 -0400, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
>
>> Hey y'all,
>>
>> So as per my earlier mail to the dev lists, we need to talk about...
>>
>> * Which subprojects should be promoted to TLPs?
>> * Which subprojects should be migrated to the Attic?
>> * What should the structure look like for what remains?
>>
>> Here's what we've got to work with.
>>
>> 1. Axiom (commons)
>> 2. Neethi (commons)
>> 3. XmlSchema (commons)
>> 4. Tcpmon (commons)
>> 5. Guththila (commons)
>> 6. JaxMe
>> 7. jUDDI
>> 8. Scout
>> 9. Muse
>> 10.Woden
>> 11.WSIF
>> 12.WSS4J
>> 13.XMLRPC
>>
>> Let's talk Attic first. It seems WSIF and Muse have been pretty much
>> inactive for some time now, so I'd propose we get the ball rolling with
>> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>>
>> I think that it's pretty clear jUDDI and Scout should migrate together
>>
> to a
>
>> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>>
That seems reasonable to me. We've been working fairly independently
from the other ws projects for a while now and Scout and jUDDI are
tightly related to eachother.
--Kurt
>> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
>> migrate to Axis.
>>
>> Is there enough activity on XMLRPC to keep it alive? Jochen?
>>
>> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and
>> Tcpmon
>> as subprojects of WS. I'd like to get rid of the "commons" layer,
>>
> though,
>
>> since I think the "new" WS project should itself be a set of commonly
>> useful
>> WS components. I know other ideas have been discussed for the commons
>> stuff,
>> so let's start that discussion and get the various opinions out on the
>> table?
>>
>> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for
>>
> WSS4J,
>
>> I'm not sure if it should stay or become a TLP.
>>
>> So... what do you guys think?
>>
>> Thanks,
>> --Glen
>>
>> P.S. Reminder - please fill out your sections of our board report for
>>
> this
>
>> month if appropriate!
>>
Re: What's next for WS@Apache? Discuss.
Posted by Benson Margulies <bi...@gmail.com>.
I am on vacation. expect a few remarks on xmlschema next week.
On Apr 16, 2010, at 10:28 AM, Glen Daniels <gl...@thoughtcraft.com>
wrote:
>
> Hm, mostly crickets chirping.
>
> Should we just Attic everything then? :)
>
> --G
>
> On Wed, 14 Apr 2010 23:08:17 -0400, Glen Daniels <glen@thoughtcraft.com
> >
> wrote:
>> Hey y'all,
>>
>> So as per my earlier mail to the dev lists, we need to talk about...
>>
>> * Which subprojects should be promoted to TLPs?
>> * Which subprojects should be migrated to the Attic?
>> * What should the structure look like for what remains?
>>
>> Here's what we've got to work with.
>>
>> 1. Axiom (commons)
>> 2. Neethi (commons)
>> 3. XmlSchema (commons)
>> 4. Tcpmon (commons)
>> 5. Guththila (commons)
>> 6. JaxMe
>> 7. jUDDI
>> 8. Scout
>> 9. Muse
>> 10.Woden
>> 11.WSIF
>> 12.WSS4J
>> 13.XMLRPC
>>
>> Let's talk Attic first. It seems WSIF and Muse have been pretty much
>> inactive for some time now, so I'd propose we get the ball rolling
>> with
>> proposals to Attic both of those. JaxMe also seems ripe for the
>> Attic.
>>
>> I think that it's pretty clear jUDDI and Scout should migrate
>> together
> to a
>> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>>
>> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest
>> that
>> migrate to Axis.
>>
>> Is there enough activity on XMLRPC to keep it alive? Jochen?
>>
>> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema,
>> and
>> Tcpmon
>> as subprojects of WS. I'd like to get rid of the "commons" layer,
> though,
>> since I think the "new" WS project should itself be a set of commonly
>> useful
>> WS components. I know other ideas have been discussed for the
>> commons
>> stuff,
>> so let's start that discussion and get the various opinions out on
>> the
>> table?
>>
>> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for
> WSS4J,
>> I'm not sure if it should stay or become a TLP.
>>
>> So... what do you guys think?
>>
>> Thanks,
>> --Glen
>>
>> P.S. Reminder - please fill out your sections of our board report
>> for
> this
>> month if appropriate!
Re: What's next for WS@Apache? Discuss.
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hm, mostly crickets chirping.
Should we just Attic everything then? :)
--G
On Wed, 14 Apr 2010 23:08:17 -0400, Glen Daniels <gl...@thoughtcraft.com>
wrote:
> Hey y'all,
>
> So as per my earlier mail to the dev lists, we need to talk about...
>
> * Which subprojects should be promoted to TLPs?
> * Which subprojects should be migrated to the Attic?
> * What should the structure look like for what remains?
>
> Here's what we've got to work with.
>
> 1. Axiom (commons)
> 2. Neethi (commons)
> 3. XmlSchema (commons)
> 4. Tcpmon (commons)
> 5. Guththila (commons)
> 6. JaxMe
> 7. jUDDI
> 8. Scout
> 9. Muse
> 10.Woden
> 11.WSIF
> 12.WSS4J
> 13.XMLRPC
>
> Let's talk Attic first. It seems WSIF and Muse have been pretty much
> inactive for some time now, so I'd propose we get the ball rolling with
> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>
> I think that it's pretty clear jUDDI and Scout should migrate together
to a
> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>
> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> migrate to Axis.
>
> Is there enough activity on XMLRPC to keep it alive? Jochen?
>
> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and
> Tcpmon
> as subprojects of WS. I'd like to get rid of the "commons" layer,
though,
> since I think the "new" WS project should itself be a set of commonly
> useful
> WS components. I know other ideas have been discussed for the commons
> stuff,
> so let's start that discussion and get the various opinions out on the
> table?
>
> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for
WSS4J,
> I'm not sure if it should stay or become a TLP.
>
> So... what do you guys think?
>
> Thanks,
> --Glen
>
> P.S. Reminder - please fill out your sections of our board report for
this
> month if appropriate!
Re: What's next for WS@Apache? Discuss.
Posted by Andreas Veithen <an...@gmail.com>.
I think that Axiom would be a good candidate for a TLP.
Andreas
On Thu, Apr 15, 2010 at 05:08, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hey y'all,
>
> So as per my earlier mail to the dev lists, we need to talk about...
>
> * Which subprojects should be promoted to TLPs?
> * Which subprojects should be migrated to the Attic?
> * What should the structure look like for what remains?
>
> Here's what we've got to work with.
>
> 1. Axiom (commons)
> 2. Neethi (commons)
> 3. XmlSchema (commons)
> 4. Tcpmon (commons)
> 5. Guththila (commons)
> 6. JaxMe
> 7. jUDDI
> 8. Scout
> 9. Muse
> 10.Woden
> 11.WSIF
> 12.WSS4J
> 13.XMLRPC
>
> Let's talk Attic first. It seems WSIF and Muse have been pretty much
> inactive for some time now, so I'd propose we get the ball rolling with
> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>
> I think that it's pretty clear jUDDI and Scout should migrate together to a
> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>
> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> migrate to Axis.
>
> Is there enough activity on XMLRPC to keep it alive? Jochen?
>
> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and Tcpmon
> as subprojects of WS. I'd like to get rid of the "commons" layer, though,
> since I think the "new" WS project should itself be a set of commonly useful
> WS components. I know other ideas have been discussed for the commons stuff,
> so let's start that discussion and get the various opinions out on the table?
>
> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for WSS4J,
> I'm not sure if it should stay or become a TLP.
>
> So... what do you guys think?
>
> Thanks,
> --Glen
>
> P.S. Reminder - please fill out your sections of our board report for this
> month if appropriate!
>
Re: What's next for WS@Apache? Discuss.
Posted by Samisa Abeysinghe <sa...@gmail.com>.
On Sat, Apr 17, 2010 at 8:09 AM, Supun Kamburugamuva <su...@gmail.com>wrote:
> Guththila is a module of Axis2/C project. Guththila code is in the Axis2/C
> code base. So we can remove it from the commons.
+1.
Samisa...
--
blog: http://samisa-abeysinghe.blogspot.com/
Re: What's next for WS@Apache? Discuss.
Posted by Supun Kamburugamuva <su...@gmail.com>.
Guththila is a module of Axis2/C project. Guththila code is in the Axis2/C
code base. So we can remove it from the commons.
Thanks,
Supun..
On Thu, Apr 15, 2010 at 8:38 AM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hey y'all,
>
> So as per my earlier mail to the dev lists, we need to talk about...
>
> * Which subprojects should be promoted to TLPs?
> * Which subprojects should be migrated to the Attic?
> * What should the structure look like for what remains?
>
> Here's what we've got to work with.
>
> 1. Axiom (commons)
> 2. Neethi (commons)
> 3. XmlSchema (commons)
> 4. Tcpmon (commons)
> 5. Guththila (commons)
> 6. JaxMe
> 7. jUDDI
> 8. Scout
> 9. Muse
> 10.Woden
> 11.WSIF
> 12.WSS4J
> 13.XMLRPC
>
> Let's talk Attic first. It seems WSIF and Muse have been pretty much
> inactive for some time now, so I'd propose we get the ball rolling with
> proposals to Attic both of those. JaxMe also seems ripe for the Attic.
>
> I think that it's pretty clear jUDDI and Scout should migrate together to a
> new TLP, Apache jUDDI, with Kurt as chair. Thoughts?
>
> Does anyone outside of Axis2/C use Guththila? If not, I'd suggest that
> migrate to Axis.
>
> Is there enough activity on XMLRPC to keep it alive? Jochen?
>
> Personally, I'd probably prefer to leave Axiom, Neethi, XmlSchema, and
> Tcpmon
> as subprojects of WS. I'd like to get rid of the "commons" layer, though,
> since I think the "new" WS project should itself be a set of commonly
> useful
> WS components. I know other ideas have been discussed for the commons
> stuff,
> so let's start that discussion and get the various opinions out on the
> table?
>
> That leaves Woden and WSS4J. Maybe Woden should stay in WS? As for WSS4J,
> I'm not sure if it should stay or become a TLP.
>
> So... what do you guys think?
>
> Thanks,
> --Glen
>
> P.S. Reminder - please fill out your sections of our board report for this
> month if appropriate!
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com