From pelargir at gmail.com Fri Jan 13 14:27:16 2006 From: pelargir at gmail.com (Matthew Bass) Date: Fri, 13 Jan 2006 14:27:16 -0500 Subject: [raleigh.rb] The Ruby Journal Message-ID: Greetings fellow Rubyists: For those who were interested, here are details on the new Ruby e-zine I mentioned at the meetup last night. Matt ===================== After a brief hiatus over the winter holidays, Red Letter: The Ruby Journal is again making progress towards issue #1. You can visit the journal's initial web site at http:// redletter.therubyjournal.com. Click on the "Subscribe" link to pre- order your subscription. Click on the "Advertise" link to learn about opportunities to reach the readers of Red Letter. An interim editorial calendar can be found at the "Editorial" link. The writer's kit is coming shortly. Many, many people asked for it. We were very pleased with the number of responses to our initial post. We are currently accepting proposals for feature stories. While the writer's kit is assembled, please feel free to send a three-five paragraph proposal to writers at therubyjournal.com. Proposals should: 1/ Identify the target audience; 2/ Enumerate the article's goals ("teach the reader about objects", "master Ruby debugging"); 3/ Describe how you intend to achieve your goals; 4/ And summarize (if possible) the three-five most important lessons the reader will take away. We also want to choose six-seven columnists that would write regularly for Red Letter. You can see the list of currently proposed columns on the front page of the Red Letter web site. If you want to be a columnist, send email with your qualifications and column idea (or choose one that is already listed) to editors at therubyjournal.com. If you are interested in becoming a columnist, please be prepared to write for at least a six-month term. (Bonus points for enumerating the six topics you would cover in your tenure on a certain column.) You can send community events (local programming groups, conferences, new software releases) for the community pages to announce at therubyjournal.com. Questions are always welcome, as are suggestions, opinions, and assistance. Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/raleigh-rb-members/attachments/20060113/e90f36b2/attachment.htm From nathaniel at talbott.ws Mon Jan 16 11:07:27 2006 From: nathaniel at talbott.ws (Nathaniel Talbott) Date: Mon, 16 Jan 2006 11:07:27 -0500 Subject: [raleigh.rb] February Meeting Message-ID: When: Thursday, February 9, 2006, 7:00 PM Meeting Plan: Show & tell this month - if you've been working on anything in Ruby, we'd love to see it and hear about your experiences with it. As usual things will be very informal, and of course you're welcome even if you don't have anything to share - we'll need plenty of hecklers :-) More Info: http://rubyholic.com/groups/show/20 I wanted to go ahead and send this out so folks can get it on their calendars - I'll send a reminder when things get closer, too. Hope to see you there! -- Nathaniel Talbott <:((>< From nathaniel at talbott.ws Mon Jan 23 09:50:13 2006 From: nathaniel at talbott.ws (Nathaniel Talbott) Date: Mon, 23 Jan 2006 09:50:13 -0500 Subject: [raleigh.rb] Interesting perspective from another Zope guy Message-ID: At the January meetup TJ gave us his perspective on Ruby and Rails coming from extensive experience with Zope. Yesterday I ran across someone else musing about the same thing, and thought ya'll might be interested: http://times.usefulinc.com/2006/01/21-rails-zope Hope everyone had a great weekend, -- Nathaniel Talbott <:((>< From matthew.todd at gmail.com Mon Jan 23 13:03:23 2006 From: matthew.todd at gmail.com (Matthew Todd) Date: Mon, 23 Jan 2006 13:03:23 -0500 Subject: [raleigh.rb] code coverage, fyi Message-ID: <8932dfd40601231003h48fd0df5l6158f192573806a4@mail.gmail.com> Hi, all, at a meeting a while back, some of us tried spiking a code coverage tool. That was cool, but of course it was intended primarily as a learning excercise rather than something we were going to take all the way. If you're into code coverage, I just noticed this: http://eigenclass.org/hiki.rb?rcov+0.1.0+prerelease FYI, -- Matthew From pelargir at gmail.com Mon Jan 23 23:51:24 2006 From: pelargir at gmail.com (Matthew Bass) Date: Mon, 23 Jan 2006 23:51:24 -0500 Subject: [raleigh.rb] code coverage, fyi In-Reply-To: <8932dfd40601231003h48fd0df5l6158f192573806a4@mail.gmail.com> References: <8932dfd40601231003h48fd0df5l6158f192573806a4@mail.gmail.com> Message-ID: Hey, that is fantastic. Thanks, Matthew. My group SAS is big into code coverage and continuous integration of our Java stuff. Having a tool to point them to for Ruby (however beta it might be) is a good thing. Many developers are still skeptical about the language, if not downright hostile. Sad, since it's such a relaxing, pleasant language to code in. =) Hope everyone is having a productive week. Matt On 1/23/06, Matthew Todd wrote: > > Hi, all, at a meeting a while back, some of us tried spiking a code > coverage tool. That was cool, but of course it was intended primarily > as a learning excercise rather than something we were going to take > all the way. > > If you're into code coverage, I just noticed this: > http://eigenclass.org/hiki.rb?rcov+0.1.0+prerelease > > FYI, -- Matthew > > _______________________________________________ > raleigh-rb-members mailing list > raleigh-rb-members at rubyforge.org > http://rubyforge.org/mailman/listinfo/raleigh-rb-members > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/raleigh-rb-members/attachments/20060123/3cad500d/attachment.htm