| 8 Nov 2018 |
 davidak | very good news. thanks! | 21:01:46 |
 holger.waechtler | It all takes much more time than expected, yet, considering how much gogs/gitea accelerated maturing in recent weeks, hopefully worth stressing the patience | 21:02:53 |
| holger.waechtler | And that German authorities are really slow, ... well, we should know | 21:03:39 |
| holger.waechtler | But the worst is (hopefully) behind us now | 21:04:00 |
 fnetx | Hey there ... will there be a data merge between the staging and the official platform? I want to try teahub with a new project and I don't know if I should use my existing (staging) account or register a new one at the 'official' site. | 22:23:20 |
| holger.waechtler | Please use the TLD teahub.io, not staging | 22:43:02 |
| holger.waechtler | We will try to migrate accounts and repos as complete as possible | 22:44:47 |
| holger.waechtler | Yet there might be conflicts (double accounts, same repo names etc) | 22:45:24 |
| holger.waechtler | We will have to see how this will work out | 22:45:42 |
| 13 Nov 2018 |
| holger.waechtler | Hi | 19:52:13 |
| 17 Nov 2018 |
| fnetx | What I meant is that I have been using staging.teahub.io already, so I tried not to create these conflicts by not creating a second account. | 16:19:07 |
| holger.waechtler | fnetx: have you tried the „Create ... New Migration“ function (the „+“ button top right corner)? Staging will live on until migration is complete and we can be certain that no data loss occured | 16:29:30 |
| holger.waechtler | In any case thank you for the heads-up, I will double check with you that everything is alright then | 16:30:09 |
| fnetx | Hmm okay ... If I get you right, I should create a new account at teahub.io and create my existing projects in "migration", so it copies the content from the staging instance? | 16:32:13 |
| holger.waechtler | Yes, and from then on commit/push to teahub.io (update the git remote on your client or work on a fresh checkout from teahub.io) | 16:54:49 |
| 26 Nov 2018 |
 techknowlogick | version 1.6.0 of Gitea is out: https://blog.gitea.io/2018/11/gitea-1.6.0-is-released/ | 06:25:52 |
| holger.waechtler | Thank you for heads up! (already deployed on the testing node) | 07:08:11 |
| davidak | techknowlogick: again a very nice update with some useful features, but there are still 18 security issues open. | 09:57:55 |
| holger.waechtler | techknowlogick: playing with the image, I realized that the heatmap widget is allocated, but not rendered (spinning wait wheel forever). Is some special database migration or setup required or the feature simply not yet finalized? | 10:31:52 |
| 27 Nov 2018 |
| techknowlogick | holger: no DB migration required, although it will be replaced with updated version in 1.7.0 release. If it isn't working for you, then I recommend disabling it via settings, and re-enabling when 1.7.0 comes out. | 17:28:13 |
| holger.waechtler | Thank you! I will try | 17:45:12 |
| 3 Dec 2018 |
|  Zeratax?utf8=✓ changed their profile picture. | 19:44:15 |
| 4 Dec 2018 |
| Zeratax?utf8=✓ changed their profile picture. | 17:51:59 |
| 3 Jan 2019 |
|  thw changed their display name from thw to thw[m]. | 22:32:38 |
| 13 Jan 2019 |
| davidak | i would like to get the information from the uptime monitoring ticket from staging and the wiki page with press feedback | 14:50:01 |
| 11 Mar 2019 |
|  stlix left the room. | 19:28:48 |
| 20 Mar 2019 |
| techknowlogick left the room. | 13:50:24 |
| 2 Apr 2019 |
| Zeratax?utf8=✓ changed their display name from Zeratax?utf8=✓ to ZerataX. | 12:46:14 |
| 25 Aug 2019 |
|  harthollbarking2 joined the room. | 07:05:31 |
| harthollbarking2 left the room. | 07:05:39 |
