TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Don't be that open-source user, don't be me

242 点作者 1una将近 3 年前

45 条评论

mooreds将近 3 年前
&gt; However I now see that my use of the tool provided no value to the company, and I was not a paying customer of any of their services, so why should they provide me with free support.<p>That is not true. If the use of the tool provides &quot;no value&quot; to the company, then why on earth are they making the tool available. Yes, there is no money exchanging hands, but there is definitely some value.<p>Here&#x27;s some value a company gets when someone uses a tool&#x2F;piece of software without paying money (source: my company has a full feature free tool that competes with our paid offering, and often wins).<p>* awareness of the solution in the marketplace<p>* developer attention (way way easier to get a developer to try a free tool vs one that costs $0.01)<p>* bug finding (often in environments that would be hard to stand up for the company)<p>* user testing (related to bug finding, but often users will give feedback about feature direction)<p>* market share (if they are picking your free tool, they aren&#x27;t paying for a competitor)<p>At my current job, we often leverage this (our GitHub issues repo and forum are main sources of our roadmap).<p>That&#x27;s not to say that you should expect the same kind of service when you are a free user as when you are paying money. But attention is valuable too, esp of developers.<p>And it&#x27;s not like if you pay money, a product company jumps to build whatever you ask for. Unless you pay a large amount compared to their current revenue and even then, if what you want conflicts with their long term vision, wise leaders won&#x27;t.
评论 #31799544 未加载
welder将近 3 年前
As an open source maintainer[1], the etiquette tips are great. However, I think +1 and status check comments are ok in certain situations where the issue might have been forgotten or it&#x27;s a high priority issue.<p>I also like when someone reminds me they&#x27;re blocked by an issue. It helps me prioritize fixing bugs so I work on things actually affecting people instead of things nobody is using. Just be polite and your comments are welcome.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;alanhamlett&#x2F;pip-update-requirements" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;alanhamlett&#x2F;pip-update-requirements</a>
评论 #31798672 未加载
评论 #31797698 未加载
评论 #31797725 未加载
评论 #31798645 未加载
评论 #31798201 未加载
评论 #31799925 未加载
评论 #31806102 未加载
评论 #31797691 未加载
laurent123456将近 3 年前
Regarding adding +1 to issues - rather than doing this, up-vote the issue on GitHub (thumb up). This can be useful to maintainers because they can sort by thumb up and see the most popular ones.<p>Adding a +1 comment really does nothing - it&#x27;s just one more useless notifications for everyone, and it won&#x27;t allow filtering or sorting issues. People might even unwatch the issue because of this and thus missing useful comments.
评论 #31797800 未加载
评论 #31797919 未加载
评论 #31798316 未加载
评论 #31797772 未加载
评论 #31800736 未加载
nmstoker将近 3 年前
&quot;If you take anything away from this post I hope it is that these costs need to be paid by someone, the maintainer.&quot; - there will be a minimal cost attending to <i>any</i> interaction but provided the efforts made by a reporter are sufficiently well focused then that reporter is saving time for the maintainers.<p>The issue i observe is countless people do such a stunningly bad job at reporting problems. I&#x27;ve some sympathy for those whose first language is not the same as the maintainers, but putting thosr aside, the list of inept&#x2F;time wasti reports is very very long.<p>- subject only issue with only vague adherence to a complete sentence!<p>- no unambiguous description of the problem<p>- no indication why it&#x27;s thought to be deviating from (reasonably) expected functionality<p>- no indication of steps before issue<p>- nor if it&#x27;s a one off, repeated, always happened&#x2F;just started&#x2F;happens to others<p>-no mention of context (eg system, installation method, any reasons it might be expected not to work)<p>and more!
评论 #31800522 未加载
dom96将近 3 年前
Thank you to the author for writing this.<p>Entitlement in open source is a massive problem, I have experienced it first-hand many times. The problem is that it discourages contributions not only from the existing maintainers but also from people who may volunteer to fix issues in the future. Would you be willing to contribute if most of the issues are just asking for things (often rudely) and not even saying thanks when an issue is resolved?<p>Unfortunately I have seen far worse examples than the one linked in the article[1]. I would encourage people to not only think twice before acting this way but to also call out people that are acting entitled in open source to discourage such actions.<p>1 - <a href="https:&#x2F;&#x2F;github.com&#x2F;dom96&#x2F;httpbeast&#x2F;pull&#x2F;35#issuecomment-721877680" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dom96&#x2F;httpbeast&#x2F;pull&#x2F;35#issuecomment-7218...</a>
评论 #31802710 未加载
评论 #31798634 未加载
strken将近 3 年前
Sometimes you can just go fix the software yourself.<p>Maintainers always seem to say you should file an issue before working on a PR. However, I find for features you really need, you should just fork the software yourself[0] and implement what you need, then put up a quick PR with your changes. The worst they can do is reject your changes, in which case...well, you&#x27;re using your fork anyway.<p>[0] Github forks are lightweight, easy(ish) to keep up to date, and integrated into a lot of package managers.
评论 #31798074 未加载
评论 #31797929 未加载
评论 #31798109 未加载
评论 #31797904 未加载
FatalLogic将近 3 年前
This is a thoughtful and important article for anyone who uses or creates open-source software, which is everyone.<p>But, if we follow this advice? If some more thoughtful and considerate users kindly reduce their input into support conversations to avoid overwhelming developers, doesn&#x27;t this mean that support conversations will become dominated by users who are not thoughtful and considerate?
评论 #31797628 未加载
评论 #31802958 未加载
评论 #31798172 未加载
bambax将近 3 年前
&gt; <i>If you were to develop a closed source iOS app and charge for it in the Apple App Store your user base will have certain expectations.</i><p>What&#x27;s weird is that paying users have lower expectations and are much nicer than those who don&#x27;t pay. Why do free users feel entitled? It&#x27;s a bit of a mystery, yet can be observed often.
评论 #31797767 未加载
评论 #31797779 未加载
orbital-decay将近 3 年前
<p><pre><code> The biggest thing that I failed to understand was that with every user commenting this feature is essential for me to keep using Grafana or asking why hasn’t this been implemented yet? a barrier was being built to stop anyone from ever working on it. </code></pre> Wait, does the article not explain why, or does my comprehension fails me?<p>Other points have been reiterated a million times, and still worth to be reiterated. Sure, the most useful attitude for free software is <i>free to contribute to</i>, not <i>free as in beer</i>. Recently I discovered that Photoshop is pretty poor in handling color for the industrial standard it is. Could I suggest an improvement? Nah. In addition to their imaginary &quot;average consumer&quot; (who of course always wants bells and whistles instead of core improvements), Adobe often cater to the requests of large companies, which I am not. Moreover, they have their own business interests such as market segmentation - they had great software called Speedgrade that they butchered and integrated into Premiere, so video folks got everything and photo folks like me got nothing. Meanwhile, Darktable was free to contribute to, which I did.
评论 #31802762 未加载
andris9将近 3 年前
I also run a few popular open-source projects (eg. Nodemailer) and what grinds my gears the most are the support requests disguised as bug tickets. It takes so much time to handle these – first to verify that this in fact is not a bug, and then come up with some kind of response.<p>For example - someone uses Nodemailer and the server they are running their code on has the firewall configured to block non-HTTP&#x2F;S ports, including email ports. Now their app gets timeouts left and right and the obvious thing to do in that case seems to be to go and file the 1000th bug ticket in Github with the same &quot;works on my developer machine, but not in the server&quot; subject.
评论 #31798400 未加载
davedx将近 3 年前
Counterpoint: you have a successful open source project and you even “branded and marketed” it (like Grafana). You obviously want it to be successful? Then <i>listen to your users and respond to their questions</i>.<p>Entitlement is a two way street.
评论 #31798289 未加载
评论 #31798328 未加载
评论 #31798545 未加载
评论 #31799019 未加载
lmeyerov将近 3 年前
As a maintainer of a graph OSS project with an optional commercial tier, we are 100% fine with his original approach.<p>A clearly written issue or a +1 vote (not comment, which causes an alert) is definitely appreciated. We get to learn usage patterns to optimize, bugs to fix, etc, before they hit users in our paid tiers. Sometimes feedback isn&#x27;t well thought out, so we added templates to steer users, and that worked pretty well. Various tricks like that have helped over time.<p>Likewise, when there is a commercial tier or outside funding, as in his case of Grafana, <i>much</i> less expectation of code giveback. Typically the maintainers have blown the path to open governance, and through that, significant OSS community It&#x27;s freemium, and the interactions are more about issues vs PRs. Yes it&#x27;s better when a true OSS community, not just license, but that&#x27;s just not how most big ones work nowadays. So a helpful ticket is fine.
评论 #31799781 未加载
bsder将近 3 年前
I kinda blame Github for all this.<p>In the past, there was just a bit of friction before filing a bug or dropping a comment on a project.<p>You had to sign up for bugzilla. You had to sign up for the mailing list. Something. Anything.<p>It was just enough friction that you had to <i>want</i> to post that comment or file that bug. You weren&#x27;t going to waste your time just to be a shit.<p>With everything on Github, it&#x27;s simply too easy to quickly slap a thoughtless comment on a project (guilty as charged--sadly).<p>I know that if I were releasing a project today, I would make sure to use anything other than Github.
评论 #31797905 未加载
评论 #31798841 未加载
评论 #31797925 未加载
评论 #31798417 未加载
tgsovlerkhgsel将近 3 年前
One pattern I&#x27;ve noticed that leads to low quality bug reports is that high quality bug reports take time, and bug reports, even if they&#x27;re high quality, are often ignored if they&#x27;re not an absolutely critical issue.<p>After spending an hour of time writing the perfect bug report a couple of times, and each time receiving no reward (= fix), often not even seeing a sign that anyone <i>looked</i> at the report, this gets incredibly frustrating, and creates a temptation to not put in the effort anymore.<p>Which results in low quality bug reports, which exacerbates the issue (makes work harder for the maintainers, makes bugs less likely to get looked at&#x2F;fixed, makes it more likely that the user encounters more such frustration).<p>I see the pattern, but I don&#x27;t have a solution. One thing I&#x27;ve started to do is filing an initial low-quality bug report and offering to follow up (and actually doing it) once anyone shows any amount of interest, but that still leaves a crappy and non-actionable bug report.
评论 #31803745 未加载
svrtknst将近 3 年前
Something I believe is overlooked that is relevant here is the effect of large volumes of feedback, even positive. Sara Chipps wrote about it in her blog post on Stack Overflow[1].<p>I don&#x27;t believe we as people are desgined to handle feedback and opinions from a large number of people, and it&#x27;s very easy for even neutral or benign questions (&quot;is this planned for a release?&quot;, &quot;any news on this?&quot;) to become grating.<p>Kinda similar to when kids go &quot;Mom, mom, mom, mom&quot; - nothing harmful is being said, but the cumulative effect is exhausting.<p>IMO it&#x27;s a good idea to question, has someone else asked this? has someone else already stated this opinion? before posting on forums.<p>1. <a href="https:&#x2F;&#x2F;stackoverflow.blog&#x2F;2019&#x2F;07&#x2F;18&#x2F;building-community-inclusivity-stack-overflow&#x2F;" rel="nofollow">https:&#x2F;&#x2F;stackoverflow.blog&#x2F;2019&#x2F;07&#x2F;18&#x2F;building-community-inc...</a>
badrabbit将近 3 年前
Don&#x27;t be entitled but at the same time nothing wrong with respectfully asking for support. User support is the whole point of maintainance. Replying to issues to add &quot;weight&quot; allows maintainers to prioritize fixes.
评论 #31798333 未加载
andresp将近 3 年前
For better or worse, open source software is competing with paid software, so expectations for basic support and maintenance need to exist. If there is not enough capacity for this, the maintainers should make it clear upfront in very visible ways so people can use that information when deciding what to use.
rwmj将近 3 年前
I&#x27;m an open source developer (and user of course), and I don&#x27;t like people acting entitled. However I don&#x27;t mind people commenting on bugs that they&#x27;re also have the bug, because it gives some indication about which bugs are affecting lots of people and which are rare. I also have a rule of thumb that for every user who comments on a bug, probably another 9 are affected.<p>Also please file bug reports that I have some hope of reproducing locally, or if not, include all the information you have, such as the full commands and errors, the versions of everything that might be relevant etc.
pydry将近 3 年前
I see this almost as a technical problem.<p>Developers want polite, clear, obvious, deduplicated, fully fleshed out bug reports. They want to hear the praise but dont want the shit talk.<p>Users want somebody to talk to who can help fix their problem and to lobby for their pet feature requests. They generally dont know what to file under bug or support request.<p>A system with a different UI for both that could be intermediated by some low-time-investment support roles filled by enthusiastic power users would help immensely.
gumby将近 3 年前
&gt; …I was one of those open source users who had service expectations despite never paying for anything.<p>Brian Fox had a default reply for these messages back in the early 90s: “Please return bash for a full refund”.
encryptluks2将近 3 年前
I can partially agree but we live in a day and age where asking someone their name may be considered offensive. I think there is a lot more value in teaching people self-worth and to not be so easily offended by people asking questions and then they run sway and hide and say that you hurt their feelings by asking them.<p>A simple disclaimer that says they don&#x27;t have any obligation, or heck most open source licenses indicate that. Who cares it people +1 something. If open source developers want to focus on perfecting their code to be a haiku there is nothing wrong with that.<p>However, if they don&#x27;t get around to implementing important features or merging PRs then they shouldn&#x27;t be surprised nor offended when people abandon their projects either.<p>Sometimes people can be demanding and rude, but the key to get anything accomplished is learning how to interact and deal with people. If you can&#x27;t handle people asking questions or +1 or +2&#x27;ing your public GitHub issues then you&#x27;re probably not cut out for software development even as someone who is an unpaid open source contributor.
评论 #31797724 未加载
deepsun将近 3 年前
&gt; While some open source projects are created by large companies in a structured and planned way I think it is fair to say that most grow organically.<p>&gt; Coming back to the Grafana example, I was one of those open source users<p>Well, Grafana is definitely a large company. They recently devoured Prometheus community, that was really open source before.
layer8将近 3 年前
I see this a bit more nuanced. On the one hand I believe it’s important that users communicate what they’d like the software to be, and also when they are frustrated about a lack of progress, but on the other hand they shouldn’t act like entitled assholes about it and&#x2F;or constantly complain about the same thing over and over again. It’s possible to express dissatisfaction with the software while still being respectful towards the maintainers. And the number of “me too”s (+1) can be useful information.<p>With regard to time and attention, that’s more a matter of tooling and push vs. pull. As a maintainer, I’m responsible to not let my time and attention be strained too much, just as with any other communication. For example, by auto-filtering issue tracker notifications into a dedicated folder and only looking into it at scheduled, time-boxed intervals.
eCa将近 3 年前
&gt; As time went on the wording of the +1s got stronger<p>I think a +1 (as a thumbs up reaction, or similar) can’t be a bad thing. Comments that turn more passive&#x2F;agressive (or just agressive) most certainly can. I don’t think the later should be mixed up with the former.
评论 #31797879 未加载
评论 #31797880 未加载
vegetablepotpie将近 3 年前
Reminds me of the wiring pi debacle. Gordon got tired of supporting novice users for free and stopped publishing updates to his project in 2019.<p>&gt; I’ve had over 10,000 emails from people who upgraded their Pi and found that code stopped working because they were reliant on a system, which had statically linked an older version. This sheer incompetence on their part has saddened and depressed me hugely.<p><a href="https:&#x2F;&#x2F;www.i-programmer.info&#x2F;news&#x2F;136-open-source&#x2F;13036-wiring-pi-deprecated.html" rel="nofollow">https:&#x2F;&#x2F;www.i-programmer.info&#x2F;news&#x2F;136-open-source&#x2F;13036-wir...</a>
kazinator将近 3 年前
Here is the main problem, highlighted by this comment, from user itmecho:<p>&gt; I&#x27;m subscribed to it because I want to know when it gets implemented, not because I want to know every time someone else wants it implemented.<p>&gt; I&#x27;m now unsubscribing because I&#x27;m finally fed up of the +1 emails so I&#x27;ll have to manually check this issue periodically instead. All because people can&#x27;t just put a reaction on the initial message<p>Maybe Github should a conditionally shown dialog box which says: &quot;your comment will generate a notification seen by 150 watchers; do you want to proceed?&quot;
评论 #31802037 未加载
jmull将近 3 年前
My general advice on this is to never rely on other people reading your mind. It&#x27;s a path to frustration for you and the other people.<p>In this article I see a lot of phrases where OP is hoping other people share the same perspective. Like, &quot;Hopefully we agree that...&quot;, &quot;I want to argue here...&quot;, &quot;Users... shouldn’t expect...&quot;<p>It&#x27;s just not going to happen like that automatically, though.<p>I suggest that if, as an open source author, you&#x27;re seeing seeing potential for broad usage of your project, spend some time to think about what you&#x27;re willing (and able) to give, and make an explicit statement to that effect (and put it somewhere that potential new users will see it).<p>I suggest that if you&#x27;re considering using an open source project in something, spend a few minutes to think about what you will do if you get no more support than what is explicitly promised and&#x2F;or paid for (which means no support in most cases). If that&#x27;s not acceptable for your project, then don&#x27;t use it.<p>(Oh, and sadly, I think this the purpose of this article is a bit hopeless. I think there are thoughtful people that will read this and take it to heart, but those people are probably only causing a tiny fraction of the unpleasantness that open source maintainers experience.)
评论 #31803071 未加载
gigatexal将近 3 年前
If you don’t pay for something and that something is written by a volunteer and shared for free then sit down and shut up and wait for that volunteer to maybe get to your feature request. One can always propose a PR implementing that feature. Or wait.<p>Even more egregious is if you’re a company making money on this free software and yelling about a missing feature and not willing to sponsor its development then you’re even further behind in the line.
pella将近 3 年前
the other part: <a href="https:&#x2F;&#x2F;polite.technology&#x2F;preview" rel="nofollow">https:&#x2F;&#x2F;polite.technology&#x2F;preview</a>
lifeisstillgood将近 3 年前
Just a thought (vaguely connected here) but voting on features to be implemented is ... pretty much same as voting IRL on policies not parties.<p>I have often wondered what would be the thing to trigger companies to stop being totalitarian dictatorships and become democratic to their (employees &#x2F; stakeholders) - is it crazy to say voting on features to build would be the one?
评论 #31798789 未加载
评论 #31797762 未加载
cube00将近 3 年前
<i>&gt; I also occasionally returned to issues that hadn’t been resolved to [..] ask if there was an ETA on a fix. I felt I was being helpful.</i><p>I irrationally get annoyed when someone asks for an ETA like this, I&#x27;m sure it&#x27;s a genuine question but it just feels like a nag to &quot;hurry the fork up already!&quot;
评论 #31810626 未加载
witcher将近 3 年前
Amazing write up! Something I would add as open source maintainer:<p>* Feedback is needed. After years I built up a filter to annoying users, and I would simply ignore their feedback, but +1 and mentioning the feature would be useful is invaluable (and why you cannot use workarounds). Please do that in a nice, productive way (:<p>* It might be that the feature you and others are asking for was in paid version of the project, thus maintainers actively ignored it. Not the healthiest thing to do, but this happens, business matters, especially if governance is poor (single vendor behind the project).<p>* I think it would be useful to mention that if it&#x27;s just a work needed and not other blocker, anyone would be welcome to create PR for the needed feature or at least moving it forward 10%. Sometimes faster that motivating your rights in issues (:
jacobtomlinson将近 3 年前
Hey HN folks! Author of the post here, wow I didn’t expect this to make the front page. It’s really fun to see all the discussion here around this topic. I’d originally written this post to just have something up my sleeve to send to folks who were being unkind to open source maintainers. I’m enjoying seeing some of the counter arguments too.<p>The general intent of this post is to try and communicate to folks that if you consume open source software the authors of that software don’t owe you anything. However they all contribute for a reason, whether that is personal enjoyment, presence in the market, user testing, etc. They are excited to have folks use their software and they definitely want to hear from you. But it’s important to remember that this isn’t a commercial arrangement like when you buy Photoshop. So if you want to interact with a maintainer remember to be kind and respectful (you probably should be with all humans anyway). It is up to them where they focus their effort, and if they have a choice between interacting with nice folks or rude folks who do you think they will choose?<p>I also regularly see folks being rude on the most important issues, which results in maintainers avoiding them and even more folks being rude. It can snowball into having things that are critical to the community becoming a low priority to the maintainers.<p>TLDR; Be kind to folks who give you things for free.
einpoklum将近 3 年前
&gt; What I didn’t consider was that my interactions were taking time&#x2F;attention&#x2F;resources&#x2F;patience from the project. User support is a cost.<p>A lot of it - especially what OP mentioned - is an _investment_ in the project: Bug reports and feature requests are important input for developers, and often even save them more time than they take away.<p>&gt; Lastly you always have the option to fork the project.<p>Mostly not. I mean, a fork for creating a merge request, sure, but maintaining a fork is either impossible or overly costly in the large majority of cases AFAICT.
YmiYugy将近 3 年前
Rude and entitled behavior is of course unacceptable. That said I think the project developers and maintainers often share a large portion of the blame. Most projects are very keen on telling you about their amazing new features and the awesome stuff you can build with it. What they don&#x27;t do is properly document limitations of their software or honest comparisons with competing solutions. Additionally many developers overhype the status of their project. They&#x27;ll call it production ready, mature, claim it has a vibrant community and ecosystem and so on, when these things really bend the truth. That builds expectations and running into critical, well known bugs that don&#x27;t get fixed can be extremely frustrating.
评论 #31800247 未加载
tbwriting将近 3 年前
Wrote about this several months ago, and specifically the vastly larger scale on which corporations do it: <a href="https:&#x2F;&#x2F;tylerberbert.substack.com&#x2F;p&#x2F;cooperation" rel="nofollow">https:&#x2F;&#x2F;tylerberbert.substack.com&#x2F;p&#x2F;cooperation</a>
fellellor将近 3 年前
Reading all this, I realise it’s very hard not to piss people off on the Internet. Mostly avoidable by not coming off as entitled, and being patient.<p>… to be honest, I never thought the +1 emoji would make someone mad.
a-dub将近 3 年前
this is all true. and yes, one should never be rude and one should always be respectful of others&#x27; time and efforts.<p>but there is indeed another side to the equation: software does not succeed in a vacuum. it is a symbiosis between users and developers that make software great. a software package gains momentum because users invest time and effort into making use of it or building on it. these investments are nontrivial! the maintainers enjoy notoriety and potential financial benefits (sometimes massive) as a result of this notoriety.<p>so while yeah, entitled attitudes on oss issue trackers are pretty odious, so are illusions that all open source software is built upon a world of altruism. there&#x27;s money involved, and sometimes quite a lot of it.<p>that said, we do need better funding models. one thing that open source does teach us is that some people do their best work outside of a classic corporate structure. some of that best work is literally the best work in software. the problem with funding is that it typically comes with hooks which then drive the projects towards what you see coming out of most corporate environments, so the challenge is to figure out how to fund open source software in a way that doesn&#x27;t actually influence or drive its design.
ocdtrekkie将近 3 年前
One thing I&#x27;ve done from time to time is just say &quot;hey, I would like this a lot, I&#x27;d put a $100 bounty on it&quot;. Probably wouldn&#x27;t work in the corporate case described here, and certainly is below the &quot;actually paying for a developer&#x27;s time&quot; level.<p>But I&#x27;ve thrown a bonus in there for doing it. Maybe if it&#x27;s already something they wanted to do, it moves the needle into &quot;sure, let me give it a shot&quot;.
paulcarroty将近 3 年前
I like &quot;business first&quot; approach: <a href="https:&#x2F;&#x2F;drewdevault.com&#x2F;2021&#x2F;03&#x2F;03&#x2F;To-make-money-in-FOSS-build-a-business.html" rel="nofollow">https:&#x2F;&#x2F;drewdevault.com&#x2F;2021&#x2F;03&#x2F;03&#x2F;To-make-money-in-FOSS-bui...</a><p>Yeah, it can be very hard depending on the case, at least some premium features&#x2F;merch&#x2F;books&#x2F;guides should be used to keep an open source project alive.
mproud将近 3 年前
I think the wrong message is getting made.<p>The takeaway I am getting is: don’t interact or communicate with open source projects you use.
floor_将近 3 年前
I feel like this is the end result of giving away hard work for free when it should have been charge for all along. When you give your work no value, people will perceive no value in your work.
Zenzengele将近 3 年前
Grafana is a bad example.<p>They switched to agpl and pushing companies in paying for it.<p>Which is okay of course but grafana labs is no longer a free open source project.<p>Of course potentially feature request might come in by key account manager or other hidden business agreements but I myself still comment on the opensource front like GitHub issues.<p>When my company now pays money for it, my expectation definitely changes.
评论 #31798631 未加载
评论 #31797910 未加载
WesolyKubeczek将近 3 年前
I feel like there is a lot of articles lately that call for empathy towards oh so ever poor and overworked and burned out maintainers. All true, but this is only half of an issue.<p>The issue is that the concept often brandished in those articles, empathy, is a two-way street. There are maintainers on one side of this, and there are, on the other hand, users, who often are integrating multiple software projects and products to produce a solution of some kind. Mind you, those users are not always entitled prima donnas at FAANGs making another service to track you or something inconsequential like an online game. Sometimes they are integrating stuff at your local ISP. Or it&#x27;s some system at a local school. Or they are making systems that are just means to an end, like in a hospital, or a bakery, or whatnot. Or it&#x27;s an automotive shop. You get the idea; the world doesn&#x27;t run on cat pics alone, and sometimes a complex software system is just an ingredient.<p>And you know what? When integrating all this stuff, you end up not with that small insignificant bug in that one project, but with multiple bugs in many pieces of software that have all to work together and be reliable. You also deal with not so much bugs per se as impedance mismatches that you have to paper over. It really ends up bleeding from a thousand cuts.<p>&quot;Fix it yourself&quot; is possible, but it doesn&#x27;t scale. Upstream doing it scales.<p>And before you tell me, &quot;well if you&#x27;re so upset then don&#x27;t use it&quot;, or &quot;nobody owes you anything so fuck you&quot;, I have to say that it works the other way too.<p>I get a feeling that many open source software maintainers get into this business because they think that either a big company is going to pay them dearly, or their résumé will be stellar, or that they will become rockstars and get all the bitches from it. And when harsh reality sinks in, they start writing about being overworked and burned out. Not every maintainer does it, but many do, or at least it looks like it.<p>And if you get burned out and whatnot, you have an option to just stop working on stuff that is deteriorating your health. Walk away. If a popular project is hinging on an unhealthy development model and is going to die if you walk away, so be it! The market will cope, believe you me. The community will find a way around it. What is not good, though, is if you, the maintainer, are burned out, or overworked, but stubbornly insist on being a bottleneck in the project under your inept stewardship nevertheless, and just whine and moan about your burnout to get internet points and worldwide pity.
评论 #31799364 未加载
rurban将近 3 年前
Looks more like the new US youngsters becoming more like brainwashed Chinese or Russian apostates, who need to make public apologies before being allowed into society again. mea culpa, mea maxima culpa. What&#x27;s wrong with you? Seriously.<p>There&#x27;s nothing wrong in these tickets to apologize for. Issues are for public discussions of issues. If maintainers cannot deal with public issues, they cannot be maintainers. Problems don&#x27;t come with silverspoons, And this case there were not even problems at all.
评论 #31798791 未加载
评论 #31799058 未加载