[Chirb] Meeting Proposal

[Ryan Platte]

If this turns into multiple sessions, let's please get some hands-on coding
into those sessions. If we're discussing Merb, I should have a start at a
Merb app at session's end, for example.

On Mon, Jun 30, 2008 at 10:43 AM, Kris Hicks <krishicks at gmail.com> wrote:

> Josh,
>
> The 14th works for me.
>
> The way I was thinking of doing it originally was to run through the why
> and how of its creation, and then how it was scaled.  That would expose the
> different pieces of it and how they were used, which could then be used to
> figure out where people's interests lie for scheduling later meetings about
> specific parts of it.
>
> It's up to the group, really;  I just need to know how to organize my
> slides.
>
> Thanks,
>
> Kris
>
>
> On Mon, Jun 30, 2008 at 10:20 AM, Josh Cronemeyer <
> jcroneme at thoughtworks.com> wrote:
>
>>
>> Kris,
>>
>> Are you interested in giving your presentation at the July meeting?  If we
>> play by the rules July 7th is our next meeting, but as it falls on the first
>> day after a holiday weekend people might want to delay until July 14.  So if
>> you prefer that date we can make it happen.  If you weren't thinking July,
>> let me know which month you want to schedule for and I'll put you on the
>> calendar.
>>
>> Josh Cronemeyer
>>
>>
>>  *"Kris Hicks" <krishicks at gmail.com>*
>> Sent by: chicagogroup-members-list-bounces at rubyforge.org
>>
>> 06/28/08 09:40 AM
>>  Please respond to
>> Chirb discussion list <chicagogroup-members-list at rubyforge.org>
>>
>>   To
>> chicagogroup-members-list at rubyforge.org  cc
>>   Subject
>> [Chirb] Meeting Proposal
>>
>>
>>
>>
>> Hello,
>>
>> I have a proposal for a Chirb meeting.
>>
>> I'm using the Watir library (*http://wtr.rubyforge.org/*<http://wtr.rubyforge.org/>)
>> as an automation tool, packaging it as an executable and distributing as an
>> internal application at First American Title, where I work.  The executable
>> is created with Exerb (*http://exerb.sourceforge.jp/index.en.html*<http://exerb.sourceforge.jp/index.en.html>),
>> and includes a Ruby interpreter and open-uri.  Upon execution, the
>> executable contacts a webserver (running Nginx/Merb/Thin) and downloads any
>> gems that are required to run the actual application from a source on the
>> webserver.  The user is then presented with a list of what automation tasks
>> they have available to them, they choose one, it downloads the automation
>> task as a Watir script, and they're off to the races.
>>
>> I've talked with a few people about it and there seems to be a fair amount
>> of interest in a) Exerb, b) Merb, c) the basic premise of distributing a
>> barebones executable (running Ruby, no less) which is then built up
>> dynamically to run the automation script, d) using Watir as a sort of
>> end-user application instead of just as a tool for regression testing.
>>
>> I can go to some lengths discussing this in a variety of different ways.
>>  How the application was built, how it was then made to scale (it used to be
>> a self-contained executable), Merb, Watir, subverting the IT department of a
>> Fortune 500 company.. the list really goes on and on.
>>
>> Thanks,
>>
>>
>> Kris Hicks _______________________________________________
>> ChicagoGroup-Members-List at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/chicagogroup-members-list
>>
>> _______________________________________________
>> ChicagoGroup-Members-List at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/chicagogroup-members-list
>>
>
>
> _______________________________________________
> ChicagoGroup-Members-List at rubyforge.org
> http://rubyforge.org/mailman/listinfo/chicagogroup-members-list
>



-- 
Ryan Platte
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/chicagogroup-members-list/attachments/20080630/9ce95351/attachment.html>