This was basically my life with building Ansible for three years. Given, I loved many aspects of it, but it was really hard and it took a major toll. (clarification: this has post has absolutely nothing to do why I am not working on it anymore) I've been considering a bit of a blog post on this (particularly the unknown parts of wide scale OSS projects), but basically open source projects get harder as you have more…
I think parent referred more to contentious issues (e.g. sexism, systemd hate) rather than uncontrollable growth of a project. That said, excellent post, thank you! The opposite of course are projects with too few contributors that accept any patch out of desperation, be it reasonable or not. (ZFS on Linux comes to mind, it's a super nice community and Brian Behlendorf does a great job as project lead but sometimes f…
Ask HN: How do you deal with social media pressure on your GitHub project?
41–50 of 84 posts
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#42This would place additional overhead on the project maintainers, but IMO this is more ideal because emails from trolls and people not contributing to the conversation can easily be ignored by filtering out messages from that Github user.
It would not be perfect but it might be better than what we currently have?
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#43This was basically my life with building Ansible for three years. Given, I loved many aspects of it, but it was really hard and it took a major toll. (clarification: this has post has absolutely nothing to do why I am not working on it anymore) I've been considering a bit of a blog post on this (particularly the unknown parts of wide scale OSS projects), but basically open source projects get harder as you have more…
Django enforces this strongly. Anything other than trivial pull requests will be ignored. Contributors are strongly advices to start a discussion on the dev mailing list before working on code and for anything big there's now a formal process for 'Django Enhancement Proposals' (obviously modelled on Python's PEPs)
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#44Too bad GitHub can't weight comments/issues by quality of contributor/user instead of only providing a binary choice of "only the contributors" vs "allowing everyone".
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#45Earlier quoted context omitted.
The recent witch hunt against projects that don't have Code of Conducts. 'meh' did a masterful job with those: https://github.com/opal/opal/issues/941 https://github.com/opal/opal/issues/942 https://github.com/opal/opal/issues/945
My god those comments are a shitshow
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#46Too bad GitHub can't weight comments/issues by quality of contributor/user instead of only providing a binary choice of "only the contributors" vs "allowing everyone".
But how do you measure that quality? Based on amount of contributions? Based on +1's they've received on comments?
You know, GitHub developers are quite smart.
They could just write their own weighting algorithm if they wanted to. :-)
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#47Earlier quoted context omitted.
what are some nice ones?
Gitlab is an excellent self-hostable alternative to github. https://about.gitlab.com/
We're bringing GitLab to FreeBSD. :-)
Check the ruby@ list for current status, things left to do, etc.
https://lists.freebsd.org/pipermail/freebsd-ruby/2015-July/t...
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#48My most popular product at the moment has maybe 150k installs and I could spend the rest of my life trying to appease every request. I can only imagine a massively successful software project must be a deluge of requests.
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#49Earlier quoted context omitted.
You got some great points there but I don't think contributing a change without asking get before is bad even if it misses the project goals. I sometimes need a feature and posting it on mailing lists, etc tasks too long (considering the contribution is only going to be a few lines ~100). If it misses the goal of the project, I don't reallt care. It has fulfiled the licensing agreement (to post code back upstream). I…
There is a sense of pressure to merge PRs, though. When you have a lot of open PRs it starts to discourage further contributions. And if you reject a lot of PRs, or if you are too strict about it (i.e. nit-picking their PRs) it can also create a negative atmosphere that discourages further contributions. Also... when you deal with dependencies in a package manager (like npm dependencies), it is less than ideal to rel…
So quickly outline the reason why it's not ready for merge, and if the contributor doesn't respond in a reasonable window you can reject the PR with a clear conscience. If someone else takes an interest and offers to clean up the code, you can reopen the PR.
Re: Ask HN: How do you deal with social media pressure on your GitHub project?
#50Earlier quoted context omitted.
My god those comments are a shitshow
Meh is a genius in handling those people, you do have to admit that.
If he was a genius, you probably wouldn't ever have known the issue existed. At least it seems that way to me.