Having a bugtracker or not is a tough decision. You have to keep your ways of communicating limited to a few channels. You _will_ need to address the social aspect of your project in one way or another. It's probably either a mailinglist or a bugtracker. Having both means one of them is probably heavily underused.<p>What you see a lot with projects is that everything happens through a bugzilla. New features, feature requests, bugs are posted there, some invalid because the user doesn't understand a program. The 'bugtracker' aspect forces you to put your message in a certain style.<p>With mailinglists like git@vger you get a mixture of posts. Some are from newbies that don't understand the system, some are comments on the current system and most of them are patches or status updates. Having a mailinglist allows a user more freedom in the form in which he wants to communicate, which lowers the barrier. You also get a nice mixture of users and developers on the same channel, by which you get better feedback.<p>The flipside of that is that you don't have any overview. You'll have to manage bugs yourself. If you want something fixed, you'll either have to make a patch yourself, get somebody else interested or just keep bringing the bug to attention.<p>Now compare this to a bugtracker. You post a bug there and nobody will look at it until you make a patch yourself, get somebody else interested or keep bringing the bug to attention. See the difference? Exactly.