On Monday, June 27, Marc Prewitt and I will be making a presentation at
YAPC::NA::2005 in Toronto entitled "Phalanx from the Trenches: A Local
Perl Users Group's Experience."
While the main focus of our talk will be on our experience with the Perl
Seminar NY Phalanx contingent
On Thu, Jun 02, 2005 at 06:57:24PM +0200, David Landgren wrote:
> >My understanding is that inclusion on the Phalanx 100 doesn't constitute
> >any sort of endorsement of the modules. It's hopefully a statement that
> >the module is widely used, but not a judgme
On Thu, Jun 02, 2005 at 06:48:30AM -0400, Dave Paris ([EMAIL PROTECTED]) wrote:
> It was brought to my attention that Crypt::DES is included in the
> Phalanx 100 list. While I'm flattered, I think this should be replaced
> by a better symmetrical crypto module like Crypt::Rijnd
Kevin Scaldeferri wrote:
My understanding is that inclusion on the Phalanx 100 doesn't constitute
any sort of endorsement of the modules. It's hopefully a statement that
the module is widely used, but not a judgment on whether it ought to be.
They are not endorsed, but they are
On Jun 2, 2005, at 3:48 AM, Dave Paris wrote:
Greetings,
It was brought to my attention that Crypt::DES is included in the
Phalanx 100 list. While I'm flattered, I think this should be
replaced by a better symmetrical crypto module like Crypt::Rijndael.
The reasoning is simple.
Greetings,
It was brought to my attention that Crypt::DES is included in the
Phalanx 100 list. While I'm flattered, I think this should be replaced
by a better symmetrical crypto module like Crypt::Rijndael.
The reasoning is simple. Crypt::DES is terribly weak and slow by
comparison.
Walter Goulet wrote:
Looks like the phalanx kwiki as well as the phalanx subversion
repository is down.
Any ETA on when it will be back up?
I can get the repository but not the kwiki. But, IIRC, the kwiki is
hosted by Ingy and is physically independent of the repository, which I
believe is
Looks like the phalanx kwiki as well as the phalanx subversion
repository is down.
Any ETA on when it will be back up?
thanks,
-walt
smime.p7s
Description: S/MIME Cryptographic Signature
Selon Gabor Szabo <[EMAIL PROTECTED]>:
> > So I guess my question is, what exactly am I supposed to do to improve
> > test coverage? Am I supposed to modify the existing scripts so they
> > execute more functions exported by the module? Are any of the other
> > modules currently being tested not u
Gabor Szabo wrote:
On Wed, 30 Mar 2005 21:45:23 -0600, Walter Goulet <[EMAIL PROTECTED]> wrote:
Hi,
Ok, so I've been trying to get started with testing Net-SSLeay for the
Phalanx project. Now the problem I've been having is getting my arms
around how to improve the cover
On Wed, 30 Mar 2005 21:45:23 -0600, Walter Goulet <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Ok, so I've been trying to get started with testing Net-SSLeay for the
> Phalanx project. Now the problem I've been having is getting my arms
> around how to improve the coverage
et started with testing Net-SSLeay for the Phalanx project. Now the
problem I've been having is getting my arms around how to improve the
coverage of the tests included with that module. It doesn't look like
this module uses the t/ framework, rather a series of scripts in a
given su
Hi,
Ok, so I've been trying to get started with testing Net-SSLeay for the
Phalanx project. Now the problem I've been having is getting my arms
around how to improve the coverage of the tests included with that
module. It doesn't look like this module uses the t/ framework, rath
I've been lurking perl.com for years and have always wanted to
contribute. Seems like the Phalanx project is a good place to start.
I'm particularly interested in testing the Net_SSLeay.pm module.
Take a look at the Kwiki on the Hoplites wanted page. You can be the
leader of the team i
Hi,
I've been lurking perl.com for years and have always wanted to
contribute. Seems like the Phalanx project is a good place to start.
I'm particularly interested in testing the Net_SSLeay.pm module.
Any tips on getting started or any 'hoplites' out there who need help
with
At least as originally proposed by project leader Andy Lester, Phalanx
was supposed to focus on *non-core*,
Not exactly. I just figured it's easier for teams to submit tests back
to individual authors than back to Perl itself. Also, those patches
are more likely to get out into the mains
Ofer Nave wrote:
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
Renaming thread since only the OP referred to Test::Output.
It occurs to me that the Test::* and ExtUtils::* modules should be the
first stop for the Phalanx project. :)
At least as originally proposed by project
Leon Brocard sent the following bits through the ether:
> http://astray.com/tmp/phalanx.html
This now mentions core modules and notices Mandrake contrib
(Module-Packaged 0.79 just hit CPAN), so Mandrake jumps from 28 -> 87.
Leon
--
Leon Brocard.http://www.astray.co
Leon Brocard <[EMAIL PROTECTED]> writes:
> This is what you get when you set Module::Packaged against the Phalanx
> 100. So right now FreeBSD packages the most of Phalanx, and it's kinda
> interesting to see the version numbers.
>
> There might be bugs,
Definitely. I
Johan Vromans sent the following bits through the ether:
> Definitely. I'm quite sure Getopt::Long is in _every_ distribution...
Of course, this only notices individually-packaged CPAN dists (ignores
the core).
Leon
--
Leon Brocard.http://www.astray.com/
scribot.
This is what you get when you set Module::Packaged against the Phalanx
100. So right now FreeBSD packages the most of Phalanx, and it's kinda
interesting to see the version numbers.
http://astray.com/tmp/phalanx.html
Script:
http://unixbeard.net/acme-svn/Module-Packaged/phalanx.pl
x off' stages?
I can't say that I'm clear on the Phalanx 100. I get that it's a nice
list of modules and all ... but I don't see any assignments or anything
associated with them -- most likely because there aren't any.
--brian
"Andy Lester" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'll put my hat in the ring, first: I don't want to run a module team,
> but I'm glad to join one.
>
> xoxo,
> Andy
Ditto for me. I am a Perl neophyte but I think this would be a great way to
learn so things about testi
I've started a new page on the Kwiki to replace the HereToHelp page:
http://phalanx.kwiki.org/index.cgi?TeamsWanted
Here's where I hope people looking for teams, or teams looking for
people, can get together and join forces.
I'll put my hat in the ring, first: I don't want to run a module team
"Andy Lester" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> There's a new Phalanx article on perl.com:
> http://www.perl.com/pub/a/2005/01/13/phalanx.html
>
> Let's hope we get an influx of Hoplites!
>
> xoxo,
> Andy
>
Hey Andy,
There's a new Phalanx article on perl.com:
http://www.perl.com/pub/a/2005/01/13/phalanx.html
Let's hope we get an influx of Hoplites!
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Msql-Mysql-modules
This is just the old distro that contained DBD::mysql and DBD::msql.
I don't think the latter is maintained, and DBD::mysql is already on
the list.
OK, updated. Thanks.
I really wish this were more exact. I have to wonder if this bot
traffic is totally skewing everything. :
On Mon, 17 Jan 2005, Andy Lester wrote:
Msql-Mysql-modules
This is just the old distro that contained DBD::mysql and DBD::msql. I
don't think the latter is maintained, and DBD::mysql is already on the
list.
-dave
/*===
VegGuide.Org
I've rerun the numbers on Phalanx. Following are the latest/greatest
Phalanx 100. A bunch of Test-* distros get their own special
top-of-the-list subset.
If there's any modules missing that you think belong on the list, let me
know. Anything that we specifically should NOT do, l
Selon Sébastien Aperghis-Tramoni <[EMAIL PROTECTED]>:
> Hello,
>
> Here are the final lists of the modules dependencies. This time I grouped
> the modules by their respective distribution name.
I forgot to say that these lists were made by reading the META.yml when
available, or by parsing Makefi
Hi!
On Mon, Dec 27, 2004 at 12:33:36AM +0100, S?bastien Aperghis-Tramoni wrote:
> Oops! I didn't include the list on my first reply.
> But on the other hand I have completed the analysis. So here is the
> final list:
> http://rafb.net/paste/results/p4hveb43.html
I haven't got any time in the
rticle for perl.com on the Phalanx project. Those
of
you involved, can you please give a summary of what you've done? Or
better yet, give me a summary and update the wiki as well?
Don't know if you saw Maddingue's update of his analysis of how many
modules depend on module X.
Here is
On Sat, Dec 25, 2004 at 11:04:15PM -0600, Andy Lester wrote:
> I'm working on an article for perl.com on the Phalanx project. Those of
> you involved, can you please give a summary of what you've done? Or
> better yet, give me a summary and update the wiki as well?
Do
I'm working on an article for perl.com on the Phalanx project. Those of
you involved, can you please give a summary of what you've done? Or
better yet, give me a summary and update the wiki as well?
I want to be able to say "SouthFlorida PM has improved the coverage of
Wango::Ta
=head1 Announcing the Do-It-Yourself Phalanx 100!
The Phalanx 100 is a list of the "top 100" modules on CPAN, and by
extension, those that should have the most attention paid to them by
the Phalanx project.
The first time I generated the P100 was over a year ago, and things
are old
=head1 Announcing the Do-It-Yourself Phalanx 100!
The Phalanx 100 is a list of the "top 100" modules on CPAN, and by
extension, those that should have the most attention paid to them by
the Phalanx project.
The first time I generated the P100 was over a year ago, and things
are old
On Mon, Dec 06, 2004 at 02:27:47AM +, Mark Stosberg ([EMAIL PROTECTED])
wrote:
> On 2004-12-02, Andy Lester <[EMAIL PROTECTED]> wrote:
> > I've reorganized all the trees in http://svn.perl.org/phalanx. A
> > description of how things should be is at
>
On 2004-12-02, Andy Lester <[EMAIL PROTECTED]> wrote:
> I've reorganized all the trees in http://svn.perl.org/phalanx. A
> description of how things should be is at
> http://svn.perl.org/phalanx/structure.pod.
I think I missed something. This clearly has something to do with
I'm now the point man for contacts on getting into the Phalanx
repositories. Also, I'm going to be reorganizing the existing
repositories a bit, just to help standardize. SouthFlorida, have you
done anything on Error or URI yet? If not, I'm going to restart them.
Any other h
On Mon, Aug 30, 2004 at 01:15:32PM -0700, Jim Keenan ([EMAIL PROTECTED]) wrote:
> On this page at the Phalanx web site
> (http://qa.perl.org/phalanx/distros.html), it is
> stated, "[the Phalanx 100] should NOT contain any
> modules that are part of core Perl. Those will be
> ha
On this page at the Phalanx web site
(http://qa.perl.org/phalanx/distros.html), it is
stated, "[the Phalanx 100] should NOT contain any
modules that are part of core Perl. Those will be
handled in a different phase of the project."
Can you elaborate as to how the core modules will
I'd like a blurb that I/we can post to various places about the push to
get Perl Mongers groups adopting modules as part of Phalanx.
SouthFlorida.pm is working on a couple, and Chicago.pm is going to work
on HTML::Tree at our next meeting.
If someone would be so kind as to volunteer, so I
Steve Peters sent the following bits through the ether:
> I've got Bundle::Phalanx100 out there right now. Once the list is
> updated, I can get the module updated.
And a link to this module, then ;-)
--
Leon Brocard.http://www.astray.com/
scribot
On Sunday 08 August 2004 10:25 am, Leon Brocard wrote:
> Andy Lester sent the following bits through the ether:
> > I'll be redoing the Phalanx 100 this week. I'm hoping to get FTP logs
> > from pair.com and from cpan.org. If anyone else has FTP logs they can
> >
Andy Lester sent the following bits through the ether:
> I'll be redoing the Phalanx 100 this week. I'm hoping to get FTP logs
> from pair.com and from cpan.org. If anyone else has FTP logs they can
> submit to me, I'd love to have 'em.
Please make the list ava
> Last year, I got different logs from Graham and Pair. Any other
> suggestions since they're apparently the same now? Mirror-owners I
> should talk to?
You could ask Graham for the search.cpan.org logs. Those are
potentially interesting.
-R
> I'll be redoing the Phalanx 100 this week. I'm hoping to get FTP logs
> from pair.com and from cpan.org. If anyone else has FTP logs they can
> submit to me, I'd love to have 'em.
$ host cpan.org
cpan.org has address 66.39.76.93
$ host cpan.pair.com
cpan.pair.com has address 66.39.76.93
$ host cpan.org
cpan.org has address 66.39.76.93
$ host cpan.pair.com
cpan.pair.com has address 66.39.76.93
Last year, I got different logs from Graham and Pair. Any other
suggestions since they're apparently the same now? Mirror-owners I
should talk to?
xoa
--
Andy Lester => [EMAIL PROTECTED
I'll be redoing the Phalanx 100 this week. I'm hoping to get FTP logs
from pair.com and from cpan.org. If anyone else has FTP logs they can
submit to me, I'd love to have 'em.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Thu, Aug 05, 2004 at 11:51:09PM -0500, Andy Lester wrote:
> It'd be swell if someone generated Devel::Cover dumps for the
> Phalanx 100. Like http://pjcj.sytes.net/cpancover/ but for
> http://qa.perl.org/phalanx/distros.html.
It would be nice if anyone doing the Class::DBI one
if someone generated Devel::Cover dumps for the
Phalanx 100. Like http://pjcj.sytes.net/cpancover/ but for
http://qa.perl.org/phalanx/distros.html.
I also wonder if the 100 would be different now than when I created it a
year ago.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
>> I just ran into a similar "problem" in POE::Driver::SysRW. For
>> portability I have a couple lines similar to
>>
>> $! = 0 if $! == EAGAIN or $! == EWOULDBLOCK;
>>
>> EAGAIN and EWOULDBLOCK are identical on most systems. In fact, one is
>> usually defined in terms of the other. They dif
Rocco Caputo wrote:
On Sun, Jul 11, 2004 at 10:09:38PM +0200, James Mastros wrote:
All unreachable code is either people misusing the term "unreachable", a
bug in Devel::Cover, or dead code that should be removed.
Here's a puzzle, then.
I just ran into a similar "problem" in POE::Driver::SysRW. F
On Sun, Jul 11, 2004 at 10:09:38PM +0200, James Mastros wrote:
>
> All unreachable code is either people misusing the term "unreachable", a
> bug in Devel::Cover, or dead code that should be removed.
Here's a puzzle, then.
I just ran into a similar "problem" in POE::Driver::SysRW. For
portabil
On Jul 11, 2004, at 4:09 PM, James Mastros wrote:
package Foo;
sub new {
my $class=shift;
$class=ref($class)||$class;
bless [], $class;
}
eval { Foo::new(); }
is($!, "new dies when called as a function");
Actually this doesn't die, it does even worse, given this code:
package Foo;
sub new {
foo() by itself, and
presumably Devel::Cover never notices the existence of the || in the source.
Is that a bug, then? Or is it something else? And how should I notate
that, keeping in mind the goals of Phalanx, so that it's clearly visible
that no test of that condition's failure can
On Jul 11, 2004, at 11:09 AM, Michael G Schwern wrote:
I document private code like this:
=begin private
put your normal POD here
=end private
perldoc won't show the POD but someone reading through the code (and
thus
needing to know about private functions) will see it. And POD is very
readable i
On Sun, Jul 11, 2004 at 03:07:22PM -0400, stevan little ([EMAIL PROTECTED]) wrote:
> I think that reg-ex is too loose (and incorrect, but I know you really
> meant /^[A-Z]+$/). I would rather see it check for all the documented
> magic methods rather than a catch all for UPPERCASE names. Even tho
On Sun, Jul 11, 2004 at 12:26:44PM -0400, stevan little ([EMAIL PROTECTED]) wrote:
> As for POD, in most cases, I agree with you, but to say you should have
> 100% POD coverage brings up several other questions, such as; Should I
> document private methods? What about modules which are meant to b
Micheal,
On Jul 11, 2004, at 2:09 PM, Michael G Schwern wrote:
On Sun, Jul 11, 2004 at 12:26:44PM -0400, stevan little wrote:
As for POD, in most cases, I agree with you, but to say you should
have
100% POD coverage brings up several other questions, such as; Should I
document private methods?
IMP
Subject: Re: Phalanx: What if full coverage isn't possible? (fwd)
From: stevan little <[EMAIL PROTECTED]>
Date: Sun, 11 Jul 2004 12:26:44 -0400
}As for POD, in most cases, I agree with you, but to say you should have
}100% POD coverage brings up several other questions, such a
On Sun, Jul 11, 2004 at 12:26:44PM -0400, stevan little wrote:
> As for POD, in most cases, I agree with you, but to say you should have
> 100% POD coverage brings up several other questions, such as; Should I
> document private methods?
IMPO yes, but Pod::Coverage (and thus Devel::Cover) will
On Jul 9, 2004, at 6:06 PM, Andy Lester wrote:
Don't be mesmerized by 100% coverage.
Agreed 100% here. However, I stand by my original statement that you
CAN have 100% coverage on subroutines and pod. Any disagreement on
that
one?
I agree with having 100% on subroutines, and I would add that 100
Michael G Schwern wrote:
Test coverage is a useful *heuristic* for test effectiveness. Like all
heuristics if you push it too far it falls apart. Get as close to 100% as
is useful and don't worry about the rest.
Indeed. Brian Marick wrote a great paper on this topic - "How to Misuse
Code Covera
On 7/9/2004 4:57 PM, Paul Johnson wrote:
> On Fri, Jul 09, 2004 at 12:10:52PM -0500, Pete Krawczyk wrote:
>
>> Consider [code with unreachable path] Devel::Cover will always see that as
>> a partial test, and never a full test: Is that a bug, then?
That's for you to decide. The lack of coverage s
/perl/URI-orig/blib-lib-URI-pm--condition.html#L57
>
> I don't like that code anyway, since it basically boils down to
> $impclass = $impclass = 'URI::_foreign';
> assuming $impclass and $scheme aren't set.
>
> Is that a bug, then? Or is it someth
On Fri, Jul 09, 2004 at 06:31:09PM -0400, Michael G Schwern wrote:
> Looking through a coverage analysis I just ran, here's some more idioms
> that trip up 100% coverage.
>
> my $foo = $bar || '';
>
> my $foo = $bar || 1;
>
> $this || return;
>
> Basically anything of the "$f
On Fri, Jul 09, 2004 at 05:06:09PM -0500, Andy Lester wrote:
> > There's a whole set of these sort of problems.
Looking through a coverage analysis I just ran, here's some more idioms
that trip up 100% coverage.
my $foo = $bar || '';
my $foo = $bar || 1;
$this || retu
* Pete Krawczyk <[EMAIL PROTECTED]> [2004-07-09T13:10:52]
>
> Devel::Cover will always see that as a partial test, and never a full
> test:
> [ ... ]
> Is that a bug, then? Or is it something else? And how should I notate
> that, keeping in mind the goals of Phala
On Fri, Jul 09, 2004 at 12:10:52PM -0500, Pete Krawczyk wrote:
> Consider the following code:
>
> $impclass ||= implementor($scheme) ||
> do {
> require URI::_foreign;
> $impclass = 'URI::_foreign';
> };
>
> That's in URI.pm, lines 54-58.
>
> Devel::Co
> There's a whole set of these sort of problems.
>
> sub new {
> my $proto = shift;
> my $class = ref $proto || $proto;
In this case, we probably don't want that ANYWAY. That's what I did
when I was through Data::Page for Leon Brocard, and it's now at 100%
coverage, across the
ass = 'URI::_foreign';
assuming $impclass and $scheme aren't set.
Is that a bug, then? Or is it something else? And how should I notate
that, keeping in mind the goals of Phalanx, so that it's clearly visible
that no test of that condition's failure can truly take
On Thu, 10 Jun 2004, Andy Lester wrote:
> I'm thinking that maybe instead of people picking a module to do, and
> then working on it, which has so far not worked at all, that we should
> hold up a module (or a handful of them) and say "OK, this is what we're
> working on". It certainly seemed to
Andy,
I agree, it an intimidating idea to think that you have to take on
responsibility for a whole module. I enjoyed working on the DBI tests,
and when I next have some spare time between projects, I plan on
helping again, either with DBI or some other module. You should really
encourage that
On Thu, Jun 10, 2004 at 03:35:23PM +0100, Nicholas Clark ([EMAIL PROTECTED]) wrote:
> Well, how people acn help, particularly how they can help even if they don't
> think they have time to be *the* one true hoplite for a project.
I'm thinking that maybe instead of people picking a module to do, an
On Thu, Jun 10, 2004 at 09:27:09AM -0500, Andy Lester wrote:
> So I'm giving an LT on Phalanx next week in Buffalo. Anything in
> particular y'all think I should mention?
> A brief discussion of Phalanx, a project devoted to increasing the
> testing coverage of Perl and
So I'm giving an LT on Phalanx next week in Buffalo. Anything in
particular y'all think I should mention?
xoxo,
Andy
To: Andy Lester <[EMAIL PROTECTED]>
Subject: Your Lightning Talk
Your proposal for a Lightning Talk at the 2004 YAPC::America::North has been accepted.
On May 9, 2004, at 6:48 PM, Tim Bunce wrote:
On Sat, May 08, 2004 at 03:16:45PM -0400, stevan little wrote:
On May 8, 2004, at 2:25 PM, Tim Bunce wrote:
Just some (and thanks for that). But there are still a few with
custom ok() subs and some others using the plain Test module.
Tim.
Make that 2 le
On Sat, May 08, 2004 at 03:16:45PM -0400, stevan little wrote:
> On May 8, 2004, at 2:25 PM, Tim Bunce wrote:
> >
> >Just some (and thanks for that). But there are still a few with
> >custom ok() subs and some others using the plain Test module.
> >
> >Tim.
>
> Make that 2 less tests doing the fun
On May 8, 2004, at 2:25 PM, Tim Bunce wrote:
Just some (and thanks for that). But there are still a few with
custom ok() subs and some others using the plain Test module.
Tim.
Make that 2 less tests doing the funky stuff, this is actually going a
lot faster than I thought it was going to.
I hope
On Fri, May 07, 2004 at 05:14:39PM -0500, Andy Lester wrote:
> On Fri, May 07, 2004 at 10:31:49PM +0100, Tim Bunce ([EMAIL PROTECTED]) wrote:
> > Here's what I'd like to see done soonish:
> >
> > 1. Convert all exisiting test files to Test::More
> > 2. Parts of t/10examp.t should be broken out t
Andy,
Devel::Cover and I are already very well aquainted, its one of my
favorite tools actually.
steve
On May 7, 2004, at 6:14 PM, Andy Lester wrote:
On Fri, May 07, 2004 at 10:31:49PM +0100, Tim Bunce
([EMAIL PROTECTED]) wrote:
Here's what I'd like to see done soonish:
1. Convert all exisiting
On Fri, May 07, 2004 at 10:31:49PM +0100, Tim Bunce ([EMAIL PROTECTED]) wrote:
> Here's what I'd like to see done soonish:
>
> 1. Convert all exisiting test files to Test::More
> 2. Parts of t/10examp.t should be broken out to separate test scripts
> 3. Start increasing coverage, especially pri
Tim,
I subscribed to dbi-dev and dbi-users both. I will download and install
subversion this weekend (i have been meaning to do this, but putting it
off). And then I will get to work on #1 on your list (convert all tests
to Test::More). I will also keep in mind your larger goal of developing
th
On Fri, May 07, 2004 at 03:03:10PM -0400, stevan little wrote:
> On May 7, 2004, at 1:37 PM, Tim Bunce wrote:
> >
> >But still no hoplite has actually adopted the DBI...
>
> Since I would like to get involved here, and (with the exception of
> HTML::Template, which is already taken) the module I
stevan little wrote:
On May 7, 2004, at 1:37 PM, Tim Bunce wrote:
But still no hoplite has actually adopted the DBI...
Since I would like to get involved here, and (with the exception of
HTML::Template, which is already taken) the module I know best in the
100 is DBI. Besides, it seems like Tim
On May 7, 2004, at 1:37 PM, Tim Bunce wrote:
But still no hoplite has actually adopted the DBI...
Since I would like to get involved here, and (with the exception of
HTML::Template, which is already taken) the module I know best in the
100 is DBI. Besides, it seems like Tim really want's someone
Maybe daily or weekly reminders would be helpful, because I know most of the
time when I go home from work I rarely to almost never thing about the
Phalanx project. I just think there is a huge lack of communication between
Hoplites. It would be nice to have a system where you can ask other
On Fri, May 07, 2004 at 08:12:32AM -0500, James.FitzGibbon ([EMAIL PROTECTED]) wrote:
> > Or...we could set some deadlines...like have 50% of your module tested
> by YAPC, and/or possibly have some incentives.
>
> How about asking YAS if they would offer reduced price admission if you
> flesh out
> > > Encouraging simple status reports, say monthly, may help ensure
> > > progress.
>
> > Or...we could set some deadlines...like have 50% of your
> module tested
> by YAPC, and/or possibly have some incentives.
>
> Say "..50%.. of modules tested by YAPC or we cancel the conference"?
> > Encouraging simple status reports, say monthly, may help
> > ensure progress.
> Or...we could set some deadlines...like have 50% of your module tested
by YAPC, and/or possibly have some incentives.
Say "..50%.. of modules tested by YAPC or we cancel the conference"?
How about asking YAS if t
> Encouraging simple status reports, say monthly, may help
> ensure progress.
Or...we could set some deadlines...like have 50% of your module tested by
YAPC, and/or possibly have some incentives.
~~Andrew
On Thu, May 06, 2004 at 05:09:03PM -0600, Jim Cromie wrote:
> stevan little wrote:
>
> >I looked on the site (http://qa.perl.org/phalanx/), but there was
> >nothing said about how to get involved in this project. Are you
> >looking for help? And if so, how can I help?
&
stevan little wrote:
I looked on the site (http://qa.perl.org/phalanx/), but there was
nothing said about how to get involved in this project. Are you
looking for help? And if so, how can I help?
Thanks,
Steve
sure. Pick a module from phalanx 100, based upon your personal uses,
or whichever
I looked on the site (http://qa.perl.org/phalanx/), but there was
nothing said about how to get involved in this project. Are you looking
for help? And if so, how can I help?
Thanks,
Steve
So can someone tell me what the Bundle is here for? What's it trying to
achieve? How would someone use it? Is it part of a bigger test thing
I'm not aware of?
Curious,
xoxo,
Andy
On Tuesday, Oct 28, 2003, at 23:48 Europe/London, Michael G Schwern
wrote:
On Tue, Oct 28, 2003 at 08:17:24PM +, Adrian Howard wrote:
This may be a dim question but why scan blib and lib?
[snip]
my $blib = File::Spec->catfile(qw(blib lib));
[snip]
That's not blib and lib, that's a cross p
On Wed, Oct 29, 2003 at 12:38:31PM -0600, Andy Lester wrote:
> >1) DBI (Tim Bunce specifically asked for help in re-designing the test
> > suite).
> >
> >2) CPANPLUS.
> >
> >3) Module::Build.
>
> I'm all for having those biggies handled by Phalan
ll mail the list and I expect we'll get a consensus fairly easily & then
mail Andy.
> As for how to get started, I just followed the excellent checklist
> at http://qa.perl.org/phalanx/modules.html and it has worked like
> a charm. If a module you really really like is already ta
irely. When I came back from OSCON I was awed by how much
raw Perl power is in London.pm, and how much they drive the Perl
community, especially on Perl 6. I came back to Chicago.pm and
challenged them to do something similar with Phalanx.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
1 - 100 of 188 matches
Mail list logo
