Well technically you cannot stop people from using the github issue tracker for reporting bugs and by default if you are a contributor to a repo you will be alerted via email of new issues or replies to existing github issues.
Both github and forgbuz issue tracker can happily coexist. There will be also little need create same issues on both githyb and fogbuz because there will be little benefit , both are quite efficient on what they do , I see little reason not to allow both ways of reporting bugs. Github has a bit the edge here because of how it handles pull requests which it separates from issues and it allows you to start discussions on top of the code to be merged etc. Again this is a technical detail, the important thing is to report bugs and to fix them , how you do it is a lesser concern. Github has also other advantages that I am not so familiar , especially with CI. Right now CI for Pharo is separate , this is also can be brought to gitgub in some way without actually moving the CI and have Github as a main hub for commits, issue reporting, CI discussions and free wiki and a static website (maybe as a more permanent version of the wiki). https://github.com/marketplace/category/continuous-integration Github is actually extremely flexible. Gitlab is even more so , cause its full open source and allow you to host it on your own servers and you do not need to relearn what you learned with Github as it follows a very similar interface. Gitlab allows to move repos from github and will copy not just the code but also issues etc. So that is also a good solution for some people who may way to have Pharo dev on their own server and more control of it. A rather new feature for Github is also projects, a way to visualise todo lists, roadmaps, pull requests etc https://help.github.com/articles/about-project-boards/ It also offers way to visualise other things like commits, issues etc and last but not least it can host downloads of releases so there is a convenient and obvious way to find the latest but also previous versions of pharo with Github releases https://help.github.com/articles/creating-releases/ On Sat, Aug 19, 2017 at 7:51 PM Sean P. DeNigris <[email protected]> wrote: > Guillermo Polito wrote > > Sadly, this just works for the integration of commits into the main > > branches, not pull requests. For pull request integration we will > probably > > need a home made solution. > > Now that we are moving development to GH, has there been any discussion of > moving issue tracking there as well? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >
