2012/5/15 Tom Rhodes <
trh...@freebsd.org>:
Hey Tom,
>> On Sun, May 13, 2012 at 4:23 PM, Tom Rhodes <
trh...@freebsd.org> wrote:
>> > Another thought is just breaking these out to a NoVaBug and
>> > MDBug or what not. I have some memory of this group being
>> > that way originally before going to capbug, but this might be
>> > better:
>> >
>> > capbug - General mailing list to share events, chat, questions,
>> > etc.
>> >
>> > novabug - Northern VA area group,
>> >
>> > mdbug - MD area group.
>> >
>> > I'm only suggesting this because it seems the va people have
>> > a hard time going to the md events and vice versa. Thoughts?
>>
>> Well, I've put a lot of work into building and maintaining CapBUG over
>> the years, so I don't really care for the idea of someone trying to
>> take it away from me.
>
> And who is that? Or is it just some idea you came up with after
> I suggested something that worked a little better for people?
The greater capitol region does span outside of immediate DC suburbs,
and although one might argue whether Columbia isn't part of the
metropolitan area, it's more difficult to argue that it's not part of
the greater area. And CapBUG is the "Capitol Area BSD Users' Group,"
not the "Capitol BSD Users' Group." Have you been to BAFUG meetings?
The Bay Area is *huge* and depending where you are, it can take as
long (or longer) to get to one of these meetups. There's no need for
us to start a war here because an existing group in the region has a
name that might be overloaded (and would be more accessible if it was
not).
Also, I don't think Mike meant to be inflammatory here. He's been
running CapBUG for years and it has been closer to DC and farther from
DC as time has gone on. I'm sure he's invested significant time in
building a group that does meet under that name and communicate via
this list. I'd imagine most of us would have a similar reaction to a
suggestion that would require re-branding as "MDBUG" after creating
and running it as CapBUG for such a long time. I read it simply as
"the group is currently called CapBUG, and this is what we do."
Just as you may not have explicitly stated taking the name CapBUG and
current CapBUG resources away, he didn't explicitly state that you did
either. Relax.
>> CapBUG meetings are on the last Thursday of the month in Columbia
>> (except of course, this month). We can try to use the technologies
>> available to us to have the CapBUG meetings virtualized across
>> multiple locations in the Capital Area Region. But I do not have
>> plans to rename my BUG and give away CapBUG.
>
> I won't be there, I don't much like the idea of it being the
> bug of a single person instead of a group, and a petty snarky
> reply to an honest solution to a real problem. But like you
> said, it's your bug, that (IIRC) only a handful of people can
> show up to, always in a location I ignore because it's beyond
> my access. It is much easier for me not to attend and ignore
> that it's happening rather than help find a place more
> accessible to others. I thought it was cap bug, but I guess
> it's more 'far from the capital in md bug' though, so if
> a real cap bug does pop up, I'd be happy to give that a
> shot.
I don't think these solutions are contradictory but orthogonal.
There's no reason we can't have multiple groups in the greater capital
area, communicating via this list and sharing presentations via some
video streaming session. (IIRC we had something like that in 2011 or
2010 where we had a remote presenter, and it worked fairly well.)
This seemed like an idea we could be amiable over. Why is this
suddenly not reasonable?
--dho
> Cheers,
>
> --
> Tom Rhodes