David Kastrup [off-list ref] writes:
Junio C Hamano [off-list ref] writes:
quoted
But still, I am not convinced that the release notes is a good place
to do this, and would be happier if you can think of a better venue.
"This change has been contributed by an independent developer on a
contingency base. To make this approach work, please contact him if you
consider it worth recompensating."
I write things under three personalities. As just one of the people
active in the Git development community, as the maintainer of the
project, and saying things on behalf of "the Git project".
The distinction between the latter two may be subtle, but it matters
to me. And in my mind, I write the Release Notes on behalf of the
project.
* The performance of "git blame" has been greatly improved. Thanks
David Kastrup for his huge effort.
is perhaps as far as I can go in that capacity, without singling out
one contributor among 80+ contributors with changes between 1.9 and
2.0 (among which a dozen or so have more than 10 patches---some are
trivial and patch count alone does not do justice, though) with
similar "pay them to show your appreciation" pleas.
I however feel that I can certainly do that as an active (and highly
visible) contributor, and even as the maintainer.
I guess we probably can add "See $URL if you are interested in his
further plans" after that two-line item and let you write whatever
you want at that page pointed at by the URL, though.
On Mon, Apr 28, 2014 at 12:35 PM, Junio C Hamano [off-list ref] wrote:
David Kastrup [off-list ref] writes:
quoted
Junio C Hamano [off-list ref] writes:
quoted
But still, I am not convinced that the release notes is a good place
to do this, and would be happier if you can think of a better venue.
"This change has been contributed by an independent developer on a
contingency base. To make this approach work, please contact him if you
consider it worth recompensating."
I write things under three personalities. As just one of the people
active in the Git development community, as the maintainer of the
project, and saying things on behalf of "the Git project".
The distinction between the latter two may be subtle, but it matters
to me. And in my mind, I write the Release Notes on behalf of the
project.
* The performance of "git blame" has been greatly improved. Thanks
David Kastrup for his huge effort.
is perhaps as far as I can go in that capacity, without singling out
one contributor among 80+ contributors with changes between 1.9 and
2.0 (among which a dozen or so have more than 10 patches---some are
trivial and patch count alone does not do justice, though) with
similar "pay them to show your appreciation" pleas.
I however feel that I can certainly do that as an active (and highly
visible) contributor, and even as the maintainer.
I guess we probably can add "See $URL if you are interested in his
further plans" after that two-line item and let you write whatever
you want at that page pointed at by the URL, though.
Some projects, for example samba, provide a dedicated page on the
project web site
where vendors, and I think individuals, that provide services can list
their information :
http://www.samba.org/samba/support/
Would this perhaps be a better solution?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html