Developer's guide: Expand on GitHub accounts and SSH keys

[mkoeppe]

(split out from #33687)

We move the section on creating SSH keys from the section on Trac to a later section, as creating tickets and participating in discussions on tickets does not require SSH keys.

This is also preparation for #33687 (gitlab workflow).

Depends on #33648

CC: @slel @dimpase @tobiasdiez @sagetrac-tmonteil @yuan-zhou

Component: documentation

Author: Matthias Koeppe

Branch/Commit: 4c03af3

Reviewer: Yuan Zhou

Issue created by migration from https://trac.sagemath.org/ticket/33700

[mkoeppe]

Branch: u/mkoeppe/developer_s_guide__expand_on_github_accounts_and_ssh_keys

[mkoeppe]

Last 10 new commits:

3f6c6e0	src/doc/en/developer/workspace.rst: Link to Trac #30500
8716d80	src/doc/en/installation/source.rst: Update required venv Python extension modules from build/pkgs/python3/spkg-configure.m4
f4c3604	Merge #33088
88b04d4	src/doc/en/developer/manual_git.rst: Do not recommend mixed sagetrac-mirror / trac operation when using VS Code
fc7aa4f	src/doc/en/developer/advanced_git.rst: Mention git log --first-parent
aa9faaa	src/doc/en/developer: move "git the hard way" earlier, present "git-trac" only as an additional convenience
6ae0e52	Merge #33648
106603e	src/doc/en/developer/trac.rst: Expand [GitHub](../wiki/GitHub) account instructions, remove legacy account instructions (duplicated from trac main page)
e500597	src/doc/en/developer/trac.rst: Clarify Authors field, purpose of tickets
77d1e53	src/doc/en/developer/manual_git.rst: Move section on SSH keys here from trac.rst, add links to [GitLab](../wiki/GitLab) instructions

[mkoeppe]

Commit: 77d1e53

[mkoeppe]

comment:3

Let's get this in please.

Only the last 3 commits need review, the earlier ones are all from #33648.

[yuan-zhou]

comment:4

It looks good to me, but maybe it is worth keeping a note regarding the non-github login that uses the legacy account, after deleting the following.

-**New:** Previously, it was necessary to manually request a Trac account in
-order to post anything to Sage's Trac.  Now, if you have a GitHub account, you
-may log in using it to create and comment on tickets, and edit wiki pages on
-Sage's Trac.

[mkoeppe]

comment:5

I deleted it because this information is also on the front page of Trac (https://trac.sagemath.org/#legacy-account-request).

I've just edited https://wiki.sagemath.org/#About_this_wiki to also be clearer about this.

The big problem with mentioning the legacy account requests is that no one actually tends to them. (I requested one in January for a special purpose and have not received a reply.)

[yuan-zhou]

comment:6

I didn't make it clear. Actually I was wondering if you could add a note in the guide, saying that the first login button on the trac page is only for legacy account users; and that if the user had such an account, then the login instead of github-login is the right one to use.

(If I haven't used trac for a while and I got a new laptop that does not have my Username/Password cached, then I will be confused about the trac page's login/github-login, and I won't find the instruction in the new developer's guide.)

[sagetrac-git]

Changed commit from 77d1e53 to 4c03af3

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

4c03af3

src/doc/en/developer/trac.rst: Login info for users with legacy sage-trac accounts

[mkoeppe]

comment:8

OK, done. I've also edited the top of https://trac.sagemath.org/ to make this clearer.

[yuan-zhou]

Reviewer: Yuan Zhou

[yuan-zhou]

comment:9

Great! Thank you for editing the top of trac page. I find it very helpful.

[mkoeppe]

comment:10

Thanks for the review!

[vbraun]

comment:12

docbuild fails

[mkoeppe]

comment:13

Can't reproduce an error here on top of vbraun/develop, 7950f93

[vbraun]

Changed branch from u/mkoeppe/developer_s_guide__expand_on_github_accounts_and_ssh_keys to 4c03af3