Hi all, I _may_ show up. I'm real tired, but real interested... not sure how I'll feel towards the end of the day.
That is irrelevant to my post, here, however. Really, I wanted to suggest that there be an agenda or something. Face time is good and all, but if the point is to figure out how to make a Hacker Space or Spaces happen, then at least some base level of organization would be wise. It sounds like this will end up being a sub-group of the VAGUE group. But it also sounds like there are some fairly new faces planning to attend. We should probably plan on doing an introduction-to-the-group thing where every person introduces his or herself. Here are some ideas... 1) Introduce name and general living/working location 2) Introduce 'Hacker' background... with hacker being used in the broad and proper sense of the word. A person can be an astronomy hacker according to my copy of the New Hacker's Dictionary, for example. 3) Talk about what level of involvement you would like with the Hacker Space - where in the hierarchy of the group would you want to be? Organizing and managing? A responsible and trusted user? A regular user? 4) Talk about how much time you *think* you can devote to the project? 5) Best way to contact you off list, especially if you want to be involved higher up in the hierarchy of responsibility for the project If we nominate one or two people to take notes about who wants to be involved in the higher levels of group hierarchy - meaning, basically, who wants to devote personal time to the many tasks of organizing and realizing the environment - as opposed to supportive users who do not feel like they want to, or have time to, do anything more than pay dues and use the space (which is fine, no complaints) - then we can have a list of names to contact for the first serious organizational meeting (tasks to get done, assign them to persons etc.). We can also have a sign-up sheet for just anyone that wants to keep tabs on it by e-mail. I think that keeping discussions on the VAGUE list is good, but having a short-list of the VAGUERs that actually care would be wise, so that we can organize a little more effectively, when we need to 'call in troops'. -Nick --- Nicholas Floersch (pr. Floor-sh) Stone Environmental, Inc. > -----Original Message----- > From: Vermont Area Group of Unix Enthusiasts > [mailto:[email protected]] On Behalf Of Kevin Thorley > Sent: Tuesday, April 07, 2009 9:37 AM > To: [email protected] > Subject: Re: VT Hackers Meetup > > On Mon, Apr 6, 2009 at 10:39 PM, Stanley Brinkerhoff > <[email protected]> wrote: > > > > > > On Mon, Apr 6, 2009 at 9:38 PM, Josh Sled <[email protected]> > wrote: > >> > >> Kevin Thorley <[email protected]> writes: > >> > Tomorrow (Tuesday the 7th) in Waterbury at the Alchemist. Shall > we > >> > say 6:00? Should I call in advance and try to reserve a few > tables? > >> > >> As I recall, they don't do reservations, and have precious few > tables. > >> Last time I tried was a couple of years ago, though, so you may want > to > >> confirm. > >> > > > > I also seem to remember those tables (and the bar in its entirety) > seemingly > > full anytime I have tried to have a pint there. It might be worth > > mentioning a backup plan (Waterbury Wings?) > > > > Stan > > > > I'll call them around lunch time today and find out what I can. > > Good idea re: backup plan Stan. So Alchemist at 6:00. If things > don't look good we'll head to Waterbury Wings. > > Alchemist: > 23 S Main St > Waterbury, VT 05676 > > Waterbury Wings: > 1 S. Main St. > Waterbury, VT 05676 > > I was going to post links to google maps, but google is having issues > today. The map it shows on the search results page is correct, but > when I click on the map for the bigger version, it points me to a dam > near a reservoir north of 89: > http://tinyurl.com/coyk3d > > Very strange > > Kevin This communication, including any attachments, is solely for the confidential use of the person(s) named above. If you have received this communication in error, please notify the sender immediately and delete/destroy the original. Any reader other than the intended recipient is hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.
