Code of Conduct

Code of Conduct Version 1.1

The current version of the Code is v1.1, which was approved by the Consortium Board on 2018-09-10. 

All members of the LSST:UK Consortium holding, or applying to hold, Affiliate PI or Junior Associate status are required to affirm their adherence to the Code, as are other Consortium members who attend LSST:UK meetings. You may affirm your adherence using the JISC Online Survey page.

A list of those who have affirmed adherence will be maintained here

Background

The LSST Project and Science Collaborations have worked hard to ensure that LSST activities are conducted in an inclusive manner that respects the diversity within the LSST community. The LSST:UK Consortium Board is very keen that we should do the same and have adopted a code of professional conduct for LSST:UK. It is based heavily on that for the LSST Dark Energy Science Collaboration, with some minor amendments reflecting our needs and the UK environment. 

Ombudspersons

Under the terms of the Code, the Consortium has two Ombudspersons, with whom consortium members can discuss any aspect of behaviour by another consortium member that they consider to be inappropriate. The current Ombudspersons are Martin Hendry and Andreea Font.

Meeting Contact Persons

The Code requires that there be two Meeting Contact Persons (usually one male and one female) available for consultation should issues of conduct arise during any LSST:UK meeting. The organisers of any LSST:UK meeting must contact the Project Manager (George Beckett) well before the meeting with suggestions for the names of expected attendees they believe to be suitable for the MCP role. These should be approachable people, likely to be sensitive to issues of conduct and willing to act in accordance with the Code, when necessary. The Code requires that MCPs not be members of the Executive Group, while the approach-ability criterion implies that very senior members of the community may not be suitable choices, lest meeting attendees be hesitant to report problems to them.

The suggestions will be considered by the Executive Group, who will then confirm the names of the MCPs with the meeting organisers. The names of the MCPs will be included in material advertising the meeting, along with the dedicated Gmail accounts and Skype Numbers that can be used to contact the MCPs during the meeting. They will also be introduced at the start of the meeting itself. 

Taking on the MCP role is a significant commitment and it should not impact unnecessarily on the scientific benefit that the MCPs obtain from attending the meeting. So, while they are committed to handling any problems that might arise during the meeting, they should not be questioned about the Code of Conduct more generally, since they are aiding its implementation, rather than being responsible for its definition.

Any general questions about the Code of Conduct should be addressed to the meeting organisers or to any member of the Executive Group present during the meeting