There's very little case law around Open Source software licenses, but this week we've seen an interesting case involving the Artistic License, under which Perl is distributed.
The decision makes two important points: (1) the Artistic License is a contract and (2) the failure to include the copyright notices was not a "restriction" on the scope of the license. The first point is important because the Free Software Foundation and some lawyers have taken the position that open source licenses are not contracts. They have good reasons for wishing to avoid some contract formalities, but this position has complicated discussions about the enforceability and remedies for open source licenses.
The second point is very important because it deals with remedies. Generally, the remedy for contract violations under US law is damages, not "injunctive relief" (which means that the court order a party to cease their violation). On the other hand, copyright infringement generally includes a presumption that injunctive relief is appropriate. Thus, the question of whether the violation of a license is a contract violiation or copyright infringement (it can be both) is very important, because licensors would prefer to obtain an injunction prohibiting the breach of the license.
As pointed out in the article linked above, this decision in relation to the Artistic License doesn't apply to other licenses. This will no doubt have some bearing on how Perl chooses to use the Artistic 2.0 license.
An article on use Perl asks:
- Could the same thing happen under the Artistic 2.0 or Will further revisions to the Artistic license be required?
- Should adoption of Artistic 2.0 wait until Perl 5.10?
However, as a District Court case, this decision only applies in California -- admittedly a very influential place in the tech world, but we can still hope that this decision, which many see as a bad one, will be overturned in a higher court.
ohloh.net is a social networking site built around open source projects. People give kudos to each other, and there's some sort of ranking system such that I'm #277 of 29,000 users, which shows that their ranking system is fueled by psychedelics.
ohloh has some cool analyses for the projects, since they analyze the public source repositories of the projects they track. For instance, here's the codebase size for Parrot
There are also great tools to look at who's committed to projects. Take a look at the list of committers to the Parrot project. This is a great use of sparklines to reveal the history of the project through the amount of code committed to the project.
See how Leopold Tösch works like crazy for years on Parrot, then disappears.
My Parrot contributions started out modest, and then I lost interest for a year, then came back a year later.
Compare that to my Perl 5 contributions which are more sporadic, but over a longer period of time.
I've never seen analyses like these done before. If there are others, please let me know in the comments.
Simon Cozens has been mostly absent from the Perl community since he's gone off to mission work in Japan, but he writes in to tell us:
I've begun the process of putting my (very) old book Beginning Perl, first edition, into a wiki to allow it to be updated, corrected and annotated: http://books.simon-cozens.org/index.php/Beginning_Perl It's a very rough data dump at the moment and needs a lot of gardening, but hopefully it's still a useful resource.Thanks to Simon for making this available to the community.
Welcome to Perl Buzz! Andy and I are excited to be launching a new Perl blog, and hope you'll like it as much as we do.
A lot of people have been asking us, "Why do we need another Perl blog?" We believe that there's room for as many Perl blogs, journals, and news sites as people want to set up. Each has its own flavour and will appeal to different groups of people, and that's just fine. Perl Buzz's unique selling point is that we're bringing a shiny, happy view of the Perl world to the masses. Some other sites focus on communicating within the existing Perl community. We'll do that, too, but we also hope to reach out to those who aren't yet part of the tribe, and show them just how cool Perl is.
So, let's take a look at what Perl Buzz has to offer.
The main Perl Buzz blog, which you're reading right now, is all about news, reviews, and what's exciting in the Perl world. We're interested in everything from impressive Perl websites (see our review of iusethis.com) to releases of free and commercial Perl software (like Movable Type 4.0, released last week) to interesting uses of Perl you might not know about (like attributes or how to write a LOLCODE parser using Parse::RecDescent).
Over in Project Hum, we track what's going on in Perl projects. Anything from performance tweaks to calls for help to translations of docs into other languages. We watch other Perl news sources to find out what's going on, but please let us know if you'd like us to post something about your project!
CPAN Watch is all about what's noteworthy on CPAN. Watching the full feed of CPAN uploads can be like drinking from the firehose, so we filter it and just post the most interesting releases, along with why you should care.
You can subscribe to any or all of the feeds via RSS; see the links in our sidebar.
There are basically two schools of testing that is either Test::Harness based or Test::Class based. Test::Harness school runs a series of scripts which have tests in them top down, usually with a plan at the top of the file (plan is the number of tests you are planning on running). Test::Class manages itself, using Test::Class for tests and to run them...
Most of my test files use Test::More and little else, but Test::Class is a great way to organize tests for larger projects. Best of all, it works with all test modules built on Test::Builder, which is to say almost every test module on the CPAN.