Stop supporting old releases.https://medium.com/@mikeal/stop-supporting-old-releases-70cfa0e04b0c …
-
-
In particular this section strongly disputed the "burnout" narrative the "old releases" post rests on.pic.twitter.com/hKILGliKGh
-
not really, people on older releases need to be pushed into contributing. the solution is still “more contributors”
-
"OSS burnout", "free ride", etc is all language you repudiated in your "community" essay. I take your point, but the wording was ...
-
very much from the "maintainer" POV. It would have been great to see the same argument from the "community" perspective.
-
so, the piece is predicating on being open to contributions. but ya, there's something a little different about vendor contributions.
-
I don't think so, but maybe it's a space worth drilling into.
-
In particular, smoothing the differences between different classes of contributor/customer enables a lot of unexpected contributions.
End of conversation
New conversation -
-
-
Beyond that, simply "adding contributors" is not a complete solution. Open source's biggest issue is the lack of code review for contributions; handing out commit bits without solving that issue can't be the long-term solution.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But the modern viewpoint is very much "releasing code is a commitment to maintain it, on all platforms, for all time" and "patches welcome is not an adequate response to a bug report". I read that post as "yes, patches welcome is very much the right response to a bug report".
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.