This meeting will be taking place at MeetingSpace on Sunday June 15th, 2003 at 2pm.
(Due to the FreeNetworksConference taking place on the 2nd sunday, we will need to reschedule... Of course, the 15th is Fathers Day....)
Agenda:
FreeNetworksConference summary
Update on latest exciting news about SnowNet and MtBaldi. A new directional antenna facing Tacoma has been installed, aimed, and tested. This means that Seattle Wireless members can have just ONE hop to reach TacomaZone all the way from Seattle. More arrangements being made to have an antenna aimed towards eastern Washington and another aimed at Mount Rainier in anticipation of future nodes.
Discussion and planning of events for 2003wirelessfieldday. Besides being a demonstration and/or test of wireless technology for the future of SnowNet, it is also a larger scale "get together" for Seattle Wireless.
- General question/answer period at the end of the meeting (as usual).
If you would like to propose additional items to the current or future agenda, please enter them below or the MailingList... By proposing them in advance, rather than submitting them out of the blue at the meeting, some agenda items can be researched in advance of the meeting so that there is a chance of a more thorough/detailed answer.
Discussion on the standardization of how each SWN affiliated node presents or doesn't present a "splash page" or "gateway page" when a user connects to a SWN node. Should all nodes have some sort of splash page? Currently, some nodes don't have a splash page at all, but simply give the user direct internet access. Without a splash page, the sense of belonging to a Community Wireless Network is lost (as the user only sees the node as free internet as opposed to having free internet as part of the community features menu choices). As an example, the SWN node at NodeBitstar doesn't have a splash page but simply gives me free internet access; it's be neat to at least have a splash page mentioning that the node is also webmasterd by Scrappy.
Publicity for wireless usage can be done via innovative partnership with KCLS as Netmasters. SWN volunteers can dedicate themselves to teaching "how to become wireless" classes. In this way, you get official promotion from KCLS, a ready-made audience culled by KCLS, a convenient public place to do classes all over the county because KCLS is located all over the place, etcetera. A special point can be made that KCLS right now doesn't have any classes scheduled for wireless internet computing (probably because they have no wireless expert teachers). This seems like a plum opportunity for Seattle Wireless to step up and teach some of the basics such as how to set up your laptop for wireless, etcetera. Of course, public freenetworks can be *ahem* mentioned prominently during the sessions. (StartideRising)
- With the larger number of nodes, is there any use for a offline tool that can display the locations of nodes?
What ever happened to the Jabber Server project at JabberServer? Should the Jabber Chat be used at the means that members (who are not physically at the meeting) can chat with people at the meeting?
Should TradingPost be listed on the FrontPage?
Is creation of something like http://www.seattlewireless.net/index.cgi/Vandals useful in showing users (who don't have admin powers to look at logs) those people who are vandalizing the website? I would like to propose at the next meeting that website logs be presented to University of Washington admin to get the specific person's computing privileges revoked for awhile.
In lieu of the freenetworks conference, at the meeting, is will there be discussion of the concepts in RequirementsDocument? A quote from its author: To date, no culture or community has emerged in Seattle or anywhere else, that is concerned with true owner-operated, routed wireless more than one hop. All of the WiFi groups (...) seem overwhelmingly composed of hub-and-spoke efforts such as sharing DSL or Cablemodem accounts, or point-to-point private links.
The list of varmints is growing at Vandals.
Any ideas for expanding into MustHaveCoverageArea zones?
