Having using Acl9 for some time, it was refreshing to see RailsCast's Ryan Bate's take on authorization: CanCan . Ryan put together a webcast for CanCan that you can checkout here . There have been some nice additons since this initial release so do checkout the latest documentation on GitHub. I won't go into what I dislike about Acl9. It's a good system, with a nice DSL for defining permissions. I'll just talk about some of the things …
This past weekend Rubyists from all over descended upon Kansas City (my hometown and new place of residence) for the Ruby Midwest conference. Headlined with keynotes from Chris Wanstrath (of GitHub fame) and Yehuda Katz (of Merb and now Rails fame), more than 150 Rubyists attended the single-track conference at the UMKC campus. Intridea was represented by four members, one talk, and by sponsoring a Kansas City Barbecue dinner for the first night of the conference.
…translating the days of the week and so on, and sometimes needed help with more complex sentences. This is my fork of Tolk that autotranslates your translation string with google translate to give you a sensible starting point rather than a white box.
It's on github: http://github.com/tokumine/tolk/
Tolk and Google Translate from Simon Tokumine on Vimeo .
…canonical source for OSS tends to win the citation link. Make sure that is on your site rather than on Github, etc.)
OSS in new fields in software — for example, Rails development the last few years — has landgrab economics. The first semi-decent OSS in a particular category tends to win a lot of the links and mindshare. So get cracking! And keep your eyes open for new opportunities, particularly for bits of infrastructural code which you were going to write for your business …
By which I take him to mean that lots of people throw something up on GitHub, push a gem, and provide a few lines of doc before something even works.
Levels of open source Massive ( Linux kernal), Big ( Rails, JQuery), Medium ( homebrew) Tiny (most of the rest) @ defunkt # RubyMidwest # rbmw
The tiny ones tend to be all the ones we use - and they tend to be managed poorly @ defunkt # RubyMidwest # rbmw
Some open source projects are managed really well, but it's …
…this going from here?
Not sure. It does what I need it to do right now. It's something I've found myself doing on two different projects that I thought would just make my life easier.
Project Info
ActsAsCachola is hosted on Github: http://github.com/rbrant/acts_as_cachola , where your contributions, forkings, comments and feedback are greatly appreciated. Please do add tests if you want me to pull in any changes.
…and perhaps spending a day or two in SF going to bug the EngineYard and GitHub guys.
After that? I've got invites to go visit people in Indiana, Ohio and Florida and so that's what I'll be doing. No specific dates yet, but there's definitely a whole slew of people from the Ruby community who I'd love to meet.
Thanks to the people who have already offered accommodation! In my single overseas trip experience so far, this takes a lot of hassle out of doing …
Not everyone can be at the front of the game. This of course holds true in our little open source world. We all can't be the Github's or <insert other company you believe to be successful right here>. But here is a little tip: Every time you you give someone a tidbit that because a part of their success, you too are part of that success.
Of course that doesn't mean they owe you some sort of financial prize or even acknowledgement. The real reward is just knowing you helped moved someone a little farther along.
…see more and more teams implement that sort of functionality. Rick Olson describes how GitHub implements it in How we deploy new features , and includes links to how Forrst and Flickr do it as well. At Velocity, Paul Hammond explained how to build an application-specific kind of version control into your app .
I'm a little surprised that few libraries have emerged for managing this. It would seem that, given all the excitement about continuous deployment, automated …
…project is private, we'll give you that public key and ask you to add us to your repository. On GitHub, that's as easy as adding a new Deployment Key in the Admin area of your project. And, that's not to say that we only work with GitHub; in fact, we work with any Git repository that is internet-accessible, whether it's publicly available, SSH-only, or HTTPS.
"You said this was good for the community, I just don't see it." Well, beyond helping …