The best part of Rubberduck is that it's community driven - we take input from all members of the community to make it better. If you think you have found a bug, or you have a feature to request, the process is very straightforward: first see if there isn't already an open issue on our GitHub repository that describes this bug or feature, and then simply create a new issue. The Rubberduck team (and even other community members) will begin discussion on your issue and we'll all come to a solution together.
Just like the Rubberduck IDE, we have a GitHub repository for the Rubberduck Website. We encourage users to submit their issues to it, simply check first that one does not yet exist, and if it doesn't create one. The development community will read, assess and respond to your issues as soon as we're able.
We welcome all positive contributions to Rubberduck from the community. We can't all be perfect, but if we can combine the expertise of our team and the expertise of our users we will reach new levels with Rubberduck and make it the single greatest VBE IDE in existence.
If you've fixed or added something simply submit a pull request, we'll merge it into our master branch, and ship it with the next release!
If there's something you wish to discuss with us and an issue on GitHub or question on Stack Overflow doesn't suffice, we're completely open to communication about your particular concern and will try to get back to you as soon as we can.
Send us an email email@example.com