Creation of `constructor` maintenance team about governance HOT 19 CLOSED

Okay, while we're waiting for Anaconda IT to increase the seats for the conda organization, I've added a number of people already in the new constructor team in the conda org.

So far missing there are:

• @hoechenberger
• @larsoner
• @hmaarrfk

I'll add them as soon as I can.

from governance.

I'm gonna close this ticket since I believe we've finalized everything via the @conda/constructor and @conda-incubator/constructor teams. Thank you everyone for volunteering!

Once conda.org exists we can revisit listing the status of the various projects as @beckermr suggested in #53 (comment).

from governance.

More anaconda folks added!

from governance.

Done. Most of the folks there need to accept invites to this org.

from governance.

Thank you so much, Matt!

from governance.

No worries, I couldn't respond quick enough with what the current status of my research on the Anaconda side was. Thank you @jaimergp and @beckermr for the initiative!

So I basically poked the bear a bit at Anaconda and looked into how we could make this happen in a simple way. To give some context, the governance policy describes projects like constructor etc quite nicely as "federated projects" which may be transitioned from their federated, non-community maintenance model to being community projects if the current maintainers (Anaconda) want that.

And so I've asked in the various teams at Anaconda that have worked on and with constructor etc in the past and I have received approval for the transition of these projects to community projects. 🥳

In addition to the original team list posted by @jaimergp above, the following people should also be added to the new project team:

• @bkreider
• @mcg1969

Regarding the teams in the conda-incubator and conda organzations:

Until we have cleaned up the GitHub team maintenance (semi-blocked by #51), I suggest to basically mirror the team on conda-incubator (being the source of truth) to one in the conda organization, to facilitate actual write permissions to the projects in the conda org. This is more of an intermediate step for a larger team management alignment that is needed, FWIW.

from governance.

Ah, dang, I'm gonna have to continue inviting people to the team over in the conda org next week when IT has increased the number of seats:

from governance.

Okay, the seats were added and I've invited @hoechenberger, @larsoner and @hmaarrfk as well to the constructor team in the conda org. Welcome everyone and thank you for volunteering!

I'm not sure if there is anything else needed, but I think this concludes the transition of the various projects from federated to community project status.

@beckermr @jaimergp Can you think of anything else needed to formally do here?

from governance.

I've added you here. @jezdez can sync to anaconda as he has time and energy

from governance.

@goanpeca @beckermr Done!

from governance.

I'm looking forward to helping make constructor better together with all of you!!

from governance.

@conda-incubator/steering do we want this team to live here or in the conda github org?

from governance.

I think for now it will have to live in both orgs for technical reasons. I'd be inclined to consider conda-incubator as the authoritative source of truth, and conda replicating the list there, manually for now.

from governance.

OK. We need to solve this problem at a technical level when folks are ready. I agree that for now conda-incubator is easier to have as the source of truth.

from governance.

My apologies here! If there is anything I can do to make things better let me know!

from governance.

Adding those folks now!

from governance.

Thank you, @jezdez!

from governance.

We should list the status as community in the repos on the the conda org.

from governance.

I would also like to be part of the constructor/menuinst maintenance team if there is still room for more. :)

Thanks!

from governance.