Shawn wrote:

I was hoping you guys would reconsider. I made my thoughts about this known at the meeting, and stand by them. When I started the progsig group, it was my intent to have no costs for potential members, and to focus on the needs of our members. It was not my intent to make the group a money raising organization, or to dictate what skills any potential member needed before they joined the group.



It's late, and I'd better not say much more until my brain is fully operational (I'm getting tired). But, while I will respect your choice, I will NOT be forking over $50, and I doubt I'll be attending any more meetings if this proceeds (I'm still holding onto a glimmer of hope, probably foolishly...)



I would not join if it was $50. It's too much.

I like free, But _I_ would pay money for a location to meet or other need _AS_LONG_AS_ not every one needs to.

Finally, you should be finding a different name for your group - ProgSig belongs to us (CLUG), and seeing as the new group would not be affiliated with CLUG, we can probably argue a copyright to the name.



This is the thing I don't like the most, I joined Clug's ProSig (or at least the mailing list and some meetings) because it was for (or at least I found it for) Linux programing and also programing in general, BUT Linux programing first.

Here's what I think, Sorry if I see it wrong.

Some people want a Programing user group but want to convert a current one that also deals with linux programing.
There are many programing types of user groups in Calgary, like the Calgary Java Users group, Calgary PHP Users group.
I think that they should START a whole new group (Calgary Programing user group or Calgary Programing special interest group) rather than the way I see it as ruining a current one to fit your needs.



Any way that's the end of what I think, Goodnight. Travis R.


_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying

Reply via email to