Comment 11 for bug 586893

Nikita Vetoshkin <email address hidden> writes:

> I assume that a new plugin for connman must be implemented and
> corresponding feature added to indicator-network? Is it right?

Yes, this is correct.

> Kalle, could you please write a sort of guideline: what doors can we
> knock, where else can we ask or, perhaps, where someone can start
> implementing this feature?

For connman we need a plugin for each VPN method. Here's the openconnect
pluging which is in connman:

http://git.kernel.org/?p=network/connman/connman.git;a=blob;f=plugins/openconnect.c;h=2ddb9046ef2a5f894412819ab36bb71d0e1d7a96;hb=HEAD

I think it would be best start asking for advice in implementing a vpn
plugin in the connman list:

http://connman.net/community

In case upstream doesn't take the plugin it can be also packaged
separately, but I haven't tested that yet. Naturally I recommend
submitting the plugin upstream first.

When we have a connman plugin ready, the next step should be adding VPN
support to the cmcc command-line tool in indicator-network package. Once
that is done, we should start thinking how to add it to the Network Menu
and Network Settings.

I hope this helped. And feel free to ask more advice.

--
Kalle Valo