Over the last week, Abhinav and I have been working on some enhancements and cleanup of LicenseAudit. For those that don’t know, LicenseAudit is a tool to track bundler dependencies, and their licenses. It is build on top of the license_finder gem.
The majority of the work was on stabilizing the code which resolves the dependencies, but we also managed to squeeze in a few new features, too. Most notably, we now support gems. The long term goal is to allow gems to have badges (in the same vein as travisci and codeclimate) which will show the state of the licensing information of a repo.
The other major feature that was added is designed to help with the adoption of LicenseAudit. If your app has been using the license_finder gem and you have your dependencies database checked in, the first time we audit your project we will import the data from the dependencies.db file.
We’d love as many people as possible to try LicenseAudit – http://licenseaudit.pivotallabs.com – out, and we’d love any and all feedback!
Over the last couple of weeks myself and Alex Basson have been working on stabilising, and adding some new features to, LicenseAudit. Whilst we have a long way to go, we think we have a solid foundation to build on.
What is LicenseAudit, you ask?
It is a web application wrapping the LicenseFinder gem which has been around for a few years now. You can authenticate via github, and then audit any project on which you have admin rights.
Once audited, every push to the repo will reaudit your application and notify you via email if there are any dependencies which need your attention. Similar to the LicenseFinder gem, you can configure a whitelist of licenses, and which bundler groups to ignore.
What’s new, you ask?
- Tracker integration – A chore will be created whenever you have new unapproved dependencies,
- Email notification when all dependencies are once again approved,
- Support for all versions of ruby (including jruby, rubinius, et. al.), and,
- Speed improvements.
Please try it out, and send any feedback to email@example.com!
Backbonejs 1.0 is out
Not a great deal of changes compared to 0.9x – mostly small behavior adjustments on Collection#set & Model#save.
Upgrading instructions: http://backbonejs.org/#upgrading
git rebase –edit-todo
As of git 1.8.0,
git rebase learned “–edit-todo”. This is something you can use to edit the todo list while in the middle of a rebase. For example, if you mark a commit as e (for edit) when you initially edit the todo list, when git stops at that commit allowing you to edit it you can then
git rebase --edit-todo to edit the remaining portion of the todo list.
“What are the reasons for using
to_string is for Java developers. Cathy will look into this more today and report back.
- Using jasmine’s pretty-print with ember.js was causing the browser to crash as it was recursively going through the object graph trying to construct a string representation of the object. Defining
Em.Object.Prototype.jasmineToString() to return
this.toString() fixed this.
- We were having trouble screen sharing to some of the mac minis connected to the TVs, the screen sharing app would hang on “receiving first screen”. The fix for this is to command+k from finder and enter vnc://machine-name
- Bootswatch is cool. It contains a bunch of different styles for Bootstrap.
- Corey Innis has a fork of bootstrap which removes classes like span12
Ask for Help
“Has anyone used cucumber for code coverage? We’re trying to find dead code.”
SimpleCov worked great for rspec, but when used with cucumber introduced a lot of timeouts.
Ask for Help
“Sean asked about git rebase complaining about no changes?”
The suggestion was that it was generally safe to just skip in this situation.
Ask for Help
“Brent and Kris asked if anyone had encountered an after_destroy callback being called twice?”
Few suggestions were check that it was only one object being deleted, that there are no dependent objects being cascade deleted, etc.
“Joe asked about how to set default_url_options for? There are no mailers involved as far as he knew.”
Grant suggested trying to set it per class.
“New Lee asked about were there any updates/alternatives for AccessList as the gem is causing him grief with sorting.”
Ian knew of an alternative to AccessTree, Lee is still looking.
- Jonathon pointed out that background-color: cover and :clipping were useful for playing with background images
- New Lee brought up that if you’re using a form builder on a collection Rails will create a hidden for ID which will always get inserted (and may cause a problem if you’re nesting things in a ul or table). To get around this put in a hidden for ID in an appropriate place and Rails will stop generating one.
- Jonathon ended up being pointed towards Heydown as an alternative to ShowOff for presentations by Davis
Ask for Help
“Jonathan Berger asked if anyone has much experience with ShowOff?”
Davis was going to speak to Jonathan offline.
- Joe pointed out the syntax to push remotely was:
git push remote local:remote