CommunityWorkingGroup: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
planning policy/process improvements and implementations for the space | == '''planning policy/process improvements and implementations for the space''' == | ||
ensuring clean/safe facilities (bathrooms, basically, but maybe kitchen) | ensuring clean/safe facilities (bathrooms, basically, but maybe kitchen) | ||
| Line 5: | Line 5: | ||
kitchen rebuild (content/process) (kitchen existing as a separate issue could work for us. if we minimize the "dishes and pots" aspect of the kitchen, and set it up to facilitate hacking type stuff like molecular gastronomy, and add a dishwasher, it could get better) | kitchen rebuild (content/process) (kitchen existing as a separate issue could work for us. if we minimize the "dishes and pots" aspect of the kitchen, and set it up to facilitate hacking type stuff like molecular gastronomy, and add a dishwasher, it could get better) | ||
refactoring consensus process and decision negotiation (consensus is not a monolithic model, and its also complex and mutable, kinda like agile/scrum methodology. participants in it should be informed and prepared.) | refactoring consensus process and decision negotiation (consensus is not a monolithic model, and its also complex and mutable, kinda like agile/scrum methodology. participants in it should be informed and prepared.) http://web.mit.edu/publicdisputes/practice/cbh_ch1.html | ||
making a New Member Packet containing info about processes, participation, etc, and probably stickers or something too | making a New Member Packet containing info about processes, participation, etc, and probably stickers or something too | ||
Revision as of 15:58, 2 April 2014
planning policy/process improvements and implementations for the space
ensuring clean/safe facilities (bathrooms, basically, but maybe kitchen)
kitchen rebuild (content/process) (kitchen existing as a separate issue could work for us. if we minimize the "dishes and pots" aspect of the kitchen, and set it up to facilitate hacking type stuff like molecular gastronomy, and add a dishwasher, it could get better)
refactoring consensus process and decision negotiation (consensus is not a monolithic model, and its also complex and mutable, kinda like agile/scrum methodology. participants in it should be informed and prepared.) http://web.mit.edu/publicdisputes/practice/cbh_ch1.html
making a New Member Packet containing info about processes, participation, etc, and probably stickers or something too
refactoring the redshirts role and implementation
implementing and maintaining management software (http://spiff.readthedocs.org/en/latest/ via torrie, and https://www.loomio.org/ , and https://slack.com/ and http://www.discourse.org/
separate mailing list(s) for members only, and for the working group
hosting for services (where, who pays, etc)