If you are wondering where the data of this site comes from, please visit GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

bgentry/coursera-getting-and-cleaning-data-project 11

course project for Coursera "Getting and Cleaning Data"

bgentry/actioncable-go 6

A golang ActionCable client

bgentry/dm-core 2

DataMapper - Core

bgentry/acts-as-taggable-on 1

A tagging plugin for Rails applications that allows for custom tagging along dynamic contexts. This is my own version, with a few modifications: Dropped support for Rails < 3.0; Moving towards a devise-style inclusion model for more easily extendable Tags and Taggings

bgentry/acts_as_restful_list 1

Just like acts_as_list, but restful.

bgentry/capybara-mechanize 1

RackTest driver for Capybara with remote request support

bgentry/database_cleaner 1

Strategies for cleaning databases in Ruby. Can be used to ensure a clean state for testing.

bgentry/dm-is-inheritable 1

Provides Class Table Inheritance (CTI) and proper polymorphic support, including disjoint subtables.

bgentry/dm-is-remixable 1

A rewrite of dm-is-remixable that tries to feel more dm'ish and adds desired behavior

issue commentbgentry/que-go

Opening this project to the community

Hi, I'm not opposed to this in principle, but it's challenging to vet a new owner if it's not somebody I have a history with.

Perhaps a better option would be to just create that new org/fork? I'd be happy to post a notice on this project to direct others to go there instead. My repo here isn't at all up-to-date with modern Go, nor is it the most efficient system design these days.

As long as the copyright is maintained I have no issues with this.


comment created time in 17 days