Re^2: (OT) Sponsoring open source

Theory,

Thanks for the comprehensive answer, it's very helpful.

Regarding subclassing... one of the items the first sponsor wanted was a specific kind of excerpt highlighter. What I did was open up the Highlighter API to make it more customizable, then wrote the custom subclass for them. The complexity is all within the library; they should be able to maintain the custom subclass themselves. IOW, there wasn't a "right" way to do things before, but there is now. Sounds like the kind of thing you've done with "translating" into a "generally useful" feature.

For cases where a "right" way can't be created... I dunno, I think that might not work so well. KinoSearch isn't as big as Bricolage, but it's still pretty big. Supporting hacked versions could get really complicated if the internals change. I'd lean towards declining the gig.

--
Marvin Humphrey
Rectangular Research ― http://www.rectangular.com

Comment on Re^2: (OT) Sponsoring open source

Replies are listed 'Best First'.
Re^3: (OT) Sponsoring open source by Theory (Beadle) on Jun 13, 2006 at 20:34 UTC
Sounds like the kind of thing you've done with "translating" into a "generally useful" feature. Yes, that's it exactly. And yes, if it's too hacky, by all means decline the gig. Or better still, make recommendations for a correct implementation that you'd be willing to do, instead. Be sure to include arguments as to the greater maintainability and less of a headache for them if they decide to spend a bit more and do it the right way. Most companies will agree if the difference isn't excessive. As for those who don't, who needs them? —Theory	[reply]

Replies are listed 'Best First'.

Re^3: (OT) Sponsoring open source
by Theory (Beadle) on Jun 13, 2006 at 20:34 UTC

Sounds like the kind of thing you've done with "translating" into a "generally useful" feature.

Yes, that's it exactly.

And yes, if it's too hacky, by all means decline the gig. Or better still, make recommendations for a correct implementation that you'd be willing to do, instead. Be sure to include arguments as to the greater maintainability and less of a headache for them if they decide to spend a bit more and do it the right way. Most companies will agree if the difference isn't excessive. As for those who don't, who needs them?

—Theory

[reply]

In Section Seekers of Perl Wisdom