3 ms·
This has not been my experience. I maintain various popular and not-so-popular projects (although maybe not to the level of gnome calendar) and I just work as m
by StavrosK 8y ago
This has not been my experience. I maintain various popular and not-so-popular projects (although maybe not to the level of gnome calendar) and I just work as much as I want. If I don't feel like handling an issue right then, I say I won't have time soon and that PRs are appreciated.
The vast majority of people are understanding, I don't remember anyone making a fuss about it.
- siwatanejo 8y agoMaybe because the consumers of your work are developers? GNOME Calendar (the OP's project) is an app for end users.
- deleted 8y ago[deleted]
- StavrosK 8y agoPossibly, but not all of them are. This isn't, for example: https://github.com/skorokithakis/catt https://github.com/skorokithakis/catt And at most we got a few users asking about why they couldn't install it on 2. Maybe my users are just better-behaved.
- siwatanejo 8y agoSorry, but any command-line tool is going to be used by advanced computer users, not normies. (If you reply to this that GNOME is not for normies either, or Linux in general, I'll reply 'touche' though.)
- ozim 8y agoWhy would you imply that "normies" are worse than "techies"? Just look at some places where you get couple of guys that think they are next Linus Torvalds. Other thing to search for, are holy crusaders for something like tabs or spaces. Where I would say real "normies" would not care and be "oh it just does not work, meh". There is probably the same amount of crazy people that would go full length to find you to fix their problem and do it for free.
- acdha 8y agoDevelopers tend to be worse in my experience. I picked up maintaining a few projects awhile back (django-haystack, pysolr) which are in that unfortunate position of having been popular enough to get used a lot but never getting much corporate support. The issue trackers regularly get requests which are important to someone’s business but not enough to actually do any work. Sometimes that gets as far as a pull request but that much less commonly gets to the point of passing tests or support for more of the support matrix than they need, although that often doesn’t rule out requests to just merge it anyway.
- zimbatm 8y agoDo you ever have a problem saying no to people? Some times I am wrangling internally and that has an emotional cost. I find that being super crystal clear on where I stand is absolutely necessary to be able to say no.
- karussell 8y agoYes, exactly. Saying 'no' is a very important skill you should have. Of course you can learn it too (like I did :)) Also it is very important to reverse the emotional costs. I mean, usually people come to your repo and demand/ask for a feature. Instead of feeling overwhelmed from this request, say that you welcome contributions and without this this feature won't happen and the feature request will be closed (after 1/2 a year). Or if it is a bug report, ask for a reproduce with the latest master and so on ... so: try to reverse the demand to offload your maintaining work if it is no longer fun to you :)
- StavrosK 8y agoI usually say something like "I find this very useful and will work on it", "I think this is good but will probably not have time, so feel free to issue a PR for me to review if you want it", "I will accept a PR but not really expend effort to make this myself", or "I will not accept PRs for this as I don't think it's in scope, but feel free to import my library into your extension if you want".
- fourthark 8y agoIt's often hard to tell the difference between doing this honestly, and just stonewalling. Even when I'm completely honest about it and would like to see the fix happen, there is a level of my mind where I'm all, "great, now they won't respond and I can forget about this."
- StavrosK 8y agoI never have a problem saying no. I have a problem saying no in a way that will make the other person happy, but I'm working on it and I think I manage well enough lately, but the "no" gets said regardless. It's a very important skill, as people are donating their time to helping you out, even if they're complaining about something. Especially for collaborators, I want them to feel like I listened to them and that I have concrete reasons for rejecting their proposal, even if the reason is "I don't believe this is in scope for this project, but maybe it could be implemented a layer above or as a plug-in". You aren't doing anyone any favors if you say yes to everything.
- grigjd3 8y agoI think the worst experiences are always what stands out in peoples' minds.