Closed m-mohr closed 1 week ago
I would be happy to help too.
Not knowing much about GitHub but your suggestions above seem to make sense (as does #29)
Thanks Matthias. Happy for you to re-organise as helpful to the team - let me know if there are specific items I can help with.
@avalentino I've completed all the basic tasks, but feel free to take over any of the CI related work.
Sorry - appears when I merged it closed this!
No worries, not your fault. It's a GitHub thing ;-)
@m-mohr Adding this discussion from #32. This does seem like a future topic, and perhaps needs a bit more context and a specific use case to work out if machine readability is desired, and if so how best to implement.
Looking down the track, another question: could this approach be used to automate the process in other useful ways? e.g. does this make the PFS more machine readable, opening up the possibility of scripting or tools reading the PFS directly?
Good question, in principle we could even move away from Markdown and generate this even more automatically from some kind of e.g. YAML files that are a bit more structured. And also we could actually generate them from individual building blocks so that they may only be written once and are re-used in the PFSes. But maybe that's a step for the future...?
I'm running into more and more issues with Markdown. The Markdown syntax is too simple for what we are trying to achieve here, especially with vasts amounts of tables. => #38
As partially discussed during the last meeting, here are some proposals how we could improve this repository:
Happy to help to set this up if people are happy with the proposals.