The recomended way to report a bug is to use the Gramps Bug Tracker, see How to report bugs. This allows the Gramps Developers to follow a formal method of tracking and resolving your report. Due to the high volume of email that the primary developers receive, there is always a chance that an email may slip through the cracks. Using the bug tracker will make sure that your issue will be handled.
Bug reports submitted, directly to the Gramps Bugs mailing list are not recommended.
Requesting an enhancement can be done either through the gramps-users or gramps-devel mailing lists, or by creating a feature item on the bug tracker. We would prefer that serious requests get submitted to the bug tracker. You switch to Project: Feature Requests on the top right head corner, and select Report Issue. Again, this allows us to formally track the request.
Wiki, Website/Blog, Bug Tracker applications
For problems relating to the Gramps site and the applications used to support Gramps, contact Nick Wallingford  or raise the issue on the developer list described below.
There are several mailing lists on various topics related to Gramps:
If the Sourceforge site is too slow for your liking, use the copy of the mailing lists stored on nabble.com. However, if you want to use nabble to send messages (as opposed to just reading them) then you must have subscribed to the related sourceforge mailing list first.
IRC (Internet Relay Chat)
Please feel free to drop by on channel #gramps over at irc.freenode.net server. All users and developers are welcome!
Some IRC guides:
Please, mail the Developers mailing list (subscribe first) with the wiki page containing the infringement, as well as the manner of infringement.