Le 04/10/2012 16:11, Andreas Jaeger a écrit :

On Thursday, October 04, 2012 15:38:48 denisart benjamin1 wrote:

...

Wicd is an open source software utility to manage both wireless and wired networks for Linux. Wicd is split into two major components: the daemon, and the user interface. These two components communicate via D-Bus.

I maintain wicd on network:utilities devel project. Wicd is a python software, it seems to be in conflict with networkmanager and others ( but who needs to have several network manager ?).

It's a great alternative to networkmanager, it's light with basic functions. Wicd is already functionnal.

What do you want to mean with "What are your plans going forward with wicd?" ? I don't understand (I'm french) I'm German, so no worries - English isn't my first language either, ;)

My question was: NetworkManager and the scripts are integrated into openSUSE and packages assume that either of them are in use.

What are your goals regarding integration and usage of wicd in openSUSE?

Thanks, Andreas It could be a better alternative to traditionnal but over-dependecies networkmanager and more precisely networkmanager-gnome.

For people wont have gnome as graphical environment, they don't have a choice: they use nm or suse software. Wicd is easy to use, contains just basical functions for basical uses It has not expensive dependencies, works better than nm for wireless connections. It is light and integrate fine with any gtk environment. So my goal is to provide an user-friendly networkmanager for users won't more than an utility to connect on internet. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thursday, October 04, 2012 16:18:16 denisart benjamin1 wrote:

...

Le 04/10/2012 16:11, Andreas Jaeger a écrit :

...

On Thursday, October 04, 2012 15:38:48 denisart benjamin1 wrote:

...

Wicd is an open source software utility to manage both wireless and

wired networks for Linux. Wicd is split into two major

components:

...

the daemon, and the user interface.

These two components communicate via D-Bus.

I maintain wicd on network:utilities devel project. Wicd is a python

software, it seems to be in conflict with networkmanager and others ( but who needs to have several network manager ?).

It's a great alternative to networkmanager, it's light with basic

functions. Wicd is already functionnal.

What do you want to mean with "What are your plans going forward

with wicd?" ? I don't understand (I'm french) I'm German, so no worries - English isn't my first language either, ;)

My question was: NetworkManager and the scripts are integrated into openSUSE and packages assume that either of them are in use.

What are your goals regarding integration and usage of wicd in openSUSE?

Thanks, Andreas It could be a better alternative to traditionnal but over-dependecies networkmanager and more precisely networkmanager-gnome.

For people wont have gnome as graphical environment, they don't have a choice: they use nm or suse software. Wicd is easy to use, contains just basical functions for basical uses

It has not expensive dependencies, works better than nm for wireless connections. It is light and integrate fine with any gtk environment.

So my goal is to provide an user-friendly networkmanager for users won't more than an utility to connect on internet. So, with openSUSE already support nm and the traditional scripts, how do you want to make this integration happen in an easy way inside openSUSE?

Btw. are you coming to the openSUSE Conference?

