-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving to git-scm.com #729
Comments
Sorry @chriscool, I didn't actually mean just the Rev News part, I did mean that I thought that all of git.github.io should be part of git-scm.com somehow. |
Now that git-scm.com is on Hugo, it's probably not difficult to move this content into that tree somewhere, somehow. |
No worries @schacon, I am fine with moving all of git.github.io, so that it becomes part of git-scm.com if it's done properly. Let's wait until we hear from the other git.github.io team members I cc'ed above though. And yeah, I agree it's probably not difficult to move the content. The main issue for me though is that I am not a web developer, so even if it's not difficult to move the content, I am not sure about some details like how to best put redirects in place so that users who bookmarked pages on git.github.io get properly redirected on the corresponding page on git-scm.com, or if there is a need and tools to somehow reformat some pages a bit. The git.github.io team members would need to get proper credentials to be able to work with git-scm.com as they did with git-scm.com. It might also require a bit of work to replace links that contains git.github.io. (Not sure if we have a lot of relative links by the way.) About the issues and perhaps PRs in https://github.com/git/git.github.io/issues and https://github.com/git/git.github.io/pulls, we would need to check if there are some that are worth keeping and then move them over. Also I think it would be nice if the Git history of git.github.io could be kept. |
In https://lore.kernel.org/git/CAP2yMa+PtRADLB2ZL4U3S8X+87Ddz4UZQNMmtEvV5p9nyoq5SA@mail.gmail.com/ @schacon said:
I am going to reply to his message on the list, but maybe we could also discuss it here. And if we agree on moving to git-scm.com, we could perhaps discuss here how it could happen.
cc @jnareb @mjaix @sivaraam @gitster @stepnem
The text was updated successfully, but these errors were encountered: