3 ms·

It being open-source (under your control) or not does make a difference here. In an open-source thing, with this sort of productivity-harming breakage, you cou

It being open-source (under your control) or not does make a difference here. In an open-source thing, with this sort of productivity-harming breakage, you could worst-case just pay a random freelancer to fix it for you. You don't have that option with Slack.

acdha 7y ago
That’s how you end up with critical apps which are full of known security issues because now upgrading requires reverse-engineering and migrating a bunch of one-off customizations. This approach only works if you’re committed to paying regularly to maintain your fork.
- woodrowbarlow 7y ago
  or upstream your fixes
  - gizmo686 7y ago
    That only works if upstream wants your fixes.
    - eythian 7y ago
      Then you have the proprietary problem again, only worse as then you can't make the fixes.
- joepie91_ 7y ago
  I did say "worst-case". And as another commenter suggested, upstream your fixes.
  - acdha 7y ago
    “upstream your fixes” only works if the upstream wants them. If you charge in saying “you're all dummies (per OP); here's a patch which goes against your project direction which I want you to maintain in the future”, that's probably not going to be very successful.