Olaf and Marius will talk about the network jungle (http://bootstrapping-awesome.org/schedule/#osc-60) and I suggest you three talk a bit more...

Andreas I would like to come on the Conference but i can't :( . I think a branding should be created for a better integretion with environment. An entry in Yast for choose the network manager could be a great thing or, better simply using our own GUI interface for wicd daemon. Basicaly, a few of users use already the package on network:utilities, just purpose

Le 08/10/2012 09:42, Andreas Jaeger a écrit : the package could be a start. Wicd could already supports ipv6 (http://aur.archlinux.org/packages.php?ID=46750) Unfortunately, I don't find any topics whose speaks of advantages of wicd on any others networkmanager. About article from bootstrapping-awesome.org, that makes me say there is real interests to integrate wicd into OpenSuse. But the simple fact that a numerous users use this one would be an argument. Best regards. Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Oct 08, 2012 at 06:52:23PM -0500, Rajko wrote:

On Mon, 08 Oct 2012 17:24:33 +0200 denisart benjamin1 wrote:

...

I think a branding should be created for a better integretion with environment.

Branding is the smallest issue.

...

An entry in Yast for choose the network manager could be a great thing

YaST is based on ycp language that only few people know and they are busy. That means only third party developer can make such addition, but as one has to learn ycp first, it is not likely that will happen.

Since quite some time there are bindings to more popular languages. This allows to use the full infrstructure from python for example. Call for example zypper se yast\*bindings Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

On Tue, 9 Oct 2012 10:39:18 +0200 Lars Müller wrote:

... Call for example

zypper se yast\*bindings

Status of bindings it explained in: http://lists.opensuse.org/yast-devel/2012-10/msg00006.html Martin and Josef were prompt to answer, so anyone willing to take on adding modules to YaST can use answer as a starting point and ask yast-devel@opensuse.org for anything that is not clear. In case of wicd, it is probably better to keep its own configuration dialogs, as its purpose would the last resort help in case of network problems. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le 09/10/2012 01:52, Rajko a écrit :

On Mon, 08 Oct 2012 17:24:33 +0200 denisart benjamin1 wrote:

...

I think a branding should be created for a better integretion with environment. Branding is the smallest issue.

...

An entry in Yast for choose the network manager could be a great thing YaST is based on ycp language that only few people know and they are busy. That means only third party developer can make such addition, but as one has to learn ycp first, it is not likely that will happen.

...

or, better simply using our own GUI interface for wicd daemon. That is actually the only viable way.

...

Basicaly, a few of users use already the package on network:utilities, just purpose the package could be a start. What people have to do to have wicd running? Do you have some example configuration? What works under wicd, and what not? Is YaST aware of network configured with wicd? If firewall working?

...

Wicd could already supports ipv6 (http://aur.archlinux.org/packages.php?ID=46750) Unfortunately, I don't find any topics whose speaks of advantages of wicd on any others networkmanager. About article from bootstrapping-awesome.org, that makes me say there is real interests to integrate wicd into OpenSuse. Article is talking about "something" that should help in the future, maybe even wicd.

...

But the simple fact that a numerous users use this one would be an argument.

A lot of users have opened a topic on opensuse forum. Wicd works without any tipcs or tricks, just install package and an applet is loaded of notifications area. Wicd is lite and a this step, it doesn't support vpn connections but it is the only problem. The daemon works as a backend, I imagine yast could be aware of network with wicd because it used already and robusts tools to establish network connection : wireless-tools, wpa_supplicant,... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 10.10.2012 03:39, schrieb Marius Tomaschewski:

Am 08.10.2012 17:24, schrieb denisart benjamin1: Please note: wicked != wicd

http://bootstrapping-awesome.org/schedule/#osc-60 is about wicked:

http://gitorious.org/wicked/wicked

$OBS/home:mtomaschewski:wicked

There are no plans yet to integrate wicd, but wicked.

On the another side, I think we've to get rid of the NETWORKMANAGER=yes/no variable in /etc/sysconfig/network/config first. Probably, the best way is to use a kind of "network-service" packages (provides) switching between the "suite" managing the network. So when the users choice is to use XYZ, he has to install the service package to disable current one and enable XYZ. Gruesse / Regards, Marius Tomaschewski -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le 10/10/2012 03:39, Marius Tomaschewski a écrit :

Am 08.10.2012 17:24, schrieb denisart benjamin1:

...

...

On Thursday, October 04, 2012 16:18:16 denisart benjamin1 wrote:

...

Le 04/10/2012 16:11, Andreas Jaeger a écrit :

...

On Thursday, October 04, 2012 15:38:48 denisart benjamin1 wrote:

...

Wicd is an open source software utility to manage both wireless and

wired networks for Linux. Wicd is split into two major

components:

...

the daemon, and the user interface.

These two components communicate via D-Bus. I maintain wicd on network:utilities devel project. Wicd is a python

software, it seems to be in conflict with networkmanager and others ( but who needs to have several network manager ?).

It's a great alternative to networkmanager, it's light with basic functions. Wicd is already functionnal. What do you want to mean with "What are your plans going forward

with wicd?" ? I don't understand (I'm french) I'm German, so no worries - English isn't my first language either, ;)

My question was: NetworkManager and the scripts are integrated into openSUSE and packages assume that either of them are in use.

What are your goals regarding integration and usage of wicd in openSUSE?

Thanks, Andreas It could be a better alternative to traditionnal but over-dependecies networkmanager and more precisely networkmanager-gnome.

For people wont have gnome as graphical environment, they don't have a choice: they use nm or suse software. Wicd is easy to use, contains just basical functions for basical uses

It has not expensive dependencies, works better than nm for wireless connections. It is light and integrate fine with any gtk environment.

So my goal is to provide an user-friendly networkmanager for users won't more than an utility to connect on internet. So, with openSUSE already support nm and the traditional scripts, how do you want to make this integration happen in an easy way inside openSUSE?

Btw. are you coming to the openSUSE Conference?

Olaf and Marius will talk about the network jungle (http://bootstrapping-awesome.org/schedule/#osc-60) and I suggest you three talk a bit more...

Andreas I would like to come on the Conference but i can't :( . I think a branding should be created for a better integretion with environment. An entry in Yast for choose the network manager could be a great thing or, better simply using our own GUI interface for wicd daemon. Basicaly, a few of users use already the package on network:utilities, just purpose

Le 08/10/2012 09:42, Andreas Jaeger a écrit : the package could be a start.

Wicd could already supports ipv6 (http://aur.archlinux.org/packages.php?ID=46750) Unfortunately, I don't find any topics whose speaks of advantages of wicd on any others networkmanager. About article from bootstrapping-awesome.org, that makes me say there is real interests to integrate wicd into OpenSuse.

But the simple fact that a numerous users use this one would be an argument.

Best regards. Benjamin

Please note: wicked != wicd

http://bootstrapping-awesome.org/schedule/#osc-60 is about wicked:

http://gitorious.org/wicked/wicked

$OBS/home:mtomaschewski:wicked

There are no plans yet to integrate wicd, but wicked.

Gruesse / Regards, Marius Tomaschewski It's a good news ! Bad news for wicd but I understand there is no place for it. Good continuation !

Regards. Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 11.10.2012 02:02, schrieb Rajko:

On Wed, 10 Oct 2012 03:39:03 +0200 Marius Tomaschewski wrote:

...

There are no plans yet to integrate wicd, but wicked.

Does wicd need integration? Although, I asked few questions, it seems that installation and usage are not complicated and it just works.

Well... let's start from beginning. Currently there is still the NETWORKMANAGER=yes/no variable wich says whether sysconfig/ifup or NetworkManager is in use. We've to get rid of it and solve it differently as it makes problems (see Ferederic's and my mails in this thread), at least in: - to start under systemd (NM start currently shows failure in ifup mode) - to switch between NetworkManager and sysconfig We are going to: - replace NETWORKMANAGER variable with another mechanism - introduce wicked, which will obsolete sysconfig as soon as possible, that is as soons as we've teached it all the tricks. BTW: Wicked also provides a "nanny" with NM like functionality. It is not a big problem to allow WICD beeing installable and use the new mechanizm to enable itself as the "network managing service" [1]. But this is not the end of the "integration" story. With integration I mean also the initial configuration while installation / update (not just a zypper dup, but cd/dvd boot + update), the use on a virtualization host, ... And here are no plans to support / integrate WICD.

It can be included, not as a default, nor as an official option, but as a plan B, for people that have trouble with a plan A (networkmanager, ifup, wicked). It is better to have it, specially if there no other maintenance requirements than security review on a version change.

I'd say this "non official plan B" should be IMO fine, that is [1] (+ "zypper dup" only update), when there is a bugowner/maintainer able to fix (security) issues. But this sounds for me like something for a maintained community (add-on) repository, rather than regular inclusion. Gruesse / Regards, Marius Tomaschewski -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 11.10.2012 15:51, schrieb Luiz Fernando Ranghetti:

...

But this sounds for me like something for a maintained community (add-on) repository, rather than regular inclusion.

Hi,

The community maintained repository is the official one (OSS). Thousand times people (AJ, Jos, etc) say that there isn't distinctiion between SUSE guys and 'the rest' (or community).

Well, true. Basically, I do not decide what gets included in OSS or not and I do not "reject WICD" here (I would reject to become bugowner of it ;-). But when something gets included it has IMO be maintained & supported and in case of a network managing service, it IMO requires integration beyond the bare possibility of a use as network managing service: e.g. boot from some media and installation/update has IMO to be possible, that is yast2 needs to be able to confiure it, .... Gruesse / Regards, Marius Tomaschewski -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org