You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readme looks useful, however it is totally outdated with a lot of presentations missing. So we either need to
at minimum, add a link to zenodo, or the other places where there are more recent slides/etc.
keep the repo up-to-date and add a new line whenever a new entry is added to the content. while I don't feel that this is the right platform/location for the actual slides, keeping track of abstracts and list of talks (with list to the slides elsewhere) would potentially be still useful.
come up with a way to auto generate a README/TOC
OR
delete the current content of the readme and write up a very generic overview in a paragraph or so. At the end of the day the naming of files/directories are should be clear enough.
The text was updated successfully, but these errors were encountered:
I think I agree with the second approach @bsipocz - it would make sense to have things listed in files in the repo maybe instead? Or a shared spreadsheet link which is easier to organise.
@aleesteele I think we have one of these already IIRC, could you update the Readme with it?
Since I wrote this issue it became apparent that it's in fact the repo that's missing the presentations rather than the readme being totally outdated with the repo's content.
So maybe just a sentence or two that links to a good zenodo search for the newer slidedecks would suffice.
The readme looks useful, however it is totally outdated with a lot of presentations missing. So we either need to
at minimum, add a link to zenodo, or the other places where there are more recent slides/etc.
keep the repo up-to-date and add a new line whenever a new entry is added to the content. while I don't feel that this is the right platform/location for the actual slides, keeping track of abstracts and list of talks (with list to the slides elsewhere) would potentially be still useful.
come up with a way to auto generate a README/TOC
OR
The text was updated successfully, but these errors were encountered: