2010/1/3 Eric Wilhelm
> >>>add one more level and make
> >> > the tab be "History", then history.html is a page which says " >> > href="phalanx">Phalanx 100 started in 2003..."
> >> >
> >> > Perhaps somebody would like to put together a more comprehensive
> >> > QA timeline including the developm
# from Leo Lapworth
# on Saturday 02 January 2010 10:57:
>I've renamed to 'inactive' for now.
>
>I like Eric's idea about history if someone wants to create that.
>
>>>add one more level and make
>> > the tab be "History", then history.html is a page which says "> > href="phalanx">Phalanx 100 star
--- On Sat, 2/1/10, Leo Lapworth wrote:
> From: Leo Lapworth
> I've renamed to 'inactive' for now.
>
> I like Eric's idea about history if someone wants to create
> that.
I'll second that. From a pure marketing perspective, "archive", "inactive" and
"old" all imply "dead". "History" implies
I've renamed to 'inactive' for now.
I like Eric's idea about history if someone wants to create that.
Cheers
Leo
2010/1/2 Shaun Fryer
> How about "inactive" rather than archive or old.
> --
> Shaun Fryer
>
>
> On Sat, Jan 2, 2010 at 1:36 PM, Eric Wilhelm wrote:
>
> > # from Leo Lapworth
> >
How about "inactive" rather than archive or old.
--
Shaun Fryer
On Sat, Jan 2, 2010 at 1:36 PM, Eric Wilhelm wrote:
> # from Leo Lapworth
> # on Saturday 02 January 2010 08:35:
>
> >I've renamed Old to Archive, but you've not actually told me what
> > would be best for the other stuff.
>
> "Arc
# from Leo Lapworth
# on Saturday 02 January 2010 08:35:
>I've renamed Old to Archive, but you've not actually told me what
> would be best for the other stuff.
"Archive" still implies "Old". Why not take the tab out of the
navigation bar entirely? Or, at least add one more level and make the
I missed this - apologies.
Now uploaded.
Cheers
Leo
2010/1/2 David Golden
> For the record, I'll second Barbie's suggestion.
>
> David
>
> On Wed, Dec 30, 2009 at 4:16 AM, Barbie wrote:
> > On Tue, Dec 29, 2009 at 10:10:48PM -0500, David Golden wrote:
> >> On Tue, Dec 29, 2009 at 4:54 PM, Le
Hi,
2010/1/2 Salve J Nilsen
> A few comments,
>
Thanks.
> Leo Lapworth said:
>
>> 2010/1/2 James E Keenan
>>
>> 3) Phalanx
>>
>> Though in one sense it pains me to say it, Phalanx does not need to be a
>>> major tab. It can be demoted to a link somewhere.
>>>
>>
>>
>>
>>
>> I have put it
For the record, I'll second Barbie's suggestion.
David
On Wed, Dec 30, 2009 at 4:16 AM, Barbie wrote:
> On Tue, Dec 29, 2009 at 10:10:48PM -0500, David Golden wrote:
>> On Tue, Dec 29, 2009 at 4:54 PM, Leo Lapworth wrote:
>> > 2) Testing CPAN
>> >
>> > Shaun, would you mind looking at this?
>>
James E Keenan said:
I learned a tremendous amount about testing, code coverage and
writing testable code from the Phalanx project -- knowledge which
has served me well, particularly in the Parrot project. The
approach to 'phalanx'-ing a module can be applied by anyone (and I'm
happy to men
Hi, Leo :)
A few comments,
Leo Lapworth said:
2010/1/2 James E Keenan
3) Phalanx
Though in one sense it pains me to say it, Phalanx does not need to
be a major tab. It can be demoted to a link somewhere.
I have put it is as a tab on the right called 'old projects'.
I removed the 'C
Please note this is cross posted.
2010/1/2 James E Keenan
> Leo Lapworth wrote:
3) Phalanx
>>
>
> Though in one sense it pains me to say it, Phalanx does not need to be a
> major tab. It can be demoted to a link somewhere.
I have put it is as a tab on the right called 'old projects'.
I re
Leo Lapworth wrote:
Hi,
Please note this is cross posted.
Several of the QA people have kindly said they will help with updating
http://qa.perl.org/.
3) Phalanx
Though in one sense it pains me to say it, Phalanx does not need to be a
major tab. It can be demoted to a link somewhere.
The
> 1) Testing your code - I think this will need the largest amount of work.
>
> Hilary, could I ask you to have a look at this?
>
> - Are the articles the best we can link to?
> - Do we need those articles if we update the rest of the content.
> - can the test-modules.html and testing-guidelines.
> 1) Testing your code - I think this will need the largest amount of work.
>
> Hilary, could I ask you to have a look at this?
>
> - Are the articles the best we can link to?
> - Do we need those articles if we update the rest of the content.
> - can the test-modules.html and testing-guidelines.
On Tue, Dec 29, 2009 at 10:10:48PM -0500, David Golden wrote:
> On Tue, Dec 29, 2009 at 4:54 PM, Leo Lapworth wrote:
> > 2) Testing CPAN
> >
> > Shaun, would you mind looking at this?
> >
> > - Just needs a quick review/update
>
> The CPAN Testers stuff looks fine to me. The Daily Build section
On Tue, Dec 29, 2009 at 4:54 PM, Leo Lapworth wrote:
> 2) Testing CPAN
>
> Shaun, would you mind looking at this?
>
> - Just needs a quick review/update
The CPAN Testers stuff looks fine to me. The Daily Build section
should really go to a new tab "Testing Perl" or "Testing Perl Source"
or "Tes
On Saturday 19 Dec 2009 14:54:42 Leo Lapworth wrote:
> Hi,
>
> I cleaned up http://qa.perl.org/ but the content needs a complete
> review/update.
>
> Is anyone interested in doing this?
>
I am!
You can contact me here:
http://www.shlomifish.org/me/contact-me/
Regards,
Shlomi Fish
>
2009/12/20 Salve J Nilsen
> Hi, Leo! Welcome to perl-qa! :)
Thanks
Sweet. But does ALL of it need an update? If not, which parts are you
> specifically thinking of?
Probably not all of it.
> Is anyone interested in doing this?
>
>
Wow lots of you are, Thanks Hilary and Shaun as well - coo
Hi, Leo! Welcome to perl-qa! :)
Leo Lapworth said:
Hi,
I cleaned up http://qa.perl.org/ but the content needs a complete
review/update.
Sweet. But does ALL of it need an update? If not, which parts are you
specifically thinking of?
Is anyone interested in doing this?
Ask me in febuar
On Fri, Aug 24, 2001 at 01:24:47AM -0700, Ask Bjoern Hansen wrote:
>
> Getting the word out about the various projects is something we
> need, so I made
>
> http://qa.perl.org/
>
> Schwern, I need some comments from you. :-)
Ummm, perl-qa-metrics is a mailing list about developing code metri
21 matches
Mail list logo
