You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-dev@xml.apache.org by Jeff Turner <je...@apache.org> on 2002/10/18 19:05:47 UTC
[VOTE] New committers: Kevin Ross and Vladimir Bossicard
Calling a vote is the next logical step. So..
I propose Kevin Ross <Ke...@iVerticalLeap.com> and Vladimir
Bossicard <vl...@bossicard.com> as Xindice committers. My intensive
background checks[1] suggest they both know what they're doing, and both
seem willing to drive a currently "stale" Xindice forward.
[ ] Kevin Ross
[ ] Vladimir Bossicard
--Jeff
[1] Kevin I've seen around in Jakarta-land, and Vladimir likes Forrest so
he's okay.
On Fri, Oct 18, 2002 at 10:14:19AM -0500, Kevin Ross wrote:
> Who has commit that is active? I can't tell, which may be one reason
> why some call this 'stale', though I think there a lot of people that
> want to use this.
>
> Who is the lead of xindice? We need active committers, not just ones
> who are very busy and rarely make it around to commit patches and
> enhancements (though their work is appreciated of course). We need to
> add some, now, not later. Some people can commit at times, then get
> busy at other times. That's just a fact, so maybe we need a bigger pool
> of committers to maintain a steady stream of commits?
>
> I for one am getting tired of this project not advancing (in the public
> eye), when there is a tremendous amount of potential here. It feels
> like we are moving at the speed of the government.
>
> On a similar note:
> I have spoken with Joel Rosi-Schwartz, he and his wife Barbara
> Rosi-Schwartz, developed Attrezzo per Xindice. He has already stated
> his willingness to DONATE his very fine codebase for managing Xindice as
> a plugin for Eclipse. Based on that, I have refactored the code to
> org.apache.xindice.tools.ui.eclipse and committed it to my project's cvs
> for safe keeping at the moment. If a committer, as a representative of
> apache, would be so gratious to drop Joel.Rosi-Schwartz@Etish.org a line
> and ask for the donation, we can commit this code. I will make the doc
> page for the plugin, once someone gives Vladimir commit so he can update
> the site to forrest.
>
> Thank you. I don't mean to sound negative. I support this project, but
> I am very frustrated with the commit situation.
>
> -Kevin Ross
>
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by "Vladimir R. Bossicard" <vl...@bossicard.com>.
> [ X ] Kevin Ross
of course.
-Vladimir
--
Vladimir R. Bossicard
www.bossicard.com
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Kevin Ross <Ke...@iVerticalLeap.com>.
>
>
>[ x ] Vladimir Bossicard
>
I will politely bow out of voting for myself...
-Kevin
>
>
>--Jeff
>
>[1] Kevin I've seen around in Jakarta-land, and Vladimir likes Forrest so
>he's okay.
>
>On Fri, Oct 18, 2002 at 10:14:19AM -0500, Kevin Ross wrote:
>
>
>>Who has commit that is active? I can't tell, which may be one reason
>>why some call this 'stale', though I think there a lot of people that
>>want to use this.
>>
>>Who is the lead of xindice? We need active committers, not just ones
>>who are very busy and rarely make it around to commit patches and
>>enhancements (though their work is appreciated of course). We need to
>>add some, now, not later. Some people can commit at times, then get
>>busy at other times. That's just a fact, so maybe we need a bigger pool
>>of committers to maintain a steady stream of commits?
>>
>>I for one am getting tired of this project not advancing (in the public
>>eye), when there is a tremendous amount of potential here. It feels
>>like we are moving at the speed of the government.
>>
>>On a similar note:
>>I have spoken with Joel Rosi-Schwartz, he and his wife Barbara
>>Rosi-Schwartz, developed Attrezzo per Xindice. He has already stated
>>his willingness to DONATE his very fine codebase for managing Xindice as
>>a plugin for Eclipse. Based on that, I have refactored the code to
>>org.apache.xindice.tools.ui.eclipse and committed it to my project's cvs
>>for safe keeping at the moment. If a committer, as a representative of
>>apache, would be so gratious to drop Joel.Rosi-Schwartz@Etish.org a line
>>and ask for the donation, we can commit this code. I will make the doc
>>page for the plugin, once someone gives Vladimir commit so he can update
>>the site to forrest.
>>
>>Thank you. I don't mean to sound negative. I support this project, but
>>I am very frustrated with the commit situation.
>>
>>-Kevin Ross
>>
>>
>>
>
>
>
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by "Vladimir R. Bossicard" <vl...@bossicard.com>.
Hi Kurt,
> a new interactive command-line admin (similar to
> MySQL) that may replace the existing admin tools.
If you are a committer, could you cvs add your work into the scratchpad
folder? Other will be able to help (code or documentation).
Thanks
-Vladimir
--
Vladimir R. Bossicard
www.bossicard.com
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Kurt Ward <ku...@yahoo.com>.
+1 for both.
I am still around. Since I moved across the country alot has happened and I
have not been able to contribute as much as I have in the past. I think
this will change pretty soon and I have been working on the XML-RPC stuff a
little bit as well as a new interactive command-line admin (similar to
MySQL) that may replace the existing admin tools.
Kurt
----- Original Message -----
From: "Jeff Turner" <je...@apache.org>
To: <xi...@xml.apache.org>
Sent: Friday, October 18, 2002 1:05 PM
Subject: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
> Calling a vote is the next logical step. So..
>
> I propose Kevin Ross <Ke...@iVerticalLeap.com> and Vladimir
> Bossicard <vl...@bossicard.com> as Xindice committers. My intensive
> background checks[1] suggest they both know what they're doing, and both
> seem willing to drive a currently "stale" Xindice forward.
>
> [ ] Kevin Ross
> [ ] Vladimir Bossicard
>
>
> --Jeff
>
> [1] Kevin I've seen around in Jakarta-land, and Vladimir likes Forrest so
> he's okay.
>
> On Fri, Oct 18, 2002 at 10:14:19AM -0500, Kevin Ross wrote:
> > Who has commit that is active? I can't tell, which may be one reason
> > why some call this 'stale', though I think there a lot of people that
> > want to use this.
> >
> > Who is the lead of xindice? We need active committers, not just ones
> > who are very busy and rarely make it around to commit patches and
> > enhancements (though their work is appreciated of course). We need to
> > add some, now, not later. Some people can commit at times, then get
> > busy at other times. That's just a fact, so maybe we need a bigger pool
> > of committers to maintain a steady stream of commits?
> >
> > I for one am getting tired of this project not advancing (in the public
> > eye), when there is a tremendous amount of potential here. It feels
> > like we are moving at the speed of the government.
> >
> > On a similar note:
> > I have spoken with Joel Rosi-Schwartz, he and his wife Barbara
> > Rosi-Schwartz, developed Attrezzo per Xindice. He has already stated
> > his willingness to DONATE his very fine codebase for managing Xindice as
> > a plugin for Eclipse. Based on that, I have refactored the code to
> > org.apache.xindice.tools.ui.eclipse and committed it to my project's cvs
> > for safe keeping at the moment. If a committer, as a representative of
> > apache, would be so gratious to drop Joel.Rosi-Schwartz@Etish.org a line
> > and ask for the donation, we can commit this code. I will make the doc
> > page for the plugin, once someone gives Vladimir commit so he can update
> > the site to forrest.
> >
> > Thank you. I don't mean to sound negative. I support this project, but
> > I am very frustrated with the commit situation.
> >
> > -Kevin Ross
> >
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by James Bates <ja...@amplexor.com>.
Go ahead, +1 for Kevin and +1 for Vladimir.
On Friday 18 October 2002 19:05, Jeff Turner wrote:
> Calling a vote is the next logical step. So..
>
> I propose Kevin Ross <Ke...@iVerticalLeap.com> and Vladimir
> Bossicard <vl...@bossicard.com> as Xindice committers. My intensive
> background checks[1] suggest they both know what they're doing, and both
> seem willing to drive a currently "stale" Xindice forward.
>
> [ ] Kevin Ross
> [ ] Vladimir Bossicard
>
>
> --Jeff
>
> [1] Kevin I've seen around in Jakarta-land, and Vladimir likes Forrest so
> he's okay.
>
> On Fri, Oct 18, 2002 at 10:14:19AM -0500, Kevin Ross wrote:
> > Who has commit that is active? I can't tell, which may be one reason
> > why some call this 'stale', though I think there a lot of people that
> > want to use this.
> >
> > Who is the lead of xindice? We need active committers, not just ones
> > who are very busy and rarely make it around to commit patches and
> > enhancements (though their work is appreciated of course). We need to
> > add some, now, not later. Some people can commit at times, then get
> > busy at other times. That's just a fact, so maybe we need a bigger pool
> > of committers to maintain a steady stream of commits?
> >
> > I for one am getting tired of this project not advancing (in the public
> > eye), when there is a tremendous amount of potential here. It feels
> > like we are moving at the speed of the government.
> >
> > On a similar note:
> > I have spoken with Joel Rosi-Schwartz, he and his wife Barbara
> > Rosi-Schwartz, developed Attrezzo per Xindice. He has already stated
> > his willingness to DONATE his very fine codebase for managing Xindice as
> > a plugin for Eclipse. Based on that, I have refactored the code to
> > org.apache.xindice.tools.ui.eclipse and committed it to my project's cvs
> > for safe keeping at the moment. If a committer, as a representative of
> > apache, would be so gratious to drop Joel.Rosi-Schwartz@Etish.org a line
> > and ask for the donation, we can commit this code. I will make the doc
> > page for the plugin, once someone gives Vladimir commit so he can update
> > the site to forrest.
> >
> > Thank you. I don't mean to sound negative. I support this project, but
> > I am very frustrated with the commit situation.
> >
> > -Kevin Ross
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Kevin Ross <Ke...@iVerticalLeap.com>.
Please Tom, your presence is appreciated.
Tom Bradford wrote:
> On Friday, October 18, 2002, at 10:05 AM, Jeff Turner wrote:
>
>> Calling a vote is the next logical step. So..
>>
>> I propose Kevin Ross <Ke...@iVerticalLeap.com> and Vladimir
>> Bossicard <vl...@bossicard.com> as Xindice committers. My intensive
>> background checks[1] suggest they both know what they're doing, and both
>> seem willing to drive a currently "stale" Xindice forward.
>>
>> [+1 ] Kevin Ross
>> [+1 ] Vladimir Bossicard
>
>
> I also agree that the project has become stale, especially with Kimbro
> MIA. I had been trying to stay out of Kimbro's way, and let him run
> the project as he saw fit, but if the Xindice community would like, I
> can step back up to the project's helm, and help drive a bit more.
>
> --
> Tom Bradford - http://www.tbradford.org/
> CTO - The dbXML Group - http://www.dbxml.com/
> Apache Xindice - http://xml.apache.org/xindice
>
Re: Xindice architecture re:dbXML [WAS: New committers]
Posted by Tom Bradford <br...@dbxmlgroup.com>.
On Monday, October 21, 2002, at 06:38 AM, Murray Altheim wrote:
> Perhaps I'm reading this incorrectly, but I'm a bit confused. If the
> APIs you've published [1] are accurate to your current model, you still
> do seem to expose the possibility of reading and writing via DOM
> Documents,
> such as ContentClient.setDocument() and ContentClient.getDocument().
> Since
> that's essentially the functionality I need for XNode, I'm happy. I
> haven't really used XML:DB much at all, though I think it should be
> supported.
The client APIs do provide DOM/text/binary reading and writing, and
could probably easily be extended to support SAX. The internal APIs
are what all based on the DTSM APIs and binary. And yes, the
dependency on a proprietary DOM is also removed.
--
Tom Bradford - http://www.tbradford.org/
CTO - The dbXML Group - http://www.dbxml.com/
Apache Xindice - http://xml.apache.org/xindice
Xindice architecture re:dbXML [WAS: New committers]
Posted by Murray Altheim <m....@open.ac.uk>.
[pls. note change of subject line to match thread...]
Tom Bradford wrote:
[...]
> There are several things that I've done to the low-level dbXML engine
> that can benefit Xindice. For example, I've implemented the DTSM spec
> that I proposed quite a while ago (which people kindly ignored). It
> completely removes the dependency on a proprietary DOM, improves
> read/write performance by eliminating recursive treewalking, and makes
> converting between various XML APIs much easier. It does introduce some
> major changes to the internal APIs though, as you no longer read/write
> DOM Documents. This dependency wouldn't be exposed via the XML:DB APIs
> though.
Perhaps I'm reading this incorrectly, but I'm a bit confused. If the
APIs you've published [1] are accurate to your current model, you still
do seem to expose the possibility of reading and writing via DOM Documents,
such as ContentClient.setDocument() and ContentClient.getDocument(). Since
that's essentially the functionality I need for XNode, I'm happy. I
haven't really used XML:DB much at all, though I think it should be
supported.
If what you're saying is only that the dependency on a proprietary DOM
is removed (and I'm simply reading your wrong), I would certainly welcome
that.
> Another thing I've done is removed the multi-rooted aspects of the BTree
> system. Before, unique values would resolve to a pointer to a separate
> btree root that maintained an ordered list of entries (keys, locations)
> that matched that value. This indirection not only slowed things down,
> but bloated the index files for values that weren't repeated. The dbXML
> btrees have multi-part keys, eliminated the indirection and the bloat.
Are there any unresolved i18n issues here?
> Also, dbXML abandons the XML:DB API as its primary API. It still has an
> XML:DB driver, but I've developed a set of interfaces that more closely
> resemble the dbXML internal APIs (and to a degree, the Xindice internal
> APIs).
>
> Anyhow those are some of the things that can be introduced into the
> Xindice code.
Well, I'm as sensitive as anyone about stepping on toes, but if
Kimbro (who would likely the only one with toe issues) has no
problem with you becoming again a fundamental architect in Xindice,
I'm with those others that would certainly welcome you back, with
the trust in your abilities to keep the design true.
Murray
[1]
> FYI, The dbXML JavaDoc is available at:
> http://www.dbxml.com/api/index.html The related packages are in
> com.dbxml.db.client, com.dbxml.xml, and com.dbxml.db.core
......................................................................
Murray Altheim <http://kmi.open.ac.uk/people/murray/>
Knowledge Media Institute
The Open University, Milton Keynes, Bucks, MK7 6AA, UK
If you're the first person in a new territory,
you're likely to get shot at.
-- ma
RE: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Kevin Ross <Ke...@iVerticalLeap.com>.
Hello all,
I agree with Gianugo. We need someone with core experience. My
experience lies in architecting and implementing large scale business
systems. Though I have skills to offer, my experience does not fit what
is needed here, other than the extent to which I can contribute fixes
and solid code.
Tom, you are at the helm, and I feel that the community is behind you.
You clearly have the wherewithal to move the project forward, and we
will support any strategic or architectural choices you make.
Kevin
-----Original Message-----
From: Tom Bradford [mailto:bradford@dbxmlgroup.com]
Sent: Sunday, October 20, 2002 5:01 PM
To: xindice-dev@xml.apache.org
Subject: Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
On Sunday, October 20, 2002, at 02:39 PM, Gianugo Rabellino wrote:
>> I also agree that the project has become stale, especially with
>> Kimbro MIA. I had been trying to stay out of Kimbro's way, and let
>> him run the project as he saw fit, but if the Xindice community would
>> like, I can step back up to the project's helm, and help drive a bit
>> more.
>
> Tom, please, do so. I have a strong feeling that we need someone
> capable in the "core" Xindice development. I think that most of the
> committers (myself included) have little or no skills it what the core
> engine is about, we are mostly working (well, I'm not even talking
> about myself since I have very few spare cycles ATM) on "cosmetic"
> issues and side tools, but I see no ideas or proposals about the core:
> we need an architect with strong experience in data modeling to move
> forward, and you would perfectly fit in the picture.
There are several things that I've done to the low-level dbXML engine
that can benefit Xindice. For example, I've implemented the DTSM spec
that I proposed quite a while ago (which people kindly ignored). It
completely removes the dependency on a proprietary DOM, improves
read/write performance by eliminating recursive treewalking, and makes
converting between various XML APIs much easier. It does introduce
some major changes to the internal APIs though, as you no longer
read/write DOM Documents. This dependency wouldn't be exposed via the
XML:DB APIs though.
Another thing I've done is removed the multi-rooted aspects of the
BTree system. Before, unique values would resolve to a pointer to a
separate btree root that maintained an ordered list of entries (keys,
locations) that matched that value. This indirection not only slowed
things down, but bloated the index files for values that weren't
repeated. The dbXML btrees have multi-part keys, eliminated the
indirection and the bloat.
Also, dbXML abandons the XML:DB API as its primary API. It still has
an XML:DB driver, but I've developed a set of interfaces that more
closely resemble the dbXML internal APIs (and to a degree, the Xindice
internal APIs).
Anyhow those are some of the things that can be introduced into the
Xindice code.
FYI, The dbXML JavaDoc is available at:
http://www.dbxml.com/api/index.html The related packages are in
com.dbxml.db.client, com.dbxml.xml, and com.dbxml.db.core
--
Tom Bradford - http://www.tbradford.org/
CTO - The dbXML Group - http://www.dbxml.com/
Apache Xindice - http://xml.apache.org/xindice
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Tom Bradford <br...@dbxmlgroup.com>.
On Sunday, October 20, 2002, at 02:39 PM, Gianugo Rabellino wrote:
>> I also agree that the project has become stale, especially with
>> Kimbro MIA. I had been trying to stay out of Kimbro's way, and let
>> him run the project as he saw fit, but if the Xindice community would
>> like, I can step back up to the project's helm, and help drive a bit
>> more.
>
> Tom, please, do so. I have a strong feeling that we need someone
> capable in the "core" Xindice development. I think that most of the
> committers (myself included) have little or no skills it what the core
> engine is about, we are mostly working (well, I'm not even talking
> about myself since I have very few spare cycles ATM) on "cosmetic"
> issues and side tools, but I see no ideas or proposals about the core:
> we need an architect with strong experience in data modeling to move
> forward, and you would perfectly fit in the picture.
There are several things that I've done to the low-level dbXML engine
that can benefit Xindice. For example, I've implemented the DTSM spec
that I proposed quite a while ago (which people kindly ignored). It
completely removes the dependency on a proprietary DOM, improves
read/write performance by eliminating recursive treewalking, and makes
converting between various XML APIs much easier. It does introduce
some major changes to the internal APIs though, as you no longer
read/write DOM Documents. This dependency wouldn't be exposed via the
XML:DB APIs though.
Another thing I've done is removed the multi-rooted aspects of the
BTree system. Before, unique values would resolve to a pointer to a
separate btree root that maintained an ordered list of entries (keys,
locations) that matched that value. This indirection not only slowed
things down, but bloated the index files for values that weren't
repeated. The dbXML btrees have multi-part keys, eliminated the
indirection and the bloat.
Also, dbXML abandons the XML:DB API as its primary API. It still has
an XML:DB driver, but I've developed a set of interfaces that more
closely resemble the dbXML internal APIs (and to a degree, the Xindice
internal APIs).
Anyhow those are some of the things that can be introduced into the
Xindice code.
FYI, The dbXML JavaDoc is available at:
http://www.dbxml.com/api/index.html The related packages are in
com.dbxml.db.client, com.dbxml.xml, and com.dbxml.db.core
--
Tom Bradford - http://www.tbradford.org/
CTO - The dbXML Group - http://www.dbxml.com/
Apache Xindice - http://xml.apache.org/xindice
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Gianugo Rabellino <gi...@apache.org>.
Tom Bradford wrote:
> On Friday, October 18, 2002, at 10:05 AM, Jeff Turner wrote:
>
>> Calling a vote is the next logical step. So..
>>
>> I propose Kevin Ross <Ke...@iVerticalLeap.com> and Vladimir
>> Bossicard <vl...@bossicard.com> as Xindice committers. My intensive
>> background checks[1] suggest they both know what they're doing, and both
>> seem willing to drive a currently "stale" Xindice forward.
>>
>> [+1 ] Kevin Ross
>> [+1 ] Vladimir Bossicard
+1 for both, but also:
> I also agree that the project has become stale, especially with Kimbro
> MIA. I had been trying to stay out of Kimbro's way, and let him run the
> project as he saw fit, but if the Xindice community would like, I can
> step back up to the project's helm, and help drive a bit more.
Tom, please, do so. I have a strong feeling that we need someone capable
in the "core" Xindice development. I think that most of the committers
(myself included) have little or no skills it what the core engine is
about, we are mostly working (well, I'm not even talking about myself
since I have very few spare cycles ATM) on "cosmetic" issues and side
tools, but I see no ideas or proposals about the core: we need an
architect with strong experience in data modeling to move forward, and
you would perfectly fit in the picture.
TIA,
--
Gianugo
Re: [VOTE] New committers: Kevin Ross and Vladimir Bossicard
Posted by Tom Bradford <br...@dbxmlgroup.com>.
On Friday, October 18, 2002, at 10:05 AM, Jeff Turner wrote:
> Calling a vote is the next logical step. So..
>
> I propose Kevin Ross <Ke...@iVerticalLeap.com> and Vladimir
> Bossicard <vl...@bossicard.com> as Xindice committers. My intensive
> background checks[1] suggest they both know what they're doing, and
> both
> seem willing to drive a currently "stale" Xindice forward.
>
> [+1 ] Kevin Ross
> [+1 ] Vladimir Bossicard
I also agree that the project has become stale, especially with Kimbro
MIA. I had been trying to stay out of Kimbro's way, and let him run
the project as he saw fit, but if the Xindice community would like, I
can step back up to the project's helm, and help drive a bit more.
--
Tom Bradford - http://www.tbradford.org/
CTO - The dbXML Group - http://www.dbxml.com/
Apache Xindice - http://xml.apache.org/xindice