As promised, here's my initial audit of the current CLUE documentation. Below that you'll find a proposed number of next steps. Discussion threads to follow on [EMAIL PROTECTED]
Document Audit 1. IRC Logs Summary: Three sets of IRC logs were found on the Linux. ca website dated August 10, 1998; August 24, 1998 and December 14, 1998. These logs essentially document the early formation and definition of CLUE. Various members of the Linux community from across Canada participated including representation from British Columbia, Ontario, and Nova Scotia. Issues discussed: - CLUE funding - CLUE tradeshow representation/COMDEX - CLUE membership and sponsorship - CLUE Incorporation - CLUE Installfests - CLUE Newsletters - CLUE roles and responsibilities Conclusions: The result of these IRC sessions is the current CLUE by-laws and direction statements as documented in the "Minutes of the CLUE Meeting Held 00/01/21". 2. Meeting Minutes January 21, 2000 Summary: These minutes document the original issues that CLUE organizers were facing and some resolutions. Issues discussed: - how will CLUE provide resource infrastructure - CLUE not providing value for the West Coast - CLUE not being promoted adequately - Need a National organization to hit areas that are national - i.e. national events; advocacy - CLUE should act as a resource to local LUGs; coordination between LUGs is important - local needs are sharing of information and social aspects of community - Need for national vendors/commercial organization - CLUE should play a parent/umbrella role Conclusions: - CLUE won't sell individual memberships - Key functions of CLUE are to act as a source of information to stakeholders and to facilitate communications. - Facilitation includes: market knowledge, repository, standards, coordination of events, access to customers. - Advocacy includes: Canadian specific issues, shared ideas, financing/resources, LI affiliation, vendors - Voting Members: includes LUGs that meet defined criteria such as providing a membership list to CLUE and demonstration that it has an established mean of communicating among its members; any incorporated (or registered)organization; government agencies; for-profit organizations. (??? it's unclear what the latter actually meant). - Restrictions for CLUE Board Membership: must be age of majority; geographical distribution for LUG's i.e. a minimum of 1 board member from each of the designated geographical regions given that there is a board candidate from that region - Designated regions: BC, Prairies, Ontario, Quebec, Atlantic Provinces, Northern territories. - No more than 1/3 of the board representation will be from for-profit organizations or vendors - No less than 1/3 of the board shall represent LUGs - Members of the board will be democratically elected at General CLUE meetings 3. By-laws Summary: CLUE by-laws are your basic, boilerplate not-for-profit by-laws. Points of interest: - 2 classes of Membership: general and associate - membership length is 4 months - CLUE head-office is located in Regional Municipality of Peel, Province of Ontario (NOTE: a location is required for incorporation) - Board of Directors (term): President (2 years), First VP (1 year), Second VP (1 year), Treasurer (1 year), Secretary (1 year), Past President, 7 Regional Directors (2 years) - Meetings: at least 1 annual meeting Conclusion: By-laws are essentially still valid. However, following the election and/or appointment of a new Board, an early order of business should be a review of the by-laws. 4. Website Summary: Has been dormant for well over a year. Conclusion: - very little content is reusable - design requires an update - new content must be created - Basically, the website needs to be completely redone. - Design from membership could be solicited. ----------------------------------------------------------------------- Next Steps: (in order of execution (somewhat)) 1. Assessment of CLUE assets: website - reestablish connection with hosting provider; implement mailing list archival procedure (it's currently not working). Who: currently unassigned (Matt R. can you do this?). 2. Post to all LUGs announcing the reformation of CLUE and encouraging subscription to the [EMAIL PROTECTED] mailing list. Note that once the archival mechanism is in place for the mailing lists, all future discussion of CLUE will take place on the lists. I'll also update the website with information regarding what we're up to. Who: Bill Traynor (as I've already subscribed to all the LUG lists) and have update access to the website. 3. Begin discussions online regarding the role and responsibilities of CLUE. Who: Bill Traynor (I'll get the threads started with a few thoughts, such as "should CLUE be expanded to include the BSD's?). 4. Form interim board of directors. Board Members may be appointed/solicited at this time given mailing list participation. Who: Ron Harwood, Matt Rice, Evan Leibovitch (current board members) 5. Establish working CLUE Organization Plan including functional areas such as: Projects; Advocacy; Partnerships; Education; Affinity Programs; Events; Membership Relations; Documentation; etc. 6. Develop Marketing Plan NOTE: NONE OF THE LATTER IS WRITTEN IN STONE! It is all up for modification. This is just a start obviously. We can flesh out these plans as we progress. Thanks Bill Traynor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
