> > That's pretty much the opposite of your previous question. For one thing, > it's unanswerable without knowing the scope - e.g. would it just be for > RFCs, or all discussions?
I'm thinking about a generic "forum" for all discussions that happen on the mailing lists right now, something that could be used for internals but also for other PHP mailing lists. Then, its scope can be expanded specifically for internals, to better discuss RFCs, etc., but that's not what I had in mind right now. Until we know what we're looking for, I'm really not clear why GitHub > issues should have any starting advantage over Discourse, or PHPBB, or > Trac, or Phabricator, or Bugzilla, or probably hundreds of suggestions we > could evaluate. I chose GitHub because it was mentioned several times in this thread, because it's already used to discuss PRs, and because I suspect pretty much everyone on this list either uses GitHub on a daily basis, or has at least *some *experience with GitHub issues (let's face it, I google stuff every day for many open-source projects, and most of the discussions I stumble upon are on GitHub issues/pulls), so at least we have a* starting point* that everyone knows and has learned to love or hate. Now the whole point is, if you think another software does things better, please share! Now obviously, should you hate GitHub issues from start to finish, then indeed I can understand you consider this starting point a poor choice, in this case I'd be interested to know what you dislike so much! — Benjamin
