Smalltalk › Pharo › Pharo Smalltalk Users

Please port external libraries & frameworks to Pharo 3.0 NOW !

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

1 message

Sven Van Caekenberghe-2

Please port external libraries & frameworks to Pharo 3.0 NOW !

Dear fellow Pharoers,

Pharo 2.0 was released in March 2013, after which development of Pharo 3.0 started. Since December 2013 we stopped adding new features and started concentrating on fixing bugs. We plan to release Pharo 3.0 in March 2014.

You can help: please port external libraries & frameworks to Pharo 3.0 NOW, before it is released, not after. You can help us tremendously by doing this. Together we can improve the quality and polish for a great release.

Today we already have quite some external libraries, frameworks and applications running successfully in Pharo 3, among them large ones like Moose (https://ci.inria.fr/moose/job/moose-5.0/) and Seaside (https://ci.inria.fr/pharo-contribution/job/Seaside/). But we need more and we need people collaborating, because real life projects have lots of dependencies that need to be available.

Luckily there is a CI infrastructure available to help you. You should also follow some conventions to fit into the ecosystem.

- have good unit tests

- use Monticello for source code management

- store code publicly, preferably at http://www.smalltalkhub.com/

- use Metacello for package and configuration management

- add your configuration where the configuration browser can find it, at least in http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main

- use the CI infrastructure at https://ci.inria.fr/pharo-contribution/

For example, Neo-CSV, can be loaded in Pharo 3.0 using its Metacello configuration with just one click on 'Install Stable Version':

The code lives in various repositories, including on StHub, at http://www.smalltalkhub.com/#!/~SvenVanCaekenberghe/Neo

There is a CI job checking all unit tests each time either Pharo 2.0, Pharo 3.0 or the library code changes, https://ci.inria.fr/pharo-contribution/job/NeoCSV/ and reporting all failures immediately. You can test both stable and development (or bleedingEdge) versions for a real build matrix.

And there is external documentation, https://github.com/svenvc/docs/blob/master/neo/neo-csv-paper.md ;-)

Even if you are not the original author, but just a user of (a) particular package(s), it would be useful if you tried loading the package(s) you need and see if all is well. Each action, however small, counts. Give feedback now.

Remember, it is your Pharo.

Thank you!

On behalf of the whole team, Sven