Open anenadic opened 1 year ago
We can also consider other formats - e.g. JSON instead of CSV?
Personally, I think we should go with something like JSON or YAML. This is hierarchical data that needs a corresponding nested data format.
The design of the initial application is not yet defined. However, it is likely that the backend will be build using either Strapi or Flask. In either case, the schema will be ported across from the Google Sheet into whatever framework is used. It will then be accessible in the repo as json
, and can be tagged to track changes.
In the meantime, we can continue to use the Google Sheet (https://docs.google.com/spreadsheets/d/1M8f9luJrc3w4rz4lD-cEpJUfi6qigh9PBk7Fm5sq_jQ/edit?usp=sharing) and the associated version control there?
We have the skills as a JSON in this repo: https://github.com/RSEToolkit/rse-competencies-toolkit/blob/main/_data/skills.json so I'd favour using/improving that rather than the Google Sheet (I forgot it was there until last week).
We do need to port the two RSE example profiles out of the spreadsheet though
Upload a CSV version of the competency framework we came up with at the CW23 hack day and tag it v0.1 so we can start iterative work on it and get the wider community to look at it.