6

The internal dynamics of a project are their own business. I've seen some that only publish stable versions on github (or such), others that are just distributed as tarballs (and you can send patches to the maintainer). Some, like TeX (used to) be handled just by the lead developer, who collected bug reports and proposed patches, and took a look at what has ...


5

There doesn't seem to be a copyright violation here. The code was pretty clearly released under the LGPL, and open source licenses are (almost certainly) irrevocable; it doesn't matter that the patch was never accepted, the code was still released under the LGPL, so as long as the appropriate copyright notices are being maintained (and it seems like they are)...


3

Treat them like you handle anyone else: with respect and with kindness. Don't assume evil intentions when you can assume ignorance. Teach people how to behave and how you expect contributions instead of berating them. Lead by (good) example. Tell people that you will have an open ear and are willing to listen, if they have any issues concerning behaviour or ...


Only top voted, non community-wiki answers of a minimum length are eligible