Re: Recording the current branch on each commit?

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Recording the current branch on each commit?

From: David Kastrup <hidden>
Date: 2016-06-15 23:00:54

Felipe Contreras [off-list ref] writes:
Contributors don't have any responsibility to champion their patches.
It is pro bono work.
No, that's just the appearance that should be upheld in the higher
society.  It's ok to get paid for work on Git as long as you don't
mention it in public.  It's also ok to get paid for _promises_ of work
if you can make people believe you.  Open Source is not much different
from how politics and society in general work in the U.S.A.  To get the
real wads of money, you first need to get the means not to have to talk
about money (it's ok if you do it by means totally opposed to "the
political cause" as long as you don't talk about it), then you have to
prefinance people's trust in you not being there for the money, and then
you are in a position to get paid for your work.

Anyway, I digress.  Even without all that not so "pro bono" background
to "pro bono work", there is still a difference between "pro bono" work
ending up in the wastebin and "pro bono" work ending up in a product.

Even while the ones getting the benefits from your work will not feel an
obligation to make it worth your while, there is a difference in
satisfaction between getting your work trashed and getting it used.

The satisfaction by exploding in self-righteousness tends to be a poor
substitute and is comparatively short-lived.

Yes, it may mean that you have to carry your child the last yards rather
than shout it across the finishing line.  Even though it should have
legs perfectly suited to get it across the track on its own.

Only that way you get to pat it on its head.

-- 
David Kastrup

Re: Recording the current branch on each commit?

From: Felipe Contreras <hidden>
Date: 2016-06-15 23:00:55

David Kastrup wrote:
Felipe Contreras [off-list ref] writes:
quoted
Contributors don't have any responsibility to champion their
patches.  It is pro bono work.
No, that's just the appearance that should be upheld in the higher
society.  It's ok to get paid for work on Git as long as you don't
mention it in public.
The word "contribute" implies doing something that was not necessary.
If somebody is paying you to do something, then it's not a
contribution, it is simply your duty.

That's why I used the word "contributors", to separate the people that
don't have a responsability, and the ones that do.
Even while the ones getting the benefits from your work will not
feel an obligation to make it worth your while, there is a
difference in satisfaction between getting your work trashed and
getting it used.
I don't know why this keeps poping up in the thread, but it is
starting to seem to me that you are under the impression that I'm
somehow unable to get my patches merged.

Look at the list of contributors of the past year, see who is #2:

https://www.ohloh.net/p/git/contributors?query=&sort=commits_12_mo

I know what kind of patches can get in, and what patches can't (the
ones that do any kind of relevant change). I know that from
experience.

-- 
Felipe Contreras
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help