Add new project team for pytest-conda-solvers

[danyeaw]

Hey all,

@jaimergp posted in conda-incubator/pytest-conda-solvers#11 that pytest-conda-solvers had lost its maintenance team. Since @agriyakhetarpal was going to work on the project, he gave him write access. I was also given triage access which was requested in the same issue.

Here is the current access:

Notice that the conda-incubator/conda-libmamba-solver group has read access, which doesn't give them any special permissions for a public project.

Our other conda-incubator projects typically have a Project Team for the project. I propose we create a new Project Team and include the 3 folks that have had recent contributions:

1. @jezdez
2. @jaimergp
3. @agriyakhetarpal

That Project Team would then get Contribute access, and we would remove all other access (including my triage access).

There is also a request here for access by @ryanskeith: conda-incubator/pytest-conda-solvers#68 and also I understand that @travishathaway was looking for access to help as well. I think once the Project Team is created, then that team can decide if they want to add a few more folks that they trust (after requesters open an issue).

[travishathaway]

Hi all,

I just wanted to leave a comment here publicly expressing my interest to join this team and help develop pytest-conda-solvers.

Thanks!

[jezdez]

Notice that the conda-incubator/conda-libmamba-solver group has read access, which doesn't give them any special permissions for a public project.

Note, this is most likely a bug when the team was added, as that's the default GitHub permission level at the time, but the people working on it (Jaime and me) had commit permissions due to org permissions. Klaus was removed again after he stopped working on it.

[jaimergp]

Thank you for opening this issue, so we can clarify the decisions I made in conda-incubator/pytest-conda-solvers#11, thanks. It's also helping me see that the governance docs could be a bit clearer in the project lifecycle, team charters and so on. I'll work on that separately.

Jannis' point made me understand that I should have created a project team back then instead of taking temporary shortcuts, and that has to be reverted. So instead, I propose we revert the team composition to the subset of conda-libmamba-solver that had contributed to the project so far (i.e. Jannis and I).

We can revisit the decision to add Agriya and others to the team once Jannis and I have discussed what our thresholds for solver experience are for this project, since it's vital that we get this right. Otherwise, as we are seeing on the ongoing reviews, we may end up with a green CI full of inaccurately passing tests.

[travishathaway]

@jaimergp,

Please let me know as soon as I can formally request membership here. Will be happy to join the team to help maintain this project.

[jezdez]

I support what Jaime wrote

[danyeaw]

Changes made:

1. https://github.com/orgs/conda-incubator/teams/pytest-conda-solvers
2. pytest-conda-solvers is updated so that @conda-incubator/pytest-conda-solvers has maintainer access, others are removed

[agriyakhetarpal]

Hi all, I didn’t realise it at the time – but while trying to push some commits from my work last week to my PRs at conda-incubator/pytest-conda-solvers#50 and others today, I encountered a 403 error. Since my write access to the repository has been revoked in light of this governance decision, I am no longer able to push to those PRs.

I would have been okay with reopening these PRs from a fork, but unfortunately, that isn't ideal right now for a couple of reasons:

• it creates unnecessary churn with reviews, as the comment history would need to be referenced elsewhere.
• my series of PRs relies on GitHub's Stacked PRs (previously private, now public) feature, which does not work with PRs from forks yet

May I request some form of temporary write access as a special measure—even as an outside collaborator for now, if not on the conda-incubator/pytest-conda-solvers team—so that I can write to my existing stack of PRs until they are merged? Of course, I can then use a fork for future contributions post these PRs. Thanks for your consideration!