Skip to content

website: Remove retired Jira and Slack links - #190

Open
BobbyRBruce wants to merge 1 commit into
gem5:stablefrom
BobbyRBruce:codex/remove-jira-slack
Open

website: Remove retired Jira and Slack links#190
BobbyRBruce wants to merge 1 commit into
gem5:stablefrom
BobbyRBruce:codex/remove-jira-slack

Conversation

@BobbyRBruce

Copy link
Copy Markdown
Member

The gem5 website still advertises the retired Jira tracker and Slack workspace through active documentation, navigation, and an invite page.

Remove those active references, delete the obsolete Slack invite page and logo, and retain the underlying technical explanations where Jira links previously supplied context. Dated release posts, roadmap posts, past-event material, and fixed historical tutorial artifacts remain unchanged as archival records.

Validation:

  • git diff --check
  • Active-page Jira/Atlassian and Slack-service reference audit
  • Audit of tracked PDF, presentation, and document artifacts

A local Jekyll build was not run because the installed Ruby 2.6 environment cannot resolve the current nokogiri dependency, which requires Ruby 3 or newer.

Remove live Jira links from documentation and retire the Slack invite
page and homepage link. Dated posts and the past boot-camp page remain
unchanged as archival content.

Change-Id: I329868e354a716a59494b2cfc65361ad7bcd48ea
Copilot AI lite review requested due to automatic review settings August 26, 2026 02:40

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes active references to the retired gem5 Jira tracker and Slack workspace across the website’s navigation and documentation, while keeping historical/archival content intact.

Changes:

  • Removed the Slack link from the homepage “Connect with us” section and deleted the obsolete /join-slack/ redirect page.
  • Replaced Jira-linked references in active documentation with non-Jira explanatory text.
  • Updated the “Ask a question” page to remove Slack as a contact option and streamline guidance toward GitHub Discussions + mailing lists.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
index.html Removes the Slack external link/logo from the homepage.
_pages/join-slack.md Deletes the Slack invite redirect page.
_pages/documentation/learning_gem5/part1/part1_1_building.md Replaces a Jira link with a short explanation of the protobuf-version issue.
_pages/documentation/general_docs/developement/release_procedures.md Removes a Jira link from release procedures text.
_pages/documentation/gem5-stdlib/2-tutorial-x86-fs.md Removes a Jira link while retaining the limitation note.
_pages/ask-a-question.md Removes Slack as a contact channel; keeps mailing lists + GitHub Discussions.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

This problem can occur when gem5 is built with an incompatible version of
Protocol Buffers.

To resolve this problem, you may need to update the version of ProtocolBuffer,
Comment thread _pages/ask-a-question.md
Comment on lines 38 to +42
used: <https://stackoverflow.com/questions/tagged/gem5>). Please make sure
that your question complies with the [site guidelines](
https://stackoverflow.com/help/asking) before posting. Interested users can opt
to receive email notifications for such questions as explained at
<https://meta.stackexchange.com/questions/25224/email-notifications-for-new-questions-matching-specific-tags>).
<https://meta.stackexchange.com/questions/25224/email-notifications-for-new-questions-matching-specific-tags>).
* Special permissions are needed to push to the <ghcr.io>.
Please contact Bobby R. Bruce (bbruce@ucdavis.edu) for help pushing images.
* It is a future goal of ours to move [the Dockerfiles from `util/dockerfiles` to gem5-resources](https://gem5.atlassian.net/browse/GEM5-1044).
* It is a future goal of ours to move the Dockerfiles from `util/dockerfiles` to gem5-resources.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants