By far the quickest and easiest way to get involved in our community is by joining one of our chat rooms.
Our official chat room is the #nim channel on irc.freenode.net. You can access it in multiple ways:
Join the Gitter chat room, which relays messages both ways between IRC and Gitter, by clicking here.
You can join this chat room to ask a quick question, or engage in a discussion about features and projects that interest you. For formal feature requests and issue reporting consult the Issues and RFCs section.
Be aware that all messages in Gitter and IRC are logged. You can access the IRC logs of the #nim channel here.
The #nim channel is primarily for on-topic discussion. There is also a semi-official #nim-offtopic channel for off-topic discussion.
This is a good place for long questions or to gauge the community’s interest on specific topics such as new features.
For announcements including news about releases, events and projects. Be sure to follow the official Twitter account and remember to mention the account when tweeting about Nim!
The blog is where we will be posting release announcements and other news first. If you are an avid RSS user then it should be just for you.
The Nim subreddit contains many user submitted announcements, blog posts, discussions. It is a good place to share your work with the Nim community and to get updates about the project so be sure to hit that subscribe button.
There is already an active number of Nim developers answering questions on
StackOverflow, you can be one of them. It is also a good place for newcomers to
get help with their project. Be sure to use the
nim tag when asking
If you’re planning on organising a Nim meetup, please let us know, we would love to include it here and announce it via Twitter and other means.
As of right now, there don’t appear to be any active meetups, although the following groups have been set up:
The issue tracker is hosted on GitHub together with the main repository. Most projects under the Nim umbrella have their own issue tracker:
If you have found an issue in the compiler, the standard library or any of the tools then please create an issue in the relevant repository. If appropriate include a minimal example reproducing the issue.
If you have a feature request then consider creating a formal RFC (Request for comments). In it you should describe the feature clearly, including the use cases that you foresee for the feature and anything else that you think is relevant. RFCs are currently submitted to the issue tracker.