Am Dienstag, 17. Februar 2015, 16:48:34 schrieb Matthew Toseland: > Generally fair, but just to be clear: When API changes are a necessary > part of a paid developer's work, they should not generally be expected > to fix unofficial plugins. Obviously if an official plugin is broken by > core fred changes, the dev should fix that.
I guess if they are truly necessary, few people will mind. But unofficial plugins are important - at least as important as official ones. They are community-projects; stuff which gets people to invest deeper. They are programs people actually use, and breaking them will drive away future developers. If something is official, people might feel an obligation to keep it working. If it is unofficial and an update breaks it, the chance is much higher that the developer will just give up in frustration and invest time where he or she perceives it as being valued more. Few things are more frustrating than having to invest work just to keep things working. In short: Do not break the API without *really* good reason. Always act as if a change in the API will break a program which >10% of the users consider as essential for their Freenet usage. Best wishes, Arne
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
