Morgan Briggs
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Dear Jean and Mark, We welcome the commitment in your recent respective updates at the Town Hall to having an open and inclusive conversation and to define an action plan in order to understand issues related to EDI at the Turing Institute. In your comments during last Monday's Town Hall, you said the Institute is at a critical moment of making **choices** to align with Turing 2.0. We believe strongly that one of these choices should be to follow through on longstanding commitments to prioritise equality, diversity and inclusion (EDI) and take clear, deliberate actions to achieving true diversity and inclusion at the Institute. EDI is integral to [the Turing 2.0 strategy](https://www.turing.ac.uk/sites/default/files/2023-03/turing_2.0_-_institute_strategy_-_final.pdf) as it has been embedded thematically across the strategy. To be clear, it states: "To make the great leaps in research that we aspire to, we promote and embed equality, diversity and inclusion in all of our functions and activities. Our EDI Strategy details our commitment to how we are tackling this challenge through our roles as an employer, a research institute and a national leader" (p. 23). The Institute made a decision to prioritise EDI, making it one of the ten principles of the Turing 2.0 strategy, which has been welcomed and endorsed by our funders and stakeholders. As you continue to make choices about aligning the Institute with Turing 2.0, we continue to ask you to remember and *actively* honour the EDI commitments outlined in the strategy. During the Town Hall, the need to have diverse teams of scientists to achieve Turing 2.0 was mentioned. However, this diversity must not begin and end with teams of scientists. It must also include senior leadership. The strategy's positioning of our value as a national institute and as a national leader states that "Our remit is one of national leadership, . . . This leadership extends not only to science and innovation, but also to . . . leading on issues of equality, diversity and inclusion (EDI)" (p. 13). It was mentioned in the Town Hall that there is a "perceived lack of trust" in the Turing's leadership from the Turing community and no clear understanding about its source. We feel a major source of this loss of trust stems from the appearance of failure by the Institute to uphold the EDI principles on which it was founded. The Institute has expressed commitment to a number of charters including Athena Swan and Stonewall; however, little, if any, work has happened relating to these charters over several years. The frequent claims made in Institute communications and annual reports about our commitment to EDI ring hollow when there is little evidence that these principles are being actioned in any meaningful way. In light of this, we believe committing to and following through on the below concrete actions and commitments from the Executive Leadership team, built on the requests in the [open letter](https://hackmd.io/VbX3jhVwQJy_hAAIpuofNg?view), is a step towards restoring trust. **We kindly request confirmation by EOD 20th of March that the following will be included as part of an action plan to be shared with the community:** - Provide a full and reflective accounting of the recruiting, interview, and hiring process for the four new directors and explain clearly why the four chosen candidates reflect no apparent gender diversity. This account should include an acknowledgement that the Institute's EDI goals were not met with these hires and a commitment to remedy the process to avoid a similar result in the future. Furthermore, this should outline how, and if, this process has been consistent with other senior hires, especially those who are members of the Board and ELT, and other hiring decisions that senior leaders have been involved with. - Update the Turing's governance documents to require benchmark hiring goals at all levels of the hierarchy and mandatory reporting of progress towards these goals for greater transparency and accountability (incorporate target setting based on new benchmark data). - Expand EDI policies and frameworks to include requirements of Equality Impact Assessments when recruiting for all positions, including senior positions, and ensure the EDI Action Plan is extended past its end of 2024 expiration date - Enforce the mandated diversity training for the Turing Board of Trustees and the Executive Leadership Team detailed in the EDI Action Plan 1.5. - Express commitment to include an EDI representative (either a member of the EDI team or a Chair of an EDI Network Group) on all senior management hires. - Clarify how EDI Network, EDI Chairs, and EDI Advisory Meetings feed into ELT and decision making processes. - Provide in writing a commitment to immediately begin working with the Turing community, both staff and stakeholders, including the EDI Network Groups, on how to repair trust and build a truly inclusive work environment. - Additionally, we expect the forthcoming action plan to be fully implemented, not only in the recruitment of any mission leads for each grand challenge, but also in the individual recruitment of all the junior researchers that will sit under the grand challenges. This new round of hiring is an opportunity for senior leadership to demonstrate a concrete application of the Turing values, and we will expect and demand a high degree of transparency into the process and outcomes of selecting mission leads and the teams that will support the delivery of a key component of the Turing 2.0 and in alignment with the principles it outlines. While we hope to work together to restore trust and to continue to promote open and cordial relations between the Turing's leadership and staff, it is a matter of urgency that these issues be addressed to ensure that the Turing community feels heard and that our concerned external partners are promptly assured that the Institute takes equality and diversity seriously. We respectfully request an open and substantive response by the deadline stated above. In the event that this deadline is not met, the community will be consulted as to further collective action needed to protect the institute and its reputation. We look forward to hearing back from you regarding the above points and continuing to discuss this important topic openly and collaboratively to work towards more inclusive and diverse representation at The Alan Turing Institute. Sincerely, Members of the Turing Community

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully