Hello everyone,
I'm happier than you can imagine to announce that we now have an
improved RubyGarden FAQ available at:
http://www.rubygarden.org/faq
Many of you have experienced problems with the FAQ going down over
the past several months. I have wrestled with it unsuccessfully until
last weekend when David Alan Black took it upon himself to do a
rewrite in Rails (http://www.rubyonrails.org). Amazingly, he had the
first cut of replicating the old FAQ code done in what seemed like
less than an hour.
What does this change mean to you? Most importantly, the FAQ is now
infrastructurally healthier, so it should be much easier to keep up to
date. David has already start with some preliminary weeding before
this release, so things should already be cleaner and more relevant as
a result.
To propose a new question or to leave a comment, you are now
required to register. With the endless conversations about Wiki spam
here, I don't think I have to explain why.
This release is part of a greater RubyGarden revitalization that is
underway. If you have ideas for content and/or RubyGarden
improvements, now's a great time to let me know.
Finally, thanks to Dave Thomas who wrote the original FAQ code,
which eventually fell sick due entirely to the neglect it has suffered
over the past few months.
Enjoy, and happy Rubying!
Chad
http://rubygarden.org
http://rubygems.rubyforge.org (over 20,000 gems served!)
Please tell me that you will do everything reasonably possible so that
the email I provide in the login will not make it into the hands of
spammers.
Please - please - please!!!
-Rich
···
On Sat, 23 Oct 2004 01:31:33 +0900, Chad Fowler <chadfowler@gmail.com> wrote:
Hello everyone,
I'm happier than you can imagine to announce that we now have an
improved RubyGarden FAQ available at:
http://www.rubygarden.org/faq
Many of you have experienced problems with the FAQ going down over
the past several months. I have wrestled with it unsuccessfully until
last weekend when David Alan Black took it upon himself to do a
rewrite in Rails (http://www.rubyonrails.org). Amazingly, he had the
first cut of replicating the old FAQ code done in what seemed like
less than an hour.
What does this change mean to you? Most importantly, the FAQ is now
infrastructurally healthier, so it should be much easier to keep up to
date. David has already start with some preliminary weeding before
this release, so things should already be cleaner and more relevant as
a result.
To propose a new question or to leave a comment, you are now
required to register. With the endless conversations about Wiki spam
here, I don't think I have to explain why.
This release is part of a greater RubyGarden revitalization that is
underway. If you have ideas for content and/or RubyGarden
improvements, now's a great time to let me know.
Finally, thanks to Dave Thomas who wrote the original FAQ code,
which eventually fell sick due entirely to the neglect it has suffered
over the past few months.
Enjoy, and happy Rubying!
Chad
http://rubygarden.org
http://rubygems.rubyforge.org (over 20,000 gems served!)
Oh, I was planning to publish all of the email addresses and passwords
in CSV format on the front page of rubygarden.org. Is that not what
you want? 
Seriously, we're not displaying email addresses on the site and there
should be no way for anyone to get to them.
Chad
···
On Sat, 23 Oct 2004 02:13:11 +0900, Richard Lyman <lymans@gmail.com> wrote:
Please tell me that you will do everything reasonably possible so that
the email I provide in the login will not make it into the hands of
spammers.
Please - please - please!!!
Something else... I'd like to throw my two cents in for the default
setting of comments shown on the bottom of the page... like php.net's
docs
-Rich
···
On Fri, 22 Oct 2004 11:13:09 -0600, Richard Lyman <lymans@gmail.com> wrote:
Please tell me that you will do everything reasonably possible so that
the email I provide in the login will not make it into the hands of
spammers.
Please - please - please!!!
-Rich
On Sat, 23 Oct 2004 01:31:33 +0900, Chad Fowler <chadfowler@gmail.com> wrote:
> Hello everyone,
>
> I'm happier than you can imagine to announce that we now have an
> improved RubyGarden FAQ available at:
>
> http://www.rubygarden.org/faq
>
> Many of you have experienced problems with the FAQ going down over
> the past several months. I have wrestled with it unsuccessfully until
> last weekend when David Alan Black took it upon himself to do a
> rewrite in Rails (http://www.rubyonrails.org). Amazingly, he had the
> first cut of replicating the old FAQ code done in what seemed like
> less than an hour.
>
> What does this change mean to you? Most importantly, the FAQ is now
> infrastructurally healthier, so it should be much easier to keep up to
> date. David has already start with some preliminary weeding before
> this release, so things should already be cleaner and more relevant as
> a result.
>
> To propose a new question or to leave a comment, you are now
> required to register. With the endless conversations about Wiki spam
> here, I don't think I have to explain why.
>
> This release is part of a greater RubyGarden revitalization that is
> underway. If you have ideas for content and/or RubyGarden
> improvements, now's a great time to let me know.
>
> Finally, thanks to Dave Thomas who wrote the original FAQ code,
> which eventually fell sick due entirely to the neglect it has suffered
> over the past few months.
>
> Enjoy, and happy Rubying!
> Chad
>
> http://rubygarden.org
> http://rubygems.rubyforge.org (over 20,000 gems served!)
>
>
Sorry - I guess I felt burned with the whole ruby-talk to spam speedway.
Thanks!
-Rich
···
On Sat, 23 Oct 2004 02:16:19 +0900, Chad Fowler <chadfowler@gmail.com> wrote:
On Sat, 23 Oct 2004 02:13:11 +0900, Richard Lyman <lymans@gmail.com> wrote:
> Please tell me that you will do everything reasonably possible so that
> the email I provide in the login will not make it into the hands of
> spammers.
>
> Please - please - please!!!
>
>
Oh, I was planning to publish all of the email addresses and passwords
in CSV format on the front page of rubygarden.org. Is that not what
you want?
Seriously, we're not displaying email addresses on the site and there
should be no way for anyone to get to them.
Chad
Sorry to be bugging you so much.... but I can't stop loving the new
functionality and setup!!
What about allowing this FAQ to branch out?
Could RubyForge tie into this so that any project on RubyForge would
have FAQ-ability using the same username and passwords - same URL?
I ask this because I'd love to have the ability to centralize
question/answer stuff, and more importantly to actually have it. There
are so many projects where because of lanugage barriers, or because of
age or neglect, a project becomes unuseable. The ruby community would
greatly benefit from a php.net styl of docs+user_comments in the form
of a centralized FAQ.
Imagine being curious about a module someone had provided on
RubyForge, downloading it to find that the code might be fantastic but
the documentation non-existent. This is where a centralized community
contributed FAQ would shine. I'm trying to do something in Ruby but
can't seem to figure it out on my own, I search the Ruby FAQ. If I
don't find anything, I post a question. A group that had previously
volunteered to 'support' that module/library/application would be
notified via email of my pending question(s), and would be abel to
supply an answer. The answer and question would then be stored in the
'Ruby FAQ'
Personally... that's a _dream come true_ for Ruby.
-Rich
Richard Lyman ha scritto:
I'm trying to do something in Ruby but
can't seem to figure it out on my own, I search the Ruby FAQ. If I
don't find anything, I post a question. A group that had previously
volunteered to 'support' that module/library/application would be
notified via email of my pending question(s), and would be abel to
supply an answer. The answer and question would then be stored in the
'Ruby FAQ'
Personally... that's a _dream come true_ for Ruby.
wow, I got caught by the simple 'imagine' word.
IMO this would be a cool thing, indeed, even if maybe a little complex 
Richard Lyman wrote:
I ask this because I'd love to have the ability to centralize
question/answer stuff, and more importantly to actually have it. There
are so many projects where because of lanugage barriers, or because of
age or neglect, a project becomes unuseable. The ruby community would
greatly benefit from a php.net styl of docs+user_comments in the form
of a centralized FAQ.
What would you be looking for? I'm creating vast amounts of documentation already for SOAP4r and XML, I'm going to be documenting most of ruby for a php.net like site and releasing with a CMS (which is whats holding me back ;))
I'm taking requests in for documentation, I'm working on it by myself for now.
David Ross
···
--
Hazzle free packages for Ruby?
RPA is available from http://www.rubyarchive.org/
Sorry to be bugging you so much.... but I can't stop loving the new
functionality and setup!!
What about allowing this FAQ to branch out?
Could RubyForge tie into this so that any project on RubyForge would
have FAQ-ability using the same username and passwords - same URL?
I ask this because I'd love to have the ability to centralize
question/answer stuff, and more importantly to actually have it. There
are so many projects where because of lanugage barriers, or because of
age or neglect, a project becomes unuseable. The ruby community would
greatly benefit from a php.net styl of docs+user_comments in the form
of a centralized FAQ.
Imagine being curious about a module someone had provided on
RubyForge, downloading it to find that the code might be fantastic but
the documentation non-existent. This is where a centralized community
contributed FAQ would shine. I'm trying to do something in Ruby but
can't seem to figure it out on my own, I search the Ruby FAQ. If I
don't find anything, I post a question. A group that had previously
volunteered to 'support' that module/library/application would be
notified via email of my pending question(s), and would be abel to
supply an answer. The answer and question would then be stored in the
'Ruby FAQ'
Personally... that's a _dream come true_ for Ruby.
I really like that idea... FWIW, here are some of my thoughts on the matter
I've always thought that the greatest thing about PHP is it's
documentation. Since users can easily add to the docs, it helps the
maintainers keep things fairly well updated, and offers extra tips and
tricks, right in the docs themselves.
Being able to ask a question and have it notify volunteer documenters
is a great idea I would see it as a subscription: If you feel
you've pretty well figured out a library, you could sign up as a
documenter. Any FAQ's submitted would be mailed to all documenters.
Then, in a "google answers" fashion, responses can be submitted until
the question is answered. The best one gets added to the FAQ.
hmmmm... nice
cheers
Mark
···
On Sat, 23 Oct 2004 02:32:40 +0900, Richard Lyman <lymans@gmail.com> wrote:
-Rich