This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: Git Project Hell
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
We're in a bad situation with the composite_primary_keys library. Just take a look at its github network.
For those of you not familiar with ActiveRecord it's the default ORM for Rails. Unfortunately, it doesn't support composite primary keys out of the box. That hoses Oracle users, who must use this library to make AR work properly with Oracle for any table with more than 1 column used for a primary key.
Back to the github project. In short, 46 forks, including forks of forks, and at least 4 independently published gems, all in various states. Few of the fork owners seem to communicating with each other.
So, what the frack are we supposed to do now? This is the sort of problem you don't see in the wild with centralized VCS' because either everyone is committing to a central project (instead of forking it). Or, in the extreme case, one guy will create a separate project (effectively forking it once), and programmers will then commit to that project going forward. Our choices are to either pick one fork and hope for the best, or fork the project ourselves, and devote resources to maintaining it.
TOTAL SUCK.
This is an awful situation to be in, especially from a business perspective. In short, we're seeing the failings of the whole "social programming" paradigm IMO. Sometimes you need a dictator to steer the project, and crush the opposition. Instead, we've got a bunch of senators all vying for power and there's no easy way to tell which one is the future Augustus.
Previous Topic
