Differences between revisions 8 and 9
Revision 8 as of 2006-11-30 20:26:58
Size: 4005
Comment: minor fixes, embellishment
Revision 9 as of 2007-11-23 18:00:51
Size: 4005
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
'''Location:''' UrbanGrind[[BR]]
'''Date and Time:''' November 29, 2006, 6:30pm[[BR]]
'''Scribe:''' CalebPhillips[[BR]]
'''Location:''' UrbanGrind<<BR>>
'''Date and Time:''' November 29, 2006, 6:30pm<<BR>>
'''Scribe:''' CalebPhillips<<BR>>

Location: UrbanGrind
Date and Time: November 29, 2006, 6:30pm
Scribe: CalebPhillips

Agenda

Notes

  • RussellSenior starts meeting, DonPark (aka ElPresidente) is out of town.

  • Talk about recent addition to Mississippi on the GrandCentralBaking roof, and a couple possible new nodes. Namely at the rebuilding center's "cathedral", SelfEnhancementInc, etc.. Russell talks about the sentencing hearing on the vandalism.

  • Russell mentions that NodeRerun is semi-functional, but has a mostly-broken AP, KeithLofstrom donates a hackable WRT54GS v2.0.

  • ElizabethLofts and YukonTavern have contacted us about becoming nodes.

  • Some discussion about the protocol for people (non-NetworkOperationsTeam) to use when they visit a node that is broken. Particularly in the context of recent trouble/non-workingness at NodeEcoTrust. The suspicion is that one of the APs is bad, flakes out when there are too many users (according to Troy). Some discussion of using PTP general funds to replace failing gear at business nodes. General sentiment is that this isn't necessary. The general answer to discovered node problems:

    • First and foremost, email PTP (ops or general or something, anything!) to let us know there is a problem
    • Talk to staff, determine where gear is
    • Make sure wiring is correct (Russell notes that in the presence of a nucab, ethernet should typically go in the AP's LAN port, not the WAN/Internet port)
    • Try to diagnose problem
    • If there is a problem with the NuCab, contact a NetworkOperationsTeam member to get access (or assistance)

    • Let ops@personaltelco.net know what you did (or needs doing). Non-subscribers to the ops list will have their messages go to the moderator queue, but Keegan says he checks it fairly regularly and forwards them on as appropriate.

  • Announce addition to NodeFirstUnitarian node. Talk about how this node is cool.

  • Board Meeting: coming up next Wednesday, December 6th. We think DonPark won't be there. Troy agrees to attend so there will at least be a quorum present. Caleb says that the chief agenda item should be to officially sign a copy of the bylaws. Caleb thinks we should add a bylaw that at all board meetings, PTP will buy beer.

  • Holiday Party: We think Don will be out of town, so discuss possible candidate locations. CalebPhillips is appointed to be the HolidayPartySteeringCommittee. He immediately delegates all responsibility to MichaelWeinberg who proceeds to do all the work.

    • 1st Choice: Rose and the Raindrop: Going out of business on Dec. 31st, so this would be a good point to collect our gear and say goodbye (and thanks). Great beer. Balcony is free if you pay 100+ in food/drink. MichaelWeinberg is going to ask about rates and availability.

    • 2nd Choice: Amnesia Brewing: Can we rent this out? Is it available. Somewhere on MGP seems a good choice. Pretty good beer too.
    • 3rd Choice: Lucky Lab, either NW or SE. Is it available. Some discussion of the goodness of their beer.
    • 4th Choice: Roots Brewing. Can we rent this out? Is it available? Will people show up to this location?
  • Troy does a Finance Report. MGP has about 1000 and PTP has about 4000. Russell asks Troy to add the figures in the notes here. MichaelWeinberg suggests changing the name of MGP monies to something else since it isn't part of the grant any more. Russell suggests MissNet.

  • ScottBrown describes an odd problem with one of his 5GHz links, where every 70 minutes some event occurs that resets the end-point hardware. Isolating power (putting it on a battery) or temporarily blocking incoming RF were suggested diagnostics.


[CategoryMeetingNotes]

MeetingNovember2006 (last edited 2007-11-23 18:00:51 by localhost)