If the group decides on that path, that too would be good. I was only
thinking from a point of a lowly user as programming is beyond my
personal competence. If the road develops and people want to follow it
- all is good.
With regards to objectives, great suggestion. The number of people, the
breadth of interest and our personal time available will dictate the
projects. Personally I am more interested in low hanging fruit, nothing
that will take longer than a month or two. I am interested in things
that will augment what I am currently doing.
Mel started the year by saying that this will be the year of the user.
I personally resonate with that, and am paddling my kayak in that
direction. If others are heading in the same direction, I'll get a
bigger canoe, otherwise kayaking as a group is a lot of fun too.
Your welcome to paddle the programming kayak if you are so inclined.
On 4/8/2011 9:21 AM, Shawn wrote:
Task number one for such a group is to define an objective. i.e. Fix
application X so that it does Y. Or create driver for hardware Z.
Having a small set of these objectives would be better than having a
lot, or having none.
Without these objectives, the meetings would become more social
oriented than working oriented.
My thoughts.
_______________________________________________
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
