First Haskell, and now Eclipse moves to GitHub. Only Git repositories are being mirrored to GitHub, but there's more than 70 repositories already created at the Eclipse Foundation page on GitHub. With EGit 0.11 being released as part of 3.6.2 and aiming for a 1.0 release in Eclipse 3.7, there's more demand than ever to move to Git for Eclipse projects.
The well-known Haskell implementation GHC is moving from Darcs to a repository on GitHub, citing wider tool support and faster operations.
With a recent announcement from Nick Quaranto, RubyGems.org has become the default gem source for RubyGems. The three domains gemcutter.org, gems.rubyforge.org, and rubygems.org now all point to the same place, and gem serving and installation work for all three. RubyGems.org is the main web front end, to which the other two sites redirect. The secure site, https://rubygems.org, is also now live.
The first public version of the org.eclipse EGit plug-in version 0.7.1 has been released at EclipseCon. EGit is based on the pure Java implementation JGit, which means that it has no external dependencies or native code requirements; something which has historically hindered the adoption of Eclipse's Subversion support.
Google's ProtocolBuffers and Facebook's Thrift are options for binary serialization, but not ones that pleased the GitHub team - so they created BERT/BERT-RPC based on the Erlang's 'external term format'. BERT/BERT-RPC now power parts of Github's internal communication.
Git# is a .NET and Mono version of the popular source code management system, Git, obtained by porting JGit to C#. Other related projects are: msysgit and gitextensions.
GitHub has stopped automatically building Gems, and will stop their Gem server a year from now. The GitHub team suggests Gemcutter as alternative Gem hosting site next to RubyForge.
With the sudden disappearance of _why, some popular libraries as Markaby, Hpricot and others are orphaned. We look at the effort to find maintainers for some, and at replacements for other libraries.
Rip is a new package management system for Ruby. Why a new package management system? We talked to Rip developer Chris Wanstrath from GitHub to learn more.
GitHub now offers an installable version of the service for users who want to keep their code inside their network - and it's built on JRuby. TorqueBox is a new solution for running JRuby on Rails on JBoss, complete with integration for job queues and SIP integration Also: EngineYard announced it will start providing JRuby as a hosting option in July.
GitHub now also offers an issue tracker, integrated with their Git repository hosting. The issue tracker is also accessible through their new API 2.
RunCodeRun is a hosted continuous integration service for Ruby projects on GitHub, developed by Relevance. We take a first look at the project and talked to its developer Rob Sanheim.
Microsoft recently announced they had moved their IronRuby project to GitHub. The announcement, like many projects these days, shows the project moving from its current Subversion repository to a Git repository located on Github.
In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
GitHub recently added its own RubyGems server with an integrated Gems release process. Only problem: these Gems are not automatically available because RubyGems defaults to RubyForge as source. We talked to RubyGems maintainer Eric Hodel, PJ Hyett from GitHub, and Tom Copeland from RubyForge about the problems and possible solutions.