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 (vaio)" <di...@webweaving.org> on 2001/03/14 21:09:44 UTC
[XML] PMC Vote - less than 4 hours left :-)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
XML Committers,
Just a reminder; less than 4 hours left to submit your final vote
on the new XML PMC. Our counters tell me that about a third of you
people have voted sofar - I am sure we can do better ! And get
this new PMC started on an even keel and with everyone involved.
So if you have not yet voted; fill out the template below and
send it to:
"Jim Jagielski" <ji...@apache.org>
"Ben Laurie" <be...@apache.org>
who are the ASF board members which are counting the votes. Your
votes should be in before the 15th of March - 00:00 UTC.
Thanks a lot !
Dw
- --
Dirk-Willem van Gulik, ASF Board Member, interim chair XML project.
Start of template:
What: Vote for the new PMC for the xml.apache.org
project.
Who: To be voted upon by comitters of the XML project.
Deadline: 15th of March 2001 00:00 UTC
(time of arrival on an apache.org MX its MTA).
Non-vote related information:
The following information is needed to verify validity
of your vote.
Name: (for verification committer status)
Userid on Locus: (for verification committer status)
Email: (to contact you in case of problems)
The above information will be separated from the information
below for archival and counting purposes insofar as required
to keep the vote fair.
Process:
Please place exactly five 'X' onto the entries of choise,
e.g. [X]. If you do not want to use all your five votes;
use the blank entries at the bottom to ensure you have 5
(five) entries marked.
After voting please send this form to the following
two ASF board members:
"Jim Jagielski" <ji...@apache.org>
"Ben Laurie" <be...@apache.org>
with
Subject: [VOTE] XML PMC
Please send this form ONLY to the above two addresses,
sending it to general@ or making it in some way public
before the results are announced is considered vote
rigging and may cause the ASF board to intervere.
Privacy: OPTIONALLY you can PGP encrypt the message for
both receipients. It is your responsibility to be familiar
with PGP and to correctly encrypt the message. Use
of PGP is OPTIONAL - and only for the truly concerned
Machiavelli's of the world, plaintext is fine too.
Only votes which are received before the deadline by
both counters, which have exactly 5 votes, which contain
the complete template as an text message and which are
readable are valid. The board members doing the counting
as supervised by the ASF board are the final authority.
You can change your vote by sending in a new copy
of the template. The counters will only take the
most recent message.
Vote:
[ ] Scott Boag
[ ] Matthew B Brandabur
[ ] Kelly A. Campbell
[ ] Luc Chamberland
[ ] Shane Curcuru
[ ] Vincent Hardy
[ ] Ted Leung
[ ] Ram Mareddy
[ ] Tinny Ng
[ ] Sam Ruby
[ ] Davanum Srinivas
[ ] Kimbro Staken
[ ] Rajesh Thiharie and
[ ] Dirk-Willem van Gulik
[ ] Blank vote 1
[ ] Blank vote 2
[ ] Blank vote 3
[ ] Blank vote 4
[ ] Blank vote 5
End of Template
Appendix A
Optional.
PGP keys of ASF supervised voting committee.
Type Bits/KeyID Date User ID
pub 768/A0BB71C1 1997/06/03 Jim Jagielski <ji...@jaguNET.com>
pub 1024/2719AF35 1995/05/13 Ben Laurie <be...@algroup.co.uk>
Ben Laurie <be...@gonzo.ben.algroup.co.uk>
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3
mQBtAzOUkNMAAAEDANZdTUJQPwrFI9526Qf+DEWL8dXgfhWW8o6CzewdcCoHYEpu
9CiOMD3f9bgo1VozOPceGzCu/9FF2hMLUvVsTAZkzC3rre5TtPo/vOf5HJ+ac9M7
aqxW+gRu2/90oLtxwQAFEbQfSmltIEphZ2llbHNraSA8amltQGphZ3VORVQuY29t
PokAdQMFEDOUkNRu2/90oLtxwQEB8iEC/i9Qo55TlT8bRpcqeM3lzNDqzU9cqKRf
9X8pGJIVE5m2JPm99qPLs8RPeepLChi8ZZ+2hSfb7ldQhvVLgNqQqLpsjGtJjJOU
C+MrKDeSk2WAicg6Uo0FWCsEHxrssw139A==
=pwim
- -----END PGP PUBLIC KEY BLOCK-----
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAi+0jQEAAAEEAK7oX0FeNncaHfa1v+V7SMUviAm8qB8orWG0zvja4ZtSrHVg
/PMwppUh44t5ERA9lltRBdHu30+YSh8a1dYt1XOD83nknzj9rhtpFAPqyywlLVhN
VY3PVLyMbULw27aEAGc+StFqrDoUQ0+j9QU/YH/IyVN9rBaJyhsIDEUnGa81AAUR
tB5CZW4gTGF1cmllIDxiZW5AYWxncm91cC5jby51az6JARUDBRAyb2Doc3AsNzyk
Yh0BARa6CACUBnsP9Vb+T/PvNYKVQBIODz+90tz5GozWwCVfPVSaRd8Dz+oF1sFs
YCz/KuxqBhL5PkiCuSMfOVlPA5nirjoktMF/af5saZqhPr5rvr67Z1OzZnVDvWe4
DhFrn8EoLrY5YNJhUwfINnZqyKaQu8TW6p4caLkTCW0KM+4ztTe74xRG9NeE+K0+
0RMpAF3jEY36LGRjq6miazt2bVZQDTl6CuWE+gAaFlX2ojV7e1xdxVvpBIEc34MP
g9ORJ0evx1QilMt1VyGcS/pe4IQgjdJqjU/4fzqFZkT2nntQMbV9kQyNe2+qfqP7
giTryIanmBAfd3oOCTsRz2VKPfdhCqCRiQB1AwUQMRdzEEyr2GZv4ALJAQEuhAL6
A8I84BR+87uNAHD0ZJkTM73WdyMEGvAKBvrZK/g0VLYj0NtgkSuRJfrXnGkuh27I
ZrjfL952Q/mXgMtHhJHJ9YfenGFWSEDHnolNzKOzTQJpE01IZ3nWv7ezA9N1LZVC
iQCVAgUQMROrdRsIDEUnGa81AQEUNgQAlvyjt534RDQd2AYGoZriaFzjaL7dTCRH
4b1zxuWBNWf3pI4W0iwU02Q5rEWEmY5DLl6/ie+vcQKOWSqXVgnM/s6EARdKEN56
d6PzkwszgfEybDYrcAxReJcTCcV8ItJer/iqpBLgtaxyUpI77NvKcDGHp6BgYpnv
1lNkH0FISK+JAJUDBRAwtzlWdGx7qH+PTVkBARFWA/99NTCMihlOZS7LmHDVic/q
H1K1DVdMcv0iL39+7Pq4+AA/ET8dWIgcjaIreSqAZTpjwU1pMPaWgecDD1rEMCYX
R+JoofLJ24BLcSlpXJ/gWMifYNxqdDeMRkw/aW/kaXQJWIz+oDYNuOyi5VvB6faF
6Lm7P5cw1mX0I5rYc3woh7QoQmVuIExhdXJpZSA8YmVuQGdvbnpvLmJlbi5hbGdy
b3VwLmNvLnVrPokAlQIFEDEXgCUbCAxFJxmvNQEBiL8D/3MLjfHGvuByqP1VFQrF
QeMNd2aIQuC7ys3lkDvrLkkPJQANua0/MdDaZk6F5pCGcTmmmaJOjcOcCheD7FU5
w9zxkQGR3Swr3opFHSr/CkEl83jRy3oq1MFydWoGajQjIr/c23X8zr+XntPyO6VX
q5He4RrTiXeAEFBzz+J+R+EQ
=zh1u
- -----END PGP PUBLIC KEY BLOCK-----
Appendix B:
Volunteers for the next PMC of the XML projects:
* Updated/Added entries for Scott Boag and Vincent Hardy.
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. 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).
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.
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.
1. Tinny Ng
==========================================================
2. Committer for Xerces-C
3. IBM XML Parsers Development
4. I have been involved in the Xerces-C project for over six months, and am
one of the primary Xerces-C developer. Dedicated to bring improvement
to the Xerces-C project such as introduced the use of Bugzilla, improved
the Xerces-C website and its documentation.... etc. Current ambition is
to bring Schema support to Xerces-C. I am also a user of Xerces-J,
Xalan, Cocoon and FOP, and am very interested to work on the bigger
picture.
1. Luc Chamberland
==========================================================
2. Subscriber to xerces-j and xerces-c and parser licensee.
3. IBM, XML Parsers Development Manager (IBM XML4J and XML4C)
4. I have an extensive background in project management, and would like to
bring those skills over to the XML sub-projects so that we can improve
our planning, bug tracking, and coordination amongst the sub-projects. I
currently provide similar project management to XML parser development
occuring within IBM. I answer a lot of questions pertaining to licensing
of Apache technology by IBM, and would be happy to do same for Apache.
I'm particularly interested in working with the other sub-projects to
ensure they work well together, and maintain some level of application
agnosticism. Some of the closed source efforts in the industry are
putting out compelling suites of XML tools/runtimes, and our community
needs to better ensure our tools compliment one another. (I concur with
Ted on the need for common design points and a technology stack.)
As a technical writer for several years, I'd like to lend my help to
improving our overall doc strategy, particularly by focussing on "big
picture" scenarios that illustrate how the various sub-project
technologies work together. I've written similar articles for the Java
Developer's Journal and IBM publications.
1. Scott Boag
==========================================================
2. Xalan Developer
3. IBM
4. My primary interest in the PMC is to build a larger technical
community that builds a robust set of technologies that are cleanly
coordinated. I am deeply in touch with the software requirements and
architectual issues between XML projects. I am also a member of the W3C
XSL working group, and am fairly involved in W3C issues and other standards
activities. My primary interest is technical, so I'm somewhat on the
border about being on the PMC, since it is still unclear to me who is going
to define technical coordination. I'm not a marketing person, and I don't
care so much about legal issues. But I also don't think that reasonable
robust architecture can be done without some structured coordination, which
is what I'm interested in.
1. Vincent Hardy
==========================================================
2. Batik co-founder.
3. Employee of Sun Microsystems. Member of the W3C SVG working group.
4. Represent the Batik group. Motivated to help coordinate efforts with
other groups such as FOP or Cocoon when needed. Interested in making
Batik consistent with the other xml.apache.org projects.
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv
iQA/AwUBOq/Ewf1viMYh0KcbEQI1BACgghJQAYKdywv/mjd5YP4yZ/ghBiAAnAq5
C3e6vZ+DnWzXi9ONzoXukguQ
=US5i
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
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