I Need Help! Where Do I Look?
This depends on what you need help with. The NetLogo community have several different channels for communicating and the best way to get help quickly is to address your request to the proper channel.
If you have encountered a bug in the latest version of NetLogo, it might be worth checking the Known Issues page to see if other users have already reported the issue. If no one has reported the issue, please open a GitHub issue or email our bugs list. If possible, please include a model displaying the bug as well as information about what you were doing when the issue occurred. Including the model and information about the buggy interaction makes fixing the problem much easier and ensures we fix the exact problem you were experiencing. If the model isn't public, please send it to our bugs mailing list. This list is private and your model will not be shared publicly.
We're excited that you're learning NetLogo! NetLogo comes with a tutorial which introduces the basic concepts and can help you get started. If you're looking for a textbook which explains the concepts underlying NetLogo you might look at Introduction to Agent-Based Modeling available as a paper book and/or ebook from MIT Press. The archives of an intro courses on NetLogo titled "Introduction to Agent-Based Modeling" are available on Complexity Explorer.
Help With Modeling
There are many good resources listed on the NetLogo resources page The Netlogo-Users yahoo group frequently tackles questions on modeling. Be aware that the the group is moderated, so most messages don't go through until at least the next business day. There is also a fairly active NetLogo community on StackOverflow. NetLogo Users tends to be a better place to ask more open-ended modeling questions, for instance "I'm interested in making a model of plate tectonics, can anyone offer advice?". StackOverflow tends to be best for asking specific questions with definite answers, for instance "How can I create a small-world network of turtles and links?".
Suggestions for New Features
While the resources we have to add new features are limited, we're happy to hear new ideas! You might quickly search our issue tracker to see if someone has suggested something similar in the past (if you find something, comment on the issue to let us know it's something people are interested in). Otherwise, please open an enhancement request on GitHub or email our feedback list.
Extension API and Controlling API support
A good place to start is in our wiki. For extension developers, see the page on the extensions API. If you're a developer of an existing extension and interested in porting it to NetLogo 6, please see the 6.0 transition guide. There is also a wiki page on the controlling API.
Often extension and embedding developers have fairly specific questions. We encourage those developers to join the netlogo-devel Google Group and post their questions or problems.
Building from source
The NetLogo source is available on GitHub. More information about building from source can be found on our Building wiki page. If the information on this page doesn't work for you or you have trouble or are confused, please post to the netlogo-devel Google Group and request help. We're trying to make building NetLogo easy, so we would love to hear any suggestions you have or problems you encounter!
Google Summer of Code
We're very excited to have been accepted to Google Summer of Code 2017 as a mentoring organization! We're even more excited that you're interested in contributing to NetLogo this summer. Please join us in our GSoC 2017 chat room if you have specific questions or are just interested in chatting. Student applications will open up on GSoC on March 20th, and that will be everyone's opportunity to formally declare their interest in working on NetLogo, and what projects they would like to contribute to. Guidelines for what we would like to see in proposals are covered on our organization page.
Please note that an accepted contribution to NetLogo or NetLogo Web is necessary for an application to be considered. Before working on a contribution, please discuss it with us in the GSoC 2017 Gitter channel. This helps us stay on top of things and might save you time working on something that someone else is already planning to do!
For Other Help
Please ask by emailing our feedback list!