Agenda 2014 03 10 - nortonimperiallabs/nortonimperiallabs GitHub Wiki
- Finalize branching structure and current infrastructure tools
- Define "membership"
LLC status
----------
+ Robbiet will be calling SoS sometime soon.
Real estate
-----------
+ Waiting on us
Branding
--------
+ Tagline finalized
> "An imperial proclamation for creative cooperation"
+ Mission statement finalized
> Norton Imperial Laboratories strives to inspire collaboration, creativity, and passion in the San Francisco community by:
+ Fostering an open, collaborative space
+ Providing a safe, clean and inclusive work environment
+ Teaching and helping others
+ Need font
+ Need colors
+ Need logo
Crowdfunding
-------------------
+ Looking for help for video, robbiet480's friend Scott may be available
+ Need a meeting specifically for starting this out. Whenisgood: http://whenisgood.net/mhakcs3
+ Need action plan with line items
Logistics and Infrastructure
------------
+ Bylaws up and WiP
+ Standardized communications:
* [Weekly meatspace meetings](https://github.com/nortonimperiallabs/nortonimperiallabs/blob/master/announcements/weeklyMeetings.md) for decision-making
* ##\#SFNIL on freenode for real-time discussion
* [Google group](https://groups.google.com/forum/#!forum/sfhackerspace) for asynchronous discussion
* [Wiki](http://wiki.nortonimperiallabs.org/) for asynchronous temporary content
* [@NIL/NIL github repository](https://github.com/nortonimperiallabs/nortonimperiallabs) for persistent content
+ Autodeployment still an open issue (we need to resolve this quickly so we can get branding and such on our static webpage pronto)
+ Mailing list vs. forum
+ Infra documentation
+ CMS
+ Current decision making structure (@NIL.NIL\master/documents/bylaws/TemporaryBylaws.txt
> *Decree, if you have problems with what happens in a meeting, show up at the next one to change it*
* Decisions made at weekly group meetings are put into effect immediately (unless otherwise specified) and apply to the whole group.
* For decisions made at weekly group meetings, a minimum of 3 members must be present to establish a quorum.
* If you were absent from a meeting and have concerns with a decision that was made there, show up next week and add it to the agenda during the "summary of previous week" section. This section comes first, so be on time.
* Decisions made in the process of completing action items from a weekly meeting should generally be considered equivalent to those made in weekly meetings.
-
Temporary branching structure
- Commits to master should represent finalized content. Please do not commit working copies to master. Changes to master should be discussed at weekly meetings prior to merging.
- For changes relating to specific action items from weekly meetings, create a private branch in @NIL/NIL/dev/ for your work. For example, Badg created @NIL/NIL/dev/bylaws to work on his assigned action items from the 2014 03 03 meeting.
- Collaborators should submit suggestions to private branches. For example, rrix might add suggestions in @NIL/NIL/dev/bylaws/rrix
- The action item assignee (in this example, Badg) is free to adopt or ignore those suggestions
- Specific action-item development branches may be merged directly to master
- For changes unrelated to specific action items, create a private branch in @NIL/NIL/unassigned/ for your work. For example, Badg might create @NIL/NIL/unassigned/procedures to draft a procedure for lathe access control.
- Unassigned branches may be courteously merged into by others. The creator of the branch has every right to revert those commits.
- Unassigned branches should not be merged directly into master, but should first be merged into the intermediate @NIL/NIL/development branch
- Pending changes on the catch-all @NIL/NIL/development branch will be discussed at weekly meetings.
-
weeklyMeetings.md
-
README.md (propagating pertinent sections to relevant other parts)
- Order food
- CMS update (arcon will be absent)
+ Bylaws update
+ People power
+ Meeting night reconsidering
> https://docs.google.com/spreadsheet/ccc?key=0AhgPSRuTOHOPdGFGV05mN3FESjNmQVYxZ0RaX1E0bGc&usp=sharing
> https://docs.google.com/forms/d/1iVblRaraSemq_6ZOKiGABwJy3NL3-FD89CpV6iPZXW8/viewform
+ Autodeploy
Logistics and Infrastructure
----------------------------
+ Finalize as many tools as possible and document decisions (I'm looking at you, mailing list vs forum question)
Membership definition
---------------------
+ Membership levels
+ Rights, responsibilities, privileges, etc
+ What defines a "member"?
+ Who is our ideal "member"?
+ Goals for next week
+ Task review
+ Task assignment