Move conda-pack out of constructor team governance

[ryanskeith]

conda-pack is currently under the constructor team maintenance. This feels out of place as it is more of an environment management tool then an installer like tool.

I propose that it is moved under another team (maybe a new team) that deals with projects that deal with conda environment tasks.

[DaveKaretnyk]

I'm new here. I cannot judge the implications of moving governance out of the Constructor team. I can say that where I work both Constructor and conda-pack are used as core parts of the installers we build. In the case of conda-pack, it is wrapped up in an Inno installer which is then used to install on target systems. Our use is primarily, though not exclusively, on Windows.

[xhochy]

I'm a bit indifferent here as I'm a member of neither team, but still seem to be the main reviewer on this project. The main argument initially was that this is a different form of installation, and thus should eventually share a bit code with the remaining constructor work.

[jaimergp]

I'm in favour of splitting responsibilities, because in practice that code sharing didn't happen, and the people working on each project are different. I can add a request for a conda-pack team in conda/governance and add you there, @xhochy. WDYT?

[xhochy]

That sounds right! Please also add @ryanskeith as he is currently doing the majority of the work here.

[danyeaw]

Hi @jaimergp, did you get the chance to open a conda/governance item for this? Could I help out to get it going? Thanks!

[jaimergp]

Opened conda/governance#337