Migrate Eclipse CDT from Gerrit/Bugzilla/etc to GitHub

[jonahgraham]

The Eclipse CDT project is moving to GitHub. We are using this issue to track all the items that need to be completed. Many of the items in this list need to be submitted to webmaster when we are ready at the helpdesk issue

This issue was migrated from eclipse-cdt/cdt-infra#62 that had been used to track the move ahead of us having the new repo

TODO list for the move:

• Create https://github.com/eclipse-cdt/.github
  • Do not enable Issues, Discussions, Wiki - these will all be handled by the main repo https://github.com/eclipse-cdt/cdt
• Create a minimal README.md file in eclipse-cdt/.github that redirects to eclipse-cdt/cdt
• Archive https://github.com/eclipse-cdt/cdt-new-managedbuild-prototype
• Archive https://github.com/eclipse-cdt/cdt-vscode
• Migrate CDT's git repo stored in gerrit to https://github.com/eclipse-cdt/cdt
  • This may be as simple as stopping mirroring https://git.eclipse.org/r/admin/repos/cdt/org.eclipse.cdt,general?
• Rename master branch to main
• Delete/disable https://github.com/eclipse-cdt/cdt wiki
  • This was never used (bar a single/simple page)
  • Proposal/intent is that all documentation is part of the main repo, especially New and Noteworthy
  • See item farther down about future of the Wiki
• Enable Issues and Discussions on https://github.com/eclipse-cdt/cdt
• Set description on https://github.com/eclipse-cdt/cdt to Eclipse CDT™ C/C++ Development Tools
• Make https://git.eclipse.org/r/admin/repos/cdt/org.eclipse.cdt,general readonly
  • There is a lot of stuff on CDT's gerrit that is of differing value. My preferred option to leave CDT's gerrit in read-only state until gerrit is shutdown. That should give plenty of time for people to extract anything of value from gerrit and contribute it to CDT (as a GitHub PR)
• Protect branches from force pushes, deletions and direct pushes
  • All pushes need to be via PR.
• Migrate Process, Policy, etc from Wiki to README.md/CONTRIBUTING.md
• Migrate FAQs and sample code to markdown
• Move N&N pages from Wiki to Help pages https://help.eclipse.org/latest/topic/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew.htm or to markdown and update links in cdt_c_whatsnew.htm to point at that markdown
• Move these manual pages from Wiki to Help pages
  • https://wiki.eclipse.org/CDT/Autotools/User_Guide
  • https://wiki.eclipse.org/CDT/StandaloneDebugger
  • https://wiki.eclipse.org/CDT/Meson/User_Guide
• Move CDT Calls pages from Wiki
  • This is the only item I don't know where to put. We could have a wiki just for calls, but I am not keen on Wikis anymore.
• Save old CDT presentations somewhere https://wiki.eclipse.org/CDT:Presentations These will be kept alive as long as the WIki exists, when EF decides to get rid of the wiki we may revisit this.
• Mark all https://wiki.eclipse.org/CDT pages as obsolete or archived with redirections to new pages where possible
  • If there is additional info that needs to be kept, put it somewhere sensible
• Review all links in CDT (especially help) that are to the Wiki and update them
• Move https://github.com/eclipse-cdt/cdt-infra wiki contents to cdt-infra's root README or similar
• Delete/disable https://github.com/eclipse-cdt/cdt-infra wiki
• Redirct https://www.eclipse.org/cdt/ to https://github.com/eclipse-cdt/cdt
  • Maybe one day we can make a new website, many years ago at Kichwa we had an intern make this https://jonahgraham.github.io/cdt-website-prototype/ but the feedback pushed us to not persue it further
  • If we do a new one a Jekyll one similar to have embed CDT does it or just a simple gh-pages one.
• Announce on the Eclipse Forum for C/C++ IDE (CDT) the move to GitHub discussions ahead of shutdown.
• Make the Eclipse Forum for C/C++ IDE (CDT) read-only. The forum will stay open as a user-to-user forum as long as the Eclipse Foundation chooses to run it. Message posted on forum.
• Update CDT.setup - see Bug 580505 and integrate instructions into contributing file.
• Create an issue template
• Create some standard tags
  • Consider a bot to auto tag bugs?
• Create a PR template Created one but it doesn't work?
• Create a discussions template
• Disable new bugs being created in Bugzilla
• Reformat markdown files to one sentence per line as that gives better diffs (meant to do this before merging my big markdown changes but I forgot)
• Merge cdt-infra repo into main cdt repo.
  • Now that many of the security issues are resolved regarding gerrit we should be good to keep the infra code in sync more easily with the main repo.
• Test failures cause Jenkins to report back a failure rather than an unstable state. So we need either better reporting back from Jenkins or find a different solution.

[jonahgraham]

More items for EF Helpdesk

[jonahgraham]

Following today's CDT call, this is what we will do with remaining Wiki pages that need to be moved:

• CDT Calls: create a new page on hackmd.io and link to it from somewhere in the repo (either root readme or contributing)
• manual pages/user guides: Turn off the wiki -> html translation and maintain those pages in the HTML only from now on
• Old CDT presentations: Leave them on wiki and decide where to move them once EF wiki actually gets shut down

[jonahgraham]

CDT calls moved from https://wiki.eclipse.org/CDT/calls to https://hackmd.io/@jonahgraham/EclipseCDTCalls

[jonahgraham]

The forum will stay open as a user-to-user forum as long as the Eclipse Foundation chooses to run it. Message posted on forum

[jonahgraham]

xref: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2308 - request to disable creating new bugs in bugzilla, but not modify existing bugs.