Subject: Re: Perl XML: next steps - msg#00015

Previous Message by Date: click to view message preview

Re: Perl XML: next steps

--- Grant McLean wrote: > Would I look foolish if I were to ask what's the derivation of 'Dahut'? I don't think it's too foolish, I was wondering the same m'self. > And while I'm asking tangential questions, are any other Perl-XMLer > at OSCON? I'm not at OSCON (too expensive), but I do live in town and have been going to the various free alternatives to OSCON (PHP>>PDX, FOSCON,...). -- Live well, ~wren __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Perl-XML mailing list Perl-XML@xxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Next Message by Date: click to view message preview

XML::Twig pre-release testing

Hi all, I am getting ready for a new release of XML::Twig, and I need some help to test it on various platforms. The release candidate is at http://www.xmltwig.com/xmltwig/ tar.gz: http://www.xmltwig.com/xmltwig/XML-Twig-3.18.tar.gz Linux is mostly covered. I can do Solaris and OS X (10.2/10.3, I don't think it matters) I would appreciate reports on Windows But in any case, it would be useful if you could test it with your configuration, as I can't possibly test all combinations of OS + perl + XML::Parser + expat + the many optional modules that can be used with XML::Twig. Thank you -- Michel Rodriguez Perl & XML xmltwig.com _______________________________________________ Perl-XML mailing list Perl-XML@xxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Previous Message by Thread: click to view message preview

Re: Perl XML: next steps

On Wed, Aug 03, 2005 at 03:20:57AM +1200, Grant McLean wrote: > Robin Berjon wrote: > > Here are the rules I can think of: > > > > - anyone who has an XML module can join the project, unless another > > committer disagrees (I doubt that'll happen, but you never know); > > - people who don't have an XML module can of course join if they > > provide regular patches; > > - everyone who's a committer can commit to every module. Any other > > option is just too complicated; > > - everyone who has a module in there must give co-maintainer status to > > user DAHUT so that other committers can make a release when they > > need to; > > - every committer has the password for user DAHUT; > > - even though everyone can make a release, it's not polite to do so > > without asking the module author and other committers first; > > - patches can be sent here or attached to rt.cpan.org. > > > > That's all I can think of, basically it's just common sense IMHO. > > Agreed. We're all smart enough to not need lots of rules. If I'm correct, access can be done through auth.perl.org, so the same access that is used from rt.perl.org, books.perl.org, etc. Ask would be the best source of information on that. > > > Ask says a repository is not a problem at all, we'll like be hosted at > > http://svn.perl.org/modules/xml/. I've asked for a mailing as well. I > > don't expect it to see much discussion (it should mostly happen here) > > but it would be convenient if for instance we want to have commits send > > diffs somewhere or chat about really boring in-project admin issues. I > > don't have the details yet but Ask will probably be giving them to me > > soon. > > Sounds good. > > Would I look foolish if I were to ask what's the derivation of 'Dahut'? > See http://dahut.pm.org/dahut_story.html Steve Peters steve@xxxxxxxxxxxxxxx _______________________________________________ Perl-XML mailing list Perl-XML@xxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Next Message by Thread: click to view message preview

Re: Perl XML: next steps

Robin Berjon wrote: Here are the rules I can think of: - anyone who has an XML module can join the project, unless another committer disagrees (I doubt that'll happen, but you never know); - people who don't have an XML module can of course join if they provide regular patches; Formally, if a maintainer makes them co-maintainers. - everyone who's a committer can commit to every module. Any other option is just too complicated; Yes, technically. But it should be a good and strongly recommended practice not to commit to other people modules without prior communication with maintainers in duty. Chaotic commits from many sides wouldn't be really helpful. - everyone who has a module in there must give co-maintainer status to user DAHUT so that other committers can make a release when they need to; - every committer has the password for user DAHUT; I would ask who is DAHUT but Grant already did so :) - even though everyone can make a release, it's not polite to do so without asking the module author and other committers first; Again, I think it's not only impolite; there should be a good practice not to do so. - patches can be sent here or attached to rt.cpan.org. That's all I can think of, basically it's just common sense IMHO. [...] Ask says a repository is not a problem at all, we'll like be hosted at http://svn.perl.org/modules/xml/. I've asked for a mailing as well. I don't expect it to see much discussion (it should mostly happen here) but it would be convenient if for instance we want to have commits send diffs somewhere or chat about really boring in-project admin issues. I don't have the details yet but Ask will probably be giving them to me soon. It would be great to get also a web hosting from perl.org, preferably xml.perl.org. -- Petr Cimprich Ginger Alliance www.gingerall.com _______________________________________________ Perl-XML mailing list Perl-XML@xxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs