LoCoWorkingWithOtherGroups

Differences between revisions 10 and 11
Revision 10 as of 2007-02-13 23:24:35
Size: 1894
Editor: c-71-196-138-19
Comment: LoCos => LoCoTeams
Revision 11 as of 2007-03-03 22:21:14
Size: 2057
Editor: c-24-98-177-125
Comment: Giving the page some structure
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Coming Soon.

Notes:

  * Common feelings:
    * "LUGs are meatspace" - LoCo teams tend to be more virtual (national/statewide vs. "local")
    * "LUGs are dying" - Linux is widely demystified, Internet/forums have taken the need for meatspace stuff
      * A contentious statement with no evidence to back it up.
      * In the UK there are over 100 LUGs, some generate hundreds of mails a month, some are less active of course
      * LUGs do good things in the community.
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
LoCos are not meant to replace existing LUGS, but instead to complement them. Here we discuss how LoCoTeams and LUGs can work together.
= Common Misconceptions =
== LUGs are meatspace ==
LoCo teams tend to be more virtual (national/statewide vs. "local"), but many LoCoTeams do meet regularly.
== LUGs are dying ==
Linux is widely demystified, Internet/forums have taken the need for physical interaction. This is not true for the following reasons:
    * LUGs do good things in the community.
Line 17: Line 15:
   * LUGs provide an on-tap resource of local knowledgable technical people
   * LUGs are not tied to one distro, and can therefore be distro/technology agnostic.
  * Some LoCoTeams can complement this by
    * LUGs provide an on-tap resource of local knowledgable technical people
    * LUGs are not tied to one distro, and can therefore be distro/technology agnostic.
= What LoCoTeams Can Provide =
Line 36: Line 34:
  * LoCoTeams should ''not''
   * Be seen to be taking over a LUG or competing with a LUG
    * Drive LUGs down a single distro (i.e., Ubuntu) path.
    * Interfere with the operation of a LUG.
= What LoCoTeams Should Not Do =
  * Be seen to be taking over a LUG or competing with a LUG
  * Drive LUGs down a single distro (i.e., Ubuntu) path.
  * Interfere with the operation of a LUG.

Working With Other User Groups

Include(LoCoMenuHeader)

LoCos are not meant to replace existing LUGS, but instead to complement them. Here we discuss how LoCoTeams and LUGs can work together.

Common Misconceptions

LUGs are meatspace

LoCo teams tend to be more virtual (national/statewide vs. "local"), but many LoCoTeams do meet regularly.

LUGs are dying

Linux is widely demystified, Internet/forums have taken the need for physical interaction. This is not true for the following reasons:

  • LUGs do good things in the community.
    • Info Points
    • Software Freedom Day mobilisation of troops to raise awareness
  • LUGs provide an on-tap resource of local knowledgable technical people
  • LUGs are not tied to one distro, and can therefore be distro/technology agnostic.

What LoCoTeams Can Provide

  • Providing support to LUGs e.g.:
    • Speakers at LUG meetings
    • Ubuntu expertise to assist in LUG activities
    • Advocate Ubuntu at LUG meetings
    • Ubuntu specific support
    • Language Translation
    • CD distribution
    • Release parties
    • Press releases based on the Fridge
    • Outreach programs with local schools
    • Marketing support
    • Establish a generally community aspect within your local area
    • Participate or hold Installfests

What LoCoTeams Should Not Do

  • Be seen to be taking over a LUG or competing with a LUG
  • Drive LUGs down a single distro (i.e., Ubuntu) path.
  • Interfere with the operation of a LUG.
  • LUGs could be called upon to assist the LoCo in activities.

  • There are probably other groups, e.g., local societies etc., that LoCo teams could interact with.

LoCoWorkingWithOtherGroups (last edited 2010-08-13 18:54:58 by terminus-est)