(Current draft Code of conduct)
Tthe 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 , so we are currently developing and have adopted a code of professional conduct for LSST:UK. The current draft It is based heavily on that of for the LSST Dark Energy Science Collaboration, but it may be amended, better to reflect with some minor amendments reflecting our needs and the UK environment. In due course, agreement to adhere to that code will be part of the process for applying of PI status, and that status may be revoked for violations of the code. It is important, therefore, that we get this right, but, equally, we want to start to enjoy the benefits of having such a code sooner, rather than later, so we are rolling it out in stages.
That started in January, when Tim Naylor emailed the lusc-announce list to note that Kathy Romer (romerATsussexDOTacDOTuk) and Albert Zijlstra (aDOTzijlstraATmanchesterDOTacDOTuk) had agreed to serve as our first Ombudspersons,
The current version of the Code is v1.0, which was approved by the Consortium Board on 2017-09-13.
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. A list of those who have affirmed adherence will be maintained here.
Ombudspersons
Under the terms of the Code, the Consortium has two Ombudspersons, with whom consortium members could discuss any aspect of behaviour by another consortium member that they consider to be inappropriate. They are currently Kathy Romer (romerATsussexDOTacDOTuk) and Albert Zijlstra (aDOTzijlstraATmanchesterDOTacDOTuk).
The second stage is trialling of the code of conduct for meetings. Central to that is the appointment of two Points of Contact for each meeting, who are available for consultation should issues arise during the meeting. Taking on the Meeting Point of Contact
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 approachability criterions implies that the most senior members of the community may not be suitable choices, lest meeting attendees are 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. They will include the names of the MCPs 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.
Taking on the MCP role is a significant commitment and we do not want it to impact unnecessarily on the scientific benefit that the MPoCs 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 o to the meeting organisers or to any member of the Executive Group present during the meeting. Since this is a draft code, that has not yet been approved by the Consortium Board, we cannot require you to adhere to it during LSST:UK meetings, but we request that you do, so that we gain experience of operating meetings under the conditions specified by the code. The meeting organiser will give the names and contact details of the MPoCs by email in advance of each meeting and at the start of each meeting, and it will be assumed that you have agreed to be bound by the code if do not tell the meeting organiser by that point. Once a version of the code has been approved by the Consortium Board, an announcement to that effect will be made on the lusc-announce email list and the information on this page will be amended, accordingly.