You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The simplest way could be a markdown file stored in the app files.
But only one admin could edit it.
It could be interesting to add the ability to allow moderators edit the rules.
AND
The most complex but interesting strategy could be to use a git-like rule system, but using a vote system to validate rules or not.
Voters could be mods of course, but also some users as defined by user-classes.
This could as well be done by some external dedicated tools, with a SAML connection #40 🥺 But I doubt on this solution.
Actually vote system for rules are very related to important aspects of this project. This would be a great implementation but maybe not too soon as it need a lot of work to do it well.
The text was updated successfully, but these errors were encountered:
As writen in #46, a rule could be an entity in the database. That way it could be cited in warnings. This could be a simple way to do this at first.
A rule classwould be defined by:
an ID
name
text (in markdown ? not so shure.. )
createdAt
lastEdiAt
The question is: should rules have the ability of being edited ?
Or should they only be "forked". Do we need a historic of this ? It's clearly more complicated.
I like the idea of an ID will be for ever linked to one written rule.
The simplest way could be a markdown file stored in the app files.
But only one admin could edit it.
It could be interesting to add the ability to allow moderators edit the rules.
AND
The most complex but interesting strategy could be to use a git-like rule system, but using a vote system to validate rules or not.
Voters could be mods of course, but also some users as defined by user-classes.
This could as well be done by some external dedicated tools, with a SAML connection #40 🥺 But I doubt on this solution.
Actually vote system for rules are very related to important aspects of this project. This would be a great implementation but maybe not too soon as it need a lot of work to do it well.
The text was updated successfully, but these errors were encountered: