Added Typelevel Scala article.

For review and feedback before publishing ...
I would argue strongly for merging regularly, rather than rebasing regularly.  For one thing, it makes merge conflicts more reasonable.  More importantly, it allows seamless contribution to the fork without having "stop the world" moments when everyone must get the new force-pushed master.  As long as the test suites are sufficiently comprehensive, we shouldn't have anything to worry about in terms of "merge drift" (in any case, Git is less susceptible to this problem than SVN and predecessors).