alan-turing-institute / tric-dt

Open Project Pages for the TRIC-DT
Other
5 stars 0 forks source link

Update README #17

Open cassgvp opened 1 year ago

cassgvp commented 1 year ago

The intention is for this repo to be relevant to all work of the TRIC-DT, and not just the Hub. As such the README should reflect all TRIC-DT interest/activities, but managed by the Hub.

The readme has been copied from a TRIC-DT-Hub repo. This needs to be reviewed for appropriate content and updated to contain all relevant community information. Suggestions for inclusion here on Open WIN (via OLS).

cassgvp commented 1 year ago

Hi @ZGGhauch !

I've just updated the README with some basic details and placeholders 🥳. As discussed, we'd love to hear your feedback on what useful information we could include in there? Lots of the detail is missing, but your early thoughts would be great!

Feel free to comment on this issue or submit a PR with any suggestions for changes! Thank you!

cassgvp commented 1 year ago

@aranas Would you like to add something about your seminar series to the REAME? Perhaps in the CONTRIBUTING section?

kallewesterling commented 1 year ago

This issue is too broadly formulated to ever get closed, and as such, needs to be split up into smaller, resolvable issues. Alternatively, we can keep this issue open as a meta-issue linking to the other issues, so we can track progress for updates on the README file.

chrisdburr commented 11 months ago

This issue is too broadly formulated to ever get closed, and as such, needs to be split up into smaller, resolvable issues. Alternatively, we can keep this issue open as a meta-issue linking to the other issues, so we can track progress for updates on the README file.

Agreed. @cassgvp, please can you update the README to a place you're happy with, add the changes here and then we can close this issue? Any specific future updates can then have new issues.

cassgvp commented 11 months ago

Only thing missing is a link to the knowledge commons jupyter book (currently links to #6). This issue can be closed after that has been added!