GITHUB!

[Mike Sassak]

Hi Everyone,

After the last meeting, Larry asked me if I could upload the codes to
my demo of cucumber. I said I would, but as he never extracted a due
date from me at gun point, I dawdled. I'm sorry, Larry. :-(

It's up now though. First I created a github account for detroitrb.
It's at http://github.com/detroitrb. I also added everyone I could
find as collaborators on the detroitrb repo
(git://github.com/detroitrb/detroitrb.git). (Currently this means only
Larry and my friend Greg who will be at the next meeting because I've
CC'd him and no way will he back out now... in other words, not a lot
of people). I'm sure there are more of you with Github accounts,
right?

I'm looking at you, Mike and Derek and Mike and Mike and Dan and Mike
and Mike and Mike and Adam.

Sorry for the scattershot email, I'm racing before I go to bed.

Mike

P.S. What are we talking about next time?

[Adam Elhardt]

Let's use this thread to get some input on next time. So far here's
the suggestions:

1. Create a ruby wrapper for the Google Wave api
2. ?
3. ?

If you're super excited about some topic and can't stop talking about,
it's a sign you should give a talk. If you're stuck on something and
need to learn more about a topic, do some research, put it on slides
and give a talk. Or talk someone else into giving the talk for you.
;)

--

===================
Sapphire Internet Media
www.sapphireim.com
313.582.2636

[Daniel Parker]

Let's use this thread to get some input on next time.  So far here's the suggestions:

 

1.  Create a ruby wrapper for the Google Wave api

2.  ?

3.  ?

2? 3? Let's just make that ruby wrapper. Now, are we talking about the Robots API? I really want to do that. I have a really cool idea that I can reveal to you guys at that meeting, that would make this ruby wrapper (rubygem probably) very useful to many people, and if any of you want to jump on the boat and make the website, you can share in any benefits of owning the thing.

If you're super excited about some topic and can't stop talking about, it's a sign you should give a talk.   If you're stuck on something and need to learn more about a topic, do some research, put it on slides and give a talk.  Or talk someone else into giving the talk for you. ;)

I will be presenting on my new super-fast mini framework, Cilantro (see github), at the Grand Rapids group next month. I could do the same for you guys, although I imagine it could be a mini-presentation (15 minutes) for the beginning of the meeting. It could likely start up conversation about the design choices I made, and whether they actually do encourage good app design and quicker coding (like I think they do). Then we could make a quick app (suggestions, anyone?). BUT I'm excited about the next meeting being ALL about Ruby + Google Wave, and I don't want to take any time from that. So, just a suggestion for the following meeting(?) -- only if there is interest -- I don't have to present it, I'll have my venting over with in Grand Rapids. :)

- daniel parker -

"You have granted me life and steadfast love, and your care has preserved my spirit." Job 10:12
"The LORD is my chosen portion and my cup . . . indeed, I have a beautiful inheritance." Psalm 16:5-6
"Give what you can ... take nothing back!"

[Mike Sassak]

On Tue, Oct 27, 2009 at 11:56 AM, Daniel Parker <dcpa...@gmail.com> wrote:
>> Let's use this thread to get some input on next time.  So far here's the
>> suggestions:
>>
>>
>>
>> 1.  Create a ruby wrapper for the Google Wave api
>>
>> 2.  ?
>>
>> 3.  ?
>

> 2? 3? Let's just make that ruby wrapper. Now, are we talking about the
> Robots API? I really want to do that. I have a really cool idea that I can
> reveal to you guys at that meeting, that would make this ruby wrapper
> (rubygem probably) very useful to many people, and if any of you want to
> jump on the boat and make the website, you can share in any benefits of
> owning the thing.
>

Starting with the Robot API would be cool, but I think we should focus
on the basics at first. It's probably going to take a while for all of
us to settle into a good rhythm while working together. If anything
comes of it, we can upload it to github and start from there. I can
maintain a canonical repo on the detroitrb account, and we can
push/pull as we develop it.

