New Version of Autobase: Payware?

Posted by: Robert Fischer on 2009-10-27 12:13:00.0

Since nobody’s come out of the woodwork to fund the Autobase Grails plugin, but that plugin desperately needs a new version and extensions, so I’m considering working on it over the holidays and releasing it early next year as payware, or perhaps under a GPL/payware scheme a la Zed Shaw’s GPL approach or Clojure’s use of the SCA. Note that using a plugin under the GPL will GPL your code by extension.

I don’t want Autobase to stagnate and die, but I also can’t afford to be burning time on something that won’t produce money in some form: grad school is sucking up all that kind of time.

Thoughts?


Comments

  • October 27, 2009, Hamlet D\'Arcy wrote: integrate a text based nag screen so that users must type something into the console for their migrations to succeed. you could have some sweet ascii art in it too. perhaps someone else has a better idea ;)
  • October 27, 2009, Robert Fischer wrote: I'm totally going to rock the sweet ASCII art. :)
  • October 28, 2009, Andres Almiray wrote: Will it include unicorn ASCII art? seriously, go for it.
  • October 28, 2009, Dean Del Ponte wrote: I'm surprised no company is willing to step up and pay you to work on it. Well managed database alterations are an integral part of deployment.
  • October 28, 2009, Robert Fischer wrote: You and me both, Dean. Is your company interested? To the more general audience: Should I warn the Grails community about this plan and give someone a chance to step up and fund its development?
  • October 28, 2009, Hamlet D'Arcy wrote: maybe the idea of paying someone to clean their own toilet they set out in their front yard themselves is off putting to some enterprises?
  • October 29, 2009, Robert Fischer wrote: 1) That post came out long after Autobase was released. And if people don't want to pay me to work on Autobase, that's fine, but then the improvements/work is catch-as-catch-can. 2) Adoption of Autobase doesn't seem to be the problem. People contributing back up-stream is the problem.
  • November 1, 2009, Michael Kimsal wrote: It would probably not matter to too many people if it was payware as long as the pricing was reasonable. I want to say you set up a different set of expectations when you charge money for something, but I get the feeling that many people basically expect you to fix all their issues for them anyway. An in-depth autobase piece for GroovyMag would certainly net you a small writer's fee - probably not enough to live on for any length of time, but good for a few Chinese dinners. :)
  • November 1, 2009, Robert Fischer wrote: @Michael I'll do an Autobase article as I'm rewriting it: you can publish it as I announce the new system. The new rewrite should enable some cool stuff, and if I'm doing the charging thing, I'm going to do Autobase right.

Creative Commons License
This article was a post on the EnfranchisedMind blog. EnfranchisedMind Blog by Robert Fischer, Brian Hurt, and Other Authors is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.

(Digital Fingerprint: bcecb67d74ab248f06f068724220e340 (69.147.112.169) )


be the first to rate this blog


About Robert Fischer

Robert Fischer is a multi-language open source developer currently specializing in Groovy in Grails. In the past, his specialties have been in Perl, Java, Ruby, and OCaml. In the future, his specialty will probably be F# or (preferably) a functional JVM language like Scala or Clojure.

Robert is the author of Grails Persistence in GORM and GSQL, a regular contributor to GroovyMag and JSMag, the founder of the JConch Java concurrency library, and the author/maintainer of Liquibase-DSL and the Autobase database migration plugin for Grails.