I was more thinking of a bug party _à la Debian_. Trying to squash the maximum bugs from Nim distribution. It could be simply improving the documentation of the system libraries, adding a missing feature in a frequently used library, writing test cases or for Nim experts trying to tackle some compiler bugs.
Attracting other developers to the language can be done by adding more lower quality projects or by improving the quality of existing projects. By low quality projects, I mean non-maintained or documented projects on a long term. Increasing the number of libraries for Nim is important, but personally I was never blocked because a library was not available. One of the strength of Nim is to bridge external libraries very easily. Both ways are important. And I'm questioning what is the main reason why people who tried Nim drop it after a while. Knowing that answer would help putting the efforts to the right place. For me, coming back to Nim after a few years pause because the compiler was not mature enough, the main reason I would keep off Nim a second time is still because I encounter too many compiler bugs and lack of documentation: I spend too much time on trying to find workarounds or even to code something the Nim way.
