Central | Interface maintanence workflow is to cumbersome (#8)

[Gedare Bloom (@gedare)]

Gedare Bloom commented: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/8#note_130566


I tend to agree that it is a burden. The submodules are challenging to work with in general, and I find that I have to reset them often, since they do not track across branches nicely. I would much rather point the rtems-central tools to my checked-out versions of the rtems/rtems-docs/rtems-tools repos, that way I can control the branches and keep them independent from the tools. However, merging the specification items and documentation back with the RTEMS sources feels like a step backward. We went to some trouble before to remove the documentation from the sources.

A good first step might be to refactor the specification items out of `rtems-central.git` so that only the tooling remains. I don't see a reason we cannot create a rtems-spec.git repo that contains the content of the specification items and keep it in sync and even release it.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/8#note_130566
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250908/c0e30bd0/attachment-0001.htm>