WISPiab work meeting 200806: Difference between revisions

From WirelessAfrica
Line 46: Line 46:
==Agenda==
==Agenda==


The meeting should be a mix of a
===Technology: Review of technical requirements and specifications===
 
* Review and finalize concrete low level Requirements / Specifications for WISPiab
* Test and compare implementations
** Linksys/BookPC base test system (Meraka, Sebastian)
* Revisit the Data/Voice topic
 
 
===Organization: Synergy and Cooperation===
 
====Advisory Group====
 


decision meeting


and a
====Direct cooperation====


concrete work sprint,
There are several projects with similar agendas and significant overlap on the the technical layer.


possibly in break out group work.
* Dabba
* CuWin
* WISPiab in the context of Wireless Africa, Phase 2
* IP04


Primarily, with focus on South Africa, there is the Dabba project.


* Working business models: identify and agree on ...
The Dabba project focusses on the creation of a Village Telco (as in Voice Services Provider), while the WISPiab project puts focus on the general ISP operations, connectivity and ISP billing, creating infrastructure for a variety of services, with Voice being one of those.
** Revisit the Data/Voice topic
 
* Review and finalize concrete low level Requirements / Specifications for WISPiab
The overlap on technical level is significant, in that both projects to a large extent draw on the same ingredients (e.g. OpenWRT and derived, CoovaAP, OpenSER on Software level, Linksys WRT54GL as current Hardware choice).
* Test and compare implementations
 
** A Linksys/BookPC base test system (meraka, Sebastian) will be ready)
Taking into account the difficult human resources and skills situation in South Africa, cooperation on both technological and organizational level makes sense.
** Dabba
 
** Ndlovu implementations (?)
 
* Identify alliances (hardware, development, rollout)
 
** Cooperations
===Business models===
** Shared needs
 
* Resources
* Review and discussion of valid business models and their implications on technical requirements
** Development
** What needs to be implemented in order to accomodate the various models - see e.g.
** Dissemination

Revision as of 08:23, 21 May 2008


Proposed Work meeting of the WISP-in-a-box project

The WISP-in-a-box project


Date

June 2-3-4, 2008

Location

Meraka Institute

Pretoria

Invited

People and organisations with an active interest in building a concrete product that helps bringing

connectivity to underserviced, underprivileged and overcharged communities in Africa.


Invitation 20080409 sent to:

  • Steve Song
  • Rael Lissos
  • Henry / Ndlovu
  • Kobus Roux et al at Meraka
  • Mark Summer, Inveneo (with request to forward to Ubiquiti)
  • Elektra (if possible to have her in SA at the time)


Budgets for travel, if needed, still TBC!


More proposals are welcome!

Agenda

Technology: Review of technical requirements and specifications

  • Review and finalize concrete low level Requirements / Specifications for WISPiab
  • Test and compare implementations
    • Linksys/BookPC base test system (Meraka, Sebastian)
  • Revisit the Data/Voice topic


Organization: Synergy and Cooperation

Advisory Group

Direct cooperation

There are several projects with similar agendas and significant overlap on the the technical layer.

  • Dabba
  • CuWin
  • WISPiab in the context of Wireless Africa, Phase 2
  • IP04

Primarily, with focus on South Africa, there is the Dabba project.

The Dabba project focusses on the creation of a Village Telco (as in Voice Services Provider), while the WISPiab project puts focus on the general ISP operations, connectivity and ISP billing, creating infrastructure for a variety of services, with Voice being one of those.

The overlap on technical level is significant, in that both projects to a large extent draw on the same ingredients (e.g. OpenWRT and derived, CoovaAP, OpenSER on Software level, Linksys WRT54GL as current Hardware choice).

Taking into account the difficult human resources and skills situation in South Africa, cooperation on both technological and organizational level makes sense.


Business models

  • Review and discussion of valid business models and their implications on technical requirements
    • What needs to be implemented in order to accomodate the various models - see e.g.