Packages affected: None
Seek out other groups in Minnesota with computing-related focus and communicate this group's existence to them and offer an invitation for collaboration where appropriate.
A lot of people in Minnesota still aren't aware of our group, but might be excited about it if they did. Also, communicating with other groups in the state will foster relationships that will be helpful for working together on common goals. For instance, at a face-to-face meeting with members of TCLUG a few months back, members were interested in our LoCo but not yet aware.
We should have a pre-written script of sorts written to save people time and effort and to make sure we have a consistent message. This would apply to e-mail, letter, or phone contact.
List of Groups and contact tracking
[Location][ABBR][Web site][IRC][Mailing List][Assigned Member][Contact Status]
Website: http://tclug.org IRC: #tclug on irc.freenode.net Other LUGs from their website: St. Cloud Area Linux Users Group
Web site: http://scalug.mn-linux.org/
The Northfield Minnesota Linux Users Group (NORLUG)
Web site: http://norlug.org/
The Linux Users Group of Rochester (K-LUG)
Web site: http://www.k-lug.org
Mankato Area Unix Group (MAUG)
Web site: http://maug.wireless.mnsu.edu/
Duluth Superior Linux UNIX Users Group (DSLUUG)
Web site: http://www.dsluug.org/
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.