Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

Alias
  (email not shown publicly)
http://ali.as/

Journal of Alias (5735)

Saturday December 06, 2008
01:32 AM

Microsoft partners with Strawberry Perl to improve the CPAN

[ #38036 ]

It would appear I have finally I achieved my long-time goal of slashdotting pudge's private Slashdot beta testing site :)

For the last 2 years, starting with the Vertical Metre of Beer competition, I've been working to make Win32 a truly first class citizen of the Perl platform world.

The goal, as I keep repeating on the Strawbery Perl website, is Complete Platform Equality. Not different, or "better", just equal and identical. When writing Perl code, your platform should ideally be irrelevant.

I feel that Strawberry Perl has managed to achieve this for the Perl core.

In the year since it was released, the community has used it to help fix many of the largest and most important CPAN modules as well. Modules that have improved their release process and are now reliably problem-free on Windows include Bundle::CPAN, the DateTime family, Template Toolkit, POE, Wx, and a number of XML modules.

Unfortunately, we are now reaching the end of the large important modules that have big teams and are relatively well resourced. For smaller modules, and many individual CPAN authors, problems accessing legal licenses or the hardware to run it on, is now becomming a critical limiting factor. Some authors have simply never used Windows before, and don't want the hassle of learning how to set it up.

So it's time to remove that problem.

At YAPC::NA this year, at the beginning of my world tour, I was introduced to an attendee from the Microsoft Open Source Software Lab. He was interested in finding out if there was anything Microsoft could do to help with Strawberry.

Later in my tour, after diverting my first week in Portland over to Seattle, with Ingy and I took a trip out to Redmond to visit the Microsoft OSSL. After some discussions there, lunch, and a look at what they are doing for people like the Samba team, one interesting very possibility started to emerge.

A week or two later at OSCON, I managed to catch up with Sam Ramji (the head of the OSSL) briefly in the hallway track after his keynote, and bounced the idea off him directly. He was extremely positive about it, so after I returned to Australia I polished the idea into a formal proposal and sent it off for consideration.

The proposal was accepted about 3 weeks later, and last night at OSDC we announced a new partnership between Microsoft and Strawberry Perl.

So, finally, I can now stop with the waffling around and just unveil The Sekrit.

Commencing this month, Microsoft will be providing every CPAN author with free access to a centrally-hosted virtual machine environment containing every major version of Windows.

The result is now practically the entire Perl community has a zero-cost and zero-setup way to doing light development, problem replication, debugging, and ad-hoc hesting on every version of Windows.

This arrangement is particularly amazing because it is, to my knowledge, several orders of magnitude larger than anything of this nature ever attempted before with the Open Source community.

Neither the Microsoft guys nor I know quite what is going to happen once we turn this baby on. With 7,000 potential users and endless possible use cases, I expect at the very least something of an adventure. :)

So as a result, we are treating the initial implementation as completely experimental. Within Microsoft, the partnership is being lead directly by the locals in Microsoft Australia.

They have already procured and installed the hardware, and the OSSL guys in Redmond have prepared the Windows system images.

The actual hosting service itself needs to be provided by a non-Microsoft Sydney-based hosting company, due to some legal wrinkles relating to the Australian Trade Practices Act.

Once some final paperwork issues are resolved (which should happen over the next few business days) the admin passwords will be handed over to me, and then we have to work out the specific mechanics for how to manage everyone@cpan.org, and how we'll be dealing with instancing and rollback of the environments.

The launch set of Windows system images is currently exoected to be the following:

Windows XP Professional
Windows Server 2003 32-bit
Windows Server 2003 64-bit
Windows Vista Ultimate
Windows Server 2008 32-bit
Windows Server 2008 64-bit

All environments will be updated to the current service packs, and are (I believe) the default English (American) versions.

It's worth nothing that this initial set is based on the MINIMUM useful variations I identified as necesary. Once the environment is running, it's likely that more environments will be added.

I've already suggested we add internationalisation as the next major priority, so hopefully we can also shortly see localised instanced that represent typical install configurations from Germany, Japan and China.

As for types of activities you can use the environment for, initially I want to contain it to relatively light activities to prevent over-loading the servers.

Ad-hoc testing, debugging and experimentation is fine. Resource-intensive CPAN Testers installs and other heavy smoke testing activities will initially not be allowed, until I have some idea of just what the resource implications of this whole exercise will be.

I'd very much like to avoid melting the servers for at LEAST the first week :)

More information (and press releases) will follow, the entire program under which this partnership will be run is so new it's only just been given a name, so some of the organisational details will ironed out as we go.

But for now, to all the CPAN authors, all I have to add is...

Merry Christmas

Adam K

