On Thu, Jan 09, 2014 at 07:58:15PM +0100, Johan Engelen wrote:
On 9-1-2014 5:08, Martin Owens wrote:
On Wed, 2014-01-08 at 17:05 -0800, Bryce Harrington wrote:
Or, they neglected to make the strings translatable. Or developed only on Linux and introduced platform issues for OSX/Windows that only show up after it's in mainline. Or adds a performance impact.
Part of the packet of information could include strong recommendations to factor in some resources dealing with any after bugs. Some guidelines such as: We recommend that you price in a 10% increase to deal with issues that may crop up after you have delivered code.
We can't guarantee anything; but at least we can reasonably ask developers to take responsibility as they're given fair warning to factor some of that cost in too.
That's a good idea. Maybe some "1-month after commit" review for larger projects, to see if there is anything left to mop up.
Yeah, I like the sound of this. So then the 10% would be paid after the 1-month period, for fixing some number of bugs? I suppose if there's no bugs reported, they just get it as a bonus? :-)
Bryce