There are many newbies already on the program, but since the ruby
community is so nice, we currently have more volunteers than users
requiring help, as far as I'm aware.
···
On 2/19/07, Edwin Fine <efine145-nospam01@usa.net> wrote:
SonOfLilit wrote:
> Like to see it done? Do it!
>
> Sorry, just had to. I'm saying this because it really excites me, the
> idea.
Well, so far I have not received any emails although my link is there on
the Wiki. Is there not enough interest yet, or maybe word has not gotten
around yet, or do I personally scare newbies off somehow? I don't bite
For now, should I return to doing it myself or should I let the newbies do it?
Aur
···
On 2/19/07, Avdi Grimm <avdi@avdi.org> wrote:
On 2/19/07, SonOfLilit <sonoflilit@gmail.com> wrote:
>
> Until yesterday, that was me.
>
> Hopefully soon there will be a ruby program that will do that.
>
> Do you think I should return to my role as coordinator instead of
> letting business run alone in the wiki?
>
I think *someone* should do it, and no, I'm not volunteering
If you do go with a technical solution, a repurposed bug-tracking system
would probably do the trick. The main thing is to make sure mentoring
requests don't fall through the cracks, which bugtrackers are pretty good
at. Maybe set it up so it emails all the people who have registered as
potential mentors whenever an application is made, and whoever decides they
have the time can mark it "accepted".
There are many newbies already on the program, but since the ruby
community is so nice, we currently have more volunteers than users
requiring help, as far as I'm aware.
Wow! What a community! I've never heard of such a thing. The Ruby
Community should be proud.
On 2/19/07, Edwin Fine <efine145-nospam01@usa.net> wrote:
SonOfLilit wrote:
> There are many newbies already on the program, but since the ruby
> community is so nice, we currently have more volunteers than users
> requiring help, as far as I'm aware.
Wow! What a community! I've never heard of such a thing. The Ruby
Community should be proud.
Wow! What a community! I've never heard of such a thing. The Ruby
Community should be proud.
Yay for that!
And, to avoid quoting all way back -I'm too lazy to do that-, I'll just
say I find great the idea of small "study groups". Of course, the term
may seem scary for all of us who hate school, but enjoy programming ,
but the idea is to make it on a enjoyable, relaxed and productive way.
Should we let the newbies do it? Of course, that's the best way to
learn.
Edwin Fine wrote:
Somebody is working on a Rails app.
Finally, to start putting into actions all what I've said... I'm a Rails
newb... totally noob. But I'll be glad to work on the project with Mr.
Somebody
"Somebody" is Alexandru (to whom I cannot express all of my thanks for
taking this up) and all of the relevant discussion is in this thread.
When there will be something running, I guess I'll afford to hack on
it myself, too.
And Craig Beck and Steven Quinones-Colon also volunteered to help,
also I haven't heard from them yet.
What a great community!!!
Lately I've tried to learn a few languages and figured that Ruby was
so great and easy that it made my expectations rise to the point of
laziness. Well, today I understood that this refers not only to my
expectations from a language. It is true about communities too.
Thank you, Ruby users everywhere!
Aur Saraf
···
On 2/19/07, Ruben Medellin <chubas7@gmail.com> wrote:
Edwin Fine wrote:
> Wow! What a community! I've never heard of such a thing. The Ruby
> Community should be proud.
Yay for that!
And, to avoid quoting all way back -I'm too lazy to do that-, I'll just
say I find great the idea of small "study groups". Of course, the term
may seem scary for all of us who hate school, but enjoy programming ,
but the idea is to make it on a enjoyable, relaxed and productive way.
Should we let the newbies do it? Of course, that's the best way to
learn.
Edwin Fine wrote:
> Somebody is working on a Rails app.
Finally, to start putting into actions all what I've said... I'm a Rails
newb... totally noob. But I'll be glad to work on the project with Mr.
Somebody
An infrastructure for prompting the "study group" approach for Ruby
newbies would be (relatively) easy to set up. All you'd really need is
a very simple bloglike and mailing list interface. With the blog
someone starting a group can create a blog for posting something akin
to "progress reports" and otherwise archiving what's going on for
reference, including some "this is the task we should attempt to
complete by the end of this week" scheduling stuff. There'd be one of
these for each study group, that lasts only as long as the group does,
so the software need not be very complex. For the mailing list, there'd
be a mailing list created at the same time, with the list archives
attached to the blog, so that anyone registered with one of them is also
registered with the other, and can post to both.
Archives for both should probably be kept in perpetuity so that they can
serve as examples of how various study concepts work out, and so that
people too shy about their Ruby learning can use the example of study
groups to provide some structure to their own autodidactism* rather than
leaving them flailing about trying to sort out which online resources to
use, what constitutes a reasonable learning schedule, and so on.
I'd set up something like that myself for the Ruby community -- could
probably get it put together in about two days, with some web software
packages that are available so that little or no actual programming
would be required to set them up initially (thus speeding up the
process, though of course ultimately it should be written in Ruby for
maximum relevance to the community) -- but since I'm already putting
together something more centralized and less Ruby-specific, I'm afraid
my attention is directed elsewhere at the moment.
Wow, that was a long sentence.
···
On Tue, Feb 20, 2007 at 06:14:23AM +0900, Ruben Medellin wrote:
And, to avoid quoting all way back -I'm too lazy to do that-, I'll just
say I find great the idea of small "study groups". Of course, the term
may seem scary for all of us who hate school, but enjoy programming ,
but the idea is to make it on a enjoyable, relaxed and productive way.
Should we let the newbies do it? Of course, that's the best way to
learn.
--
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
print substr("Just another Perl hacker", 0, -2);
Sorry I didn't get back to you sooner. I spent the last couple of days
sending my daughter off to a D.C. school trip. I have a server that I
can volunteer but the problem is that I'm a noob when it comes to
rails apps and such, so I wouln't know what to do. But the physical
hardware is there for anyone that want to develop something on it.
···
On 2/19/07, SonOfLilit <sonoflilit@gmail.com> wrote:
"Somebody" is Alexandru (to whom I cannot express all of my thanks for
taking this up) and all of the relevant discussion is in this thread.
When there will be something running, I guess I'll afford to hack on
it myself, too.
And Craig Beck and Steven Quinones-Colon also volunteered to help,
also I haven't heard from them yet.
As a Ruby newbie I'd like to give a big thumbs up to the "study group"
idea, especially if a group of newbies got together to actually work
on some sort of project. Personally, while 1:1 attention can be great,
I find working in a group to be one of the best learning methods
around. Mix a group into a real-world project and I'm willing to bet
you're going to have a lot of newbies (including myself) hooked.
I think this idea would be especially beneficial to people like myself
who are interested in starting to contribute to existing open source
projects, but find themselves slightly overwhelmed, and unsure as to
where to start. I know that I've been looking for some kind of project
that I can start contributing to, not only to help make some
contributions to the community, but also to learn more about
developing code in such a large, distributed environment.
As a Ruby newbie I'd like to give a big thumbs up to the "study group"
idea, especially if a group of newbies got together to actually work
on some sort of project. Personally, while 1:1 attention can be great,
I find working in a group to be one of the best learning methods
around. Mix a group into a real-world project and I'm willing to bet
you're going to have a lot of newbies (including myself) hooked.
I think this idea would be especially beneficial to people like myself
who are interested in starting to contribute to existing open source
projects, but find themselves slightly overwhelmed, and unsure as to
where to start. I know that I've been looking for some kind of project
that I can start contributing to, not only to help make some
contributions to the community, but also to learn more about
developing code in such a large, distributed environment.
,