Open development/Why the closed packages - Revision history

imported_>amigadave: /* List of outstanding requests that are still relevant */ fix typo, format link

2011-02-25T12:40:21Z

List of outstanding requests that are still relevant: fix typo, format link

← Older revision		Revision as of 12:40, 25 February 2011
Line 110:		Line 110:
	*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases such as SMS)		*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases such as SMS)
	*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.		*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.
	*Support for different ring and SMS tones for different contacts. ~~Relavent~~ bug is https://bugs.maemo.org/show_bug.cgi?id=11983. What needs to be open sourced is hildon-plugins-notify-sv (as thats what plays the ringtones)		*Support for different ring and SMS tones for different contacts. Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11983 11983]. What needs to be open sourced is hildon-plugins-notify-sv (as thats what plays the ringtones)

	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]

imported_>jonwil: /* List of outstanding requests that are still relevant */

2011-02-25T10:35:16Z

List of outstanding requests that are still relevant

← Older revision		Revision as of 10:35, 25 February 2011
Line 110:		Line 110:
	*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases such as SMS)		*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases such as SMS)
	*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.		*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.
			*Support for different ring and SMS tones for different contacts. Relavent bug is https://bugs.maemo.org/show_bug.cgi?id=11983. What needs to be open sourced is hildon-plugins-notify-sv (as thats what plays the ringtones)

	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]

imported_>jonwil: /* List of outstanding requests that are still relevant */

2011-02-17T10:10:05Z

List of outstanding requests that are still relevant

← Older revision		Revision as of 10:10, 17 February 2011
Line 105:		Line 105:
	* Cell Broadcast SMS support. Relevant bugs are [https://bugs.maemo.org/show_bug.cgi?id=8347 8347] and [https://bugs.maemo.org/show_bug.cgi?id=10870 10870]. Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is the relevant bug for the UI stuff.		* Cell Broadcast SMS support. Relevant bugs are [https://bugs.maemo.org/show_bug.cgi?id=8347 8347] and [https://bugs.maemo.org/show_bug.cgi?id=10870 10870]. Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is the relevant bug for the UI stuff.
	* Support for non-standard WPA keys or passphrases. Relavent bugs are [https://bugs.maemo.org/show_bug.cgi?id=9864 9864] and [https://bugs.maemo.org/show_bug.cgi?id=1002 1002]. Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other useful enhancements such as improved output of signal strength for WiFi and cellular. [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is a related bug for the UI stuff.		* Support for non-standard WPA keys or passphrases. Relavent bugs are [https://bugs.maemo.org/show_bug.cgi?id=9864 9864] and [https://bugs.maemo.org/show_bug.cgi?id=1002 1002]. Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other useful enhancements such as improved output of signal strength for WiFi and cellular. [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is a related bug for the UI stuff.
	* Proper ability to query all aspects of battery status (including on MeeGo). Relevant bug is https://bugs.maemo.org/show_bug.cgi?id=11922 11922]. Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and MeeGo) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.		* Proper ability to query all aspects of battery status (including on MeeGo). Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11922 11922]. Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and MeeGo) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.
	Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is [https://bugs.maemo.org/show_bug.cgi?id=11924 11924]. What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin). Having this source code may also allow [https://bugs.maemo.org/show_bug.cgi?id=8460 Bug 8460] to be solved (i.e. gaining control of how the code determines which GPRS APN it chooses to connect to). It may be that the policy plugin infrastructure is not fine-grained enough for this in which case the entire source code to the ICD daemon may be required.		Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is [https://bugs.maemo.org/show_bug.cgi?id=11924 11924]. What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin). Having this source code may also allow [https://bugs.maemo.org/show_bug.cgi?id=8460 Bug 8460] to be solved (i.e. gaining control of how the code determines which GPRS APN it chooses to connect to). It may be that the policy plugin infrastructure is not fine-grained enough for this in which case the entire source code to the ICD daemon may be required.
	*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11794 11793]. There is open source code for this [http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories] but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.		*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11794 11793]. There is open source code for this [http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories] but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.

imported_>jonwil: /* List of outstanding requests that are still relevant */

2011-02-17T10:09:28Z

List of outstanding requests that are still relevant

← Older revision		Revision as of 10:09, 17 February 2011
Line 106:		Line 106:
	* Support for non-standard WPA keys or passphrases. Relavent bugs are [https://bugs.maemo.org/show_bug.cgi?id=9864 9864] and [https://bugs.maemo.org/show_bug.cgi?id=1002 1002]. Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other useful enhancements such as improved output of signal strength for WiFi and cellular. [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is a related bug for the UI stuff.		* Support for non-standard WPA keys or passphrases. Relavent bugs are [https://bugs.maemo.org/show_bug.cgi?id=9864 9864] and [https://bugs.maemo.org/show_bug.cgi?id=1002 1002]. Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other useful enhancements such as improved output of signal strength for WiFi and cellular. [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is a related bug for the UI stuff.
	* Proper ability to query all aspects of battery status (including on MeeGo). Relevant bug is https://bugs.maemo.org/show_bug.cgi?id=11922 11922]. Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and MeeGo) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.		* Proper ability to query all aspects of battery status (including on MeeGo). Relevant bug is https://bugs.maemo.org/show_bug.cgi?id=11922 11922]. Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and MeeGo) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.
	Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is [https://bugs.maemo.org/show_bug.cgi?id=11924 11924]. What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin).		Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is [https://bugs.maemo.org/show_bug.cgi?id=11924 11924]. What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin). Having this source code may also allow [https://bugs.maemo.org/show_bug.cgi?id=8460 Bug 8460] to be solved (i.e. gaining control of how the code determines which GPRS APN it chooses to connect to). It may be that the policy plugin infrastructure is not fine-grained enough for this in which case the entire source code to the ICD daemon may be required.
	*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11794 11793]. There is open source code for this [http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories] but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.		*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11794 11793]. There is open source code for this [http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories] but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.
	*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)		*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases such as SMS)
	*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.		*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.

	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]

imported_>amigadave: /* List of outstanding requests that are still relavent */ fix some typos, format links

2011-02-16T08:50:09Z

List of outstanding requests that are still relavent: fix some typos, format links

← Older revision		Revision as of 08:50, 16 February 2011
Line 101:		Line 101:
	* [https://bugs.maemo.org/show_bug.cgi?id=3635 Alarm framework].		* [https://bugs.maemo.org/show_bug.cgi?id=3635 Alarm framework].

	== List of outstanding requests that are still ~~relavent~~ ==		== List of outstanding requests that are still relevant ==

	* Cell Broadcast SMS support. Relevant bugs are https://bugs.maemo.org/show_bug.cgi?id=8347 and https://bugs.maemo.org/show_bug.cgi?id=10870 Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). https://bugs.maemo.org/show_bug.cgi?id=11923 is the ~~relavent~~ bug for the UI stuff.		* Cell Broadcast SMS support. Relevant bugs are [https://bugs.maemo.org/show_bug.cgi?id=8347 8347] and [https://bugs.maemo.org/show_bug.cgi?id=10870 10870]. Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is the relevant bug for the UI stuff.
	* Support for non-standard WPA keys or passphrases. Relavent bugs are https://bugs.maemo.org/show_bug.cgi?id=9864 and https://bugs.maemo.org/show_bug.cgi?id=1002 Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other ~~usefull~~ enhancements such as improved output of signal strength for WiFi and cellular. https://bugs.maemo.org/show_bug.cgi?id=11923 is a related bug for the UI stuff.		* Support for non-standard WPA keys or passphrases. Relavent bugs are [https://bugs.maemo.org/show_bug.cgi?id=9864 9864] and [https://bugs.maemo.org/show_bug.cgi?id=1002 1002]. Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other useful enhancements such as improved output of signal strength for WiFi and cellular. [https://bugs.maemo.org/show_bug.cgi?id=11923 Bug 11923] is a related bug for the UI stuff.
	* Proper ability to query all aspects of battery status (including on MeeGo). ~~Relavent~~ bug is ~~this~~ https://bugs.maemo.org/show_bug.cgi?id=11922 Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and ~~meego~~) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.		* Proper ability to query all aspects of battery status (including on MeeGo). Relevant bug is https://bugs.maemo.org/show_bug.cgi?id=11922 11922]. Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and MeeGo) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.
	Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is https://bugs.maemo.org/show_bug.cgi?id=11924 What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin).		Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is [https://bugs.maemo.org/show_bug.cgi?id=11924 11924]. What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin).
	*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. ~~Relavent~~ bug is ~~this~~ https://bugs.maemo.org/show_bug.cgi?id=11794 There is open source code for this http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.		*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11794 11793]. There is open source code for this [http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories] but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.
	*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The ~~relavent~~ bug is ~~here~~ https://bugs.maemo.org/show_bug.cgi?id=11921 What needs to be opened at a ~~minumum~~ is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)		*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relevant bug is [https://bugs.maemo.org/show_bug.cgi?id=11921 11921]. What needs to be opened at a minimum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)
	*firmware image file format and flash tool source. ~~Relavent~~ bugs include https://bugs.maemo.org/show_bug.cgi?id=7964 ~~and~~ https://bugs.maemo.org/show_bug.cgi?id=4871 and https://bugs.maemo.org/show_bug.cgi?id=11809 Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.		*firmware image file format and flash tool source. Relevant bugs include [https://bugs.maemo.org/show_bug.cgi?id=7964 7964], [https://bugs.maemo.org/show_bug.cgi?id=4871 4871] and [https://bugs.maemo.org/show_bug.cgi?id=11809 11809]. Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.

	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]

imported_>jonwil: /* List of outstanding requests that are still relavent */

2011-02-16T00:10:35Z

List of outstanding requests that are still relavent

← Older revision		Revision as of 00:10, 16 February 2011
Line 105:		Line 105:
	* Cell Broadcast SMS support. Relevant bugs are https://bugs.maemo.org/show_bug.cgi?id=8347 and https://bugs.maemo.org/show_bug.cgi?id=10870 Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). https://bugs.maemo.org/show_bug.cgi?id=11923 is the relavent bug for the UI stuff.		* Cell Broadcast SMS support. Relevant bugs are https://bugs.maemo.org/show_bug.cgi?id=8347 and https://bugs.maemo.org/show_bug.cgi?id=10870 Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). https://bugs.maemo.org/show_bug.cgi?id=11923 is the relavent bug for the UI stuff.
	* Support for non-standard WPA keys or passphrases. Relavent bugs are https://bugs.maemo.org/show_bug.cgi?id=9864 and https://bugs.maemo.org/show_bug.cgi?id=1002 Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other usefull enhancements such as improved output of signal strength for WiFi and cellular. https://bugs.maemo.org/show_bug.cgi?id=11923 is a related bug for the UI stuff.		* Support for non-standard WPA keys or passphrases. Relavent bugs are https://bugs.maemo.org/show_bug.cgi?id=9864 and https://bugs.maemo.org/show_bug.cgi?id=1002 Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other usefull enhancements such as improved output of signal strength for WiFi and cellular. https://bugs.maemo.org/show_bug.cgi?id=11923 is a related bug for the UI stuff.
	* Proper ability to query all aspects of battery status (including on MeeGo). Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=~~11794~~ Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and meego) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.		* Proper ability to query all aspects of battery status (including on MeeGo). Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11922 Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and meego) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.
	Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is https://bugs.maemo.org/show_bug.cgi?id=~~11794~~ What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin).		Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is https://bugs.maemo.org/show_bug.cgi?id=11924 What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin).
	*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11794 There is open source code for this http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.		*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11794 There is open source code for this http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.
	*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relavent bug is here https://bugs.maemo.org/show_bug.cgi?id=11921 What needs to be opened at a minumum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)		*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relavent bug is here https://bugs.maemo.org/show_bug.cgi?id=11921 What needs to be opened at a minumum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)

imported_>jonwil: /* List of outstanding requests that are still relavent */

2011-02-15T16:36:28Z

List of outstanding requests that are still relavent

← Older revision		Revision as of 16:36, 15 February 2011
Line 109:		Line 109:
	*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11794 There is open source code for this http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.		*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11794 There is open source code for this http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.
	*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relavent bug is here https://bugs.maemo.org/show_bug.cgi?id=11921 What needs to be opened at a minumum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)		*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relavent bug is here https://bugs.maemo.org/show_bug.cgi?id=11921 What needs to be opened at a minumum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)
			*firmware image file format and flash tool source. Relavent bugs include https://bugs.maemo.org/show_bug.cgi?id=7964 and https://bugs.maemo.org/show_bug.cgi?id=4871 and https://bugs.maemo.org/show_bug.cgi?id=11809 Seems like there was interest in opening up some/all of this stuff (flashing tool, firmware image format, firmware builder) in the past from Nokia but there was no community interest at the time. Not sure if there is still community interest but it might be worth having this. Would allow porting to OSs not supported by Nokia (such as x86_64 linux) as well as potentially enhancing the tools.

	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]

imported_>jonwil at 16:04, 15 February 2011

2011-02-15T16:04:47Z

