Re: Promoting Git developers

Christian Couder [off-list ref] writes:

I wrote something about a potential Git Rev News news letter:

I read it.  Sounds promising.

Just one suggestion on the name and half a comment.

How would "Git Review" (or "Git Monthly Review", or replace your
favourite "how-often-per-period-ly" in its name) sound?  I meant it
to sound similar to academic journals that summarize and review
contemporary works in the field and keeps your original "pun" about
our culture around "patch reviews".

I obviously do not know how the actual contents would look like at
this point, but depending on the quality of the publication I might
be able to steal some descriptions when keeping the notes on topics
in flight that appear in my "What's cooking" report.  And it can go
the other way around, too.  The publication may want to peek my
"What's cooking" report for hints on how to characterize each topic
and assess its impact to the evolution of Git.

On March 15, 2015 6:19 PM Christian Couder wrote:

<snip>

Just one suggestion on the name and half a comment.

How would "Git Review" (or "Git Monthly Review", or replace your favourite
"how-often-per-period-ly" in its name) sound?  I meant it to sound similar

to

academic journals that summarize and review contemporary works in the

field

and keeps your original "pun" about our culture around "patch reviews".

If I may humbly offer the suggestion that "Git Blame" would be a far more
appropriate pun as a name :)

On Sun, Mar 15, 2015 at 11:43 PM, Randall S. Becker
[off-list ref] wrote:

quoted

On March 15, 2015 6:19 PM Christian Couder wrote:

<snip>

quoted

Just one suggestion on the name and half a comment.

How would "Git Review" (or "Git Monthly Review", or replace your favourite
"how-often-per-period-ly" in its name) sound?  I meant it to sound similar

to

quoted

academic journals that summarize and review contemporary works in the

field

quoted

and keeps your original "pun" about our culture around "patch reviews".

I would be ok for that but there is already this Gerrit related command:

http://www.mediawiki.org/wiki/Gerrit/git-review

Maybe I can just use "Git Rev", but it doesn't tell that it is about news?

If I may humbly offer the suggestion that "Git Blame" would be a far more
appropriate pun as a name :)

You don't want me to steal Junio's blog title:

http://git-blame.blogspot.fr/

don't you?

On Sun, 15 Mar 2015, Junio C Hamano wrote:

Christian Couder [off-list ref] writes:

quoted

I wrote something about a potential Git Rev News news letter:

I read it.  Sounds promising.

Just one suggestion on the name and half a comment.

How would "Git Review" (or "Git Monthly Review", or replace your
favourite "how-often-per-period-ly" in its name) sound?  I meant it
to sound similar to academic journals that summarize and review
contemporary works in the field and keeps your original "pun" about
our culture around "patch reviews".

I obviously do not know how the actual contents would look like at
this point, but depending on the quality of the publication I might
be able to steal some descriptions when keeping the notes on topics
in flight that appear in my "What's cooking" report.  And it can go
the other way around, too.  The publication may want to peek my
"What's cooking" report for hints on how to characterize each topic
and assess its impact to the evolution of Git.

I'll bet that LWN would publish, or at least link to, such articles on a regular 
basis, and if you end up doing an in-depth writeup on a particularly discussed 
topic, they would probably give it pretty good visibility.

David Lang

On Sun, Mar 15, 2015 at 11:18 PM, Junio C Hamano [off-list ref] wrote:

Christian Couder [off-list ref] writes:

quoted

I wrote something about a potential Git Rev News news letter:

I read it.  Sounds promising.

Thanks!

[...]

I obviously do not know how the actual contents would look like at
this point, but depending on the quality of the publication I might
be able to steal some descriptions when keeping the notes on topics
in flight that appear in my "What's cooking" report.  And it can go
the other way around, too.  The publication may want to peek my
"What's cooking" report for hints on how to characterize each topic
and assess its impact to the evolution of Git.

Yeah, it would be a very nice thing if we could steal these kind of
things from each other's work!

Thanks,
Christian.