On Sun, Dec 31, 2017 at 4:03 PM, Andy Burnett <andy.burn...@knowinnovation.com> wrote: > Denis wrote >>>> > > It's same as any other code. Just follow instructions > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo. It > is now simplified a lot. > > <<< > > Wow! That has improved a lot. I have bookmarked the site, and I now have a > reason to learn iceberg. > > Out of curiosity, and perhaps this has been answered elsewhere, why are we > using fogbugz for issue tracking, rather than github's issue tracker? I know > nothing much about either of them. I am just curious if fogbugz is much > better?
- Free for us (normally it cost 25$ per seat) - Maintained - Working - When we migrated out of this code.google.com the git tracker was clearly not sexy. - The new version of fogbugz is working really nicely. I prefer that we do not lose again a lot of engineering time to migrate and update our process. We have too many fronts open right now. We should really pay attention because starting something is super easy finishing it super difficult. Stef
