Mention using GGG on github.com/git/git

[phil-blain]

As discussed in gitgitgadget/gitgitgadget#146, here is a small update to the GGG homepage to mention that it can also be used on github.com/git/git.

This PR also adds the following to the homepage:

• Add a couple of links to other resources
• Mention the CC syntax
• Add a section mentioning GGG's features and which work on GGG's git fork vs github.com/git/git

@dscho @webstech

Note: the table and its CSS was generated using an online HTML table generator, which I tried to clean up a bit. Also if we'd rather not use emoji in the table we could use "yes"/"no".

Don't hesitate if you think of other features that should be mentioned or that are not available on github.com/git/git.

[phil-blain]

I've activated GitHub pages on my fork so that the formatted result can be reviewed:
https://phil-blain.github.io/gitgitgadget.github.io/

[dscho]

Looks good!

Two comments:

• the table and the Cc: example seem too small when I look at it on a phone screen
• the table entries would read better to me in the 3rd person, e.g. "adds a PR comment when the patches made it to pu, next, master or maint

What do you think?

[webstech]

Good idea.

• The <tt> tag is deprecated and does not look very good on an iPad (both Chrome and Safari look bad). Actually, it looks like there is an alignment issue in chrome on a pc as well (too low).
• The CC: example has tabs which are causing a positioning problem. Use html/css for positioning? From a phone:
  
• GitGitGadget will use these as the cover letter. Not sure where else the cover letter is mentioned but there isn't really one now for single commit PRs. I understand it is included in the email and maybe it just needs to say that and not specifically the cover letter.

[dscho]

The cover letter is still sent for multi-patch contributions, and for single-patch ones, it is included between the --- line and the diff stat.

I agree that it is less important for single-patch contributions, but even in those cases, it is a good space to provide ephemeral context (e.g. to mention on what occasion the contributor stumbled over the problem, or that they want to participate in Outreachy etc)

[phil-blain]

thanks for the review!

the table and the Cc: example seem too small when I look at it on a phone screen

Fixed.

the table entries would read better to me in the 3rd person

Fixed

The <tt> tag is deprecated

Fixed.

The CC: example has tabs which are causing a positioning problem

Fixed

Not sure where else the cover letter is mentioned

I've added a pointer to an explanation in MyFirstContribution

[phil-blain]

Also I thought about adding a third column to compare with the mailing list workflow, is that something that you think would fit/ be valuable ?

Most entries in that column would be something like “Via the "What’s cooking" emails”...

[dscho]

I thought about adding a third column to compare with the mailing list workflow, is that something that you think would fit/ be valuable ?

While that might be interesting to already-active contributors familiar with the mailing list workflow, the main goal of GitGitGadget is to support new contributors (who generally want to tackle challenges in the code, not in the contributing process), therefore I'd like to avoid that column here. Maybe in an FAQ?

[phil-blain]

OK I agree. Let's leave it at that for now then.

[dscho]

Thank you very much!