lowest complexity. Complexity is a function of both task 'complexity'
and task 'scope'.
+
Core
====
Priority: High
Complexity: C4
Owner: Daniel Wagner <daniel.wagner@bmw-carit.de>
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Owner: Patrik Flykt <patrik.flykt@linux.intel.com>
The session API should provide a connection abstraction in order to
prioritize applications network accesses, prevent or allow network
See http://www.mail-archive.com/connman@connman.net/msg01653.html
-- WiSPR support
+- Personal firewall
- Priority: Medium
- Complexity: C4
- Owner: Marcel Holtmann <marcel@holtmann.org>
+ Priority: Low
+ Complexity: C8
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
- Based on the portal detection parsing results, and provisioned
- credentials, ConnMan should be able to initiate a WiSPR authentication.
+ Discuss and implement a basic and safe firewalling strategy into
+ Connman. Provide a D-Bus API for personal firewalling.
-- DNS caching
+- PACRunner extensions
Priority: Low
Complexity: C4
- A simple initial implementation would see ConnMan's dnsproxy
- caching the DNS record based on their TTL.
+ Support more URI schemes, support multiple connections, tighter
+ security integration.
-- Power management
+- Check logging produced by connman_info()
Priority: Medium
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Complexity: C1
- Implement a simple device pm hook that ConnMan's core code would
- use whenever it decides to put devices in power save mode. Although
- the kernel runtime power management code should take care of that,
- not all driver (especially WiFi ones) implement runtime PM hooks.
+ Check that logging produced by connman_info() contains meaningful messages
+ and get rid of the unnecessary ones.
-- IP ranges allocation and check
+- Support for multiple agents
- Priority: High
- Complexity: C2
+ Priority: Medium
+ Complexity: C2
- For both tethering and private networks, but also to detect invalid
- static IP configurations, we need to have a core IP range layer
- that manages all currently used IP blocks.
+ Allow to register multiple agents. Each unique system bus name owner
+ however is only allowed to register one agent.
+ The selection of which agents is used should be matched by bus name
+ owner if possible or first come first serve. A graceful fallback to
+ the next agent should be also used in case of malfunctional agents.
-- Personal firewall
+- Remove --nobacktrace option
- Priority: Low
- Complexity: C8
+ Priority: Medium
+ Complexity: C1
+ When: 2.0
- Extend the iptables code and provide a D-Bus API for personal firewalling.
+ Remove the --nobacktrace option or change it to --backtrace depending on the
+ level of systemd integration or other factors.
-- PACRunner extensions
+- Clean up type definitions
- Priority: Low
+ Priority: Medium
+ Complexity: C1
+
+ Go through variable types and use the following:
+ * bool from <stdbool.h> instead of connman_bool_t and gboolean, in the
+ latter case in those places it makes sense
+
+
+- Clean up data structure usage
+
+ Priority: Medium
Complexity: C4
- Support more URI schemes, support multiple connections, tighter
- security integration.
+ Use hash tables, queues and lists in the code. Replace GSequences with
+ simpler structures. At the same time do a check on the currently used
+ data structures and see if something can be simplified.
+
+- Unit tests for DHCP, DNS and HTTP
+
+ Priority: Medium
+ Complexity: C4
+
+ Create unit tests for these components starting with DHCP. Use gtest
+ from GLib for this task similarly to what has been done for OBEX in Bluez
+ and oFono in general.
WiFi
====
-- Ad-Hoc support
+- Clean up WiFi data structure usage
Priority: Medium
Complexity: C2
- Owner: Samuel Ortiz <sameo@linux.intel.com>
-
-- Fast Connect
-
- Priority: Low
- Complexity: C4
- Owner: Samuel Ortiz <sameo@linux.intel.com>
+ Struct wifi_data is passed as a pointer in some of the wifi plugin
+ callbacks. For example removing a WiFi USB stick causes RTNL and
+ wpa_supplicant to call the wifi plugin at the same time causing the
+ freeing of the wifi data structure. Fix up the code to have proper
+ reference counting or other handling in place for the shared wifi data
+ and the members in the data structure.
- EAP-AKA/SIM
Complexity: C2
+- Removing wpa_supplicant 0.7.x legacy support
+
+ Priority: Low
+ Complexity: C1
+ Owner: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
+
+ Removing global country property setter in gsupplicant, and removing
+ wifi's technology set_regdom implementation. Removing autoscan fallback.
+ (Note: should be done around the end 2012)
Bluetooth
=========
-- DUN client
-
- Priority: Low
- Complexity: C4
- Owner: Mario Tokarz <mario.tokarz@bmw-carit.de>
+- Remove Bluez 4.x support
+ Priority: Low
+ Complexity: C1
+ Remove plugins/bluetooth-legacy.c support in about 6 month (July 2013) or
+ when Bluez 4.x usage becomes minimal.
Cellular
========
VPN
===
-- l2tp support
+- IPsec
- Priority: Low
- Complexity: C2
- Owner: Mohamed Abbas <mohamed.abbas@intel.com>
+ Priority: Medium
+ Complexity: C4
+ Owner: Jukka Rissanen <jukka.rissanen@linux.intel.com>
+- L2TP & PPTP compatibility prefix removal
-- pptp support
+ Priority: Medium
+ Complexity: C1
+ When: connman 2.0
- Priority: Low
- Complexity: C2
- Owner: Mohamed Abbas <mohamed.abbas@intel.com>
+ The VPN config file provisioning patchset contains code that makes
+ PPP options to be marked by "PPPD." prefix. The code supports also
+ old "L2TP." and "PPTP." prefix for PPP options. Remove the compatibility
+ code and only allow "PPPD." prefix for PPP options.
+Tools
+=====
-- IPsec
+- Add Agent mode to connmanctl command line tool
- Priority: Low
- Complexity: C4
+ Priority: Medium
+ Complexity: C2
+
+ connmanctl should implement agent prompting when started with a suitable
+ command line option. Agent mode should also be enabled when in interactive
+ mode.
-- Split tunnelling
+User Interface
+==============
+
+- GNOME3 UI
Priority: Low
- Complexity: C8
- Dependencies: Core:Private networks
+ Complexity: C4
+ Owner: Alok Barsode <alok.barsode@linux.intel.com>
- The current VPN support puts the VPN interface at the top of the
- service list, giving VPNs the default route. When doing split
- tunneling, the system routes packet to the VPN interface for
- private IPs, while going through the default interface for the rest
- of the traffic.
+ A GNOME3 shell user interface would make it easier for mainstream distros
+ users to use ConnMan.