[ANN] the Ruby Programming Shop

[pat eyler]

Announcing the Ruby Programming Shop (RPS)

It's no secret that there is a lot of Ruby code out there that needs
to be cleaned
up (it's old, untested, undocumented, and maybe even abandoned). The RPS
povides a way to 'rescue' that code and make it shine. We'll limit
ourselves to
free software, and will contact the original author (when possible) to
get his/her
blessing.

There are a lot of Ruby-nubies out there (and more every day). They (and we)
could all use the opportunity to sit down with a veteran Ruby programmer, to
learn 'the Ruby way'. The RPS will give them the opprtunity to do just that.

We'll pick one library to work on for two months at a time, this will
a project.
One person (or a Ruby Brigade) will take charge of coordinating each project.
Every project will be split into 4-5 two week iterations. Each iteration will
conclude with a release to the community of the work done so far. Each
project will conclude with a final release of the project back to the original
maintainer (should one exist) or to a new maintainer (if the library was
abandoned).

Please join us at our wiki:
http://therps.rubyforge.org/wiki/wiki.pl

and on our mailing list:
http://rubyforge.org/pipermail/therps-discuss/

Right now, we need to flesh out our list of libraries to work on, and select a
library for May/June. Come on in, sit down, and help make Ruby shine!

 

[Ghislain Mary]

Very good initiative!

I'll keep an eye on the project and try to help if I can

See you

 

[pat eyler]

Huh? On a rubyforge site what wiki.pl (perl) is for?


Both the mailing-list archiver 'pipermail' and mailing-list manager
'mailman' are python powered here too; but why?

Dr. Dheeman. I believe (but can not answer authoritatively) that
RubyForge uses these because they're part of the basic sourceforge(?)
installation. They both work well enough that trying to replace them
would be a misuse of resources.

 

[mark sparshatt]

Huh? On a rubyforge site what wiki.pl (perl) is for?



Both the mailing-list archiver 'pipermail' and mailing-list manager
'mailman' are python powered here too; but why?

I don't mean to alarm you but Rubyforge uses the Gforge system which is
written in PHP ;-)


If I was to hazard a guess as to why I'd say becuase reusing a system
written in PHP, perl or python rather than rewriting them in ruby meant
there was more time available for administering the site.

 

[Peter Suk]

Huh? On a rubyforge site what wiki.pl (perl) is for?

Would we be glad if some Perl-folks decided to use instiki? Or would
we use this fact as ammunition in our holy language war? Tools work.
Use them or not. Hope people do the same for the tools we build.

Both the mailing-list archiver 'pipermail' and mailing-list manager
'mailman' are python powered here too; but why?

Language jingoism is not productive, IMHO. Tools work. Use them or
not. I'd want someone to use Ruby or Smalltalk, even if they were
running a project in Java/C/C#/Lisp/Perl. I note that there is a vmlm
mailing list manager written in Ruby. (Google: Ruby Mailing List
manager) Perhaps someone who is concerned should take a look, dust it
off, and give it a try. Or, if you want to write something better, you
are welcome! If you are not that concerned, and the list works, why
worry?

--Peter

 

[James Britt]

I don't mean to alarm you but Rubyforge uses the Gforge system which is
written in PHP ;-)


If I was to hazard a guess as to why I'd say becuase reusing a system
written in PHP, perl or python rather than rewriting them in ruby meant
there was more time available for administering the site.

This has been discussed before, and while eating your own dog food is
strongly encouraged, there are certain practical aspects. Ruby versions
of mailman or gforge would be sweet, but I'd rather see people spend
time breaking new ground or filling current needs where there are no
suitable applications.

I believe, though, that the perl-based wiki will be replaced with a Ruby
one before too long.

James

P.S.

This one also gives me a chuckle:
http://www.rubyonrails.com/index.php



--

http://www.ruby-doc.org
http://www.rubyxml.com
http://catapult.rubyforge.com
http://orbjson.rubyforge.com
http://ooo4r.rubyforge.com
http://www.jamesbritt.com

 

[Peter Suk]

P.S.

This one also gives me a chuckle:
http://www.rubyonrails.com/index.php

Hmm, maybe Ruby code cleanup group using the Perl wiki and the python
MLM is like a cook letting someone else make his/her knives. The rails
php site is more of a not "eating your own cooking" thing.

--Peter

 

[Tom Copeland]

I believe, though, that the perl-based wiki will be replaced with a Ruby
one before too long.

Yup, replacing it with Ruwiki:

http://rubyforge.org/projects/ruwiki/

is the master plan...

Yours,

Tom

 

[Peter Suk]

It definitely should; Though I'm a newbie, but I have learned (you may
please read it as read) somewhere from (and, or in) the Ruby documents
that Ruby outperforms many other scripting and, or interpreted
languages.

You really shouldn't believe what you read! ;-)