Neat example:

24 views
Skip to first unread message

Austin Ziegler

unread,
Mar 16, 2011, 7:46:03 PM3/16/11
to ruby...@googlegroups.com
Trawling through the examples, I found this:

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.comaus...@halostatue.ca
http://www.halostatue.ca/http://twitter.com/halostatue

Austin Ziegler

unread,
Mar 16, 2011, 7:49:43 PM3/16/11
to ruby...@googlegroups.com
OK. I'm a bit of an idiot. "Trawling through the forums…"

That said, I'm sort-of in favour of closing down the forums. They're not used often, and we can point people to this mailing list a bit more aggressively.

James Hewitt

unread,
Mar 16, 2011, 8:10:31 PM3/16/11
to ruby...@googlegroups.com
I'm in favour of closing down the rubyforge project entirely, and
sending everyone to github, even turning on the github tracker.

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.

Austin Ziegler

unread,
Mar 17, 2011, 12:09:02 AM3/17/11
to ruby...@googlegroups.com
On Wed, Mar 16, 2011 at 8:10 PM, James Hewitt <james....@gmail.com> wrote:
> I'm in favour of closing down the rubyforge project entirely, and
> sending everyone to github, even turning on the github tracker.
>
> 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 :)

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.)

James Hewitt

unread,
Mar 17, 2011, 6:21:38 AM3/17/11
to ruby...@googlegroups.com
I agree that having it under a proper project is a good idea too.

I'm less worried about that than having a single home for the project,
but that's just me :)

James.

Reply all
Reply to author
Forward
0 new messages