@@ -33,24 +33,24 @@ Once you've entered all the information, you'll be presented with a pop-up windo
### Through Lemmy (Recommended)
You will need to post that message to the community (`!2024lemmycanvasatlas@toast.ooo` for 2024 or `!2025fedicanvasatlas@toast.ooo`) via Lemmy (or another Activity-Pub powered service that allow long enought messages).
You will need to post that message to the community (`!2024lemmycanvasatlas@toast.ooo` for 2024 or `!2025fedicanvasatlas@toast.ooo`) via Lemmy (or another Activity-Pub powered service that allow long enough messages).
Paste the whole JSON file in the body, and then post it. Eventually, a bot should answer that your post has been processed (or not) in less than 30 minutes. If that does not happen after 1 hour, then this is a bug, and you can report it. You can also use the second contributionn method.
Paste the whole JSON file in the body, and then post it. Eventually, a bot should answer that your post has been processed (or not) in less than 30 minutes. If that does not happen after 1 hour, then this is a bug, and you can report it. You can also use the second contribution method.
### Through the forge
If you know about Git, and know how to create a merge request on GitLab, you can create a patch that will be merged as-is in the repo.
For that, you first need to create an account on the forge used, [git.sc07.company](https://git.sc07.company), if you do not already have one. This instance is managed by grant, and have manual approval to avoid spam.
For that, you first need to create an account on the forge used, [sc07.dev](https://sc07.dev/), if you do not already have one. This instance is managed by grant, and have manual approval to avoid spam.
The, you can fork the repository, create a local clone of it, and then:
- If you create a new entry, just crate a new file ending in .json in that folder, and paste the JSON
- If you create a new entry, just create a new file ending in .json in that folder, and paste the JSON
- If you modify an existing entry, find the file with the same "id" in it, and replace it with the JSON
Please note that `entries/` if for 2024 and `entries2025` for 2025.
Please note that you should use `entries/` if for contributing to the 2024 atlas and `entries2025` for the 2025 one.
The commit message and description doesn't matter, but you may change it into something more descriptive to make it easier for checking (e.g. <kbd>Add Foo Bar</kbd> or <kbd>Edit Foo Bar</kbd> for the commit message). However, we suggest you to edit the title (at least) and the description of the pull request, containing the changes that you want to do (something like <kbd>Add Foo Bar</kbd> or <kbd>Edit Foo Bar</kbd> for the title, similar to the commit message, is also sufficient).
The commit message and description don't matter, but you may change it into something more descriptive to make it easier for checking (e.g. <kbd>Add Foo Bar</kbd> or <kbd>Edit Foo Bar</kbd> for the commit message). However, we suggest you to edit the title (at least) and the description of the pull request, containing the changes that you want to make (something like <kbd>Add Foo Bar</kbd> or <kbd>Edit Foo Bar</kbd> for the title, similar to the commit message, is also sufficient).
Once you have successfully created the patch, the file can be committed, and a pull request towards the `main` branch can be created. A member will merge the pull request if it is adequate.
