Sameer Verma [EMAIL PROTECTED] writes:
Sorry, but I couldn't make it. Meeting conflict on campus. Does anyone
have notes/irc logs?
Here is what I have:
[18:03]*** You have joined channel #olpc
*** Topic for #olpc: Web support: http://forum.laptop.org | IRC
support: #olpc-help | Deployment:
http://radian.org/notebook/first-deployment | GUI,
activities: #sugar | Content: #olpc-content
*** #olpc: topic set by neuralis, 05:44:05 2008/02/04
*** Users on #olpc: bz_g jdub johnf garycmartin nessy dsaxena
wcohen_ CanoeBerry Hiro2 greebo ivazquez Lerc_tablet webar7
Sargun homunq eightdot reynaldo_ J5 faw xuxa nteon behdad
isforinsects scorche|sh unmadindu hpachas-PE rgs_ joern aa
pschulz01 rennj kfm82 Neskaya nullwork nullman pepe__ nealmcb
xobot mether Kevin` dermoth _sj_ Renault mstrobert dwmw2
blisto1 lars zmedico _bernie philipl paulproteus sjoerd RP
cjb tarbo_ toi mako eMBee blistov svu araujo
*** Users on #olpc: h01ger Robot101 bluehole clajo04_ bluefoxicy
Ian_Daniher_ keithy bbs mpr scorche par gnu{- xjjk jwhite pgf
christel fragalot mburns saigo mtd YChao_ pepse dogmeat
kristian-m dirkx_logon sm|CPU bigeasy lkundrak ThomasWaldmann
danjared [knurds]adc fche cassidy Zdra coderanger orospakr
besonen_mobile__ smithbone m_stone IDoNotKnow ffm|sh shenki
PecisDarbs nickr tglx Blaketh Lerc bdale nrp erikg
summatusmentis dgilmore
*** #olpc modes: +tnc
*** #olpc was created on dimanche 2006/11/26 01:42:47
isforinsects good morning/evening jdub
johnf hi all
nessy hi :)
[18:04]isforinsects garycmartin, I'm not ignoring your last email re
SOM's, I just haven't had time to parse the health stuff.
isforinsects hi johnf, nessy
garycmartin isforinsects: no worry, it's a busy timejust nowfor
all I'm sure!
greebo let's start, isforinsects do you want to run it or me?
:)
[18:05]garycmartin isforinsects: excuse my missing spaces, you can
guess mt HW :-)
isforinsects You know more about the requirements than me.
_sj_ hiya greebo
greebo _sj_, heya!
bz_g aloya
[18:06]greebo ok, how about we start with briefly isforinsects or _sj_
recapping what hq are trying to do, then we can touch base on
what we are tring to achieve and go from there?
[18:07]isforinsects Let's have _sj_ recap, I don't know most/any of
the details of projectdb
[18:08]greebo isforinsects, I mean more about a recap on what hq are
trying to do with getting consistency of what the regions are
doing
greebo let's talk about projectdb after we have a clear picture
of what everyone wants :)
[18:10]_sj_ sure
[18:11]_sj_ olpc wants to provide a steady stream of hardware to
contributors, esp. developers
_sj_ including XOs and active antennas
CanoeBerry and serial adapters
_sj_ and to hand off the process of identifying good
projects/conributors to the community
*** jrb ([EMAIL PROTECTED]) has joined
channel #olpc
*** dwmw2 ([EMAIL PROTECTED]) is now known as
dwmw2_gone
[18:12]_sj_ the current projectdb is too opaque
_sj_ it was set up to catch personal data from contributors
_sj_ but most of the project-definition process, including
reviews and suggestions about where to get hardware
_sj_ (your local community SIG, another person at your
institution, a national chapter, via the contributors program)
[18:13]_sj_ happens before personal data is needed, and can/should be
public
_sj_ a larger-scope projectsharing program to help people
announce projects, find collaborators, and work on
testing/outreach/development with others
_sj_ is related to this data (and sounds closely related to
what you have in mind, pia)
[18:14]_sj_ currently we have this set of db scripts that maintains
submissions from projectdb.olpc.at, but the code is hard to hack
on and stored on dev.olpc.at
_sj_ hard as in -- you have to send a privkey to one of the two
machine maintainers, who are busy...
_sj_ it hasn't seen many people hack on it, mainly c. hager and
a. kaplan to date
[18:15]greebo because it is so hard to find to hack on :)
_sj_ its other main prupose is to produce neat xml exports (and
import shipping updates from brightstar once they confirm
shpiment)
_sj_ so that we have a better-ordered set of email alerts as
the process of getting hardware proceeds
[18:16]_sj_ right now we have to confirm manually that machines have
gone out, and that they've arrived; all of which should be
scriptable (b* provides in the end the tracking #,
