Comments on: Flashbake http://thecommandline.net/2009/02/13/flashbake/ Podcast and blog exploring digital citizenry as a creator and a consumer. Sun, 29 Jan 2012 03:51:03 +0000 hourly 1 http://wordpress.org/?v= By: cmdln http://thecommandline.net/2009/02/13/flashbake/comment-page-1/#comment-1787 cmdln Sat, 14 Feb 2009 06:41:33 +0000 http://thecommandline.net/?p=1294#comment-1787 There is an unofficial git module for python, I will be switching to that shortly. The emphasis isn't on driving git, it is on building up the commit message automatically. Otherwise, why even bother automating git? Bear in mind the original target audience, someone savvy enough to know git and other source control systems exist but have never used them. I'd welcome pointers to seamless source control usable by anyone less technically adept than a programmer or a system administrator. The point of asking for contact wasn't because of any license concern. Fork away if you are okay with the boiler plate conditions of the license. The point was that I already had given some thought to pluggable back ends for different version control systems. I'd prefer to get contributors to help build that out in the original code if possible but the non-commercial license condition restriction aside, the fact that I am doing anything other than all rights reserved should signal my willingness to allow forks and other customizations. I am open to re-considering the license choice at some future point. There is an unofficial git module for python, I will be switching to that shortly. The emphasis isn’t on driving git, it is on building up the commit message automatically. Otherwise, why even bother automating git?

Bear in mind the original target audience, someone savvy enough to know git and other source control systems exist but have never used them. I’d welcome pointers to seamless source control usable by anyone less technically adept than a programmer or a system administrator.

The point of asking for contact wasn’t because of any license concern. Fork away if you are okay with the boiler plate conditions of the license. The point was that I already had given some thought to pluggable back ends for different version control systems. I’d prefer to get contributors to help build that out in the original code if possible but the non-commercial license condition restriction aside, the fact that I am doing anything other than all rights reserved should signal my willingness to allow forks and other customizations. I am open to re-considering the license choice at some future point.

]]> By: James http://thecommandline.net/2009/02/13/flashbake/comment-page-1/#comment-1786 James Sat, 14 Feb 2009 06:26:16 +0000 http://thecommandline.net/?p=1294#comment-1786 Congratulations of half-rewriting the Perl Git module which comes with git just so you could try out python. Does 'Attribution-Noncommercial-Share Alike' really require seeking permission before forking? Not that I would, non-commercial is a killer there. Congratulations of half-rewriting the Perl Git module which comes with git just so you could try out python.

Does ‘Attribution-Noncommercial-Share Alike’ really require seeking permission before forking? Not that I would, non-commercial is a killer there.

]]> By: Aaron http://thecommandline.net/2009/02/13/flashbake/comment-page-1/#comment-1785 Aaron Fri, 13 Feb 2009 22:24:36 +0000 http://thecommandline.net/?p=1294#comment-1785 One way to find out good snapshot intervals would be to record a given directory in parallel multiple ways with different parameters into separate repos. It doesn't look like that's currently possible. One way to find out good snapshot intervals would be to record a given directory in parallel multiple ways with different parameters into separate repos. It doesn’t look like that’s currently possible.

]]>