dweinberger / newclues

56 stars 19 forks source link

I suggest to use 'empathetic' in place of 'sympathetic' #2

Open itraor opened 9 years ago

dweinberger commented 9 years ago

Isaka,

Thanks for the pull request. I'm a github n00b, so please let me know if I'm misunderstanding it. (Also, please let me know if you got this email. Thanks.)

I appreciate the suggestion, but I want to stick with "sympathetic." For me "empathetic" raises the bar too high. I take sympathy as "feeling with" someone (which is the root meaning of the word) -- understanding, appreciating, and being moved by someone else's feelings and experience. Asking people to be empathetic -- to actually feel the feelings of others -- is more than is required (in my opinion) for us humans to live together well.

But -- and here's where my being bad at github becomes obvious -- I am likely to reject all pull requests because I view the New Clues as a publication, not a sw project. The New Clues are what we published on Jan.

  1. So, people should feel free to create forked versions, but I think I want to maintain the original published version without revisions.

Does that make sense?

Thanks for your help.

David

MY EMAIL ADDRESS HAS CHANGED: self@evident.com will cease to work soon. My new email address is david@weinberger.org.

On Sat, Jan 10, 2015 at 9:24 AM, Isaka Traore notifications@github.com wrote:


You can merge this Pull Request by running

git pull https://github.com/itraor/newclues master

Or view, comment on, or merge it at:

https://github.com/dweinberger/newclues/pull/2 Commit Summary

  • suggest to use 'empathetic' in place of 'sympathetic'

File Changes

Patch Links:

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2.

itraor commented 9 years ago

Hi David,

Yes I got this email correctly. Thanks a lot for your considerate words. I knew as much, New Clue #50 point caught my imagination a little more perhaps.

Your points make perfect sense, indeed raising the bar up to ‘empathy’ level might be asking too much in a general case. I can imagine there to be a much higher number of instances where one would rather not share part or any of the values expressed or embodied in some particular messages. In such instances, empathy would be out of order. In the same vein though, even sympathy could be a tall order if, for instance the message being furthered would be going against one's own set of values or interest - on a more personal level, that is.

The challenge I see is this: inside one's own tribe, one should have empathy, with regards to other tribes however, one might have sympathy. Clue #50 made me think about this, but I’ve certainly bundled the two aspects together into one.

On GitHub.

Indeed, by allowing people to submit pull request, you are inferring that suggestion of changes are welcome. That is how most would interpret it as well, it is a how folks have been nurturing collaboration around software project they wish to see wider adoption of. This rule could well apply to a publication like the New Clues, although you might be aiming for a wider consumption rather than a wider ownership. But, I am thinking that this is just a consequence of GitHub public repositories, not specifically your intention.

As users and contributors of GitHub, it is absolute fair game that suggestions get rejected. In fact, that’s more often the case than otherwise.

In any case, thanks for the chance of this conversation.

All the best, Isaka

On 10 Jan 2015, at 15:57, David Weinberger notifications@github.com wrote:

Isaka,

Thanks for the pull request. I'm a github n00b, so please let me know if I'm misunderstanding it. (Also, please let me know if you got this email. Thanks.)

I appreciate the suggestion, but I want to stick with "sympathetic." For me "empathetic" raises the bar too high. I take sympathy as "feeling with" someone (which is the root meaning of the word) -- understanding, appreciating, and being moved by someone else's feelings and experience. Asking people to be empathetic -- to actually feel the feelings of others -- is more than is required (in my opinion) for us humans to live together well.

But -- and here's where my being bad at github becomes obvious -- I am likely to reject all pull requests because I view the New Clues as a publication, not a sw project. The New Clues are what we published on Jan.

  1. So, people should feel free to create forked versions, but I think I want to maintain the original published version without revisions.

Does that make sense?

Thanks for your help.

David

MY EMAIL ADDRESS HAS CHANGED: self@evident.com will cease to work soon. My new email address is david@weinberger.org.

On Sat, Jan 10, 2015 at 9:24 AM, Isaka Traore notifications@github.com wrote:


You can merge this Pull Request by running

git pull https://github.com/itraor/newclues master

Or view, comment on, or merge it at:

https://github.com/dweinberger/newclues/pull/2 Commit Summary

  • suggest to use 'empathetic' in place of 'sympathetic'

File Changes

Patch Links:

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2.

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2#issuecomment-69458491.

dweinberger commented 9 years ago

Thanks!

Is there a way for me to turn off the ability to do pull requests, while still enabling branching/forking?

David

MY EMAIL ADDRESS HAS CHANGED: self@evident.com will cease to work soon. My new email address is david@weinberger.org.

On Sat, Jan 10, 2015 at 11:10 AM, Isaka Traore notifications@github.com wrote:

Hi David,

Yes I got this email correctly. Thanks a lot for your considerate words. I knew as much, New Clue #50 point caught my imagination a little more perhaps.

Your points make perfect sense, indeed raising the bar up to ‘empathy’ level might be asking too much in a general case. I can imagine there to be a much higher number of instances where one would rather not share part or any of the values expressed or embodied in some particular messages. In such instances, empathy would be out of order. In the same vein though, even sympathy could be a tall order if, for instance the message being furthered would be going against one's own set of values or interest - on a more personal level, that is.

The challenge I see is this: inside one's own tribe, one should have empathy, with regards to other tribes however, one might have sympathy. Clue #50 made me think about this, but I’ve certainly bundled the two aspects together into one.

On GitHub.

