KubuntuFeistyNetworking

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2006-10-29 12:13:30 →
Size: 1756
Editor: 65-86-255-2
Comment:
← Revision 4 as of 2006-11-10 01:54:06 → ⇥
Size: 2387
Editor: 207
Comment: feedback from BOF
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
 * Should we install ''knetworkmanager'' by default (just not auto started on logon?)?
    * Concusion: according to NetworkRoaming spec, it will be by default
Line 33: Line 35:
 * Should we install ''knetworkmanager'' by default (just not auto started on logon?)?     * Conclusion: do nothing, we have WPA only for dynamic through knetworkmanager
Line 37: Line 39:
    * Conclusion: knetworkmanager is the way to go
Line 38: Line 41:
   * Kopete: automatically reconnect, no error if network is unavailable    * Kopete/Konversation: automatically reconnect, no error if network is unavailable
Line 40: Line 43:
   * Conclusion: review the patches in other distos that provide similar functionality
Line 42: Line 46:
   * Conclusion: we do not need it as knetworkmanager will provide enough info
 * Avahi/Zero-config - see ZeroConfNetworking
   * We do not need enable/disable zero-conf anymore
   * Conclusion: As we will have .local TLD by default, we can drop System settings module completely as it will just work out of the box

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

We are lacking static configuration for WPA networks (knetworkconf), better handling of network availability by key applications (kopete, kmail...) and have to reduce some duplication (knetworkmanager, wlassistant).

Rationale

Good networking support is critical, particularly for mobile people.

Use cases

Scope

Design

Implementation

Code

Data preservation and migration

Unresolved issues

BoF agenda and discussion

  • Should we install knetworkmanager by default (just not auto started on logon?)?

  • Network configuration GUI:

    • stay with knetworkconf (add WPA support) or

    • implement new Guidance networking module
    • Conclusion: do nothing, we have WPA only for dynamic through knetworkmanager

  • Should we drop wlassistant?

    • replaced by knetworkmanager?

    • should we consider KWlan (see alse KubuntuKWlanInclusion)

    • Conclusion: knetworkmanager is the way to go
  • Make network applications aware of network availability
    • Kopete/Konversation: automatically reconnect, no error if network is unavailable
    • KMail: go to offline mode if not connected, no (or less invasive) errors if network down
    • Conclusion: review the patches in other distos that provide similar functionality

  • Tray icon notification: nothing (in edgy) vs. knetworkmanager (only wireless) vs. knemo (in universe)

    • Integrating tray icon notification (if any) and network configuration GUI
    • Conclusion: we do not need it as knetworkmanager will provide enough info

  • Avahi/Zero-config - see ZeroConfNetworking

    • We do not need enable/disable zero-conf anymore
    • Conclusion: As we will have .local TLD by default, we can drop System settings module completely as it will just work out of the box

CategorySpec

KubuntuFeistyNetworking (last edited 2008-08-06 16:13:58 by localhost)