← Older revision		Revision as of 16:04, 15 February 2011
Line 101:		Line 101:
	* [https://bugs.maemo.org/show_bug.cgi?id=3635 Alarm framework].		* [https://bugs.maemo.org/show_bug.cgi?id=3635 Alarm framework].

			== List of outstanding requests that are still relavent ==

			* Cell Broadcast SMS support. Relevant bugs are https://bugs.maemo.org/show_bug.cgi?id=8347 and https://bugs.maemo.org/show_bug.cgi?id=10870 Code that needs releasing is source for libsms and libcsd-sms (plus headers needed to compile it). For the userspace bits, it would be ideal (but not essential) to have source code or -dev packages for the connectivity UI shared libraries (libconnui, libconnui-cellular etc). Opening up the SMS code would allow other enhancements (such as a low level method to filter SMSs before they even get written to any permanent storage). https://bugs.maemo.org/show_bug.cgi?id=11923 is the relavent bug for the UI stuff.
			* Support for non-standard WPA keys or passphrases. Relavent bugs are https://bugs.maemo.org/show_bug.cgi?id=9864 and https://bugs.maemo.org/show_bug.cgi?id=1002 Code that needs releasing is source for connui-iapsettings, connui-iapsettings-wlan and connui-conndlgs-internet (plus their dependancies) as these are the libraries that relate to setting the WPA key. http://www.internettablettalk.com/wiki/index.php/HOWTO:_WPA-PSK_when_you_only_have_the_64-hexit_PSK,_no_passphrase claims that its possible to manually set the key via gconf editing so all we need is to be able to change the UI for this. Opening the connectivity UI (control panels, status widgets etc) would also allow other usefull enhancements such as improved output of signal strength for WiFi and cellular. https://bugs.maemo.org/show_bug.cgi?id=11923 is a related bug for the UI stuff.
			* Proper ability to query all aspects of battery status (including on MeeGo). Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11794 Requires releasing development package for libbmeipc so we can talk to that library (which exists on both maemo and meego) and do things like getting information on what sort of charger is connected, how much juice is in the battery etc. Anything sensitive (i.e. "use this the wrong way and you could damage the battery") could be removed when publishing this package.
			Better control over which network the phone will connect to (e.g. letting you set a "home" WiFi network that it will always connect to no matter what. Relavent bug is https://bugs.maemo.org/show_bug.cgi?id=11794 What needs to be opened up is the source for (and required headers for) the ICD2 policy plugins (libicd_policy_) so we can understand how they work and modify/enhance them (or write our own new policy plugin).
			*Better control of various hardware components such as accelerometer, keypad lighting, status LED, vibrator, screen brightness and others. Relavent bug is this https://bugs.maemo.org/show_bug.cgi?id=11794 There is open source code for this http://meego.gitorious.org/meego-middleware/mce in the MeeGo repositories but it is not a match for the Maemo version and is missing pieces required to use it with Maemo.
			*Ability to support features of the cellular modem not currently supported by the telephony stack in use (whether that stack is the maemo stack, ofono on MeeGo, ogsmd on FreeSmartPhone or otherwise). The relavent bug is here https://bugs.maemo.org/show_bug.cgi?id=11921 What needs to be opened at a minumum is permission to use the header files we already have but ideally release of correct headers for the N900 cell modem (the headers we have are not a 100% match in a number of cases)

	[[Category:Development]]		[[Category:Development]]
	[[Category:Community]]		[[Category:Community]]

imported_>lardman: Added comment about availability of dspctl

2011-01-11T17:16:51Z

Added comment about availability of dspctl

← Older revision		Revision as of 17:16, 11 January 2011
Line 55:		Line 55:
	* show_image		* show_image
	* battest		* battest
	* dspctl		* dspctl - this is available in the open osso-dsp-loader package.
	* the script linuxrc		* the script linuxrc
	* libbmeic.so		* libbmeic.so

imported_>hrw: added note about Calendar

2010-02-19T15:44:34Z

added note about Calendar

← Older revision		Revision as of 15:44, 19 February 2010
Line 95:		Line 95:
	* [https://bugs.maemo.org/show_bug.cgi?id=6961 telepathy-spirit] - This connection manager might be useful for people using Telepathy framework and Skype on desktop computer.		* [https://bugs.maemo.org/show_bug.cgi?id=6961 telepathy-spirit] - This connection manager might be useful for people using Telepathy framework and Skype on desktop computer.
	* [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate]		* [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate]
	* [https://bugs.maemo.org/show_bug.cgi?id=7811 Calendar]		* [https://bugs.maemo.org/show_bug.cgi?id=7811 Calendar] - will remain closed for Fremantle and MeeGo.

	== Opened ==		== Opened ==