Mission Center auto-connection requests

store-requests
21

To summarize up to this point, votes for auto-connection are as follows:
hardware-observe +1 @alexmurray
network-observe +1 @alexmurray
system-observe +1 @alexmurray
process-control +1 @alexmurray -1? @jslarraz
network-manager +1 @alexmurray

Is there any other information that I can provide to help the process along?

Thanks everyone for the quick feedback, really appreciate it

22

Hey @kicsyromy

I think we can say votes currently are:

hardware-observe +3 @alexmurray @cav @jslarraz

network-observe +3 @alexmurray @cav @jslarraz

system-observe +3 @alexmurray @cav @jslarraz

process-control +1 @alexmurray

network-manager +2 @alexmurray @jslarraz

network-manager: although network-manager-observe looks more appropriate for the use case, the interface does not fulfill the snap requirements in its current form. Thus, +1 from me for auto-connecting `network-manager for now.

process-control: considering that there are similar applications auto-connecting process-control I will also give it a +1 if the snap description is updated to make this functionality (killing processes) more evident.

Thanks

23

PR to add GetDeviceByIpIface method to network-manager-observe created in snapd upstream

1 Like
24

Thanks for the summary.

Sure thing, I’ll update the Snap description to mention terminating and stopping processes.

EDIT: I’ve updated the description

25

Thanks @kicsyromy

Then +1 also from me for auto-connecting process-control

hardware-observe +3 @alexmurray @cav @jslarraz

network-observe +3 @alexmurray @cav @jslarraz

system-observe +3 @alexmurray @cav @jslarraz

process-control +2 @alexmurray @jslarraz

network-manager +2 @alexmurray @jslarraz

The request will proceed at the end of the voting period

1 Like