Background ========== - Priority scale: High, Medium and Low - Complexity scale: C1, C2, C4 and C8. The complexity scale is exponential, with complexity 1 being the lowest complexity. Complexity is a function of both task 'complexity' and task 'scope'. Core ==== - Session API implementation Priority: High Complexity: C4 Owner: Daniel Wagner Owner: Patrik Flykt The session API should provide a connection abstraction in order to prioritize applications network accesses, prevent or allow network and bearer roaming, or provide applications with a way to request for periodic network connections. On-demand connections will be implemented through this API as well. See http://www.mail-archive.com/connman@connman.net/msg01653.html - main.conf FallbackTimeservers, FallbackNameservers Priority: Medium Complexity: C2 Owner: Both entries should take a string list as arguments and can contain mixed combination of fully qualified domain names, IPv4 and IPv6 addresses. In absence of main.conf or if this entry is not present then no fallback servers are used. These configuration file values will obsolete plugins/meego.c and plugins/google.c. See http://lists.connman.net/pipermail/connman/2012-March/008605.html - main.conf DefaultAutoConnectTechnologies Priority: Medium Complexity: C2 Owner: The default autoconnect value for a new service that has not been seen. After that it can be changed on a per service level via AutoConnect property. The default value if not present should be "ethernet,wifi". See http://lists.connman.net/pipermail/connman/2012-March/008605.html - main.conf PriorityTechnologies Priority: Medium Complexity: C2 Owner: Patrik Flykt Handle automatic switch from one technology to another one. By default this value should be empty and no automatic switching is happening as long as technology is connected. The list is ordered. See http://lists.connman.net/pipermail/connman/2012-March/008605.html - Personal firewall Priority: Low Complexity: C8 Owner: Tomasz Bursztyka Discuss and implement a basic and safe firewalling strategy into Connman. Provide a D-Bus API for personal firewalling. - PACRunner extensions Priority: Low Complexity: C4 Support more URI schemes, support multiple connections, tighter security integration. WiFi ==== - EAP-AKA/SIM Priority: Medium Complexity: C2 Owner: Samuel Ortiz This EAP is needed for SIM card based network authentication. ConnMan here plays a minor role: Once wpa_supplicant is set up for starting and EAP-AKA/SIM authentication, it will talk to a SIM card through its pcsc-lite API. - EAP-FAST Priority: Low Complexity: C1 - Wireless background scan Priority: Medium Complexity: C4 Owner: Samuel Ortiz While connected ConnMan should offload the background scanning to wpa_supplicant. Wpa_supplicant allows for a fancy background scan which frequency increases after the current connection signal level drops below a defined threshold. We should also be able to have wpa_supplicant do the background scanning for us when we're not connected, if we have configured our favorite networks. - WiFi p2p Priority: Medium Complexity: C2 Bluetooth ========= - DUN client Priority: Low Complexity: C4 Owner: Mario Tokarz Cellular ======== VPN === - IPsec Priority: Medium Complexity: C4 Owner: Jukka Rissanen Tools ===== - Command line tool Priority: Low Complexity: C4 Owner: Patrik Flykt For platforms not running python, it could prove useful to provide them with a native single binary command line tool. User Interface ============== - GNOME3 UI Priority: Low Complexity: C4 Owner: Alok Barsode A GNOME3 shell user interface would make it easier for mainstream distros users to use ConnMan.