Update meeting-notes.md for Gabin's 1:1 with me

[malvikasharan]

Store notes here

[malvikasharan]

• CoC issue
• DCE Community Project
• Monthly Newletters

[malvikasharan]

CoC

• Adapted a CoC for ADViCE, have contacted legal and will follow up, don't have a response yet
• Have a deadline for next week: Making knowledgebase live
  • Change the name to "Term of Participation" - communicate with the team
  • It is not a legal document but addresses the need to have a way to set norms and receive reports
• Report handling team don't have to have representation from all partnering organisation - but all stakeholders should know and approve
• Report handling team should have more than 1 person - definitely GK

[malvikasharan]

Newsletter:

• Coordinate with Alice and collect info for the newsletter
• The first newsletter is sent - Alice is handling it, and Gabin will be taking a tutorial for backup
• Are you archiving it on GitHub? There is no auto-archiving, TPS members manually archive on GitHub
• Useful for communicating with people who have not already subscribed and reporting about the progress
• It is sent external members

[malvikasharan]

DCE Community Project

• Started reformatting how DCE is communicating
• Rather than having a static page, have a dynamic way to present community information - GitHub project board for public access to what we are doing at a given time
• trying to put everything on Project board - once this becomes a habit, it will be easier
• Creating and tagging issues that the community can engage with
• Some (senior) folks can't/don't engage with GitHub infra - PMU have shown a lot of support
• This is a standard, unfortunately -- things could be easier if we all use the same place to share updates
• Use GitHub to make things open and transparent
• Not naively thinking that everyone will engage but at least get people on board
  • creating some level of curiosity so people do what is in their interest
  • AI UK is a massive work -- if we don't make it open, we will lose them
    • What is stopping us from putting this out? - want to get approval from the theme lead
    • Can you create an issue with a summary of what to expect from a demo - collect notes there for folks who are not attending
    • AS and FM are your biggest champions in demo-ing the open behaviour
    • If others are afraid of speaking in public, support them - be their champion -- provide them ways to share their thoughts

[GabinWK]

Previous

• CoC issue
  Solved. Moved to less prescriptive "Participation Guidelines"
• DCE Community Project
  Moved to Projects features. Not yet visible for MS
• Monthly Newsletters
  Started archiving old issues.

Current

• Retro on AI UK - the workshop went well - recorded in the delivery meeting report
• GK to review Balance TPS / DCE commitment.
• Engaging with Team Leaders and aligning themes' vision with a community engagement strategy
• Engaging (DCE) with E&S GC, under which terms? what are the boundaries at this initial time where remits aren't clearly defined
• DCE and Open science tools. Look at intersecting DCE and TPS ( TTW?)

[GabinWK]

Previous

• DCE Community Project
  • Moved to Projects features. Visible ?
• Monthly Newsletters
  • Started archiving old issues. Completed
• GK to review Balance TPS / DCE commitment.
  • In progress
• Engaging with Team Leaders and align themes' vision with community engagement strategy
  • In progress
• Engaging (DCE) with E&S GC, under which terms? what are the boundaries at this initial time where remits aren't clearly defined
  • Clarified
• DCE and Open science tools. Look at intersecting DCE and TPS ( TTW?)
  • Pending

Current

• RAM/RCM workflow
• Blockers : accreditations
• IEEE workshop
• ADViCE community . Opportunity RAM/RCM joint work

[malvikasharan]

Notes:

Newsletter archive

• Thank you: Zenodo link seems to be broken: Create newsletters.md to archive notes dce-community#17

DCE & E&S

• Had a chat with Cass, she will talk to Sam
  • GK to talk to both after 3/5
• Relation to be clarified in the coming time

Open source licensing

• We discussed open source for high-profile projects
• Looked into CLA, examples from Redhat, git and other projects could be good places to look for real-world cases
  • Legal team has asked to look at it again. Discussions in course, will update on that.
• Chapter from The Turing Way is very comprehensive - https://the-turing-way.netlify.app/reproducible-research/licensing

RAM/RCM overlap

• This is very interesting work!
• Would love to see an example from E&S (asking Cass and Alden to a case study)

[GabinWK]

• Putting in place communication DCE - Bridge AI, and DCE - TRIC DT:
  • DCE- Bridge AI:
    • RCMs to meet monthly using TPS coworking time slot
    • shared documentation on respective programme/projects to envision attending/creating common knowledge sharing events
    • DCE and Bridge AI share the same Project Coordinator thus facilitating engagement
  • DCE - TRIC DT:
    • DCE humanity & SC Theme Lead engaging with TRIC DT senior researcher on potential collaboration
    • DCE RCM/RAM and TRIC DT RAM to start meeting regularly
    • DCE - TRIC DT to harmonise calendars of community meetings and create space for respective communities to engage with one another
• DCE's EDI strategy:
  • Turing team (Amy) supporting DCE's strategy (alignment with institute's plans and resources, training, knowledge sharing, good practices
• Challenges in organisation of IEEE workshop ( keynotes speakers availabilities, authors, calendar deadlines)
• GK asked to look at call with possibility of international outreach, with involvement of LRF https://www.rai.ac.uk/funding/skills?mc_cid=0e6b43a598&mc_eid=3b8be30fc1