[ckaraca]

Adds a project status notice to the README.

plugged.in, the hosted service, is moving to a new, separately developed platform. After that move, this repository will no longer run plugged.in. It stays open source under its current license and continues with open collaboration: issues, pull requests, forks and new maintainers are welcome, and self-hosting remains supported. The cutover date will be announced at least 60 days in advance.

The notice links to PROJECT_STATUS.md in pluggedin-app, added in VeriTeknik/pluggedin-app#262. Merge that one first so the link resolves.

Summary by Sourcery

Documentation:

• Add a prominent README notice explaining the project’s transition away from the hosted plugged.in service while reaffirming open-source, community-driven development and self-hosting support.

[sourcery-ai]

Sorry @ckaraca, this account has used its review budget of 2,500,000 diff characters for the last 7 days.

You can request another review in 18 hours and 58 minutes by commenting @sourcery-ai review.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates README.md with an Important project-status notice explaining the planned hosted-service transition, the repository’s continued community-driven development and self-hosting support, the cutover-notice timeline, and a link to further details.

File-Level Changes

Change	Details	Files
Adds a prominent project-status notice to the README documenting the hosted-service transition and ongoing open-source support.	States that the hosted service is moving to a separately developed platform and this repository will no longer run it after cutover. Clarifies that the repository remains open source, community-driven, and self-hostable, with contributions and new maintainers welcome. Commits to announcing the cutover date at least 60 days in advance. Links readers to the detailed PROJECT_STATUS.md notice in the pluggedin-app repository.	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.