... or in other words: When/how is the next circle's DB entry created?
So far, I've designed the models in a way, that the views would have to take care of initializing the circle instance. This may have several pro's and con's. For instance, the collection of topics for the upcoming circle could only be done once the moderator and/or transcript writer have been assigned - as in: the circle is currently bootstrapping IRL. Topic proposals would still have to be sent to the mailing-list and would have to be copy-pasted into the circleapp.
cmile proposed that there should always be exactly one upcoming circle instance where any authenticated member could drop topics any time they want, as long as the circle hasn't been formally opened. This would limit the topic-collection task to ordering and declining the topics not wanted.
I like that idea!
An easy fix would look something like this:
There can only exist one circle with an unset date. The date is set when the circle is formally opened (and has been verified to do so). Once this circle is formally closed a new instance of the circle model will be created automatically.
cmile
commented
9 years ago
... or in other words: When/how is the next circle's DB entry created?
So far, I've designed the models in a way, that the views would have to take care of initializing the circle instance. This may have several pro's and con's. For instance, the collection of topics for the upcoming circle could only be done once the moderator and/or transcript writer have been assigned - as in: the circle is currently bootstrapping IRL. Topic proposals would still have to be sent to the mailing-list and would have to be copy-pasted into the circleapp.
cmile proposed that there should always be exactly one upcoming circle instance where any authenticated member could drop topics any time they want, as long as the circle hasn't been formally opened. This would limit the topic-collection task to ordering and declining the topics not wanted.
I like that idea!
An easy fix would look something like this: There can only exist one circle with an unset date. The date is set when the circle is formally opened (and has been verified to do so). Once this circle is formally closed a new instance of the circle model will be created automatically.