Hello everyone, I found it difficult to understand exactly what this document is saying, so please correct me if I'm wrong, but it seems to state the default position for research computers will be that researchers won't have administrative access to their own computers. Exceptions to this can be requested through a process that, in the document itself, is acknowledged to need improvement, and it is warned that the ability to request this capability may not always be provided. As has been discussed already in this group, this would be profoundly detrimental to the research and teaching objectives of this university and so I am opposed to this. The justifications given for this (e.g., Cyber Essentials qualification, automatically shipping devices to users) strike me as either straw men arguments or things that we already have. I realise that's quite a blunt statement; I appreciate there is more subtlety to the argument than this. Cheers, Will --- Measuring phylogenetic structure? Try install.packages('pez') Will Pearse (pearselab.com) <http://pearselab.com/> (he/him) Senior Lecturer, Imperial College London Department of Life Sciences LGBTQ+ champion On 30/11/2022 10:38, David Colling wrote:
FYI ...
Please feel free to send comments ... I have a very busy up to the meeting this afternoon and will not have really enough time time to scrutinise the attached (so far I have not even had a chance to open it) so your comments will be very useful.
Best, david
-------- Forwarded Message -------- Subject: FoNS Device Management - Defining a research devices and user group Date: Tue, 29 Nov 2022 18:22:48 +0000 From: Joannou, Ingrid <i.joannou@imperial.ac.uk> To: Hanham, Neil A <n.hanham@imperial.ac.uk>, Prescott-Jones, Steven <s.prescott-jones@imperial.ac.uk>, Taylor, James A <james.a.taylor@imperial.ac.uk>, Willson, Thomas H <t.willson@imperial.ac.uk>, Colling, David J <d.colling@imperial.ac.uk>, Bresme, Fernando <f.bresme@imperial.ac.uk>, Jaffe, Andrew H <a.jaffe@imperial.ac.uk>, Harrison, Nicholas M <nicholas.harrison@imperial.ac.uk>, Bearpark, Michael J <m.bearpark@imperial.ac.uk> CC: David Colling <david.colling@gmail.com>, Pengelly, Ellen <e.pengelly@imperial.ac.uk>, Richards, Andrew <a.j.richards@imperial.ac.uk>, Villamil, Juan <juan.villamil@imperial.ac.uk>
Dear All,
Apologies for the late sending of this.
Attached is a draft proposal based on some of the discussion so far. We are hoping this can be the basis for our conversation tomorrow with the aim to define further that middle layer of research machine.
David, please feel free to forward to anybody else that you think might need to be included in this discussion.
Kind Regards,
Ingrid
Dear All,
I hope you are well.
As per our previous meeting, I am setting up this meeting so we can follow up on defining the research devices with services used and user group for FoNS.
A few of us will be on site for this meeting so I have added the room number in ICT but also happy to go to you if you can book a room for us?
Kind Regards,
Ingrid
________________________________________________________________________________
Microsoft Teams meeting
*Join on your computer or mobile app***
Click here to join the meeting <https://teams.microsoft.com/l/meetup-join/19%3ameeting_MmFlNzM4YWEtMmRhNy00ZjQ2LTllNTAtMTU5ZTg3NGQ1YzZk%40thread.v2/0?context=%7b%22Tid%22%3a%222b897507-ee8c-4575-830b-4f8267c3d307%22%2c%22Oid%22%3a%22add04a20-8545-483d-b58c-3bdaef4ca508%22%7d>
Meeting ID: 328 697 732 543 Passcode: CgLPAv
Download Teams <https://www.microsoft.com/en-us/microsoft-teams/download-app> | Join on the web <https://www.microsoft.com/microsoft-teams/join-a-meeting>
Learn more <https://aka.ms/JoinTeamsMeeting> | Meeting options <https://teams.microsoft.com/meetingOptions/?organizerId=add04a20-8545-483d-b58c-3bdaef4ca508&tenantId=2b897507-ee8c-4575-830b-4f8267c3d307&threadId=19_meeting_MmFlNzM4YWEtMmRhNy00ZjQ2LTllNTAtMTU5ZTg3NGQ1YzZk@thread.v2&messageId=0&language=en-GB> | Legal <https://www.imperial.ac.uk/media/imperial-college/administration-and-support-services/secretariat/public/ICL---Events-privacy-notice---10-October-2018.pdf>
________________________________________________________________________________