1

You mention a ruby gem for fogbugz access, but there is no code associated with it. There is a gem on github https://github.com/austinmoody/ruby-fogbugz-api with 14 forks. None of the folks who forked are actively supporting it any more.

I would really like to see a FogCreek 'sponsored' repo for this. I'm not asking for much - I just want to be able to check out a codebase, add some functionality, and add to the effort in a meaningful way - not just create another fork that's going to get lost in the noise.

Thanks!

flag
Have you talked to the folks who maintained it about transferring management of the project to you? – adambox Jun 6 at 19:24
That's not really the problem. I can fork it and claim ownership and do whatever I want. It's github, after all. But that's not what I want to have happen. I want to poke at it enough to get what I want working and hand it to fogcreek. Then fogcreek can be the central repo for it and I can come back at some future date and maybe get updates/fixes from fogcreek. It's not my project, area of expertise, or what I get paid for. I just want to help and move on. – Kurt Werle Jun 7 at 22:39

2 Answers

1

API wrappers are always out of date unless they use some functional magic like FogBugzPy does with Python's getattr.

That wrapper is stable, comprehensive, and easy to use. It appears the Ruby has a similar feature, send.

There are a few additional Ruby libraries that we've been meaning to add to our extras page. These should be much more up to date than what you might have already seen:

link|flag
0

I recommend https://github.com/firmafon/ruby-fogbugz , now.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.