CMS tlog Implementation

[alexlyp]

This is re-implements the various CMS functionality in the new plugin/hook model that was introduced with the tlog implementation.

[xaur]

Is there a plan how to migrate past data into tstore?

[lukebp]

Is there a plan how to migrate past data into tstore?

CMS will run into the same problems that Pi has, which have not been fun to deal with. All signatures will be broken, all timestamps will be broken, and it's a lot of work to build out a tool to convert the data types between the git backend and the tstore backend.

The signatures being broken is the main source of pain because it breaks a lot of built in validation both client side and server side.

I would recommend following the same route as Pi. Throw up an archived site for now that contains the git backend data and gives you time to figure out the best way forward.

[xaur]

Thanks for the details.

I just want to highlight that we absolutely need to retain access to past invoice data.

Archived site may work, but fragmenting the database will have consequences. Perhaps the worst will be broken reporting on owned proposals. Imagine I need to report to the stakeholders on my budget spending. Proposal reports in the store-based CMS will be incomplete if it does not have all data in. I would very much prefer to avoid such disruption and not lose the numbers I need to show to the stakeholders once in a while.

Could CMS reuse any of the Git>tstore migration developed in https://github.com/decred/politeia/issues/1425 ?

[lukebp]

Could CMS reuse any of the Git>tstore migration developed in #1425 ?

Only the comment parts, which doesn't help very much.

Also, this decision has nothing to do with you. Everybody understands that, ideally, we don't want two databases. You're stating the obvious. I will be ignoring all future comments from you on this issue and I shouldn't have entertained your questions in the first place. That's my mistake.