WISP in a Box Development: Difference between revisions
| Line 20: | Line 20: | ||
=== Project Infrastructure === | === Upstream Projects === | ||
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly: | |||
* [http://code.google.com/p/afrimesh '''Afrimesh'''] - the WispBox component integration toolkit and the core management dashboard code. | |||
* [http://uck.sourceforge.net/ '''Ubuntu Customization Kit''' - A set of scripts used by our build system to generate the WispBox livecd images. | |||
=== Core Project Infrastructure === | |||
Project Communication | |||
{| | {| | ||
- | |||
| User mailing list | |||
| | |||
| Users, Contributers and Developers should subscribe to and follow this list. | |||
|- | |||
| Development mailing list | |||
| | |||
| Contributers and Developers should subscribe to and follow this list. | |||
|- | |||
| Bug reports and feature requests | |||
| [http://code.google.com/p/wispinabox/issues/list] | |||
|- | |||
| IRC | | IRC | ||
| | | irc.freenode.net #afrimesh | ||
| | |||
|- | |||
| WispBox wiki | |||
| [http://code.google.com/p/wispinabox/w/] | |||
| | |||
|- | |- | ||
| | | Afrimesh wiki | ||
| | | [http://code.google.com/p/afrimesh/w/] | ||
| | |||
|- | |- | ||
|} | |||
Development Resources | |||
{{{ | |||
| afrimesh project site | |||
| http://code.google.com/p/afrimesh | |||
|- | |||
| | |||
|Butter | |Butter | ||
|Ice cream | |Ice cream | ||
}}} | |||
---- | ---- | ||
Revision as of 14:43, 4 August 2009
Developer Guide
WISP in a Box development is organized as an Open-Source or Libré software project.
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:
- Upstream - We use the term Upstream to refer to projects which our project makes use of. For example net-snmp and afrimesh are both upstream projects of the WispBox.
- 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 WispBox as a dependency then that project would be considered to be downstream from our project.
- 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.
- 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.
- Developers - Developers perform the bulk of the development work and have full access to the project source repositories, servers and other infrastructure.
Upstream Projects
WISP in a Box has many upstream dependencies. The following list are the ones you will see referred to most commonly:
- Afrimesh - the WispBox component integration toolkit and the core management dashboard code.
- [http://uck.sourceforge.net/ Ubuntu Customization Kit - A set of scripts used by our build system to generate the WispBox livecd images.
Core Project Infrastructure
Project Communication
-| User mailing list | Users, Contributers and Developers should subscribe to and follow this list. | |
| Development mailing list | Contributers and Developers should subscribe to and follow this list. | |
| Bug reports and feature requests | [1] | |
| IRC | irc.freenode.net #afrimesh | |
| WispBox wiki | [2] | |
| Afrimesh wiki | [3] |
Development Resources
afrimesh project site