#7137 NORM Retriag: Renewed G1G1 needs a logistics solution, and perhaps an entre team.
Zarro Boogs per Child
bugtracker at laptop.org
Fri May 30 15:05:21 EDT 2008
#7137: Renewed G1G1 needs a logistics solution, and perhaps an entre team.
-------------------------------------+--------------------------------------
Reporter: sph0lt0n | Owner: djbclark
Type: defect | Status: new
Priority: normal | Milestone: Retriage, Please!
Component: infrastructure-internal | Version: Mass Production Hardware
Keywords: | Verified: 0
Blocking: | Blockedby:
-------------------------------------+--------------------------------------
This is not a software bug report.[[BR]]
This is not a hardware bug report.[[BR]]
This is a logistical bug report; please route to the logistics team.[[BR]]
This ticket tracks deficiencies in the OLPC Fund-raising / non-educational
deployments, also known as Give One Get One or G1G1.[[BR]]
The characteristics of these deployments (and prime difference from the
standard deployment model) seem to be:[[BR]]
- XO-1 (or later model) systems are sold to private individuals in single
unit quantities (as opposed to large scale deployments).[[BR]]
- Deployed units are not associated with a 'school deployment', i.e. often
with no other mesh-accessible devices (other XO's or school server) are
available to the recipient.[[BR]]
- No 'school server' available (so registration is pointless, backups
cannot be made, cached content is unavailable, no opportunity for central-
point content filters, etc)[[BR]]
- No deployment prime (such as a school server administrator or teacher)
for 'getting started' questions or as a point-of-contact.[[BR]]
- Spares and repairs solution expected to be provided external to the
deployment (by 'repair centers' as opposed to being a part of the
deployment).[[BR]]
- Heavy reliance on an unconstrained variety of 802.11 WiFi networking (as
opposed to mesh) access points, often poorly administered or
unadministered.[[BR]]
- Primary users are expected to be adults with the primary applications
ranging from software development platform to technology demonstration
unit to low-cost laptop computer.[[BR]]
- Much better availability of high-speed Internet access (often broadband)
than is expected in standard deployments. [[BR]]
- Much more reliable power infrastructure (AC always available, off grid
solutions viewed as a novelty as opposed to a requirement).[[BR]]
- Printing is ubiquitous, (as opposed to highly cost prohibitive and
centralized at a school) and support for personal printers is
expected.[[BR]]
- Much greater demand to interoperate with non-XO computers (Windows, Mac,
Linux) and to virtualized XO's on those platforms.[[BR]]
- Much better distribution infrastructure than usually expected (secure
3-day delivery of individual units by truck is the norm, anti-theft
measures are largely unneeded, the possibility of central stocking of
repair parts with on-demand delivery exists, etc.)[[BR]]
- Greater demand for 'security disabled' software, including developer
builds, and non-OLPC-maintained operating system stacks (Ubuntu, Debian,
etc.)[[BR]]
These vastly different characteristics in deployment needs dictate the
need for a seperate deployment strategy to address the needs of G1G1-style
donors, or a clear (and strongly marketed) statement of non-support for
the needs of this market. This is especially true if an identical product
is being delivered into both traditional educational programs and non-
traditional fund-raising programs.
Failure to address this will impact development for both the traditional
educational environment and the non-traditional fund-raising programs as
developers are pulled-off the critical demands of one to address the needs
of the other. Neither will be well served.
Failure to recognise the differing needs of the two programs inhibits even
the reporting of defects for both programs. A statements like [[BR]]
"''This is'' [[BR]]
{ "an educational" | "a fund-raising" }[[BR]]
''program, so you shouldn't expect a device developed for'' [[BR]]
{ "a fund-raising" | "an educational" }[[BR]]
''program to effectively address your needs''."
can be used to dismiss a problem report for either program.
Much of the information associated with this defect would be better
tracked on the wiki. I would request that if this ticket is not rejected
such a wiki page should be created and listed in the response.
--
Ticket URL: <http://dev.laptop.org/ticket/7137>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list