> For the complete documentation index, see [llms.txt](https://legal.desmoinesmaker.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.desmoinesmaker.space/meeting-minutes/meeting-minutes/2014/november-2014-board-meeting.md).

# November 2014 - Board Meeting

## Agenda items

* Financials
* Membership status - how are we doing? What should we do to bring in new members?
* Do we want to have Jeff under our lease?
* The door-parts are actually on order
* Plan for the garage
* Bylaw review-example would be procedure for removing members

Call to order: 18:15 members present: Ray, Tom, Nabil, Sean, Barry, Bailey

### Financials

* rumors of 3 new members
* ideas for recruiting
  * gift to iowa bike coalition
  * gifting to corps
    * ray has concerns about practicality, and fitting in with the culture - no vetting of the recipient
  * classes / merch
    * sparkfun plans on hold, need to decide what lines to carry
    * there were further concerns about the $1000 minimum, it was decided to go with adafruit until we know demand
    * another arduino class planned for Feb.
    * need help for website content
* now that we're official, we can do kickstarter / crowdfunding campaigns
* donations
  * tom has a meeting with his corporate "head of global donations"

### Jeff

* tom mentioned we have refusal on existing space, jeff would prefer to sublease from us
  * the majority opinion was that the risk was not worth the reward vs. him taking on his own lease
  * sean advocated that expanding into that area would allow us to claim the middle area
    * vote to take jeff under our lease failed, but we'd be happy for him to come in on his own

### Door parts

* parts still on order, no further status update
  * tom will contact
    * if they keep failing, do we pass?
      * that would be bad as it may limit large tool availability - repurpose the current front room as the heavy area?
      * could we trade for the rest of the space?

### Garage plan

* security
  * contact emma from tikly about the sets from lovejoy
  * pallets / chain link
* layout
* needs cleaning
  * determine what's ours and what's not
  * need to scare off the oldsmobile that parks in our spot

### Whittier

* cleanout
  * plans are afoot tonight
    * if the keys work

### Bylaw review

* tabled for next month

### Actions for next month

review bylaws - <https://area515.org/wiki/index.php/Bylaws>

\
meeting adjourned: 19:05


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legal.desmoinesmaker.space/meeting-minutes/meeting-minutes/2014/november-2014-board-meeting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
