6 ms·

> useless code of conduct #Code of Conduct This is not a community project. This is my project. I know that will disappoint some people, but I do this for f

> useless code of conduct #Code of Conduct This is not a community project. This is my project. I know that will disappoint some people, but I do this for fun in my own spare time. If it stops being fun, I will stop working on it, which will pretty much kill the project. There are millions of projects in the world and the only reason they continue (if they actually do) is because the maintainers stubbornly stick at it. With that in mind, here is the code of conduct: If it is fun for me then it is good. If it is not fun for me, then it is not good. Things I find fun include: Bug reports that explain what you saw and what you expected to see. Suggestions for features that would make your life better. Stories of how the software so far has already made your life better. Entertaining stories of how you used the software (bonus points if it includes pictures of cats). Offers to volunteer to improve something (super bonus points if you actually improve it). Questions about how the software works. Offers to write documentation (super, executive class bonus points if you actually write some). Answering questions that other people ask (bonus points if you get the answers right). Things I don't find fun: Drama. That is all. To some extent, I will accept drama in exchange for money. But it has to be a lot of money. Think FANG level money. If you don't have FANG level money that you are willing to give me in exchange for drama, just don't do it -- even if you think it is the most important thing in the world. There is no other code of conduct. I may arbitrarily declare some things fun for me and some things not fun. Please pay attention when I declare one way or the other and act accordingly. Thank you.

qaq 8y ago
Are you OK with other people using this ? This looks to be the perfect #Code of Conduct
- mikekchar 8y ago
  Feel free :-) I warn you that the only way I had the courage to write it was that I drank a considerable amount of nihonshu (Japanese sake). It was pink. The label said that the pink colour was a natural result of the kouji (aspergillus oryzae). I'm skeptical :-) But, in all seriousness, I've been thinking about it a lot and really the main thing, I think, is for everyone (even the maintainer) to avoid drama. If you find yourself in a dramatic situation that seems to have been caused by your actions, simply apologise for the drama that you have unintentionally invoked. I think that's all that is necessary.
  - hartator 8y ago
    You just got another project to maintain. :)
  - qaq 8y ago
    Thank you! I think if you put this code of conduct in it's own repo you'll get thousands of stars :)
  - meruru 8y ago
    You should definitely host this document somewhere.
    - gnomewascool 8y ago
      Well, if you find it sufficiently fun. :)
aboutruby 8y ago
# Code of Conduct This is a dictatorship, I do what I want. Thanks.
- blattimwind 8y ago
  This is my .git, there are many like it, but this one is mine.
hypfer 8y ago
I will adopt this as soon as someone tries to force me to add a CoC to one of my projects. Thank you
silvestrov 8y ago
Things I don't find fun: Drama and entitlement. You are not entitled to other people implementing whatever features you want.
GorgeRonde 8y ago
> This is my project Ownership is essentially the main problem of OSS here. > If it stops being fun, I will stop working on it, which will pretty much kill the project. See what I mean ? Makes me think of Hickey's "Open source is not about you" rant and I can't prevent myself from hearing "It's about me". https://news.ycombinator.com/item?id=18538123 https://news.ycombinator.com/item?id=18538123
- bhaak 8y ago
  It doesn't need to be about me. But if it isn't about me, somebody else has to do the project management and the code commits. That's just the way it is. When OSS goes further than the "my itch to scratch" scenario, it gets complicated and there needs to be a way to motivate people to scratch other people's itches.
  - deleted 8y ago
    [deleted]
- blihp 8y ago
  I don't see a problem: any given author / contributor has their own reasons for providing something... and you and I are most likely not one of them. We can choose to tag along for the ride or not. If it is of value and we have issues or need missing features, we can contribute to the project to make it better. For many people, that is often one of the reasons they even bothered to open source it to begin with: to get help. If one lacks the skills to or time & interest in helping, the two most productive courses of action are either to move along or throw money at the problem. Now maybe your issue is the developer/maintainer themselves. i.e. the project has value but you don't want to deal with the author(s)/maintainer(s). That's fine: fork the project. If enough people feel like you do, the original project will likely die due to these open source 'market' forces. That's a risk any author takes making the project open source to begin with. I have absolutely no problem with a developer saying 'this is my project' or 'I'm not interested in your problem' as a default answer. It is their project/time and my problem after all. Assuming I don't have the time/skills and really want their help, I can offer to throw money at them and many will develop an interest in solving my problem. If that doesn't work, I can offer to throw money at someone who will. Note that none of these issues are unique to open source: try to get Apple/Microsoft/Google to fix a longstanding bug or add a feature that you really want or need. Odds are, you don't have the order of magnitude of money to get them to care. And you usually don't have the source either, so you're out of luck.
legel 8y ago
This is cool and valuable. FANG or FAANG seems like an unproductive reference though. https://en.wikipedia.org/wiki/Facebook,_Apple,_Amazon,_Netflix_and_Google https://en.wikipedia.org/wiki/Facebook,_Apple,_Amazon,_Netfl... If you're not representing one of these companies, you feel excluded. If you are, you don't want to be represented by the word FAANG.
- protomyth 8y ago
  Think FANG level money. If you don't have FANG level money that you are willing to give me in exchange for drama, just don't do it -- even if you think it is the most important thing in the world. The poster is talking about a level of money, not the exact companies. The whole point of the line is that you should feel excluded from bringing drama if you don't have that level of money to give the developer.
