3 ms·

> How are they misleading people? By encouraging contributions but not accepting practically any of them and not communicating this. Go have a poke around your

by jahnu 2y ago

> How are they misleading people? By encouraging contributions but not accepting practically any of them and not communicating this. Go have a poke around yourself in the repo and the community forums and you'll see what I have already described happen many many times. Edit the README and spell out the actual state of affairs and all that wasted effort will stop. It's not entitlement on behalf of contributors, it's Signal org falsely proposing to people and giving the impression to the wider world that they can contribute when in practical terms they cannot. I didn't even say it was deliberate and maybe it's not but it sure as heck is unprofessional.

palata 2y ago
The README says [1]: > If your pull request follows all of the advice above but still has not been merged, this usually means that the developers haven't had time to review it yet. We understand that this might feel frustrating, and we apologize. The Signal team is still small, but we are hiring. Again, this is how open source works. If you need the README to tell you "btw, we don't owe you anything, it is all best effort, and it may be that we don't have time to address your PR", then you haven't (yet) understood open source. Don't take it personally, a ton of people complain like you do. Which is why I don't open source my code anymore. Then people can't benefit from it, but at least they won't feel like they can put pressure on me to work for them for free. Because that's exactly what you are doing: even if you did put efforts into your PR, you are asking them to work for you for free right now. And you don't only put pressure by complaining on their GitHub issues: you go one step further by trying to get the HN community to help you put pressure on them. I have had a lot of people telling me "be careful: if you don't work in your free time to implement that feature for me, I won't use your project for free". And many people say that in a much less polite way. [1]: https://github.com/signalapp/Signal-iOS/blob/main/CONTRIBUTING.md#merging-can-sometimes-take-a-while https://github.com/signalapp/Signal-iOS/blob/main/CONTRIBUTI...
- deleted 2y ago
  [deleted]
- deleted 2y ago
  [deleted]

by jahnu 2y ago

palata 2y ago

The README says [1]: > If your pull request follows all of the advice above but still has not been merged, this usually means that the developers haven't had time to review it yet. We understand that this might feel frustrating, and we apologize. The Signal team is still small, but we are hiring. Again, this is how open source works. If you need the README to tell you "btw, we don't owe you anything, it is all best effort, and it may be that we don't have time to address your PR", then you haven't (yet) understood open source. Don't take it personally, a ton of people complain like you do. Which is why I don't open source my code anymore. Then people can't benefit from it, but at least they won't feel like they can put pressure on me to work for them for free. Because that's exactly what you are doing: even if you did put efforts into your PR, you are asking them to work for you for free right now. And you don't only put pressure by complaining on their GitHub issues: you go one step further by trying to get the HN community to help you put pressure on them. I have had a lot of people telling me "be careful: if you don't work in your free time to implement that feature for me, I won't use your project for free". And many people say that in a much less polite way. [1]: https://github.com/signalapp/Signal-iOS/blob/main/CONTRIBUTING.md#merging-can-sometimes-take-a-while https://github.com/signalapp/Signal-iOS/blob/main/CONTRIBUTI...

deleted 2y ago
[deleted]
deleted 2y ago
[deleted]