Suggest Changes to APE0: term limit for Coco, remove "only one Coco member per employer", allow returns officer to vote, for group of projects to share Ombuds duties

20 views
Skip to first unread message

Moritz Guenther

unread,
Nov 4, 2023, 6:29:49 PM11/4/23

Hi,

I want to suggest several changes to APE0, but I think it's easier to keep track in one location, so I'm describing them all in this email. I know that we usually discuss APEs on the mailing list first in general terms, but in this case I think it's easier to have a suggested text to look at, so I've gone ahead and opened a PR: https://github.com/astropy/astropy-APEs/pull/89

Let's discuss what we think here by email or on that PR. Since this is a modification of APE0, the voting members will eventually have to vote on these suggestions and I think they should be voted on separately so that you can agree with one and disagree with the other, but to make it more convenient to discuss I've put them in the same PR.

I've discussed all these suggestions with different people on different occasions and I want to thank all of them for their input. In the current form, there is no "author list" for this PR, since it's just a bunch of changes to APE0, but, if any of these changes are accepted, we might want to add people to the author list of APE0 as appropriate.

Moritz


Coco: Only one person from each employer, unless...

I believe the original motivation for the requirement was to prevent any one employer to take over Astropy by stuffing the Coco with their staff. I think our experience has shown that this is trying to solve a problem that does not exist. Coco members act as individuals and not as representatives of their employer and the community will only vote for people they trust. On the other hand, large employers have very different centers, e.g. "a NASA employee" might be someone at a NASA center such as JPL or work thousands of miles away at NASA headquarters, so I don't see why we could not have two Coco members from the same employer. Then, there are centers where people might share an office but technically have separate employers (e.g. SAO/Harvard, or a faculty member on sabbatical at a different institution). Thus, this rule does not guarantee the diversity of the Coco - it's up to the members to vote in the right people.

Note that this change also removes the "unless it would be short of candidates otherwise" exception. While I initially suggested it, I now thinks it's a bad idea to have such an exception. Astropy is big enough that we can find candidates if we try. Having such an exception just reduces the motivation for the leadership to look to the right candidates and motivate them.

Term limits for Coco

Instead of a "only one per employer" rule, I suggest a limit of one consecutive term. This will guarantee that the membership regularly chooses new leaders and that no one (and not any one institution) can dominate Astropy for too long. I do think people can be re-elected after a while, but it is important to cycle in and out of power to prevent a situation where Astropy relies too much on any one individual and that person becomes so crucial to running Astropy that, should that person leave the Project or take a different career, the Astropy Project itself suffers.

This is equally about team building and growing our capabilities. One of the most effective ways to "be part of the project" and "be really involved" is to be part of a leadership group such as the Coco that regularly meets to discuss issues. The Astropy project as a whole can only profit from having more people involved in that way; and once involved as Coco members, that experience stays with the project after the end of their term. Former Coco members are available for re-election after some time period or to help and advice in other roles. The fact that Coco terms are already staggered under the current APE0 guarantees that there is continuity and sharing of experience.

returns officer for votes

Currently, we require the return officer for Coco election to be "non-voting". I suggest to remove this restriction. In practice, that means that we've always asked NumFOCUS staff to act as our returns officer and that is just additional complexity in organizing for little benefit. They don't have direct access to the list of email addresses for voting members, they don't know the timelines for APE0 by themselves, and they are not always available, e.g. we had to reschedule the 2023 Coco election because it happened too close in time to the NumFOCUS summit. So, in practice, we have to say "take this text and input it in this field, then press that button". On the other hand, there is nothing to gain from having the return officer be non-voting. The current APE0 does not specify that the returns officer is "external" or "neutral", only that they don't vote themselves, so it could be a project member, they just have to abstain from voting. As long as we use a secure voting system like helios where all voters get a receipt and can check the hash to see that the vote is counted correctly,it does not matter if the return officer is voting themselves or not; and if we use an insecure system (e.g. "just send a slack DM to the returns officer") then the returns officer could cheat weather or not they vote themselves.


Share Ombudspeople between projects

It is hard to find qualified people for the job of Ombudsperson. Most if us join Astropy to code and advance research, not to mange interpersonal conflicts. That also means that most project members don't have experience or training in this role and, fortunately, the number of serious incidents is low, so that there is not a lot of on-the-job training either. On the other hand, the stakes are high, so we do not want to fill the Ombudsposition lightly.
At the same time, I believe that this really should not be any one person, but a group of people who perform the Ombuds duties together. In that way, they can discuss amongst themselves and in confidentiality any ethics concern or Code of conduct violation. A discussion between several people will almost certainly lead to a more balanced view than a single opinion. It also provides a back-up should an issue arise with the Ombudsperson themselves. If there is a group, an issue could be reported to other members of that group and the person accused can recuse themselves.

So, how do we find a group of Ombudspeople? I suggest to join forces with other NumFOCUS sponsored or affiliated projects and form a joint group of ~5 projects where each project sends one representative and then the 5 of them together act as "Ombuds" for all projects. I have discussed this idea at the NumFOCUS level and several other projects are interested. However, there is chicken-and-egg problem here: Until such a group exists, nobody can change their rules to join it, and as long as no project sets up their rules to join it, it won't exist. Thus, I'm suggesting changes to APE0 to empower the Astropy Ombuds to start / join such a group.

Reply all
Reply to author
Forward
0 new messages