From 129282d8a9b3756a9effd0b195b6531eaa765a2e Mon Sep 17 00:00:00 2001 From: Simon Aronsson Date: Tue, 13 Feb 2024 10:50:16 +0100 Subject: [PATCH] Update README.md --- README.md | 53 ----------------------------------------------------- 1 file changed, 53 deletions(-) diff --git a/README.md b/README.md index 4775ae3..d1e6d0c 100644 --- a/README.md +++ b/README.md @@ -28,56 +28,3 @@ sudo snap install grafana-agent ## Configuration Once installed, a default configuration file will be created at `/etc/grafana-agent.yaml`. Before starting the agent, make sure to update this configuration file to suit you needs, consulting the [official documentation](https://grafana.com/docs/agent/latest/configuration/). - -## Remaining tasks - -Snapcrafters ([join us](https://forum.snapcraft.io/t/snapcrafters-reboot/24625)) are working to land snap install documentation and the [snapcraft.yaml](https://github.com/snapcrafters/fork-and-rename-me/blob/master/snap/snapcraft.yaml) upstream so Grafana can authoritatively publish future releases. - - - [x] Click the green "Use this template" button above to create a new repository based on this template - - [x] Give the newly created repository a sensible name, like `godzilla` if you're snapping the Godzilla software (*Note: Do not use `snap` in this name.*) - - [x] Update the description of the repository to `Unofficial snap for [Project]` - - [x] Update logos and references to `[Project]` and `[my-snap-name]` - - [x] Create a snap that runs in `devmode` - - [x] Convert the snap to `strict` confinement, or `classic` confinement if it qualifies - - [x] Register the snap in the store, **using the preferred upstream name** - - [x] ~~Add a screenshot to this `README.md`~~ - - [x] Add install instructions to this `README.md` - - [ ] Update snap store metadata, icons and screenshots - - [ ] Publish the confined snap in the Snap store beta channel - - [ ] Update the install instructions in this `README.md` - - [ ] Post a call for testing in the Snapcraft Forum ["Snapcrafters" category](https://forum.snapcraft.io/c/snapcrafters/23) - [link]() - - [ ] Add the Snapcraft store account (snap-advocacy@canonical.com) as a collaborator to your snap in the [Dashboard](https://dashboard.snapcraft.io) and ask a [Snapcrafters admin](https://github.com/orgs/snapcrafters/people?query=%20role%3Aowner) to accept this request - - [ ] Fix all important issues found during testing - - [ ] Make a post in the Snapcraft Forum ["store-requests" category](https://forum.snapcraft.io/c/store-requests/19) asking for a transfer of the snap name from you to Snapcrafters - [link]() - - [ ] Ask a [Snapcrafters admin](https://github.com/orgs/snapcrafters/people?query=%20role%3Aowner) to fork your repo into github.com/snapcrafters, and configure the repo for automatic publishing into edge on commit - - [ ] Add the provided Snapcraft build badge to this `README.md` - - [ ] Publish the snap in the Snap store stable channel - - [ ] Update the install instructions in this `README.md` - - [ ] Post an announcement in the Snapcraft Forum ["Snapcrafters" category](https://forum.snapcraft.io/c/snapcrafters/23) - [link]() - - [ ] Ask the Snap Advocacy team to celebrate the snap - [link]() - - [ ] Submit a pull request or patch upstream that adds snap install documentation - [link]() - - [ ] Ask upstream if they are interested in maintaining the Snap. If they are: - - [ ] Fork the upstream project, add the snap build files and required assets/launchers to that repo and submit a pull request or patch - [link]() - - [ ] Add upstream contact information to the `README.md` - - If upstream accept the PR: - - [ ] Request upstream create a Snap store account - - [ ] Add upstream account as a collaborator on the snap - - [ ] Contact the Snap Advocacy team to request the snap be transferred to upstream - -If you have any questions, [post in the Snapcraft forum](https://forum.snapcraft.io). - - - -