& XSLT Hi Petr, all,

Petr Cimprich wrote:
>  If we can ask Bjorn Hansen for anything, it would make sense to point 
>  xml.perl.org to the Perl XML homepage.

A few things I'd like to note:

  - I agree with almost everything that's been said so far;
  - I would add the PerlSAX specs to what needs to be commonly maintained
    (as part of XML::SAX);
  - doing it using svn on xml.perl.org is IMHO the best place -- I'm
    happy to contact Ask about that if everyone agrees;
  - and most importantly, it did *not* take 21 beers to convince me that
    this was a good idea, the 17 first beers did make me digress into
    trying to figure out the reasons why some modules were not
    maintained rather than be practical, but I agreed from the start ;)

The current list is:

XML::Schematron
XML::Simple
XML::NamespaceSupport
XML::SAX::Writer
XML::Filter::BufferText
XML::SAX::ExpatXS
XML::Validator::Schema
XML::Filter::ExceptionLocator
XML::Parser
XML::XPath
XML::SAX
XML::LibXML
XML::LibXSLT

To that I would add (off the top of my head at 4am on vacation) 
XML::Twig, not because it's not maintained but because it's core), and 
XML::SAX::Expat because even though ExpatXS deprecates it in many ways, 
it's still used by people who might have trouble installing XS modules 
but have XML::Parser installed by default. I think that XML::Writer is 
also used by quite a few people, and in general I don't think that we 
should exclude any XML module that wishes to be there. 
XML::SAX::Machines and XML::XSH definitely need to be in there as well. 
And I'm probably forgetting some. How about XML::Sablotron, should it 
not be there too? I want my Symbian Perl to be able to use my Symbian 
sablotron :)

The issues are:

  - who gets to decide who becomes a new committer to that repository. I 
would guess that all the authors of the listed distros would naturally 
be committers. For new ones, I suggest that one Fearless Leader would 
propose them on this list, and if two existing committers +1 that person 
s/he is in. For Fearless Leader, I vote PetrC :)

  - making CPAN releases requires at the least co-maintainership on a 
module. Having each current maintainer give co-maint status to whoever 
is currently in charge of releases (I think it should be anyone in the 
committers gang) is going to be complicated, and will cause bottlenecks 
at the least convenient moments. I suggest creating a common PAUSE user 
that all will give co-maint or maint status to, and all the committers 
will have the password.

All in all that's not much work, and I can handle part of it (notably 
the CPAN admin stuff). Thoughts?

-- 
Robin Berjon
   Senior Research Scientist
   Expway, http://expway.com/

_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs