Separate Public Repo for Issues

[basepi]

Was reading something or another and the thought crossed my mind of being able to have users submit bugs and so forth. After a little looking around, turns out you can't make issues public on a private repo -- however, someone suggested making a public repo for the product which is just used for issues. When we get towards release time, IMO we should do this. Obviously most people will just e-mail support, but if we can give them the ability to throw up a bug-report on github, that would be awesome as well.

We could also convert support e-mails TO public issues so people could see the active status of their bug report/feature request.

Only problem is there's no way to sync those issues to the private repo, which means that we have to maintain two different issue trackers -- our internal one, and the public one.

Your thoughts?

[basepi]

Also, we should make a chatosaurus account/github team, so our github URL would use chatosaurus/chatosaurus instead of trane/chatosaurus or whatever. Gives more consistency and polish.