31 ms·
> To be perfectly clear, this absolutely is applying pressure and being rude. I don't think so. The person was perfectly polite in my opinion. You don't owe a
by matheusmoreira 3y ago
> To be perfectly clear, this absolutely is applying pressure and being rude.
I don't think so. The person was perfectly polite in my opinion.
You don't owe anyone anything, they aren't paying you and it's absolutely fine to just drop everything and go do something else if you want. However, the people using your project will want to know what's up so they can deal with the consequences. They find out what's up by asking perfectly reasonable questions like the ones in the first screenshot. It's simple to provide a sincere answer to all of those questions. No response is also a valid and clear answer, there's no actual pressure to respond either. The point is it's not rude to ask.
As a free software developer and user, when I ask such questions it's because I'm wondering whether I should fork the project or try to work with the maintainer. I've sent patches to projects, most recently cosmopolitan libc, because I knew the developers were actively maintaining the project. I've forked the pug/jade templating language into my own static site generator tool because the maintainer seemed to have moved on, I went there and asked just to confirm before I did so. I don't think there's anything rude or pressuring about it. We're just trying to decide what to do with our own time. Our decisions depend on your decisions and therefore we ask.
It gets rude when people start subtly shaming you for not working on things. That's absolutely unacceptable but I don't think that happened in the first screen shot which was just polite questions.
- rgoulter 3y ago> It gets rude when people start subtly shaming you for not working on things. Seems like OP perceived shame by being asked this, though. -- Why would anyone ask "what's the status of this project?" (or however politely you want to phrase it) if the project were clearly being maintained? There's at least a meta-message of "you're not working on this enough", even without otherwise being hostile/rude. I'm reminded of the "ask vs guess culture" differences. But as you say, users aren't owed reliability. Perhaps a better interaction would have been "Is this dead?" "I haven't been working on it. I hope to work on it soon, though. But, I would rather not have to deal with PRs from others". Still, I think it'd be better if people didn't have to walk on eggshells when making interactions; and to reserve accusations of rudeness for more overt or persistent badgering.
- matheusmoreira 3y ago> There's at least a meta-message of "you're not working on this enough", even without otherwise being hostile/rude. There's many implied messages in everything we say and do. The action of not working on something sends a clear message and communicates a lot of information: you're doing something else with your time. The "you're not working on this" message will be received and understood by others because the repository is public and anyone can see the activity. It's just a statement of fact. The "not working on this enough" message is definitely insulting because it implies obligation but I didn't receive that message in this case. Maybe it's just me. What that action doesn't communicate though is intent. Perhaps the developer intends to work on it but hasn't been able to because life happens. Perhaps they're just sick of the project and want out which is also absolutely fine. I think the questions were just attempting to clarify the intent. Another message that I felt was overlooked and led to my comment: "I care enough about this project to ask about its future". People ignore things they don't care about, it's like it doesn't even exist. Even hate could be preferable to oblivion. > I think it'd be better if people didn't have to walk on eggshells when making interactions I agree. People are extremely hard.