| Paul M Jones 2005-09-13, 6:57 pm |
| Hi Bertrand; hi, Justin,
I've copied PEAR-QA on this one. This is in relation to HTML_BBCode,
but also in relation to a "mid-term" strategy on migrating Text_Wiki
to a more generic package name, e.g. Text_Markup. The idea, as
Bertrand outlines below, is to have subpackages or parallel packages
to the main Text_Wiki package, and later transition into a new
Text_Markup package (with its own corollary packages).
Bertrand says:
> Anyway, as a mid point, the proposal is to keep the core Text_Wiki
> as it is:
> core files, Default parser and the 3 basic renderers Xhtml, Plain
> and Latex
>
> For the add-ons, the most convenient seems to do 1 package /
> syntax, including the parser and/or renderer:
> * Text_Wiki_BBCode (to be released)
> * Text_Wiki_Cowiki (to be released)
> * Text_Wiki_Doku (to be released)
> * Text_Wiki_Mediawiki (in build)
> * Text_Wiki_OOo (OpenOffice.org) (in build)
> * Text_Wiki_Tiki (to be released)
>
> Do you agree this scheme ?
I do.
> Could you create the 6 corresponding packages ?
QA guys -- do we need to start a proposal process for this, or can we
just set them up in CVS and start releasing? What would be the
correct procedure?
--
Paul M. Jones <http://paul-m-jones.com>
Solar: Simple Object Library and Application Repository
for PHP5. <http://solarphp.com>
Savant: The simple, elegant, and powerful alternative to
Smarty for templates in PHP. <http://phpsavant.com>
|