As far as i understand the limit is only due to the calendar getting too crowded and for some reason "does not support" more than N items - unclear to me what exactly is the cause of this limitation though - the Gantt chart html component that is used looks too ugly or something else?
This I gathered from reading the comments in the github issue that
@Marlonc created (
github.com/ornicar/lila/issues/8925).
Is there any other reason for having to spread out tournaments for each variant - I would find it very surprising if it is actually due to limited servers capacity or anything similar?
Seems to me more like a side effect of an ill conceived unilateral decision made by one developer while his focus was on another task (adding new tournaments for other variants) who decided they don't want to fix the issues with the Gantt chart (aka Calendar) or decided subjectively it looks too ugly and space is limited and so instead removed existing tournaments.
If that is the case, maybe the decision to add more items to the Calendar should have been made after the Calendar feature was improved to support more items and not at expense of existing items?
---------
IMHO community organized schedules are a great idea, but while I am not familiar with what
@pepellou is talking about that teams thing, my impression is that lichess does not currently support enough tools/infrastructure to allow communities to organize and promote tournaments easily. If proper tools existed I would even suggest ALL (hourly/daily/weekly/whatever) tournaments to be organized bottom up by communities and not "coded" top-down by developers whose focus is usually on completely different things and "do not care about one variant or another".
Currently however if a communitiy organized event is only promoted within the existing members of this community this will only lead to capsulation. As someone already mentioned - hourly tournaments are the gateways to these communities.
-----
It is also unclear to me what is the decision making process that lead to the current problem (again i have described what my guess is above), and what is the decision making process that would get us to fix it?
Creating a github issue is ok, but who to assign it to? Who is the decision maker? Obviously the one who responded there "does not care either way" (which is totally fine). So who is the person responsible for these decisions that this whole process should have been addressed to (
@TBest ,
@Toadofsky ,
@thibault ? )
---
I would happily volunteer time and effort to learning scala+typescript+lichess codebase and to fixing whatever limitation causes the current hassle, but would do that only if I have understanding who makes what decision and what should the expected behaviour of the app should be, so i know if i do something it would not be a waste of time, because "no one wanted it" or "someone already fixed it" (admitting i say that while i haven't actually googled for any developer's resources and info about organization etc.)