Gitlab.com has an import tool for fogbugz issues. Their hosted service is https://about.gitlab.com/gitlab-com/ I'm not sure of the quality of their issue tracker but it could be a way out. The gitlab source issue tracker is here: https://gitlab.com/gitlab-org/gitlab-ce/issues to see what its like. They also include mattermost.org which is an open source Slack alternative. If the fogbugz integration with the image is just some REST calls, maybe it wouldn't be too bad to convert to gitlab's API (http://doc.gitlab.com/ee/api/README.html) I know that this change would require some serious time investment in the analysis and deployment phase. Marcus Denker-4 wrote
On 22 Oct 2015, at 17:26, Tobias Pape <
Das.Linux@
> wrote:
Hi Marcus On 22.10.2015, at 16:44, Marcus Denker <
marcus.denker@
> wrote:
On 22 Oct 2015, at 16:13, Marcus Denker <
marcus.denker@
> wrote:
Thats what I thought. Probably we want to present this (Mersenne PRNG + new UUID gen) to the Pharo core developers (cc) so that we can just remove the UUID plugin from the VMs (cc vm-dev)?
That sounds good!
I added an issue tracker entry so we do not forget:
https://pharo.fogbugz.com/f/cases/16846/integrate-non-Plugin-UUIDGenerator-f...
Is there any way to view those issues without creating a fogbugz account?
Sadly not. Just for that it was a mistake to use FogBugz. But moving now is difficult.
Marcus
-- View this message in context: http://forum.world.st/Re-squeak-dev-The-Trunk-Network-topa-166-mcz-tp4857311... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.