| 6 Feb 2024 |
 jolheiser | Re-reading the issue I linked, it does somewhat talk about both structure and permissions, but I still think a separate issue may be worthwhile in the context of GH. | 18:53:55 |
 Ryuno-Ki (André Jaenisch) | Took a note that I'm following up tomorrow on it | 19:02:46 |
|  @jojo404:matrix.org left the room. | 19:25:06 |
| 7 Feb 2024 |
| Ryuno-Ki (André Jaenisch) | Filed https://github.com/go-gitea/gitea/issues/29078 | 11:30:03 |
| jolheiser | Thanks! | 12:28:39 |
| 10 Feb 2024 |
|  @jan.christian:gruenhage.xyz left the room. | 12:46:41 |
| 17 Feb 2024 |
|  @+tommy_plug:matrix.org joined the room. | 15:36:04 |
| 18 Feb 2024 |
|  Mert Gör 🇹🇷☭ changed their profile picture. | 15:21:57 |
| 22 Feb 2024 |
|  qubidt joined the room. | 10:04:27 |
| @+tommy_plug:matrix.org left the room. | 12:24:14 |
| 2 Mar 2024 |
|  jochen joined the room. | 13:20:02 |
| 11 Mar 2024 |
| Ryuno-Ki (André Jaenisch) | Reading the Forgejo chats on Matrix today makes it appear that fnetX (a.k.a. Otto) of Codeberg is increasingly frustrated with the state of accessibility in Forgejo. Even more so as putting the blame on Gitea for „accidentally“ adding changes after they landed in Forgejo. I consider it unfair to claim that Forgejo cannot be accessible as long as it holds ties with Gitea. But then, every critique from this direction is silenced for „trolling“. | 18:03:08 |
| Ryuno-Ki (André Jaenisch) | I feel offended as kind of sitting between the chairs and not improving the situation on either end. | 18:03:52 |
| Ryuno-Ki (André Jaenisch) | Hm, I know that it is subject to change, but perhaps a theme focused on accessibility and usability would be a good first step to show how it could be done? In the hopes that it would gradually influence the default themes. | 18:14:34 |
| jolheiser | Are there any good accessibility linters available? Or something that could be added to CI? | 18:43:21 |
| jolheiser | When I think "theme" I generally think CSS, but I get the idea that's not what you're referring to? Since (to the best of my knowledge) CSS isn't the accessible part, rather it's the HTML layout and/or attributes? | 18:45:19 |
| Ryuno-Ki (André Jaenisch) | axe being used by Lighthouse and Storybook is pretty much the de facto standard. I think the package is called axe-core. | 18:55:02 |
| Ryuno-Ki (André Jaenisch) | CSS can impact the accessibility (for example the display property). But I mainly refer to HTML, yes. | 18:55:49 |
| 14 Mar 2024 |
|  kiti_nomad joined the room. | 18:42:34 |
| 17 Mar 2024 |
|  kralya joined the room. | 22:32:55 |
| 18 Mar 2024 |
|  Marc Lewis joined the room. | 21:37:48 |
| 26 Mar 2024 |
|  Benjamin joined the room. | 08:57:28 |
| 2 Apr 2024 |
| Benjamin | i think this is the right place to ask if anyone has experienced this problem:
I have installed gitea and gitearunner via Docker on my Synology DS923+.
I have now noticed several times that when I cancel a job, the networks and some of the generated dockers remain.
Then the new jobb fails because the port used is already occupied. is this a known error or have I configured something incorrectly? | 07:20:12 |
| jolheiser | Perhaps it could be related to https://gitea.com/gitea/act_runner/issues/509 or similar. Are there any logs or other indications of things going awry? | 13:43:56 |
| Benjamin | In reply to @jolheiser:matrix.org
Perhaps it could be related to https://gitea.com/gitea/act_runner/issues/509 or similar. Are there any logs or other indications of things going awry? thank you very much. yes, it is very similar in terms of the errors. fortunately, as a service it works for me most of the time.
I have added my comments in the issues. if you need more information, feel free to ask me.
| 20:53:12 |
| 6 Apr 2024 |
|  michaelten joined the room. | 16:17:16 |
| 10 Apr 2024 |
|  oranki joined the room. | 13:38:01 |
|  thompson_plug joined the room. | 22:40:22 |
| 13 Apr 2024 |
| Mert Gör 🇹🇷☭ changed their profile picture. | 10:43:35 |
| 16 Apr 2024 |
|  Snoweuph joined the room. | 00:44:51 |
