And sometimes implementing strict rules about how things have to be done (for many everything besides writing code, like tests, management stuff, ...) might hurt more than one might expect
I agree strongly with this statement, we need to keep the bar to contributing as low as possible, while still maintaining some loose quality control, perhaps after the fact. As must be fairly obvious by now, I am not a programmer by training, more of an occasional dabbler. The only reason that I initially got involved with Inkscape was because Python was a very friendly language, and not too intimidating. From there I slowly graduated to doing some small bug fixes. If I had known up front that I would have to submit all code changes to some kind of formal software review process, and if it had been necessary to create my own personal branch of code and then make a proposal to merge the branch, etc, etc, then those requirements would have been enough to convince me not to even attempt to get involved. Luckily those requirements did not exist 7 years ago, which is how I somewhat accidentally got involved, through curiosity about dxf export.
Alvin
-- View this message in context: http://inkscape.13.x6.nabble.com/Create-releases-more-regularly-tp4969922p49... Sent from the Inkscape - Dev mailing list archive at Nabble.com.