To pile on, I agree as well. Unless the topic is specifically related to
open source and/or Linux, like an initiative that would force WA state to
consider using OSS and/or Linux, I would like to see LFNW stay as far away
from politics as possible.

That all being said, BTC is a public institution, and BTC runs the actual
LFNW event, so the point may be moot. It may not be legal to prevent
someone from gathering signatures in a public place like BTC, but IANAL...

..Ch:W..

On Sat, Apr 28, 2018 at 05:25 David Griffith <[email protected]> wrote:

> On April 27, 2018 6:57:57 PM PDT, "Brian C. Lane" <[email protected]>
> wrote:
>>
>> On Fri, Apr 27, 2018 at 12:30:27PM -0700, Aaron wrote:
>>
>>>  My wife just signed up to collect signatures for something call "Yes on
>>>  1631" (a Washington State proposal to collect fees on fossil fuel energy
>>>  production to promote alternative energy development) and would like to
>>>  know what the policy is on that at LinuxFest. Would someone be allowed
>>>  to show up with a clipboard and collect signatures at the linuxfest
>>>  event (outside? inside?), or if one would need to find a community
>>>  sponsor that would be willing to allow them to collect around their
>>>  table, or if it is just too darn late.
>>>
>>
>> Personally I'd rather not see signature gathering at LFNW, no matter
>> what the subject.
>>
>>
> I agree. To allow it would invite animosity over whatever the subject is.
> Maybe this can be discussed in depth at a planning meeting.
>
> --
> David Griffith
> [email protected]
> _______________________________________________
> Fest-list mailing list
> [email protected]
> http://lists.blug.org/cgi-bin/mailman/listinfo/fest-list
>
-- 
“I would challenge anyone here to think of a question upon which we once
had a scientific answer, however inadequate, but for which now the best
answer is a religious one."  -Sam Harris
_______________________________________________
Fest-list mailing list
[email protected]
http://lists.blug.org/cgi-bin/mailman/listinfo/fest-list

Reply via email to