You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Dirk-Willem van Gulik <di...@covalent.net> on 2001/03/03 21:29:31 UTC
Volunteers: First Cut
Folks,
Thanks everyone - here is the promised first cut of volunteers !
I've received 8 volunteer proposals sofar; but have not heard from some of
you who expressed an earlier interest. Unless my bookkeeping is wrong:
Doug Davis, Edwin Goei, A Raham, Kim Staken, James Scott, Michael Reynolds
and Arved Sandstrom all expressed some level of interest - but did not
follow up with a reply to the First cut. (This is why I left sending this
message until nowi :-)
In any case - as some of you do not have commit access I cannot put this file
in CVS to let you folks hack/edit/correct it yourselves. So I propose the
following:
1. Any one who wants to be part of the final list is to volunteer
on this mailing list before monday 2400 GMT. The entry you
submit is the final one.
2. Any of the people below who want to have their entry improved,
edited, etc can send me, or this list, a mail message before
monday 2400 GMT.
3. Any one who wants to object/comment/etc on this list please
do so by monday 2400 GMT.
So this means that we have a 'final' list of volunteers for the PMC by
monday. (Final - unless I hear that this approach is too quick - see below)
There are more than 5 and less then 15 - so we have roughly the right
number of peoplpe to make up a PMC without change.
Now what do we want to do next ?
Re: Volunteers: First Cut
Posted by Kimbro Staken <ks...@dbxmlgroup.com>.
I'm still volunteered, I thought my first message covered all the asked for
information so did not submit it again.
1. Name
Kimbro Staken
2. Apache Affiliation
None official. I am a consumer of apache XML technology including Xerces,
Xalan, Cocoon, SOAP and Stylebook along with other general apache projects.
3. Professional affiliations when considered relevant
relevant or if the need is feel to disclose them.
Developer on the dbXML project http://www.dbxml.org, Founding member and
member of the management commitee for the XML:DB initiative.
http://www.xmldb.org The process used by the XML:DB organization is heavily
influenced by the workings of the ASF sub-projects process.
4. The beef - What you bring to the table
My interest is in the long term growth of XML and Open Source software. In
addition, as a user of the software, the efforts of the XML organization
have significantly helped the efforts of the other projects that I am
currently involved with. So my interest is also in contributing back in some
way. What I bring is a more strategic management level view of the Open
Source and XML landscape. I'm very familiar with, and believe strongly in
the fundamentals of the Apache process but I also believe there are a few
aspects of its application that can be improved in the XML sub-project.
Whether I can actually help or not depends on what the real role of the PMC
is. If it is focused more on directing the organization growth and general
oversight I could probably help, but if it is a commitee tasked with hands
on solving of cross project technical issues then I wouldn't really be able
to help that much. If it is both, well ... then that is one of the things
that I think needs to be tweaked in the process.
Kimbro Staken
Chief Technology Officer
The dbXML Group L.L.C.
http://www.dbxmlgroup.com
----- Original Message -----
From: "Dirk-Willem van Gulik" <di...@covalent.net>
To: <ge...@xml.apache.org>
Sent: Saturday, March 03, 2001 1:29 PM
Subject: Volunteers: First Cut
>
> Folks,
>
> Thanks everyone - here is the promised first cut of volunteers !
>
> I've received 8 volunteer proposals sofar; but have not heard from some of
> you who expressed an earlier interest. Unless my bookkeeping is wrong:
> Doug Davis, Edwin Goei, A Raham, Kim Staken, James Scott, Michael Reynolds
> and Arved Sandstrom all expressed some level of interest - but did not
> follow up with a reply to the First cut. (This is why I left sending this
> message until nowi :-)
>
> In any case - as some of you do not have commit access I cannot put this
file
> in CVS to let you folks hack/edit/correct it yourselves. So I propose the
> following:
>
> 1. Any one who wants to be part of the final list is to volunteer
> on this mailing list before monday 2400 GMT. The entry you
> submit is the final one.
>
> 2. Any of the people below who want to have their entry improved,
> edited, etc can send me, or this list, a mail message before
> monday 2400 GMT.
>
> 3. Any one who wants to object/comment/etc on this list please
> do so by monday 2400 GMT.
>
> So this means that we have a 'final' list of volunteers for the PMC by
> monday. (Final - unless I hear that this approach is too quick - see
below)
>
> There are more than 5 and less then 15 - so we have roughly the right
> number of peoplpe to make up a PMC without change.
>
> Now what do we want to do next ?
>
> From an ASF perspective we need to get some sort of consensus on wether
> this is the right group, the right size and so on.
>
> Now consensus is hard to measure; but I am willing to gauge what I hear on
> this list (and by private mail to dirkx@apache.org or board@apache.org) -
> where silence indicates consent. We can also do this by an explicit vote
> amongst the committers; or we can simply set a 'no objections' deadline by
> which a '-1' needs to be in (in which case we have a fuill vote). Or by
> any other means.
>
> So also by monday 24.00 GMT tell the list how you want this to
> continue. Options I can think off:
>
> A. Silence is consent and unless I/the-board/this-lists hears
> objections we move forward with proposing this PMC to
> the board.
>
> B. We have a vote by the committers on this group as a whole.
> (Usual system, including veto's).
>
> C. We have a vote on each member (Must have N/2+1 to be part
> of the PMC; veto's do not apply. If we end up with less
> than 5 people or more than 15 - redo from start).
>
> D. Some scheme I did not think off - to be proposed.
>
> E. This is all going to fast - and I propose to .... :-)
>
> The default is 'A' unless you speak up on this list.
>
> Once we know how we continue w'll set a timeline; but I'd really
> like to keep this moving. See next message
>
> Thanks everyone for volunteering !
>
> Dw
>
>
> Volunteers for the next PMC of the XML projects:
> (in order of appearance in my inbox):
>
> Key to the entries:
> 1. Name
> 2. Apache Affiliation
> 3. Professional affiliations when considered relevant
> relevant or if the need is feel to disclose them.
> 4. The beef - What you bring to the table
>
>
>
> 1. Sam Ruby
> ==========================================================
> 2. Committer xml-soap/xml-axis. Infrequent committer to
> xml-cocoon. Jakarta PMC Chair. PHP Group Member. Apache Member.
> 3. IBM
> 4. Focus on inter-subproject versioning and compatibility issues.
> http://jakarta.apache.org/builds/gump/latest/
>
>
>
> 1. Davanum Srinivas (nickname: dims)
> ==========================================================
> 2. Working on Cocoon2 (C2) Apache project since last Oct/Nov
> 3.1 Employee of Computer Associates (working on Jasmineii -
http://www.ca.com/jasmine)
> 3.2 FAQ Manager of JNI-FAQ at jGuru.com (http://www.jguru.com/faq/JNI)
> 4.1 Integrated Xalan2's TRaX into Cocoon2(Now C2 can use SAXON too)
> 4.2 Integrated Batik into Cocoon2.
> 4.3 Looking into Turbine integration with C2 right now.
> 4.4 Occasionally submitted patches to Xalan2 and a couple to Xerces.
>
>
>
> 1. Ted Leung
> ==========================================================
> 2. Committer for Xerces-J, Member of current XML PMC.
> 3. None - I work for myself.
> 4. I've spent some time recently trying to help the Xerces-J project get
a
> little more organized. I'm willing to do "scut work" like editing
the
> website, maintaining bugzilla, etc. I am concerned about version
lock
> problems, and API consistency across the projects. I'd also like to
see
> the "infrastructure" projects (Xerces, Xalan, FOP, Batik, SOAP) move
in
> the direction of an application server stack. I think that having a
small
> set of design points that the various projects are striving for will
bring
> more unity in design and community. As an example Xerces-J is
> consistently torn by people who want to turn it into an engine for
writing
> incremental XML editors and people who want to turn it into a
component
> suitable for production level messaging. Often the goals of these
two
> camps are opposed.
>
> One last thing. Jim Allchin's recent comment about Open Source
stifling
> innovation seemed particularly relevant to me. In the past the part
of
> the charter that referenced XML standards has been used as a way to
keep
> features out of projects and projects out of xml.apache.org. I think
it
> is very important that the XML project be a place where innovation is
both
> allowed and encouraged. Our best example of this is Cocoon. Jakarta
has
> a few examples: Ant and Struts. I want to see our projects continue
to
> innovate in similar fashion, so I want to be sure that whatever we do
to
> the charter still allows for that.
>
>
>
>
> 1. Matthew B Brandabur
> ==========================================================
> 2. Working on the Oracle Internet File System which ships with Apache
and
> working on a proof oc concept project to integrate IFS with
Cocoon/Batik
> 3. Staff member of Oracle
> 4. I have been following the progress of the cocoon project for several
> months, and I would like to be involved. I am not primarily a coder,
> however. I am in charge of documenting Oracle's Internet File System
for
> developers, so I have lots of experience writing for developer
audiences.
> I get lots of hands-on experience with our API, including writing
sample
> code and testing our example projects, so I am comfortable with
enterprise
> Java and constantly practicing on my own.
>
>
>
>
> 1. Kelly A. Campbell
> ==========================================================
>
> 2. Committer on FOP. I'm also the lead developer on the Merlot XML
editor
> (www.merlotxml.org) which is not an Apache project, but is released
under
> a similar license. I also use a good amount of the Apache projects,
XML,
> Jakarta, and otherwise, and have submitted bug reports and patches
for the
> projects I use.
> 3. I work with XML and Java technologies for ChannelPoint, Inc. The
spectrum
> of how I use it ranges from producing basic documentation via
> XML/XSLT/XSLFO up to full web applications and frameworks.
> 4. I'm interested in most aspects of XML, XSLT, and XSL FO, from
development
> to a user's standpoint. I have 4 years Java experience, and almost 2
> years of experience with XML and XSL. I'm interested in the
interactions
> between our projects and the build processes Sam Ruby is working on
with
> Gump. I would like to work towards standardization of runtime linking
and
> deployment of java projects (using XML, Ant, and some of the Gump
> work)... sort of like a gnu autoconf/linker for Java. I'm also very
> interested in helping standardize how Apache projects test their
code,
> either via JUnit, or another tool as Scott Boag suggested on this
list a
> while back.
>
> Another thing I would like to promote as XML projects is UI tools for
> working with XML, XSL, etc. As a part of this, a donation of the
merlot
> xml editor might be possible, though it would require approval from
my
> company. I can't promise anything in this regard right now, but I
wanted
> to at least put it on the table.
>
> 1. Rajesh Thiharie
> ==========================================================
> 2. Working on a proof of concept project that uses EJB - XML - Cocoon
> and Servlets/JSP
> 3. Work for Aithent - a software development company based otu of New
Delhi,
> India
> 4. I have been using Xerces - Xalan for over six months now and Cocoon
for
> four months Am very interested in XML overall.
>
>
>
> 1. Shane Curcuru <sh...@lotus.com> <cu...@apache.org>
> ==========================================================
> 2. xml-xalan committer, daily xml-xerces, xml-crimson, and jakarta-ant
user
> 3. IBM Research employee (transferred from Lotus recently, hence the
email
> addr). Note that although I do work for IBM which ships the
LotusXSL
> processor (a thin wrapper on top of Xalan, mostly) I definitely feel
I
> wear separate hats as Apache committer and IBM employee. I focus my
> work on Xalan towards making it the best XSLT processor out there,
and
> to be a 'good citizen' project in the Apache community.
> 4 Lead Java API tester and test automation creator/maintainer for
Xalan
> for the past 2 years; see http://xml.apache.org/xalan-j/test/ I've
been
> a Software Quality Engineer for 12 years on multiple Lotus projects
> including being the 1-2-3 database, cell engine and UI components
> testing and automation leads; was the 1-2-3 build engineer; and was
the
> eSuite Automation Coordinator, where I implemented a common
distributed
> testing system and trained the eSuite QE team to write their own
> Java/JavaScript automation (including many without coding
experience).
>
> I could bring experience at helping drive more guidelines and
standards
> for xml.apache.org project's organizations. Although I usually hate
to
> admit it, I can help get projects more on board with a cross-project
> build system like Sam Ruby's Gump/Alexandria/whatever we call it
now.
> I'd also like to help implement Scott's idea of having common
testing
> infrastructure, although I believe this will be a significant effort
to
> fully implement. We'll need both the tools to enable common
automation
> as well as guidelines for how/what to test, and really good
> documentation on writing good tests. I have to admit that one of
the
> challenges for me will be applying my skills from large corporate
> projects into the Apache open source model - where you have few, if
any,
> dedicated 'test' engineers, and everyone's a volunteer. One very
> important thing will be to make our testing story both make sense to
> people and be *very* easy to implement for the average developer.
Oh,
> and a third area I'd like to focus on is improving and coordinating
the
> overall xml.apache.org documentation set. I think we do have very
good
> doc now; just long term I think we need to provide even better
> documentation to allow a wider audience to quickly pickup and use
Apache
> tools.
>
>
> 1. Ram Mareddy
> ==========================================================
> 2. I am currently working with xerces-c. While I don't have any formal
role
> with Apache, I used that code a lot.
> 3. Siebel Systems; Architecture Specialist (/Software Engineering --
the
> role is slightly changing). I have about ten years of industry
> experience plus the other usual qualifications like MS in Computer
> Science; along the way worked with several products, languages, and
> databases. Also, involved with the bay area Software Development
Forum
> (SDF).
> 4. I work with the Connectors group. This group builds connectors from
> Siebel to all the popular ERP/other packages (this list is
constantly
> growing). All this EAI infrastructure is solidly based on XML and
the
> dll's from the Apache effort. So, I can provide a very unique
> perspective from the sophisticated use of these technologies.
Internally
> I have an opportunity deal with a variety of departments in this
> context: from Engg to QA to tech pubs to prod mktg to services on a
> constant basis.
>
>
> 1. Dirk-Willem van Gulik
> ==========================================================
> 2. ASF Board member, httpd committer
> 3. Not relevant - but disclosed as: VP of R&D at Covalent Technologies;
a
> hybrid opensource/commercial product company that supports and
> builds upon ASF technology to make it enterprize ready.
> 4. Having seen the birth of this XML and the troublesome path of
> its PMC I'd like to be part of the efford which matures this
> group into long term stability - and I'd like to help us find
> a balance and and environment in which we can work on code, hack
> protocols and standards without an overly burdensome or top
> heavy organisational framework - whilst still addressing the worries
> with cross project versioning, release methods and our ongoing
> interwovenness with other ASF projects such as java/jakarta.
>
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail: webmaster@xml.apache.org
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
>
Re: Volunteers: First Cut
Posted by Edwin Goei <Ed...@eng.sun.com>.
Dirk-Willem van Gulik wrote:
>
> I've received 8 volunteer proposals sofar; but have not heard from some of
> you who expressed an earlier interest. Unless my bookkeeping is wrong:
> Doug Davis, Edwin Goei, A Raham, Kim Staken, James Scott, Michael Reynolds
> and Arved Sandstrom all expressed some level of interest - but did not
> follow up with a reply to the First cut. (This is why I left sending this
> message until nowi :-)
I and probably others on this list would like to have input on the
direction of XML projects at Apache. That's why I like the idea
mentioned by others that as much discussion of topics like this take
place on the open general@xml.apache.org list. Hopefully this is what
will happen and so that makes me happy and so I don't need to be on the
PMC.
-Edwin
Re: Volunteers: First Cut
Posted by Ted Leung <tw...@sauria.com>.
>
> 1. Ted Leung
> ==========================================================
> 2. Committer for Xerces-J, Member of current XML PMC.
> 3. None - I work for myself.
Change 3. to read
3. I work for myself as an independent consultant. Previously CTO
Enkubator, LLC (launching
Internet startups atop Open Source platforms). Previously Technical Lead
IBM XML4J
(became Xerces1 code base).
Re: Volunteers: First Cut
Posted by Fotis Jannidis <fo...@lrz.uni-muenchen.de>.
From: Dirk-Willem van Gulik <di...@covalent.net>
> So also by monday 24.00 GMT tell the list how you want this to
> continue. Options I can think off:
[...]
> B. We have a vote by the committers on this group as a whole.
> (Usual system, including veto's).
+1
Fotis Jannidis