Well the term is quite VAGUE to begin with. I believe it already
incorporates the enthusiasts and as others have already said, we wouldn't
have everything you mentioned without UNIX.

Just my 2 copper though.
--
There are 10 types of people in this world. Those who understand binary and
those who do not.
---
David McClellan


On Wed, Sep 15, 2010 at 10:32 AM, Josh Sled <[email protected]> wrote:

> Before an October meeting, and as a followup to the late August meeting,
> I propose interested parties meet up at 6pm on Wednesday September 22nd
> at the Farmhouse Tap and Grill in Burlington to discuss the future of
> VAGUE.
>
> VAGUE's domain is spelled out in its name: unix enthusiasts.
>
> But does that even make sense in 2010?  People hop between computers,
> platforms, devices, form-factors and even virtualized environments and
> services where the OS is irrelevant.  The focus is no longer on
> operating systems or fixed hardware platforms, but the interconnection
> beween
>
> VAGUE for a long time has been tolerant of this, and has had a broader
> view of being inclusive of FOSS, in the spirit of BSD and Linux, no
> matter the platform.  Hell, we most often meet in a lab full of Macs! ;)
>
> But, should the group's remit be broader still?  Should we actively seek
> to expand across more technologies and paradigms, in the interest of
> technological progress?
>
>
> I submit that the focus should not be on the "Unix", but on the
> *Enthusiasts*.  We should expand to encompass those passionate about a
> broad swath of technology.  However, leaving the scope too broad might,
> too, be a problem.  So what's the right scope?  And then, does the VAGUE
> brand continue to make sense?
>
>
> Wednesday, September 22nd. 6pm. Farmhouse Tap and Grill (
> http://farmhousetg.com/).
>
>
> Of course, this topic is bigger than one meeting, so the discussion
> should start now.  What do you want to see out of a local technology
> users and implementers group?
>
> --
> ...jsled
> http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo $...@${b}
>

Reply via email to