Specifications in source control too?
So, I realise this might be a bit too much for ETSI, but... I notice that the documentation repository uses the CI/CD pipeline to assemble the various MD files into a docx, presumably for distribution. Do we think ETSI could ever get to a point where the specifications themselves can be specified in a sensible, simple format (like markdown) and managed the same way as source code via MRs?
For our protocol specifications, I'd love for people to be able to look at them like a Wiki alongside the repository, rather than having to download a PDF. And it means that all the benefits of source control (automated traceability, automatic merging of accepted CRs) accrue to the published document too.
Obviously not the right thing for every specification... but still...?