>> If you're super excited about some topic and can't stop talking
>> about, it's a sign you should give a talk.   If you're stuck on something
>> and need to learn more about a topic, do some research, put it on slides and
>> give a talk.  Or talk someone else into giving the talk for you. ;)
>
> I will be presenting on my new super-fast mini framework, Cilantro (see
> github), at the Grand Rapids group next month. I could do the same for you
> guys, although I imagine it could be a mini-presentation (15 minutes) for
> the beginning of the meeting. It could likely start up conversation about
> the design choices I made, and whether they actually do encourage good app
> design and quicker coding (like I think they do). Then we could make a quick
> app (suggestions, anyone?). BUT I'm excited about the next meeting being ALL
> about Ruby + Google Wave, and I don't want to take any time from that. So,
> just a suggestion for the following meeting(?) -- only if there is interest
> -- I don't have to present it, I'll have my venting over with in Grand
> Rapids. :)

That sounds interesting. What's the elevator pitch?

[Mike Sassak]

On Tue, Oct 27, 2009 at 1:26 AM, Mike Sassak <msa...@gmail.com> wrote:

> It's up now though. First I created a github account for detroitrb.
> It's at http://github.com/detroitrb. I also added everyone I could
> find as collaborators on the detroitrb repo
> (git://github.com/detroitrb/detroitrb.git). (Currently this means only
> Larry and my friend Greg who will be at the next meeting because I've
> CC'd him and no way will he back out now... in other words, not a lot
> of people). I'm sure there are more of you with Github accounts,
> right?
>

One more thing: if you have direct access to the detroitrb repo,
please refrain from pushing directly to it. (Access is really there
for wikis and issues and such.) If you want to make changes, just fork
and send me a pull request. No sense in going back to the days of
Subversion. :-)

[Daniel Parker]

Okay, well here's a wiki page to provide a starting point for research on Ruby + Wave: http://wiki.github.com/detroitrb/detroitrb/ruby-google-wave-nov09-meeting

- daniel parker -

"You have granted me life and steadfast love, and your care has preserved my spirit." Job 10:12
"The LORD is my chosen portion and my cup . . . indeed, I have a beautiful inheritance." Psalm 16:5-6
"Give what you can ... take nothing back!"

[Daniel Parker]

 

That sounds interesting. What's the elevator pitch?

Elevator pitch:

"Cilantro is a lightweight ruby application framework for those who feel like frameworks box them in and make development just a little more cumbersome. The things about the other frameworks that make us cringe, Cilantro makes easy: setting up a dev or production environment (gems), managing routes, setting up the data environment for views and partials, and managing deployment.

"In the world of Web 2.0 where rich applications are beginning to rule the web, Cilantro is designed for sanely developing applications rather than Data APIs (Rails). In the spirit of 'convention over configuration,' Cilantro's aim is to solve cumbersome development by encouraging the simple and the best design patterns and practices. The result is less application bugs, a clearer mind for developing, easier deploying, and the satisfaction of running a fast, feather-weight framework that has less magic and more simplicity."

Misc Features:

+ Use your choice of ActiveRecord, DataMapper, or other DB engine.

+ Supports Haml, Erb, templates and partials.

+ Auto-installs gems. ( require_or_auto_install 'json', :gem => 'json-pure' )

+ Starts up in under 1 second, even normal-size apps. (largely due to a rubygems hack)

+ Commandline can easily manage several daemons on multiple ports.

+ Provides a light sample app to start from, which is also the framework.

+ Easy to upgrade the underlying framework code without bothering your app code (thanks to git magic).

+ IRB console environment is provided ).

+ Testing through Rack-Test.

It's definitely in beta still, but I'm already using it for every application I make.

[Larry Siden]

Looks like Ciliantro it might be the perfect back-end to go with the front-end app I'm thinking of doing in SproutCore for the U-M Senior Housing Bureau.  Keep me posted!

Larry Siden
http://umich.edu/~lsiden
734-926-9614
skype: lsiden