2026-02-20: Eternaltwin Council #1
Recording
Participants
Participants: Bibni, Biosha, Brainbox, Demurgos, Evian, Jowpac, Moulins, Patate404, Zen
Notes
Organization
Demurgos: I want to agree on the frequency. Everyone seems to agree to meet once every two months. The next time would be in April. Regarding the time of the week, Friday is the best day with most people available. We also have Thursday evening. On Friday Jowpac is unavailable (even though he's present today), on Thursday Evian is unavailable.
Evian: It's fine for me on Thursday from time to time.
Jowpac: I should also make it on Friday evening, it's just that it's a bit early for me due to the time zone.
Demurgos: Let's go with Friday evening, it would be just at the end of the week. Today is the third Friday of the month. We should aim for the 2nd Friday, so we can have some time to prepare reports and TMIET before the end of the month. Do we agree? Alright, then the next meeting will be on April 10th at 21:30 CET.
Welcome
Now that everybody joined, thank you all for being present and actively helping the project. I hope that these calls will help us all to work more efficiently and improve the project.
Eternaltwin forums
Biosha: People post daily but nobody looks there. What should we do? I think that each game shares the same forum. We can also get rid of forums and move to custom forums.
Zen: Not very useful for MyBrute, we already have clans and Discord
Bibni: They're pretty active for Kingdom
Brainbox: MyHordes has a deeply integrated custom forum, hard to merge them with the Eternaltwin forum
Demurgos: 1/ The forums are very simple, there are not many features. 2/ Having an independent channel is good to be self-reliant. 3/ Is it a high priority to be able to link forums in games?
Biosha: not a high priority for DinoRPG, we have a readonly view. The priority should be webhooks.
Moulins: We don’t use forums on Eternalfest. Everything is on Discord, we don’t really need the forum. We could have the list of games or achievement.
Bibni: Do we have a feature to plan notifications? Notifications would help.
Webhook
Demurgos: Webhooks should have the highest priority. It block most of the planned development. For example, password recovery needs to have email sync with MyHordes but it can because there is no webhook for user syncs. Right now application configuration in database is being developed. This development enables to structure the skeleton of how the webhook would communicate.
Brainbox: I like the idea of webhooks. Since it’s not yet started, we should start drafting the API for the webhooks.
Demurgos: Sounds good to me, let’s do it at the end of the call or async
Brainbox: Okay, I did something similar at work recently and would be happy to help.
Access to deployment logs
Zen: Access to deployment logs is important for debugging.
Jowpac: same opinion for me (logs are important)
Evian: upvote
Biosha: I will be working on Katal to provide access to logs
Demurgos: my concern is that during deployment you may see some DB credentials. Let's not block things waiting for a perfect solution, I'm fine exposing the logs and trusting you.
Development bounty
Biosha: I want to bring the topic of bounties since many people ask about it. The idea is that you can provide a bounty. People can work on it and be paid for it. I know that some people ask for it because nobody gets paid for Eternaltwin so far. I can prepare a draft contact between the Eternaltwin association and the people doing development. I could share it tomorrow.
Zen: I’m personally not very fond of the idea. It could attract people, but maybe not the kind that would benefit in the long run. If you want to contribute to an open source project, you don’t need a bounty.
Demurgos: Not fond of the idea too, but rather than giving money to contributors, maybe reward them with goodies such as tee shirt, hoodies, mugs, etc. Something seen as a nice gesture
Brainbox: if we introduce bounties when we bring the question: why is he paid and no me? I like the idea of small gifts. Maybe we could increase the visibility of developers by listing contributors in TMIET?
Evian: Agreed with everything said by Brainbox. For eMush, we highlight contributors, especially new ones.
Zen: I agree with the contributor merch. Having achievement is a good idea.
Moulins: I agree with everyone. I don’t think giving money is workable long-term. We can’t really pay money. We have to show that someone contributes something.
Demurgos: I love having a contributor section. I would also like to add achievements for Eternaltwin
Biosha: Alright, so no financial rewards. We should also decide how we reward people. I would also like to encourage people to work on Eternaltwin itself.
Bans / Unbans
Demurgos: a player contacted me last week to be banned/unbanned. I’m not really involved in moderation, so I’d like to know what your policies are currently. (e.g. multiple accounts)
Brainbox: we have some automatic system to detect multiple accounts. We are very interested in players having a single account: we ban first and unban on contact.
Evian: to give the eMush point of view. We detect multi-accounts through reports, we then ask players which account they want to keep. We have players which are pure grifters. We have a tool to ban all multi-accounts.
Zen: we should set a policy against multi-accounts. Multi-accounts should always be banned.
Jowpac: agreed
Biosha: We have another feature planned for ET: the Terms of Service. In this document we forbid multi-accounts. It’s missing a frontend, I planned to do it last year. What’s the priority? Can we do it after the logs?
Zen/Brainbox: Low priority to enforce it
Demurgos: We should probably have some endpoint for games to report
Brainbox: automatic sanctions are a bad idea because it can cause havoc on players in the same household or university
Demurgos: Alright, so automatic flagging but manual sanctions?
Brainbox: Yes
Contributions to the Eternaltwin Platform
Evian: Some used patterns are not well documented? There are no replies.
Demurgos: I was away for some time, but it feels that replies are faster now. Do you have some particular change in mind? I'll improve the documentation.
Bibni: there are no patch notes for Eternaltwin, it would be nice.
Demurgos: Okay, I’ll make sure to enforce that we keep a CHANGELOG up to date
Development priority
- Eternaltwin API with WebHook
- Deployment logs in case of failure
- Password reset
- Redis and OCI images on Katal
- Term of Services
- Achievement on the profiles
GitHub/GitLab
Zen: Can I move my app from GitLab to GitHub?
Biosha: On the technical side, there are no issues
Demurgos: From a technical point of view, no problem. From a “legal” point of view, we link to the GitLab space from Open Collective. That's the "home" of the project.
Biosha: there’s also discoverability. Having it on GitHub, at least as a readonly mirror is good for it.
Moulins: We’d need some automation because Eternalfest has too many repos, maybe 50 repos
Demurgos: there’s also the issue that GitLab has namespace, but we just have to pick some mapping
TMIET
Biosha: TMIET takes a lot of time. Demurgos started managing it, but it takes a lot of time