Personal tools

Boston Area Haskell Users' Group

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
m
(Updated Boston Haskell page)
 
(19 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
== Purpose and Goals ==
 
== Purpose and Goals ==
  
The purpose of the Boston Area Haskell Users' Group is to provide a regular forum in which area people interested in Haskell can get together, meet each other, share skills, and grow the community
+
The purpose of Boston Haskell is to provide a regular forum in which area people interested in Haskell can get together, meet each other, share skills, and grow the community
 +
 
 +
Join the [https://www.meetup.com/Boston-Haskell/ meetup group] for even more entertainment! In particular, it is the most reliable source for meeting announcements and is where meeting-related polls (time, location, topics, etc.) are sent.
 +
 
 +
== Next Meeting ==
 +
 
 +
We usually meet at [https://maps.google.com/maps?f=q&hl=en&q=41+winter+st+6th+floor%2C+Boston%2C+MA%2C+02108%2C+us thoughtbot].
 +
 
 +
== Other Events ==
 +
 
 +
Once a year or so, we try to organize a hackathon, [[HacBOS]].
  
 
== Meeting Format ==
 
== Meeting Format ==
Line 10: Line 20:
 
The ideal meeting will include two presentations and a break:
 
The ideal meeting will include two presentations and a break:
 
* A presentation of '''code that even a beginner will appreciate'''
 
* A presentation of '''code that even a beginner will appreciate'''
* A break
+
* A break (which may also include Lightning Talks or other advertisements of interest)
 
* A presentation of '''code that will make at least some experts say Ooh! and Aah!'''
 
* A presentation of '''code that will make at least some experts say Ooh! and Aah!'''
 
Demos are also encouraged, but we want to see at least a little bit of code, please.
 
Demos are also encouraged, but we want to see at least a little bit of code, please.
Line 16: Line 26:
 
== Planned schedule ==
 
== Planned schedule ==
  
The group is intended to launch in January 2009 with a schedule of six meetings per year. The calendar is designed so that most meetings are scheduled at a time when people might have something new to show off.
+
Based on feedback fron the June 2009 meeting, we've switched to a monthly schedule.  
* A meeting in late January following POPL
+
We aim for a meeting on the third Wednesday of every month.
* A meeting at the end of March or the beginning of April, just after the ICFP deadline
+
* A meeting in May after classes are out but before students and professors have dispersed for the summer
+
* A meeting in July after the POPL deadline and perhaps just after the [http://icfpcontest.org ICFP programming contest]
+
* A meeting in September following [http://www.icfpconference.org ICFP] and the Haskell Symposium
+
* A meeting in November with a special emphasis on companies who may wish to recruit interns or new employees
+
 
+
  
 
== Call for volunteers ==
 
== Call for volunteers ==
 
We need volunteers
 
We need volunteers
* To host one of the regular meetings
+
 
 
* To present
 
* To present
 
* To twist other people's arms to present
 
* To twist other people's arms to present
* To talk to John Hughes and learn how to organize a "jobs fair" for the November meeting
+
* To provide refreshments at meetings
* To acquire a mailing list (perhaps boston at haskell dot org) and populate it with interested parties
+
* To help with general organizational matters (advertising meetings, etc.).
If you want to volunteer, please visit [[Boston Area Haskell Users' Group/Volunteers|the volunteers' page]]
+
 
 +
If you want to volunteer, please join the BostonHaskell mailing list and let us know what you're volunteering to do!
 +
 
 +
At some point we may be lucky enough to have a surplus of potential presenters.  In that case we may need volunteers for a selection committee.  A reasonable structure might be to have a committee of three who serve staggered six-month terms.  If we can't find enough presenters, those same people could try to find some.  In both cases people would be volunteering to help manage the program for three meetings.

Latest revision as of 09:32, 12 September 2017

Contents

[edit] 1 Purpose and Goals

The purpose of Boston Haskell is to provide a regular forum in which area people interested in Haskell can get together, meet each other, share skills, and grow the community

Join the meetup group for even more entertainment! In particular, it is the most reliable source for meeting announcements and is where meeting-related polls (time, location, topics, etc.) are sent.

[edit] 2 Next Meeting

We usually meet at thoughtbot.

[edit] 3 Other Events

Once a year or so, we try to organize a hackathon, HacBOS.

[edit] 4 Meeting Format

The Haskell Users' Group is not a forum for academic talks. The Boston area already provides plenty of opportunities for academics to give talks. The Haskell Users' Group is a forum for informal interactions and a place where you can show us the code.

The ideal meeting will include two presentations and a break:

  • A presentation of code that even a beginner will appreciate
  • A break (which may also include Lightning Talks or other advertisements of interest)
  • A presentation of code that will make at least some experts say Ooh! and Aah!

Demos are also encouraged, but we want to see at least a little bit of code, please.

[edit] 5 Planned schedule

Based on feedback fron the June 2009 meeting, we've switched to a monthly schedule. We aim for a meeting on the third Wednesday of every month.

[edit] 6 Call for volunteers

We need volunteers

  • To present
  • To twist other people's arms to present
  • To provide refreshments at meetings
  • To help with general organizational matters (advertising meetings, etc.).

If you want to volunteer, please join the BostonHaskell mailing list and let us know what you're volunteering to do!

At some point we may be lucky enough to have a surplus of potential presenters. In that case we may need volunteers for a selection committee. A reasonable structure might be to have a committee of three who serve staggered six-month terms. If we can't find enough presenters, those same people could try to find some. In both cases people would be volunteering to help manage the program for three meetings.