http://wirelessafrica.meraka.org.za/wiki/api.php?action=feedcontributions&user=Antoine&feedformat=atomWirelessAfrica - User contributions [en]2024-03-29T15:51:58ZUser contributionsMediaWiki 1.39.6http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4775WISP in a Box Development2009-08-06T11:51:49Z<p>Antoine: </p>
<hr />
<div>{|align="right"<br />
| style="height:100%;width:20em;border:1px solid #D9D9D9;background-color:#F2F2F2;" valign="top" |<br />
*[[WISP_in_a_Box_Development|'''WISP in a Box Development Home''']]<br />
|}<br />
<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]<br />
<br />
<br clear=all><br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x Edimax 7711UM USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4763WISP in a Box Development2009-08-04T14:22:58Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributors. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4762WISP in a Box Development2009-08-04T14:22:41Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of any Libré project. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4761WISP in a Box Development2009-08-04T14:21:59Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their contributions to the project usually take the form of running the software, reporting bugs on the mailing list and requesting features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4760WISP in a Box Development2009-08-04T14:21:37Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interactions with the project are usually in the form of running the software, reporting bugs on the mailing list and requesting features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4759WISP in a Box Development2009-08-04T14:21:12Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interactions with the project are usually in the form of downloading and using the software, reporting bugs on the mailing list and requesting features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and desire to contribute code patches, documentation and their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4758WISP in a Box Development2009-08-04T14:17:28Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting [http://www.neary-consulting.com]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4757WISP in a Box Development2009-08-04T14:17:16Z<p>Antoine: /* Resources */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting ([http://www.neary-consulting.com])<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4756WISP in a Box Development2009-08-04T14:16:23Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - [http://www.neary-consulting.com/ Neary Consulting]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4755WISP in a Box Development2009-08-04T14:12:58Z<p>Antoine: /* Resources */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers to Entry''']] - Neary Consulting<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4754WISP in a Box Development2009-08-04T14:12:29Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Community Building : Barriers To Entry''']] - Neary Consulting<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4753WISP in a Box Development2009-08-04T14:10:36Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Barriers to entry for community participation''']] - Neary Consulting<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=File:Community_barriers_to_entry_checklist.pdf&diff=4752File:Community barriers to entry checklist.pdf2009-08-04T14:10:16Z<p>Antoine: </p>
<hr />
<div></div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4751WISP in a Box Development2009-08-04T14:09:59Z<p>Antoine: /* Resources */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Media:Community_barriers_to_entry_checklist.pdf|'''Barriers to entry for community participation''' - Neary Consulting]]<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4750WISP in a Box Development2009-08-04T14:07:49Z<p>Antoine: /* Resources */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[Community_barriers_to_entry_checklist.pdf Community Barriers To Entry Checklist]]<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4749WISP in a Box Development2009-08-04T14:07:37Z<p>Antoine: /* Resources */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [Community_barriers_to_entry_checklist.pdf Community Barriers To Entry Checklist]<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4748WISP in a Box Development2009-08-04T14:06:26Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Resources ===<br />
<br />
* [[file:Community_barriers_to_entry_checklist.pdf Community Barriers To Entry Checklist]]<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4747WISP in a Box Development2009-08-04T13:33:25Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
|-<br />
|}<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4746WISP in a Box Development2009-08-04T13:32:46Z<p>Antoine: /* Setup Checklist */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Task !! Description <br />
|- valign="top" <br />
| Development Workstation || <br />
* x86<br />
* FreeBSD or Ubuntu<br />
* 1x ??? USB WiFi network card<br />
|- valign="top" <br />
| WISP Server ||<br />
* AMD ION<br />
* 1GB RAM<br />
* 80GB Hard Drive<br />
* D-Link USB Ethernet<br />
|- valign="top" <br />
| Development Mesh Node ||<br />
* D-Link DIR-300<br />
|- valign="top" <br />
| Deployment Mesh Node ||<br />
* HPN<br />
|- valign="top" <br />
| Subscribe to mailing lists || TODO<br />
|- valign="top" <br />
| Join IRC || Install an IRC client and configure it for irc.freenode.net, #afrimesh (ask George if you need help)<br />
|- valign="top" <br />
| Configure WispBox Development Environment ||<br />
Read: http://code.google.com/p/wispinabox/wiki/DevelopmentEnvironment <br />
|- valign="top" <br />
| Configure Afrimesh Development Environment ||<br />
Read: http://code.google.com/p/afrimesh/wiki/DevelopmentEnvironment<br />
<br />
|-<br />
|}<br />
<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4745WISP in a Box Development2009-08-04T13:17:34Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Setup Checklist ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|- <br />
| Development Workstation <br />
| <br />
* x86<br />
* FreeBSD or Ubuntu<br />
|-<br />
|}<br />
<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4744WISP in a Box Development2009-08-04T13:14:34Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit'''] - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Setup Checklist ===<br />
<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4743WISP in a Box Development2009-08-04T13:12:18Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Version Control - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Version Control - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Setting up your development environment ===<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=File:Libre_software_cycle.png&diff=4742File:Libre software cycle.png2009-08-04T13:11:49Z<p>Antoine: uploaded a new version of "Image:Libre software cycle.png"</p>
<hr />
<div></div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4741WISP in a Box Development2009-08-04T13:09:42Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || TO COME || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || TO COME || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Sources - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Sources - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
| Package Repository || https://launchpad.net/~wispinabox || <br />
|-<br />
| Build Server || TO COME ||<br />
|-<br />
|}<br />
<br />
<br />
=== Setting up your development environment ===<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4740WISP in a Box Development2009-08-04T13:06:25Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || http://code.google.com/p/wispinabox/issues/list || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| Wiki - Main || http://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development || <br />
|-<br />
| Wiki - WispBox || http://code.google.com/p/wispinabox/w || Content hosted here still needs to be migrated to the main wiki<br />
|-<br />
| Wiki - Afrimesh || http://code.google.com/p/afrimesh/w || Afrimesh services multiple projects and as such maintains a separate wiki<br />
|-<br />
| Sources - WispBox || http://code.google.com/p/wispinabox/source/checkout || <br />
|-<br />
| Sources - Afrimesh || http://code.google.com/p/afrimesh/source/checkout || <br />
|-<br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4739WISP in a Box Development2009-08-04T13:01:06Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{| cellpadding="20" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || [http://code.google.com/p/wispinabox/issues/list] || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| WispBox wiki || http://code.google.com/p/wispinabox/w ||<br />
|-<br />
| Afrimesh wiki || http://code.google.com/p/afrimesh/w<br />
|-<br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4738WISP in a Box Development2009-08-04T12:59:55Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{| style="cellpadding="20" cellspacing="0" border="1"<br />
! Resource !! URL !! Description<br />
|-<br />
| Mailing List - User Support || || Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development || || Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker || [http://code.google.com/p/wispinabox/issues/list] || Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC || http://webchat.freenode.net/?channels=afrimesh || For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| WispBox wiki || http://code.google.com/p/wispinabox/w ||<br />
|-<br />
| Afrimesh wiki || http://code.google.com/p/afrimesh/w<br />
|-<br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4737WISP in a Box Development2009-08-04T12:56:41Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{|<br />
-<br />
| Mailing List - User Support<br />
|<br />
| Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development<br />
|<br />
| Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Issue tracker<br />
| [http://code.google.com/p/wispinabox/issues/list]<br />
| Bug reports and feature requests submitted to the Issue tracker are more likely to receive attention!<br />
|-<br />
| IRC <br />
| http://webchat.freenode.net/?channels=afrimesh<br />
| For IRC client configuration, use: irc.freenode.net, #afrimesh<br />
|-<br />
| WispBox wiki<br />
| http://code.google.com/p/wispinabox/w<br />
| <br />
|-<br />
| Afrimesh wiki<br />
| http://code.google.com/p/afrimesh/w<br />
| <br />
|-<br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4736WISP in a Box Development2009-08-04T12:53:41Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{|<br />
-<br />
| Mailing List - User Support<br />
|<br />
| Users, Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Mailing List - Development<br />
|<br />
| Contributors and Developers should subscribe to and follow this list.<br />
|-<br />
| Bug reports and feature requests<br />
| [http://code.google.com/p/wispinabox/issues/list]<br />
|-<br />
| IRC <br />
| Server: irc.freenode.net Channel: #afrimesh<br />
| http://webchat.freenode.net/?channels=afrimesh<br />
|-<br />
| WispBox wiki<br />
| http://code.google.com/p/wispinabox/w<br />
|<br />
|-<br />
| Afrimesh wiki<br />
| http://code.google.com/p/afrimesh/w<br />
| <br />
|-<br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4735WISP in a Box Development2009-08-04T12:43:07Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Upstream Projects ===<br />
<br />
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:<br />
<br />
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard code.<br />
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images.<br />
<br />
<br />
=== Core Project Infrastructure ===<br />
<br />
Project Communication<br />
<br />
{|<br />
-<br />
| User mailing list<br />
|<br />
| Users, Contributers and Developers should subscribe to and follow this list.<br />
|-<br />
| Development mailing list<br />
|<br />
| Contributers and Developers should subscribe to and follow this list.<br />
|-<br />
| Bug reports and feature requests<br />
| [http://code.google.com/p/wispinabox/issues/list]<br />
|-<br />
| IRC <br />
| irc.freenode.net #afrimesh<br />
|<br />
|-<br />
| WispBox wiki<br />
| [http://code.google.com/p/wispinabox/w/]<br />
|<br />
|-<br />
| Afrimesh wiki<br />
| [http://code.google.com/p/afrimesh/w/]<br />
| <br />
|-<br />
<br />
|}<br />
<br />
Development Resources<br />
{{{<br />
| afrimesh project site<br />
| http://code.google.com/p/afrimesh<br />
|-<br />
|<br />
|Butter<br />
|Ice cream <br />
}}}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4734WISP in a Box Development2009-08-04T12:29:46Z<p>Antoine: /* Project Infrastructure */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Project Infrastructure ===<br />
<br />
{|<br />
| IRC <br />
| Apple<br />
|-<br />
|Bread<br />
|Pie<br />
|-<br />
|Butter<br />
|Ice cream <br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4733WISP in a Box Development2009-08-04T12:29:24Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Project Infrastructure ===<br />
<br />
{|<br />
| IRC | Apple<br />
|-<br />
|Bread<br />
|Pie<br />
|-<br />
|Butter<br />
|Ice cream <br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4732WISP in a Box Development2009-08-04T12:29:04Z<p>Antoine: </p>
<hr />
<div>----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Project Infrastructure ===<br />
<br />
{|<br />
|IRC<br />
|Apple<br />
|-<br />
|Bread<br />
|Pie<br />
|-<br />
|Butter<br />
|Ice cream <br />
|}<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4731WISP in a Box Development2009-08-04T12:24:39Z<p>Antoine: </p>
<hr />
<div><br />
----<br />
<br />
== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' from our project.<br />
<br />
[[Image:libre_software_cycle.png|right|frame|The Libré Software Development Cycle]]<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
<br />
=== Project Infrastructure ===<br />
<br />
<br />
<br />
----</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4730WISP in a Box Development2009-08-04T12:21:11Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div>== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]<br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' of our project.<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
=== Project Infrastructure ===</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4729WISP in a Box Development2009-08-04T12:19:38Z<p>Antoine: </p>
<hr />
<div>== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' of our project.<br />
<br />
* '''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
<br />
* '''Contributors''' - ''Contributors'' are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
<br />
* '''Developers''' - ''Developers'' perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4728WISP in a Box Development2009-08-04T12:18:56Z<p>Antoine: </p>
<hr />
<div>== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' of our project.<br />
* ''Users''' - We live and breathe for these special individuals as, without them, none of us would have paying jobs. Their interaction with the project is usually in the form of downloading and using our software, reporting bugs on the mailing list or bug tracker and asking for more features.<br />
* ''Contributors'' - Contributors are usually also users but they have both the ability and the desire to contribute code patches, documentation and generally contribute their expertise to project development discussions. Often, future developers on a project are drawn from the pool of contributers. Contributors are a necessary condition to the long-term sustainability of Libré projects. For this reason all new developers are first required to spend some time as a contributor to the project before they are "handed the keys to the house" and gain full access to the project infrastructure.<br />
* ''Developers'' - Developers perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.<br />
<br />
[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4727WISP in a Box Development2009-08-04T12:08:24Z<p>Antoine: </p>
<hr />
<div>== Developer Guide ==<br />
<br />
WISP in a Box development is organized as an Open-Source or [http://en.wikipedia.org/wiki/Free_software Libré] software project. <br />
<br />
In order to understand what this means and be able to work together in this way we need to agree on the definitions of the following five words:<br />
<br />
* '''Upstream''' - We use the term ''Upstream'' to refer to projects which our project makes use of. For example [http://net-snmp.sourceforge.net/ net-snmp] and [http://code.google.com/p/afrimesh afrimesh] are both ''upstream'' projects of the WispBox.<br />
* '''Downstream''' - ''Downstream'' are projects who use our code. For example, if someone were to create a linux distribution which focused on adding VOIP services to a WISP and which used [http://code.google.com/p/wispinabox WispBox] as a dependency then that project would be considered to be ''downstream'' of our project.<br />
* ''Users''' - We live and breathe for these special individuals as they are our "La Raison d’entre" Their interaction with the project is usually in the form of downloading and using our software, reporting bugs and asking for more features.<br />
* ''Contributors'' - <br />
* ''Developers'' - <br />
<br />
[[Image:libre_software_cycle.png|left|frame|The Libré Software Development Cycle]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=File:Libre_software_cycle.png&diff=4726File:Libre software cycle.png2009-08-04T11:49:20Z<p>Antoine: uploaded a new version of "Image:Libre software cycle.png"</p>
<hr />
<div></div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4725WISP in a Box Development2009-08-04T11:48:13Z<p>Antoine: </p>
<hr />
<div>== Developer Guide ==<br />
<br />
[[Image:libre_software_cycle.png|frame|The Libre Software Development Cycle]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4724WISP in a Box Development2009-08-04T11:47:31Z<p>Antoine: </p>
<hr />
<div>== Developer Guide ==<br />
<br />
[[Image:libre_software_cycle.png|border|The Libre Software Development Cycle]]<br />
''The Libre Software Development Cycle''</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4723WISP in a Box Development2009-08-04T11:46:01Z<p>Antoine: </p>
<hr />
<div>== Developer Guide ==<br />
<br />
[[Image:libre_software_cycle.png|The Libre Software Development Cycle]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4722WISP in a Box Development2009-08-04T11:45:39Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div><br />
== Developer Guide ==<br />
<br />
[[Image:libre_software_cycle.png|caption]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4721WISP in a Box Development2009-08-04T11:45:23Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div><br />
== Developer Guide ==<br />
<br />
[[File:libre_software_cycle.png]|foo]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4720WISP in a Box Development2009-08-04T11:44:18Z<p>Antoine: /* Developer Guide */</p>
<hr />
<div><br />
<br />
== Developer Guide ==<br />
<br />
[[Image:libre_software_cycle.png]|foo]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=File:Libre_software_cycle.png&diff=4719File:Libre software cycle.png2009-08-04T11:43:28Z<p>Antoine: </p>
<hr />
<div></div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=WISP_in_a_Box_Development&diff=4718WISP in a Box Development2009-08-04T11:43:04Z<p>Antoine: New page: == Developer Guide == foo</p>
<hr />
<div><br />
<br />
== Developer Guide ==<br />
<br />
[[Image:libre_software_cycle.png|foo]]</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=AfrimeshToDo&diff=4714AfrimeshToDo2009-07-05T16:30:39Z<p>Antoine: </p>
<hr />
<div>[[Category: WISP in a box]]<br />
<br />
== Dashboard ==<br />
* Customers<br />
** Recharge -> Solicit feedback<br />
** Manage -> How to make MAC/IP auth obvious from interface ?<br />
** Manage -> Implement seconds left field<br />
** Manage -> Fix New/Modify/Delete/Password DONE<br />
** Manage -> Paginate when > 'x' users<br />
** Prices -> Implement DONE<br />
*** Add or delete a plan <br />
*** Set price & seconds DONE<br />
* Network<br />
** Map -> Refactor DONE<br />
** Map -> Populate popups DONE<br />
** Map -> Cache map data CODESPRINT<br />
** Map -> Satellite overlay ? <br />
** Health -> Health monitors <br />
** Health -> Mesh congestion<br />
** Health -> Messages<br />
** Health -> Use case -> Spot misbehaving doze boxes<br />
** Health -> Manage cap<br />
** Health -> Query router settings, firmware versions?<br />
** Activity -> Show seconds left<br />
** Activity -> Show router name/address<br />
** Activity -> Traffic info<br />
* Settings<br />
** Link to webmin<br />
** Mesh -> Provisioning<br />
*** use cases for: flashing firmware, installing packages, changing settings ?<br />
** Mesh -> Set throttling on coova's<br />
** Mesh -> Bandwidth/QOS<br />
*** Manage cap<br />
*** So start off with small allocation<br />
*** Track use<br />
*** Speak to David Johnson<br />
*** Release buffer into the system<br />
** Internet -> Webmin<br />
** Internet -> Drop assumption that we control the gateway and rethink DONE<br />
** Internet -> Bandwidth/QOS<br />
** Internet -> Configure DONE<br />
* Install<br />
** On first run, default to settings pages<br />
** Map -> Configure map: location, size, source (remote/local) CODESPRINT<br />
<br />
== Routers ==<br />
* Authentication<br />
** coova -> finish packaging config<br />
** a2billing -> write bridge DONE<br />
* Mini Dash<br />
** coova -> Make splash pretty<br />
** coova -> Fix time left fields<br />
** Diagnostics on splash!<br />
** Signals strength indicator<br />
* Install<br />
** On first run, default to settings page<br />
** Zoomed to max extent<br />
<br />
== Deployment ==<br />
* Start doing daily builds<br />
* Dashboard Installation<br />
** Ubuntu packages DONE<br />
** ISO<br />
** Download/Generate map data CODESPRINT<br />
** phpMyPrepaid package<br />
* Router Installation<br />
** OpenWRT Packages -> broadcom, atheros DONE<br />
*** Firewall configs<br />
*** Auto-configuration<br />
** Pre-installed firmware image<br />
* Documentation<br />
** Dashboard installation<br />
** Router installation<br />
** Instructions for using with other firmwares<br />
<br />
<br />
== Security ==<br />
* Implement auth<br />
<br />
== Logging ==<br />
* Set up some guidelines<br />
<br />
== Dev Docs ==<br />
* Document LQ colour coding<br />
<br />
== Map Biz Process ==<br />
* For docs<br />
<br />
== Reporting Interface ==<br />
* Expose the program tree to plugin / report authors DONE<br />
* Read only<br />
** What are my router channels ?<br />
** etc.</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=AfrimeshToDo&diff=4713AfrimeshToDo2009-07-05T16:29:54Z<p>Antoine: </p>
<hr />
<div>[[Category: WISP in a box]]<br />
<br />
== Dashboard ==<br />
* Customers<br />
** Recharge -> Solicit feedback<br />
** Manage -> How to make MAC/IP auth obvious from interface ?<br />
** Manage -> Implement seconds left field<br />
** Manage -> Fix New/Modify/Delete/Password DONE<br />
** Manage -> Paginate when > 'x' users<br />
** Prices -> Implement DONE<br />
*** Add or delete a plan <br />
*** Set price & seconds DONE<br />
* Network<br />
** Map -> Refactor DONE<br />
** Map -> Populate popups DONE<br />
** Map -> Cache map data CODESPRINT<br />
** Map -> Satellite overlay ? <br />
** Health -> Health monitors <br />
** Health -> Mesh congestion<br />
** Health -> Messages<br />
** Health -> Use case -> Spot misbehaving doze boxes<br />
** Health -> Manage cap<br />
** Health -> Query router settings, firmware versions?<br />
** Activity -> Show seconds left<br />
** Activity -> Show router name/address<br />
** Activity -> Traffic info<br />
* Settings<br />
** Link to webmin<br />
** Mesh -> Provisioning<br />
*** use cases for: flashing firmware, installing packages, changing settings ?<br />
** Mesh -> Set throttling on coova's<br />
** Mesh -> Bandwidth/QOS<br />
*** Manage cap<br />
*** So start off with small allocation<br />
*** Track use<br />
*** Speak to David Johnson<br />
*** Release buffer into the system<br />
** Internet -> Webmin<br />
** Internet -> Drop assumption that we control the gateway and rethink DONE<br />
** Internet -> Bandwidth/QOS<br />
** Internet -> Configure DONE<br />
* Install<br />
** On first run, default to settings pages<br />
** Map -> Configure map: location, size, source (remote/local) CODESPRINT<br />
<br />
== Routers ==<br />
* Authentication<br />
** coova -> finish packaging config<br />
** a2billing -> write bridge<br />
* Mini Dash<br />
** coova -> Make splash pretty<br />
** coova -> Fix time left fields<br />
** Diagnostics on splash!<br />
** Signals strength indicator<br />
* Install<br />
** On first run, default to settings page<br />
** Zoomed to max extent<br />
<br />
== Deployment ==<br />
* Start doing daily builds<br />
* Dashboard Installation<br />
** Ubuntu packages DONE<br />
** ISO<br />
** Download/Generate map data CODESPRINT<br />
** phpMyPrepaid package<br />
* Router Installation<br />
** OpenWRT Packages -> broadcom, atheros DONE<br />
*** Firewall configs<br />
*** Auto-configuration<br />
** Pre-installed firmware image<br />
* Documentation<br />
** Dashboard installation<br />
** Router installation<br />
** Instructions for using with other firmwares<br />
<br />
<br />
== Security ==<br />
* Implement auth<br />
<br />
== Logging ==<br />
* Set up some guidelines<br />
<br />
== Dev Docs ==<br />
* Document LQ colour coding<br />
<br />
== Map Biz Process ==<br />
* For docs<br />
<br />
== Reporting Interface ==<br />
* Expose the program tree to plugin / report authors DONE<br />
* Read only<br />
** What are my router channels ?<br />
** etc.</div>Antoinehttp://wirelessafrica.meraka.org.za/wiki/index.php?title=User:Antoine&diff=4712User:Antoine2009-07-05T13:20:42Z<p>Antoine: </p>
<hr />
<div>'''Name:''' Antoine van Gelder<br />
<br />
'''Email:''' antoine [at] 7degrees.co.za<br />
<br />
'''Afrimesh:''' [http://code.google.com/p/afrimesh/ http://code.google.com/p/afrimesh/]<br />
<br />
'''WispBox:''' [http://code.google.com/p/wispinabox/ http://code.google.com/p/wispinabox/]</div>Antoine