P.S. Or your appropriate equivalent religious or non-religious event, if any, occuring during the month of December, etc etc

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Seeing as I've now moved to Linux completely, this will hopefully prove to be quite useful. However, one aspect I'd be interested to see, and would make it most useful for one particular distribution of mine, is will it have an MS Office Suite installed? Specifically for me will it have Outlook install?

    I can potentially see a stumbling block for installing Outlook (or any email software), but hopefully monitoring will help to keep any potential abuse in check.

    Regards CPAN Testers, it might be worth looking

  • wow ! to quote "Steve Jobs" ... This is huge :)
  • Does that mean that I will be able to work on the 64-bit "port" of Win32::API ? :-)
  • Perl has been a first class citizen on Win32 starting with the GSAR port back in late 90s, then Perl for Win32 and now ActivePerl.

    In fact ActivePerl was more up to date than unix Perl during the late 5.005 and 5.6 because the pumpkin was primarily a Win32 developer.

    If you want to find the second class citizens in the Perl world look at OS2, Aix, Hpux, and other strange unixes. I know you want to make Perl better and are working hard on it, but insulting the people who put together the foundation you're

    • > If you want to find the second class citizens in the Perl world look at OS2, Aix, Hpux, and other strange unixes.

      Consider it one-and-a-half class then...

      > Perl has been a first class citizen on Win32 starting with the GSAR port back in late 90s, then Perl for Win32 and now ActivePerl.

      I don't consider a Perl that doesn't support CPAN properly "first class".

      • Hey, you're acting as an asshole!
        I consider ActivePerl firstclass, and strawberry perl is some strange shit distracting resources - and so what?
        Give some respect to people who did the port to win32!
        • ... and so what?

          Read the article and find out. If it weren't for the work of ActiveState and all of the work that went into Perl 5.6.0 to enable Win32 support, this wouldn't be possible. No one but you and Zeek have disputed that.

      • Sure Perl works and there is ActiveState and this is all very significant, appreciated, and important, but the CPAN is a very important part of any non-trivial Perl application, so without top-notch support for the CPAN, Perl applications end up as second-class citizens on Win32, which Strawberry goes a long way toward correcting.

  • This is wonderful!
    • I couldn't agree more.

      I would not be using Perl on Windows without Strawberry Perl (SP).

      I am simply reluctant to invest in yet another product (Active Perl) when with SP I can reuse the techniques so familiar to me in the old country (Unix).

      For me, SP has been a huge success. Since the second release I have been able to get modules such as Net::DNS going pretty easily (and they sometimes have been a bitch on Unix).

      Thanks alias.

      Yes, I donate to P5/P6 development because it makes my lousy

  • While I doubt I'll be porting over my currently [cpan.org] existing modules [cpan.org] anytime soon ;-), I see this as an incredibly good thing and congratulate you on bringing it about. Maybe TPF could take up the cue and try to set up something similar for other OSes out there (I for one would love to have an OS X and FreeBSD setup to test on).

    One question though, how will us *NIX-only folks access the servers? Will there be an ssh login? Possibly a cygwin install?
  • Alias - you've done some great work on this project. Thanks for your continued efforts. You're making it so that I don't have to stutter and mumble so much when people tell me that they want to learn perl and say that they only use windows. Consider this move from Microsoft validation that what you're doing is good and useful. It is.

  • there are lots of Windows users of my modules and it pains me to be unable to fix their bugs (or even see if the report -is- a bug). many thanks indeed to you, Ingy, and the OSSL folks!
  • As the great Keanu would say in such circumstances: whoa.

    This is very, very, veeeery cool.

  • For testing purposes, I don't want to personally log into six different O/Ss. It would be nice if a CPAN smoker was set up for each Strawberry and Windows combination.

    • There already is a number of these, thanks to BinGOs. Not all of them, but quite a few.

      • But nowhere near the number that there are for other platforms. The number of Windows reports I get is way too small.

  • While this is great news, I was hoping for something more, like them making Perl in IIS (FastCGI/win32 mod_perl) a first class language much like they declared for PHP/FastCGI under IIS7.

  • This is really nice news for obvious reasons.

    Now it is probably no sekrit that I don't follow p5p, haven't ever read the perl C source to find the cause of my bug, and have referred folks to perldoc perlport without doing so much as skim reading it myself.

    So with those facts of ignorance entered into evidence, what would have really been mind blowing if M$ engineers had decided to start hacking on the perl core to improve the port.

    • That would indeed be cool – in fact it would be cool if any of the big players in IT earmarked any amount of money to aid Perl. But without wanting to detract from your point… it wouldn’t replace this VM farm – because this is about improving Windows support not in perl, but in CPAN modules.