You must log in or # to comment.
I swear, i have read some issues…
So, i sometimes help people who have problems with an android CLI launcher
There is a fucking command called, “help” and when you open the launcher one of the first thing you see is “write help to get a command list”, you write help and you get a list of all commands and there is even a wiki (not complete though) that explain some commands and they STILL ASK “can you add [command that already exist]?”.
So i kinda feel why some people want a skill issue tagI’d say “sure!” Then amaze them with how good and quick I am by telling them an hour or two later to "try it now "
What you describe sounds more like a “competence” issue than a skill issue - can’t have the latter without first having the former.
That way you teach them that
- you are somehow a magician
- they can ask for any stupid thing and you will do it right away for them because what else should you be doing
- it doesn’t matter if this feature even fits into your plans because all you want to do is grant every wish
- a new feature is written and will appear instantly at the users computer. Who cares about testing or of this breaks other features as long as this guy is happy
They are beginner devs, so they should learn to understand how things work.
That’s a very smart way to go about it, and way more positive!
You don’t even need to upgrade to try this new code! Just type…
i’m a classicaly trained IT guy, I still call them “Layer 8 issue”
I don’t work on networking but I’ll be adopting this from now on. https://en.wikipedia.org/wiki/Layer_8
Layer 0 is design.
…
Layer 8 is policy.
Layer 9 is user.
No, user and (derivatives of) have always unofficially, jokingly been layer 8. Also higher layers would refer to design issues (budget/politics/design - 9/10), not layer 0.
Open source is free, but empathy is still a good feature.
I’ve seen this on a few repos and it never came across too harsh, the posts tagged with it were deserving. Wish I’d noted the repo names…
I’m fine with it tbh. FOSS devs need to squeeze every bit of enjoyment out of working on the project to keep motivated. If they (or mods) can drop a helpful reply and close an issue as ‘skill issue’ and get a little chuckle while they give their time for free answering poorly-written queries or bad bug reports then that’s a reasonable trade to keep them from burning out.
Skill issue can easily be made positive if you provide the information to acquire the skill.
Whats with the whole obessesion on “giving their time for free”? What does money have to do with this? It always comes across as a copout, implying you cant disagree with FOSS devs because they work for free. Just because they aren’t earning money off off of it (aside from donations) doesnt mean they aren’t earning some sort of reward for their work, whether its personal or social.
Besides that, its pretty common to include that type of work on a resume, which is sort of turning that work into future earnings if it helps you get a high paying job.
I appreciate what FOSS devs do, I just hear this victim narrative come up a lot in posts about them. I’m not even sure its FOSS devs posting that type of stuff on here, it might be other people defending them.
Who said they were victims? I said I don’t see any harm in devs being mildly abrasive as long as it helps keep their passion for the project alive.
How many projects do you pursue in your free time for no compensation that benefit strangers all over the world, whom can file complaints about your project, asking you to remedy or change it?
FOSS dev work is not a victim-generating machine, it’s just entirely misunderstood and underappreciated. They make a project for them, then they m0ake it free to all… and the code, and the support. But, you ask them what they dislike the most - it’s the support. The endless poorly-filled tickets, the duplicate tickets the submitter didn’t search for, the user errors that are explained clearly in the documentation. That part is thankless work. That burns people out. But if they use a joke tag on a support ticket when they close it, it’s suddenly “omg, devs are so rude”.
[…] include that type of work on a resume, which is sort of turning that work into future earnings if it helps you get a high paying job.
Ah yes, FOSS work should be its own reward because they can say they did it. Sort of like how interns should work for free at big companies ‘for experience’, and young artists/techs/small businesses should help influencers for free because they’re ‘working for exposure’. Now that attitude is a cop-out.
I think the way you frame it is absurd. They aren’t making things for themselves. If they were they wouldnt share it, or if they did they at least wouldnt maintain it or claim ownership over it. If devs open the door to allow outside help in, they really can’t act like they are victims when they have to socialize with other people.
The fact that you focus on compensation really shows what’s important to you anyways, and betrays the whole spirit of FOSS in my opinion.
^ See this is a great example of completely misunderstand FOSS. The vast majority are personal projects.
The whole point of making them open source is to share the software they’ve created for others to enjoy/use, and share the code for others to learn from or utilize in their own projects. Its not to “open the door to let outside help in” as though they’re the ones gaining from the arrangement, lol… the vast majority of FOSS code on npm for example has a single maintainer. Open Source Security Foundation discussing npm stats of almost 60% of all projects having a single maintainer, here: https://github.com/ossf/tac/issues/101
That you read my comments and focus on compensation, as though I haven’t spent 90% of the commentary on other aspects is weird. I’m done responding, but feel free to shout into the void.
Sounds like a skill issue on the dev’s part.
RTFM is not a valid response if the manual contain no information on what the software is or even how to run it (or where to even find the manual, if the manual even exists). Is this a standalone program? A plugin for another program I’m already using? No links to any useful information whatsoever.
Then the guy that sent me the original link tells me “oh yeah, all that info is on youtube”. Nope, I’m done. I’ll use something else.
Questions for you and your upvoters: when you were growing up, did you climb a lot of trees that were way too high for you or did they have fences to keep you away from them? Were you required to wear a helmet while riding a bike? Were you even allowed to bicycle anywhere on your own? Did you ever have to figure out how something works on your own, or has it always been your default response to give up when someone isn’t there spoon-feeding you the answers?
Climbed trees, rode without a helmet, and setup the home network without any documentation whatsoever. Been there, done that.
It’s not 2005 anymore. I have a job, a significant other, and other shit to do that’s more important than documenting someone else’s hobby.
