Gábor's bloghttp://www.nekomancer.net/node/162/atom/feed2008-04-24T00:17:01-05:00GitHub and adshttp://www.nekomancer.net/blog/2008/04/24/github-ads2008-04-24T00:15:53-05:002008-04-24T00:17:01-05:00gaborRuby on Rails recently started to use Lighthouse for ticket-tracking and GitHub for source-code-management. Both of these products/services are closed-source. i personally wonder if this is a good move (to base your infrastructure on closed-source). Well, for GitHub, the underlying technology is Git, so if they later decide to migrate somewhere else, it should be ok. Let’s hope that Lighhouse has some nice export-all-content functionality :)
while both of these services (GitHub, LightHouse) are closed-source, i somehow assumed that they at least ‘understand’ how open-source/free-software works. but then, yesterday i found out that GitHub Terms of Service forbids free-account-users to block ads. hmmm…maybe they should also forbid free-account-users to open Mercurial’s web page in their browser, while GitHub is open in any other window/tab.
]]>Ruby on Rails recently started to use Lighthouse for ticket-tracking and GitHub for source-code-management. Both of these products/services are closed-source. i personally wonder if this is a good move (to base your infrastructure on closed-source). Well, for GitHub, the underlying technology is Git, so if they later decide to migrate somewhere else, it should be ok. Let’s hope that Lighhouse has some nice export-all-content functionality :)
while both of these services (GitHub, LightHouse) are closed-source, i somehow assumed that they at least ‘understand’ how open-source/free-software works. but then, yesterday i found out that GitHub Terms of Service forbids free-account-users to block ads. hmmm…maybe they should also forbid free-account-users to open Mercurial’s web page in their browser, while GitHub is open in any other window/tab.