Difference between revisions of "BasicInternet:Wakoma follow-up Oct2020"

From its-wiki.no

Jump to: navigation, search
(Technology topics addressed)
(Discussion topics and conclusions)
Line 10: Line 10:
 
}}
 
}}
 
= Discussion topics and conclusions =
 
= Discussion topics and conclusions =
We had a technology exchange regarding the LMS platform by [[Wakoma]], and agreed on the following steps ahead:
+
We had a technology exchange regarding the LMS/Community Platform by [[Wakoma]], and agreed on the following steps ahead:
 
# Josef creates the notes (this page)- Eric to comment directly
 
# Josef creates the notes (this page)- Eric to comment directly
# Clarify the way ahead, on how to bring the "yeboo.com", the Wakoma portal and other developments under one header. Suggestion is to create a UNICEF Innovation project, where the structure of the portal are open source modules, and where the content can be contributed depending on the needs in the local community.  
+
# Continue to explore ways to make "yeboo.com", the Wakoma Platform, and other similar platforms, and/or the content and services therein compatible. Suggestion is to create a UNICEF Innovation project (or similar), where the structure of the portal are open source modules, and where the content and services can be selected and configured by communities in their preferred platform.
# Based on the outcome of 2, we then define the way ahead, being ''(i)'' a doc summarising what we want to achieve and ''(ii)'' an open invitation to A4AI, APC, ISOC and others to join for the OpenSource development
+
# To this end, it would be useful to create a document that lists such platforms/services/content and relevant organizations who might be willing to engage in such an open source project
  
Next meeting is agreed for '''21Oct2020 at 11:00h Oslo time'''
+
Next meeting TBD'''
  
 
== Technology topics addressed ==
 
== Technology topics addressed ==
Goals of the platform:
+
Common goals of open source platforms:
 
* be able to work in resources-constraint environments, both with respect to bandwidth costs and capabilities of the server
 
* be able to work in resources-constraint environments, both with respect to bandwidth costs and capabilities of the server
* based on OpenSource modules to ensure applicability by every community
+
* based on open source modules to ensure applicability by every community
* scalable, to be deployed in small communities on e.g. a RaspberryPi, in areas and on a country level
+
* scalable, to be deployed in small communities on e.g. low cost single-board computers, in areas and on a country level
* enables easy "drag and drop" course creation
+
* enables easy "drag and drop" content and course creation
 
* enables off-line capability, e.g. allowing students to take the content home  
 
* enables off-line capability, e.g. allowing students to take the content home  
 
* user management
 
* user management
* supporting a freemium model for content, with e.g. free courses and premium certificates through exams
+
* supporting a freemium model and other models for content, with e.g. free courses and premium certificates through exams, memberships, paid courses, etc.
 
* monitoring and usage reporting (of statistical data), to allow a feedback to donors of content
 
* monitoring and usage reporting (of statistical data), to allow a feedback to donors of content
 
* applicability in other community networks
 
* applicability in other community networks
  
The [[Learning Management System]] (LMS) introduced by Eric for Wakoma satisfies most of these requirements, and is built solely on OpenSource components. Examples are:
+
The [[Learning Management System]] (LMS)/Community Platform and Nimble https://wakoma.co/nimble/ built by Wakoma contain these features, and are built solely on open source hardware and software. Examples are:
* docker containers for each module, allowing the free mixing of functionality needed in a specific community
+
* Dockerized services, allowing the free mixing of functionality needed in a specific community or context
* Wordpress for easy creation of content (e.g. through plugin Elementor), and front-end management
+
* Wordpress for easy creation of content and front-end management
* Nextcloud for file hosting and easy sharing
+
* Nextcloud for file hosting and easy sharing, and Nextcloud Talk for video/voice chat.
* integrated SSO feature bringing all components under one login
+
 
* app support using e.g. Nextcloud app
+
Wakoma is also working with partners VPUU http://vpuu.org.za and iNethi http://inethi.org.za to collaboratively develop new features and functionality useful for community networks and other community-based connectivity initiatives around the world. Eric is also a proponent of OpenZIM https://github.com/openzim and the work being done by the Kiwix http://kiwix.org/ and Internet in a Box IIAB https://github.com/iiab teams.
Current focus is on the intelligent sync, the analysis of novel protocols like the SIM(?) protocol by Qx(?), and analytics packages
+

Revision as of 14:27, 14 October 2020


BasicInternet:Wakoma follow-up Oct2020

Title BasicInternet:Wakoma_follow-up_Oct2020
Place Zoom.us
Date, Time 2020/10/14, 1100-1200
Contact Person Josef.Noll
Participants Josef.Noll, Eric Nitschke
related to Project BasicInternet
Keywords Community Networks, Learning Management System, Village Platform
this page was created by Special:FormEdit/Meeting, and can be edited by Special:FormEdit/Meeting/BasicInternet:Wakoma follow-up Oct2020
Category:Meeting


Discussion topics and conclusions

We had a technology exchange regarding the LMS/Community Platform by Wakoma, and agreed on the following steps ahead:

  1. Josef creates the notes (this page)- Eric to comment directly
  2. Continue to explore ways to make "yeboo.com", the Wakoma Platform, and other similar platforms, and/or the content and services therein compatible. Suggestion is to create a UNICEF Innovation project (or similar), where the structure of the portal are open source modules, and where the content and services can be selected and configured by communities in their preferred platform.
  3. To this end, it would be useful to create a document that lists such platforms/services/content and relevant organizations who might be willing to engage in such an open source project

Next meeting TBD

Technology topics addressed

Common goals of open source platforms:

  • be able to work in resources-constraint environments, both with respect to bandwidth costs and capabilities of the server
  • based on open source modules to ensure applicability by every community
  • scalable, to be deployed in small communities on e.g. low cost single-board computers, in areas and on a country level
  • enables easy "drag and drop" content and course creation
  • enables off-line capability, e.g. allowing students to take the content home
  • user management
  • supporting a freemium model and other models for content, with e.g. free courses and premium certificates through exams, memberships, paid courses, etc.
  • monitoring and usage reporting (of statistical data), to allow a feedback to donors of content
  • applicability in other community networks

The Learning Management System (LMS)/Community Platform and Nimble https://wakoma.co/nimble/ built by Wakoma contain these features, and are built solely on open source hardware and software. Examples are:

  • Dockerized services, allowing the free mixing of functionality needed in a specific community or context
  • Wordpress for easy creation of content and front-end management
  • Nextcloud for file hosting and easy sharing, and Nextcloud Talk for video/voice chat.

Wakoma is also working with partners VPUU http://vpuu.org.za and iNethi http://inethi.org.za to collaboratively develop new features and functionality useful for community networks and other community-based connectivity initiatives around the world. Eric is also a proponent of OpenZIM https://github.com/openzim and the work being done by the Kiwix http://kiwix.org/ and Internet in a Box IIAB https://github.com/iiab teams.