15
edits
Difference between revisions of "Summer of Code 2014"
Jump to navigation
Jump to search
→IoT connected devices and smart services
m |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
* [http://wiki.xmpp.org/web/User:Jocke Joachim lindborg] coordination and mentoring IoT related projects | * [http://wiki.xmpp.org/web/User:Jocke Joachim lindborg] coordination and mentoring IoT related projects | ||
* [http://wiki.xmpp.org/web/User:ZoolDK Steffen Larsen] mentoring of client / server projects. (will write some projects proposals later!) | * [http://wiki.xmpp.org/web/User:ZoolDK Steffen Larsen] mentoring of client / server projects. (will write some projects proposals later!) | ||
* Yann Leboulanger mentoring Gajim related projects | |||
= Project Ideas = | = Project Ideas = | ||
| Line 30: | Line 31: | ||
== IoT connected devices and smart services == | == IoT connected devices and smart services == | ||
Internet of Things has become very big and the main game changer from early connected m2m systems is the very close connection between humans and Devices over Internet. | |||
To facilitate interoperability between these devices and towards user interactions. Standards are crucial there are several such ongoing standardisations some backed by big companies. | |||
XMPP is with its openness and the XSF to govern it's functionality is a perfect match to create a real open interoperable communication tool for IoT. | |||
To help in this effort we need alot of support at various levels and therfore we turn to the GSoC to help us in creating the open tools for the Internet of Things | |||
=== Add IoT support in chat klient of choice === | === Add IoT support in chat klient of choice === | ||
* '''Summary''': Implement the IoT extensions into a client for example [http://psi-im.org/ Psi]. | * '''Summary''': Implement the IoT extensions into a client for example [http://psi-im.org/ Psi] [http://www.xabber.org/ Xabber]. | ||
* '''Difficulty''': Easy-Medium | * '''Difficulty''': Easy-Medium | ||
* '''Details''': The IoT extensions ex [http://xmpp.org/extensions/xep-0323.html XEP-0323] and [http://xmpp.org/extensions/xep-0325.html XEP-0325] creates possibility to read and write fields to IoT devices. To be able to interact with devices a good interface is needed to edit control data and read sensor data to show diagrams of collected data and even to act as a [http://xmpp.org/extensions/xep-0324.html provisioning client] | * '''Details''': The IoT extensions ex [http://xmpp.org/extensions/xep-0323.html XEP-0323] and [http://xmpp.org/extensions/xep-0325.html XEP-0325] creates possibility to read and write fields to IoT devices. To be able to interact with devices a good interface is needed to edit control data and read sensor data to show diagrams of collected data and even to act as a [http://xmpp.org/extensions/xep-0324.html provisioning client]. With this tool any provider of a open IoT device would instantly have a uniform interface. | ||
* '''Skills (to have)''' | * '''Skills (to have)''' | ||
** Ability to code in language of the client of choice | ** Ability to code in language of the client of choice | ||
| Line 45: | Line 52: | ||
=== IoT smart logic === | === IoT smart logic === | ||
* '''Summary''': Use | * '''Summary''': Use any XMPP library for ex [http://sleekxmpp.com/ SleekXMPP] to create a logic environment to control devices and collect data. | ||
* '''Difficulty''': Easy-Medium | * '''Difficulty''': Easy-Medium | ||
* '''Details''': The IoT extensions ex [http://xmpp.org/extensions/xep-0323.html XEP-0323] and [http://xmpp.org/extensions/xep-0325.html XEP-0325] creates possibility to read and write fields to IoT devices. To let this create smart services there needs to be logic like [https://ifttt.com/ IFTTT] or [http://en.wikipedia.org/wiki/IEC_61131 IEC 61131] or other. The idea is to create such an environment and management of devices and fields to build smart logic and services in any IoT related domain | * '''Details''': The IoT extensions ex [http://xmpp.org/extensions/xep-0323.html XEP-0323] and [http://xmpp.org/extensions/xep-0325.html XEP-0325] creates possibility to read and write fields to IoT devices. To let this create smart services there needs to be logic like [https://ifttt.com/ IFTTT] or [http://en.wikipedia.org/wiki/IEC_61131 IEC 61131] or other. The idea is to create such an environment and management of devices and fields to build smart logic and services in any IoT related domain. ´prefarably the logic should be visual [https://github.com/node-red/node-red Node red project] | ||
* '''Skills (to have)''' | * '''Skills (to have)''' | ||
** Ability to code | ** Ability to code | ||
| Line 56: | Line 63: | ||
** Rule engines [http://en.wikipedia.org/wiki/Ladder_logic Ladder Logic] or | ** Rule engines [http://en.wikipedia.org/wiki/Ladder_logic Ladder Logic] or | ||
* [http://www.google-melange.com/gsoc/proposal/submit/google/gsoc2014/xsf Apply Now!] | * [http://www.google-melange.com/gsoc/proposal/submit/google/gsoc2014/xsf Apply Now!] | ||
== Gajim projects == | |||
=== Multi-user Audio / Video conference === | |||
We already have jingle audio / video for one to one chat. Find the better way to attack this problem (several things exist, like MUJI, Jitsi Videobridge) and implement it in Gajim. | |||
=== MAM === | |||
[http://xmpp.org/extensions/xep-0313.html MAM] is a way to store our logs server side, so we can share it in different locations. | |||
=== End-to-End Encryption using TLS === | |||
Gajim already support E2E, GPG, OTR. The next protocol that should be implemented is chat over TLS. There is a [https://tools.ietf.org/id/draft-meyer-xmpp-e2e-encryption-02.html proto-XEP] and a [https://tools.ietf.org/id/draft-meyer-xmpp-e2e-encryption-02.html IETF draft] about that. | |||