PORO isn't a term that was born in the Ruby community. In fact the original POXO was POJO.
The term was coined while Rebecca Parsons, Josh MacKenzie and I were preparing for a talk at a conference in September 2000. In the talk we were pointing out the many benefits of encoding business logic into regular java objects...POROs, like POJOs, are often found in discussions about simplicity and testing.
POJO is an acronym for Plain Old Java Object, and is favoured by advocates of the idea that the simpler the design, the better. --WikipediaThere's plenty of discussion around POJOs on the web, most of which applies to POROs as well.