2.1 Spotlight: External Contributions Area
In the 1.x timeframe we had a second repository called “akka-modules” which was supposed to hold modules which were not considered to be part of the core of Akka, but should still be maintained. This did not work out so well, mostly because developers are lazy and want a single unified build to check their work. Thus we moved some modules into the “akka” project proper and discontinued others (which were not actively enough maintained to make the jump to 2.0). But this left us lacking an incubation area where new modules can mature before being blessed into the core distribution.
Enter akka-contrib.
This subproject is part of the regular Akka build process, included in the online docs and part of the continuous integration testing. This ensures that the code in there stays up-to-date while Akka evolves. At the same time, this subproject is structured such that individual parts can easily be taken out and incorporated into your own projects, to make use of them and give feedback before we commit to supporting them with all bells and whistles. The idea is that a good module will be championed by external contributors, battle-tested in the field and finally incorporated as a mature member of the Akka family.
The whole setup was tested by implementing a messaging pattern I always wanted to include, but soon after that Kaspar Fischer offered the first candidate: a message throttler. You are welcome to have a look and let yourself be inspired.