Bug tracker relocation

[IAHM-COL]

This pull request relocates the bug tracker from sourceforge to github

Following the move of the main source code to be hosted in github, now the "report a bug" in the program redirect users to
the github issues page in:

https://github.com/Isarhamster/chessx/issues

Updating the bug_add icon

• The bug_add icon has been replaced to include github's octocat
• Higher resolution on the pixmap 256x256
  
• Src file included in images/src

Create the issues page on the repository is necesary for this integration.

Checking on the repository settings menu -> options -> Issues will create the URL used in the redirection function in the code:
https://github.com/Isarhamster/chessx/issues

Without this setting, github will redirect automatically to the pull requests page, which does not allow users to file the bug report.

[additional-pumpkin]

any updates? why isn't this being done?

[limitedAtonement]

It looks like the code currently points to the issue tracker in Sourceforge: https://github.com/Isarhamster/chessx/blob/1e85f7d1/src/gui/mainwindowactions.cpp#L794

Your artwork is great!

[IAHM-COL]

@limitedAtonement
Thanks

[Isarhamster]

How do I move issues from Sourceforge to github w/o losing all the information hidden inside? This includes users which do not exist on Github and users that do not exist on SF?!

[limitedAtonement]

How do I move issues from Sourceforge to github w/o losing all the information hidden inside? This includes users which do not exist on Github and users that do not exist on SF?!

That sounds heavy! I see a couple projects that attempt to automate it: https://github.com/cmungall/gosf2github https://github.com/ttencate/sf2github, but I'm guessing those are rocky at best! I don't see how you could Import users that don't exist!

I would think the best way forward might be instructing users to create new issues in Microsoft Github, and closing Sourceforge issues as they are complete. In that way, the migration will be "ongoing"! In some cases, it might make sense to create new Microsoft Github issues and close Sourceforge issues proactively, but I think it would need to be done one at a time.

Thank you for your work on this wonderful software!

[IAHM-COL]

@Isarhamster @limitedAtonement

Interesting question
I agree with limitedAtonement, that if you were to move the bugs report system to github and add the relocation as shown here, it's probably smoother to do a phased-out transition of SF, rather than trying to migrate

Regards

[limitedAtonement]

How do I move issues from Sourceforge to github w/o losing all the information hidden inside? This includes users which do not exist on Github and users that do not exist on SF?!

You should probably just make @IAHM-COL an administrator of both projects and he'll take care of it competently ;-).