You could have avoided the entire controversy by taking the entirely reasonable step of honoring the initial request to be opted out.
I think sticking with opt-out is ok since it will be the difference in having a million projects or 3 projects. But, it means you have to be more considerate of the project owners requests. Thinking that the emails "weren't that bad" is more evidence that you aren't listening very well.
> "I think sticking with opt-out is ok since it will be the difference in having a million projects or 3 projects.
There is a difference between "right" and "convenient for tip4commit". Assuming that no project maintainer wants to be part of tip4commit, should they all be made to opt-out? I'd argue that it is tip4commit that have to make a case for themselves and convince stakeholders of their benefits. Avoiding marketing by choosing defaults that are convenient for you but possibly a nuisance to your stakeholders is a very arrogant and short-sighted position to take.
I think sticking with opt-out is ok since it will be the difference in having a million projects or 3 projects. But, it means you have to be more considerate of the project owners requests. Thinking that the emails "weren't that bad" is more evidence that you aren't listening very well.