http://rubyforge.org/forum/forum.php?thread_id=48896&forum_id=585
http://rubyforge.org/snippet/detail.php?type=snippet&id=478
Looks like that might be a good item to add to the documentation as an
example. Not sure where, but it's good to add this sort of thing.
-a
--
Austin Ziegler • halos...@gmail.com • aus...@halostatue.ca
http://www.halostatue.ca/ • http://twitter.com/halostatue
I did actually go through a lot of the rubyforge tracker items to try
and get some of the items closed out, in the eventual hope of getting
them closed :)
James.
If we're going to talk about doing that, I want to talk about having a
ruby-net-ldap OSS project on github. No offense to Rory, but I'd
rather not have to visit roryo.github.com/ruby-net-ldap to get to the
documentation. With RubyForge, we have at least
ruby-net-ldap.rubyforge.org for documentation.
That said, the work I'm doing on RubyPython has a slightly uglier
setup: the homepage on RubyForge; the tracker and main repository on
BitBucket; a mailing list (which I'm not yet admin of ;); and a mirror
of the source on GitHub that's heavily used. (We use hg-git to manage
that.)
I'm less worried about that than having a single home for the project,
but that's just me :)
James.