meruru 8y ago
It's perfect.
scottlocklin 8y ago
A great CoC. I cooked one up myself after too much wine and reading of other smarmy CoCs written by the kinds of church lady busy bodies who ruin everything. https://github.com/locklin/iron-sheik-code-conduct https://github.com/locklin/iron-sheik-code-conduct It's mostly a drunken walk through Sheiky's twitter, but I'm sorely tempted to include it in a few R packages I'll eventually release.

qaq 8y ago

Are you OK with other people using this ? This looks to be the perfect #Code of Conduct

mikekchar 8y ago
Feel free :-) I warn you that the only way I had the courage to write it was that I drank a considerable amount of nihonshu (Japanese sake). It was pink. The label said that the pink colour was a natural result of the kouji (aspergillus oryzae). I'm skeptical :-) But, in all seriousness, I've been thinking about it a lot and really the main thing, I think, is for everyone (even the maintainer) to avoid drama. If you find yourself in a dramatic situation that seems to have been caused by your actions, simply apologise for the drama that you have unintentionally invoked. I think that's all that is necessary.
- hartator 8y ago
  You just got another project to maintain. :)
- qaq 8y ago
  Thank you! I think if you put this code of conduct in it's own repo you'll get thousands of stars :)
- meruru 8y ago
  You should definitely host this document somewhere.
  - gnomewascool 8y ago
    Well, if you find it sufficiently fun. :)

aboutruby 8y ago

# Code of Conduct This is a dictatorship, I do what I want. Thanks.

blattimwind 8y ago
This is my .git, there are many like it, but this one is mine.

hypfer 8y ago

I will adopt this as soon as someone tries to force me to add a CoC to one of my projects. Thank you

silvestrov 8y ago

Things I don't find fun: Drama and entitlement. You are not entitled to other people implementing whatever features you want.

GorgeRonde 8y ago

> This is my project Ownership is essentially the main problem of OSS here. > If it stops being fun, I will stop working on it, which will pretty much kill the project. See what I mean ? Makes me think of Hickey's "Open source is not about you" rant and I can't prevent myself from hearing "It's about me". https://news.ycombinator.com/item?id=18538123 https://news.ycombinator.com/item?id=18538123

bhaak 8y ago
It doesn't need to be about me. But if it isn't about me, somebody else has to do the project management and the code commits. That's just the way it is. When OSS goes further than the "my itch to scratch" scenario, it gets complicated and there needs to be a way to motivate people to scratch other people's itches.
- deleted 8y ago
  [deleted]
blihp 8y ago
I don't see a problem: any given author / contributor has their own reasons for providing something... and you and I are most likely not one of them. We can choose to tag along for the ride or not. If it is of value and we have issues or need missing features, we can contribute to the project to make it better. For many people, that is often one of the reasons they even bothered to open source it to begin with: to get help. If one lacks the skills to or time & interest in helping, the two most productive courses of action are either to move along or throw money at the problem. Now maybe your issue is the developer/maintainer themselves. i.e. the project has value but you don't want to deal with the author(s)/maintainer(s). That's fine: fork the project. If enough people feel like you do, the original project will likely die due to these open source 'market' forces. That's a risk any author takes making the project open source to begin with. I have absolutely no problem with a developer saying 'this is my project' or 'I'm not interested in your problem' as a default answer. It is their project/time and my problem after all. Assuming I don't have the time/skills and really want their help, I can offer to throw money at them and many will develop an interest in solving my problem. If that doesn't work, I can offer to throw money at someone who will. Note that none of these issues are unique to open source: try to get Apple/Microsoft/Google to fix a longstanding bug or add a feature that you really want or need. Odds are, you don't have the order of magnitude of money to get them to care. And you usually don't have the source either, so you're out of luck.

legel 8y ago

This is cool and valuable. FANG or FAANG seems like an unproductive reference though. https://en.wikipedia.org/wiki/Facebook,_Apple,_Amazon,_Netflix_and_Google https://en.wikipedia.org/wiki/Facebook,_Apple,_Amazon,_Netfl... If you're not representing one of these companies, you feel excluded. If you are, you don't want to be represented by the word FAANG.

protomyth 8y ago
Think FANG level money. If you don't have FANG level money that you are willing to give me in exchange for drama, just don't do it -- even if you think it is the most important thing in the world. The poster is talking about a level of money, not the exact companies. The whole point of the line is that you should feel excluded from bringing drama if you don't have that level of money to give the developer.

meruru 8y ago

It's perfect.

scottlocklin 8y ago

A great CoC. I cooked one up myself after too much wine and reading of other smarmy CoCs written by the kinds of church lady busy bodies who ruin everything. https://github.com/locklin/iron-sheik-code-conduct https://github.com/locklin/iron-sheik-code-conduct It's mostly a drunken walk through Sheiky's twitter, but I'm sorely tempted to include it in a few R packages I'll eventually release.