On Jun 2, 2005, at 5:04 PM, [EMAIL PROTECTED] wrote:
I found out about this program from Google the other day that would
pay
$5000 USD stipends ($500 USD to project, and $4500 to student
coder) for
spending a summer working on an open source project. There is a lot
of work
to do on Xerces 3.0, perhaps we could take advantage of this to get
a lot of
the work done.
Hi Matt,
We'd love to have the help, I'm sure. There are quite a few pieces
for Xerces 3.0 that either haven't been started, or which got no
volunteers and thus aren't currently on the docket.
I've just updated the Xerces 3.0 tentative release plan at docs/
releases_plan.xml with some interim status information. I'm also
pasting part of that below. If you see something that you think makes
a good fit, whether or not it's been spoken for by somebody, feel
free to suggest it for SOC by writing to the list...
I'm not sure I have the time in the next 2 weeks to shepherd a
proposal through the SOC process, and I'm going to be gone for a good
part of the summer, but maybe somebody will volunteer for that
process, and to be a mentor for your project... ?? ;)
James.
Here's the excerpt from the release plan:
<s3 title="Next Target Release">
<p>The &XercesCName; team is currently working on plans for
future releases.
At present, we believe there will be a 3.0 release with new
functionality
targeted roughly at the second half of 2005. As a change in the
major version allows us
to break source compatibility, we are trying to take our time in
order to
break now what needs to be broken. There is some chance that
changes breaking
source compatibility will not be needed, and that "3.0" features
will be
released in the 2.x line.</p>
<p>Further releases in the 2.x line are anticipated concurrent
with 3.0 development
in order to fix issues or bugs in 2.6. Once 3.0 is released, we
may also issue
further 2.x releases as needed by the community.</p>
<p>&XercesCName; 2.y.z - as needed to address bugs or other
issues.</p>
<p>&XercesCName; 3.0 - Targetted roughly for second half of
2005.</p>
</s3>
<s3 title="&XercesCName; 3.0 (tentative) Features list">
<p>The following table lists the potential TODO items for
&XercesCName; 3.0.
It does not include fixing bugs that are opened in Jira; unless
such Jira bug
involves a major development effort and requires an
architectural redesign,
or is an enhancement suggestion,</p>
<p>This list tracks current ideas and developer sign-up for 3.0
features. Some items
on this list have no volunteer. Items that have no volunteer
will receive no
development attention and therefore will not become part of 3.0.
If you would
like to volunteer for these or other items please email the
&XercesCName; mailing
list</p>
<table>
<tr>
<th>ID</th>
<th>Feature Description</th>
<th>Volunteer</th>
</tr>
<tr>
<td>1</td>
<td>Reorganization of public/private includes</td>
<td></td>
</tr>
<tr>
<td>2</td>
<td>Revisiting/sanity checking of install locations</td>
<td></td>
</tr>
<tr>
<td>3</td>
<td>Refactoring of x-platform support</td>
<td>Initial cut - James (done)<br/>
Basic posix support - James (done)<br/>
Mac re-port/test - James (done)<br/>
Windows re-port/test - Alberto<br/>
Linux re-port/test: Gareth, Alberto [VMWare (Red
Hat 9, Red Hat 7.3) and I can add more],
Scott Cantor [test], cargilld [w/ xlC]<br/>
Solaris - Scott Cantor [test]<br/>
Cygwin - Neil/Alberto (mostly done?)<br/>
MingGW - Alberto (mostly done?)<br/>
Interix - Alberto<br/>
AIX - cargilld<br/>
OS390 - cargilld
</td>
</tr>
<tr>
<td>4</td>
<td>A true autoconf based build infrastructure</td>
<td>James,
Jason Stewart,
Scott Cantor,
John Snelson
(mostly done--pending ports of additional platforms)
</td>
</tr>
<tr>
<td>5</td>
<td>Add a libcurl based NetAccessor</td>
<td>James (done)</td>
</tr>
<tr>
<td>6</td>
<td>DOM 3.0 support</td>
<td>Alberto,
Gareth
</td>
</tr>
<tr>
<td>7</td>
<td>XPath</td>
<td></td>
</tr>
<tr>
<td>8</td>
<td>XInclude</td>
<td>Gareth,
Caroline Rioux
Graham Innocent
</td>
</tr>
<tr>
<td>9</td>
<td>Add a ACE-based NetAccessor</td>
<td>Alberto - as time permits</td>
</tr>
<tr>
<td>10</td>
<td>Add RelaxNG support</td>
<td>(Michael Fuller -- would provide some help)</td>
</tr>
<tr>
<td>11</td>
<td>Audit/Update of XML Schema support.</td>
<td>cargilld</td>
</tr>
<tr>
<td>12</td>
<td>Const signature changes. [783, 1153, 1223]</td>
<td>cargilld</td>
</tr>
<tr>
<td>13</td>
<td>XML Catalog Support</td>
<td></td>
</tr>
<tr>
<td>14</td>
<td>Roll .c code into template headers?</td>
<td></td>
</tr>
<tr>
<th></th><th colspan='2'>Features/APIs to be removed</th>
</tr>
<tr>
<td>20</td>
<td>Remove Deprecated DOM altogether -
Whether we should actually do this is still being
debated.
</td>
<td>Gareth</td>
</tr>
<tr>
<td>21</td>
<td>Remove and/or update deprecated enums</td>
<td>Gareth</td>
</tr>
<tr>
<td>22</td>
<td>Remove non-thread-safe psvi methods</td>
<td>Gareth</td>
</tr>
<tr>
<td>23</td>
<td>Remove Mac OS Classic Support</td>
<td>James</td>
</tr>
<tr>
<td>24</td>
<td>Remove OS/2 (or update it)</td>
<td>Alberto</td>
</tr>
<tr>
<td>25</td>
<td>Remove Borland C++ 4, CodeWarrior, VACPP40 and
Unsupported from Windows platform</td>
<td>Alberto</td>
</tr>
<tr>
<td>26</td>
<td>Audit/Potential removal of all deprecated methods</td>
<td>cargilld</td>
</tr>
<tr>
<td>27</td>
<td>Remove tests/samples not invoked by sanityTest.pl</td>
<td>cargilld / James</td>
</tr>
</table>
</s3>
</s2>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
