Differences between revisions 2 and 5 (spanning 3 versions)
Revision 2 as of 2003-05-04 01:40:18
Size: 3826
Editor: 12-225-146-200
Comment:
Revision 5 as of 2007-11-23 18:01:28
Size: 3826
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
PTP Weekly Meeting - 11 February 2003[[BR]] PTP Weekly Meeting - 11 February 2003<<BR>>
Line 3: Line 3:
Time: Tuesday 7 - 8:30 pm[[BR]][[BR]]
Location: Linux Fund, 408 SW 2nd Avenue 430, Portland, Oregon[[BR]][[BR]]
Scribe: EugeneKeam[[BR]][[BR]]
Attendees: AdamShand, LonnieWormley, AaronJohnson, AaronBaer, NatPowning, DonPark, JerrittCollord, DarrinEden, AndrewWoods, NigelBallard, AlinaJensen, ChristianJensen, LucasSheehan, JackHoneycutt, EugeneKeam[[BR]][[BR]]
Time: Tuesday 7 - 8:30 pm<<BR>><<BR>>
Location: Linux Fund, 408 SW 2nd Avenue 430, Portland, Oregon<<BR>><<BR>>
Scribe: EugeneKeam<<BR>><<BR>>
Attendees: AdamShand, LonnieWormley, AaronJohnson, AaronBaer, NatPowning, DonPark, JerrittCollord, DarrinEden, AndrewWoods, NigelBallard, AlinaJensen, ChristianJensen, LucasSheehan, JackHoneycutt, EugeneKeam<<BR>><<BR>>
Line 8: Line 8:
AGENDA[[BR]] AGENDA<<BR>>
Line 10: Line 10:
1. Pebble and Bewitched distro comparison[[BR]]
2. New nodes in the queue[[BR]]
3. Site surveys[[BR]]
4. General issues (Adam)[[BR]]
1. Pebble and Bewitched distro comparison<<BR>>
2. New nodes in the queue<<BR>>
3. Site surveys<<BR>>
4. General issues (Adam)<<BR>>
Line 15: Line 15:
- - - - -[[BR]] - - - - -<<BR>>
Line 17: Line 17:
1. Pebble and Bewitched distro comparison[[BR]] 1. Pebble and Bewitched distro comparison<<BR>>
Line 19: Line 19:
briefly discussed below[[BR]] briefly discussed below<<BR>>
Line 21: Line 21:
2. New nodes in the queue[[BR]] 2. New nodes in the queue<<BR>>
Line 23: Line 23:
AlinaJensen[[BR]]
did lonnie look into easystreet usage policy?, i question qwest's usage policies, qwest should train their employees better[[BR]]
AlinaJensen<<BR>>
did lonnie look into easystreet usage policy?, i question qwest's usage policies, qwest should train their employees better<<BR>>
Line 26: Line 26:
DonPark[[BR]]
qwest's business class usage policy differs from residential[[BR]]
DonPark<<BR>>
qwest's business class usage policy differs from residential<<BR>>
Line 29: Line 29:
ChristianJensen[[BR]]
paper ips run on nat[[BR]]
ChristianJensen<<BR>>
paper ips run on nat<<BR>>
Line 32: Line 32:
DonPark[[BR]]
recommend viewing qwest's isp's usage policy on the web[[BR]]
DonPark<<BR>>
recommend viewing qwest's isp's usage policy on the web<<BR>>
Line 35: Line 35:
AlinaJensen[[BR]]
what to do about the tower donation from baker city?, requires professional installers and proper transportation plans[[BR]]
AlinaJensen<<BR>>
what to do about the tower donation from baker city?, requires professional installers and proper transportation plans<<BR>>
Line 38: Line 38:
AdamShand[[BR]]
we have professional installers available to us via our listserv, let's do it, do we have a location to store it and install it?[[BR]]
AdamShand<<BR>>
we have professional installers available to us via our listserv, let's do it, do we have a location to store it and install it?<<BR>>
Line 41: Line 41:
AlinaJensen[[BR]]
the tower is supposed to come out in june[[BR]]
AlinaJensen<<BR>>
the tower is supposed to come out in june<<BR>>
Line 44: Line 44:
AdamShand[[BR]]
hams took care of the height limitations with fcc rules adjustments, 100 feet maximum so we're okay with the donated radio tower height, private property owners supposedly own 100 feet above affected property, however need a ham license[[BR]]
AdamShand<<BR>>
hams took care of the height limitations with fcc rules adjustments, 100 feet maximum so we're okay with the donated radio tower height, private property owners supposedly own 100 feet above affected property, however need a ham license<<BR>>
Line 47: Line 47:
3. Site surveys[[BR]] 3. Site surveys<<BR>>
Line 49: Line 49:
x[[BR]] x<<BR>>
Line 51: Line 51:
4. General issues (Adam)[[BR]] 4. General issues (Adam)<<BR>>
Line 53: Line 53:
AdamShand[[BR]]
theresa interested in a summer fundraiser, need a park permit, permits are affordable, perhaps pull a stunt and get media attention, setup a public tip jar concept, npr style node usage much like the pledge drives[[BR]]
AdamShand<<BR>>
theresa interested in a summer fundraiser, need a park permit, permits are affordable, perhaps pull a stunt and get media attention, setup a public tip jar concept, npr style node usage much like the pledge drives<<BR>>
Line 56: Line 56:
ChristianJensen[[BR]]
pull a geeky stunt on television[[BR]]
ChristianJensen<<BR>>
pull a geeky stunt on television<<BR>>
Line 59: Line 59:
AaronJohnson[[BR]]
that would be a good way to encourage people to get setup on an auth account[[BR]]
AaronJohnson<<BR>>
that would be a good way to encourage people to get setup on an auth account<<BR>>
Line 62: Line 62:
AdamShand[[BR]]
specify a suggested donation, something like npr nagware, drew assigned bandwidth capping and annoyware project by adam[[BR]]
AdamShand<<BR>>
specify a suggested donation, something like npr nagware, drew assigned bandwidth capping and annoyware project by adam<<BR>>
Line 65: Line 65:
DonPark[[BR]]
nagware might encourage hacking[[BR]]
DonPark<<BR>>
nagware might encourage hacking<<BR>>
Line 68: Line 68:
AaronJohnson[[BR]]
people might share accounts to get around annoyware[[BR]]
AaronJohnson<<BR>>
people might share accounts to get around annoyware<<BR>>
Line 71: Line 71:
AndrewWoods[[BR]]
bandwidth capping might constitute paid service[[BR]]
AndrewWoods<<BR>>
bandwidth capping might constitute paid service<<BR>>
Line 74: Line 74:
AdamShand[[BR]]
drew is the pledge drive coordinator[[BR]]
AdamShand<<BR>>
drew is the pledge drive coordinator<<BR>>
Line 77: Line 77:
AaronBaer[[BR]]
we should spec out and create a timeline for completion, a project scope, note authorization server changes[[BR]]
AaronBaer<<BR>>
we should spec out and create a timeline for completion, a project scope, note authorization server changes<<BR>>
Line 81: Line 81:
don is the new ops team leader, i'm backing away from that day-to-day role, one person that shapes where ptp goes, ops defined as establishment of new nodes and maintenance of existing nodes, last year was an adminstrative year for ptp, this year it is the network year, in other words development of a mansig[[BR]] don is the new ops team leader, i'm backing away from that day-to-day role, one person that shapes where ptp goes, ops defined as establishment of new nodes and maintenance of existing nodes, last year was an adminstrative year for ptp, this year it is the network year, in other words development of a mansig<<BR>>
Line 83: Line 83:
AdamShand[[BR]]
big item goals for this year, (1) create an automated cd to setup hotspots i.e. sputnik and evilbunny, (2) standardized ap hardware such as soekris, (3) standardized distro decision and then create an image cd, (4) create automation tools i.e. pushing out changes, upgrade apps, monitoring integration for bandwidth usage, (5) build a network i.e. mansig and mesh leader, (6) develop > experimentation > load and performance testing > implementation[[BR]]
AdamShand<<BR>>
big item goals for this year, (1) create an automated cd to setup hotspots i.e. sputnik and evilbunny, (2) standardized ap hardware such as soekris, (3) standardized distro decision and then create an image cd, (4) create automation tools i.e. pushing out changes, upgrade apps, monitoring integration for bandwidth usage, (5) build a network i.e. mansig and mesh leader, (6) develop > experimentation > load and performance testing > implementation<<BR>>
Line 86: Line 86:
DonPark[[BR]]
i'll be in thailand starting march 5, lata fools[[BR]][[BR]]
DonPark<<BR>>
i'll be in thailand starting march 5, lata fools<<BR>><<BR>>
Line 89: Line 89:
- - - - -[[BR]][[BR]] - - - - -<<BR>><<BR>>
Line 91: Line 91:
Next weekly meeting: 18 February 2002[[BR]]
Location: LinuxFundOffice[[BR]]
Time: 7 - 8:30 pm[[BR]][[BR]]
Next weekly meeting: 18 February 2002<<BR>>
Location: LinuxFundOffice<<BR>>
Time: 7 - 8:30 pm<<BR>><<BR>>

PTP Weekly Meeting - 11 February 2003

Time: Tuesday 7 - 8:30 pm

Location: Linux Fund, 408 SW 2nd Avenue 430, Portland, Oregon

Scribe: EugeneKeam

Attendees: AdamShand, LonnieWormley, AaronJohnson, AaronBaer, NatPowning, DonPark, JerrittCollord, DarrinEden, AndrewWoods, NigelBallard, AlinaJensen, ChristianJensen, LucasSheehan, JackHoneycutt, EugeneKeam

AGENDA

1. Pebble and Bewitched distro comparison
2. New nodes in the queue
3. Site surveys
4. General issues (Adam)

- - - - -

1. Pebble and Bewitched distro comparison

briefly discussed below

2. New nodes in the queue

AlinaJensen
did lonnie look into easystreet usage policy?, i question qwest's usage policies, qwest should train their employees better

DonPark
qwest's business class usage policy differs from residential

ChristianJensen
paper ips run on nat

DonPark
recommend viewing qwest's isp's usage policy on the web

AlinaJensen
what to do about the tower donation from baker city?, requires professional installers and proper transportation plans

AdamShand
we have professional installers available to us via our listserv, let's do it, do we have a location to store it and install it?

AlinaJensen
the tower is supposed to come out in june

AdamShand
hams took care of the height limitations with fcc rules adjustments, 100 feet maximum so we're okay with the donated radio tower height, private property owners supposedly own 100 feet above affected property, however need a ham license

3. Site surveys

x

4. General issues (Adam)

AdamShand
theresa interested in a summer fundraiser, need a park permit, permits are affordable, perhaps pull a stunt and get media attention, setup a public tip jar concept, npr style node usage much like the pledge drives

ChristianJensen
pull a geeky stunt on television

AaronJohnson
that would be a good way to encourage people to get setup on an auth account

AdamShand
specify a suggested donation, something like npr nagware, drew assigned bandwidth capping and annoyware project by adam

DonPark
nagware might encourage hacking

AaronJohnson
people might share accounts to get around annoyware

AndrewWoods
bandwidth capping might constitute paid service

AdamShand
drew is the pledge drive coordinator

AaronBaer
we should spec out and create a timeline for completion, a project scope, note authorization server changes

AdamShandBr don is the new ops team leader, i'm backing away from that day-to-day role, one person that shapes where ptp goes, ops defined as establishment of new nodes and maintenance of existing nodes, last year was an adminstrative year for ptp, this year it is the network year, in other words development of a mansig

AdamShand
big item goals for this year, (1) create an automated cd to setup hotspots i.e. sputnik and evilbunny, (2) standardized ap hardware such as soekris, (3) standardized distro decision and then create an image cd, (4) create automation tools i.e. pushing out changes, upgrade apps, monitoring integration for bandwidth usage, (5) build a network i.e. mansig and mesh leader, (6) develop > experimentation > load and performance testing > implementation

DonPark
i'll be in thailand starting march 5, lata fools

- - - - -

Next weekly meeting: 18 February 2002
Location: LinuxFundOffice
Time: 7 - 8:30 pm

DIY or request corrections: EugeneKeam

WeeklyMeeting20030211 (last edited 2007-11-23 18:01:28 by localhost)