On Fri, Jan 27, 2012 at 3:45 PM, Ricardo Signes
<[email protected]> wrote:
> * Ricardo Signes <[email protected]> [2012-01-18T11:43:34]
>> Assuming it can, and we can provide a box suitable for login, build, and
>> test, who can be counted on to champion these fixes?  We'd be looking for
>> someone who can:
>>
>>   a. figure out how 5.15.x stands, now
>>   b. try to make sure it passes its tests
>>   c. try to figure out where EBCDIC is broken but untested
>>   d. fix it
>>   e. run a monthly iteration of testing around each 5.odd.x release

I bet there are about 17 steps in between a and b, but I guess that's
the "figure out" part of a.

> So far, nobody has expressed his or her burning desire to get access to a z/OS
> box and champion a z/OS-and-EBCDIC-portable perl 5.
>
> I'm posting this followup/reminder just in case the first was missed by an
> otherwise eager volunteer, and I won't post another one.

And I'm adding a cc to perl-mvs (just like I did back in September)
since one thing that earlier thread demonstrated is that while no one
on perl5-porters is admitting to knowledge of or access to z/OS, there
are people on perl-mvs who are currently running Perl on that platform
and would like to see that capability continue even if they can't
currently contribute to making it happen themselves.  They are the
biggest stakeholders in this, after all, though perhaps some of them
were satisfied with IBM's answer that if IBM decides a current port is
needed, IBM will do it.

I'll just note in addition that in the early stages of a renewed
porting effort, domain expertise may well be more important than Perl
expertise.  Getting a build environment set up, flinging the Perl
sources at it, examining the broken pieces for clues about what to do
next, and so forth, will likely go for several rounds before one gets
very deep into Perl's innards.  Of course both Perl and z/OS expertise
would ultimately be required.

> BTW, if you think this sounds great, but aren't big on z/OS a list of other
> platforms to be considered for deprecation was mentioned in the 
> "perl5160delta"
> thread.
>
> --
> rjbs

Reply via email to