This is a good time for a story. I opened a feature suggestion issue on vscode last month. Nothing significant, just a little potential polish on for what seemed like a common usage pattern. Within 6 days, it was triaged by an MS dev manager, and the impl had landed in master.
-
-
Prikaži ovu nit
-
I was astonished; given the size of the project and the pressure its devs must be under given how "retail" it is, I expected the suggestion to languish for weeks or months before being addressed, nevermind acted on.
Prikaži ovu nit -
The point: this is damn fine customer support, but it's happening where "open source" happens. And while vscode is open source by any objective measure, the norms (and many, many others) it sets and reinforces is are absurd that is absurd to expect elsewhere, nvm from volunteers
Prikaži ovu nit -
Nevertheless, github issues is now absolutely treated as a helpdesk, by both maintainers & consumers. Thus the burnout, mismatched expectations, cycles of drama and loss (especially when people think they're in it for the fun and feels, when others are there b/c it's their job)
Prikaži ovu nit -
Some say "we can fix this by getting OSS maintainers paid", but this is missing the fundamental point, stated at the top of this thread: OSS as generally practiced is a cost-reduction strategy. Trying to raise the cost of OSS will always be pissing up a rope.
Prikaži ovu nit -
In any case, some people just want to publish code and learn and meet and work with people that have similar interests; dropping tickets in their lap along with pennies on the dollar is rightly viewed as absurd if you're in that context
Prikaži ovu nit -
*having fun programming* «hey, this code you wrote is causing this error (or _might_ cause this error) in the application I get paid to work on. and yeah, here's an open source grant» ... "sir, this is a wendy's"
Prikaži ovu nit -
apologies to all the good people I know doing good around funding open work, maybe it really all will work out, if so, my bad
Prikaži ovu nit -
postscript: if you're going to do this open source thing anyway (ha-ha, I do, sort of badly for a long time now, lolsob) take heed of
@ztellman's piece touching on setting and modulating expectations in open sourcehttps://medium.com/@ztellman/standing-in-the-shadow-of-giants-9ac52f8b4051 …Prikaži ovu nit -
or, maybe a good strategy might be to just use a license super-hostile to anything commercial, which might well select for communities and contributors that (statistically?) have a worldview understanding that you're not down for running a helpdesk
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.