Indeed, by allowing people to submit pull request, you are inferring that suggestion of changes are welcome. That is how most would interpret it as well, it is a how folks have been nurturing collaboration around software project they wish to see wider adoption of. This rule could well apply to a publication like the New Clues, although you might be aiming for a wider consumption rather than a wider ownership. But, I am thinking that this is just a consequence of GitHub public repositories, not specifically your intention.

As users and contributors of GitHub, it is absolute fair game that suggestions get rejected. In fact, that’s more often the case than otherwise.

In any case, thanks for the chance of this conversation.

All the best, Isaka

On 10 Jan 2015, at 15:57, David Weinberger notifications@github.com wrote:

Isaka,

Thanks for the pull request. I'm a github n00b, so please let me know if I'm misunderstanding it. (Also, please let me know if you got this email. Thanks.)

I appreciate the suggestion, but I want to stick with "sympathetic." For me "empathetic" raises the bar too high. I take sympathy as "feeling with" someone (which is the root meaning of the word) -- understanding, appreciating, and being moved by someone else's feelings and experience. Asking people to be empathetic -- to actually feel the feelings of others -- is more than is required (in my opinion) for us humans to live together well.

But -- and here's where my being bad at github becomes obvious -- I am likely to reject all pull requests because I view the New Clues as a publication, not a sw project. The New Clues are what we published on Jan.

  1. So, people should feel free to create forked versions, but I think I want to maintain the original published version without revisions.

Does that make sense?

Thanks for your help.

David

MY EMAIL ADDRESS HAS CHANGED: self@evident.com will cease to work soon. My new email address is david@weinberger.org.

On Sat, Jan 10, 2015 at 9:24 AM, Isaka Traore notifications@github.com

wrote:


You can merge this Pull Request by running

git pull https://github.com/itraor/newclues master

Or view, comment on, or merge it at:

https://github.com/dweinberger/newclues/pull/2 Commit Summary

  • suggest to use 'empathetic' in place of 'sympathetic'

File Changes

Patch Links:

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2.

— Reply to this email directly or view it on GitHub < https://github.com/dweinberger/newclues/pull/2#issuecomment-69458491>.

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2#issuecomment-69460888.

itraor commented 9 years ago

As far as I know, and these changes change frequently, when you allow forking you can’t disable pull requests.

On 10 Jan 2015, at 17:19, David Weinberger notifications@github.com wrote:

Thanks!

Is there a way for me to turn off the ability to do pull requests, while still enabling branching/forking?

David

MY EMAIL ADDRESS HAS CHANGED: self@evident.com will cease to work soon. My new email address is david@weinberger.org.

On Sat, Jan 10, 2015 at 11:10 AM, Isaka Traore notifications@github.com wrote:

Hi David,

Yes I got this email correctly. Thanks a lot for your considerate words. I knew as much, New Clue #50 point caught my imagination a little more perhaps.

Your points make perfect sense, indeed raising the bar up to ‘empathy’ level might be asking too much in a general case. I can imagine there to be a much higher number of instances where one would rather not share part or any of the values expressed or embodied in some particular messages. In such instances, empathy would be out of order. In the same vein though, even sympathy could be a tall order if, for instance the message being furthered would be going against one's own set of values or interest - on a more personal level, that is.

The challenge I see is this: inside one's own tribe, one should have empathy, with regards to other tribes however, one might have sympathy. Clue #50 made me think about this, but I’ve certainly bundled the two aspects together into one.

On GitHub.

Indeed, by allowing people to submit pull request, you are inferring that suggestion of changes are welcome. That is how most would interpret it as well, it is a how folks have been nurturing collaboration around software project they wish to see wider adoption of. This rule could well apply to a publication like the New Clues, although you might be aiming for a wider consumption rather than a wider ownership. But, I am thinking that this is just a consequence of GitHub public repositories, not specifically your intention.

As users and contributors of GitHub, it is absolute fair game that suggestions get rejected. In fact, that’s more often the case than otherwise.

In any case, thanks for the chance of this conversation.

All the best, Isaka

On 10 Jan 2015, at 15:57, David Weinberger notifications@github.com wrote:

Isaka,

Thanks for the pull request. I'm a github n00b, so please let me know if I'm misunderstanding it. (Also, please let me know if you got this email. Thanks.)

I appreciate the suggestion, but I want to stick with "sympathetic." For me "empathetic" raises the bar too high. I take sympathy as "feeling with" someone (which is the root meaning of the word) -- understanding, appreciating, and being moved by someone else's feelings and experience. Asking people to be empathetic -- to actually feel the feelings of others -- is more than is required (in my opinion) for us humans to live together well.

But -- and here's where my being bad at github becomes obvious -- I am likely to reject all pull requests because I view the New Clues as a publication, not a sw project. The New Clues are what we published on Jan.

  1. So, people should feel free to create forked versions, but I think I want to maintain the original published version without revisions.

Does that make sense?

Thanks for your help.

David

MY EMAIL ADDRESS HAS CHANGED: self@evident.com will cease to work soon. My new email address is david@weinberger.org.

On Sat, Jan 10, 2015 at 9:24 AM, Isaka Traore notifications@github.com

wrote:


You can merge this Pull Request by running

git pull https://github.com/itraor/newclues master

Or view, comment on, or merge it at:

https://github.com/dweinberger/newclues/pull/2 Commit Summary

  • suggest to use 'empathetic' in place of 'sympathetic'

File Changes

Patch Links:

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2.

— Reply to this email directly or view it on GitHub < https://github.com/dweinberger/newclues/pull/2#issuecomment-69458491>.

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2#issuecomment-69460888.

— Reply to this email directly or view it on GitHub https://github.com/dweinberger/newclues/pull/2#issuecomment-69461234.