Well, first I'd have to come up with a believable business model for it, which would probably require significant restructuring of the code to fit it to a particular purpose. I don't know that I'm interested in doing that.
More likely I'll eventually get around to releasing it as open source. That's not a trivial process though; I'd have to dig up an old archive (which I /think/ I have, but I'm not sure), then I'd have to get the code into some form that I was willing to release--my developer staff never thought that silly things like "documentation" were worth doing, even when the CEO (that would be me) demanded them. Once it's in a decent form, I'd have to really think through how I feel about the various licenses...GPL and BSD would be the main candidates, but there are things that I dislike about both of them. Maybe Perl Artistic License, actually, which is pretty good on its own and gives the user the option of defaulting to GPL.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
More likely I'll eventually get around to releasing it as open source. That's not a trivial process though; I'd have to dig up an old archive (which I /think/ I have, but I'm not sure), then I'd have to get the code into some form that I was willing to release--my developer staff never thought that silly things like "documentation" were worth doing, even when the CEO (that would be me) demanded them. Once it's in a decent form, I'd have to really think through how I feel about the various licenses...GPL and BSD would be the main candidates, but there are things that I dislike about both of them. Maybe Perl Artistic License, actually, which is pretty good on its own and gives the user the option of defaulting to GPL.