makernexuswiki - User contributions [en]

Asset Tracking

2023-01-15T23:36:50Z

PatrickL: Changed from active voice / first person to passive voice. Also updated links to asset tiger

For maker spaces out there on a budget, [https://www.myassettag.com/assettiger AssetTiger] could be a viable asset tracking option. The site itself is free to use for "customers" -- their business is selling barcode labels. Users can populate their data and try before buying any labels.

Some of the nice things about this site include: the addition of custom fields, different security levels for users, a fantastic mobile app (barcode scanner from phone works from 3 feet away), data export (except photos) to an XLS or CSV for backups, and data import from a CSV.

One way to extend AssetTiger's functionality is to import asset data into an Excel VBA program that builds a database from the data, generates a wiki page of the equipment, and transfer it over FTP to a wiki site. For an example, check this out: [https://chattlab.org/wiki/equipment_list ChatLab Equipment List]

The example created a "wiki link" field on its assets, so when using the mobile app, it's just another click to pull up more info on the unit. There is also a flag "list on site" so Chat Lab can dictate what gets to the wiki, and what they just don't list. Contact jeff at chattlab.org for more information.

[[category:makerspace]]

Slack

2021-09-14T10:10:19Z

PatrickL:

==About==
From [https://en.wikipedia.org/wiki/Slack_(software) Wikipedia]
<blockquote>
Slack is a proprietary business communication platform developed by American software company Slack Technologies and owned by Salesforce from 2021. Slack offers many IRC-style features, including persistent chat rooms (channels) organized by topic, private groups, and direct messaging.
</blockquote>

==Help==
For tutorials and other guidance on how to use and extend Slack, please see the official [https://slack.com/resources product resources page]

Slack

2021-09-14T10:09:51Z

PatrickL:

==About==
From [https://en.wikipedia.org/wiki/Slack_(software) Wikipedia]
<blockquote>
Slack is a proprietary business communication platform developed by American software company Slack Technologies and owned by Salesforce from 2021. Slack offers many IRC-style features, including persistent chat rooms (channels) organized by topic, private groups, and direct messaging.
</blockquote>

==Help==
For tutorials and other guidance on how to use and extend Slack, please see the official product resources page: [https://slack.com/resources]

Injection Molding Machine

2021-09-13T23:51:12Z

PatrickL: Added photo; needs to be conformed to template https://makernexuswiki.com/wiki/MN-S_Equipment_Template

An injection molding machine (also spelled as injection moulding machine in BrE), also known as an injection press, is a machine for manufacturing plastic products by the injection molding process. It consists of two main parts, an injection unit and a clamping unit. See [https://en.wikipedia.org/wiki/Injection_molding_machine Injection Molding Machine] and [https://en.wikipedia.org/wiki/Hobby_injection_molding Hobby Injection Molding] on Wikipedia.

==Our Machine==
Maker Nexus has a [https://www.minijector.com/mini-jector-model-55p/ Mini-Jector Model 55P] injection molding machine. It is (insert dimensions here) and weighs (insert approximate weight here). It is able to provide (insert clamping force here) of clamping force for aluminum molds and can produce (insert number of pulls per hour) "pulls" per hour.

[[File:Mini-Jector-Model-55P.png]]

* Heating System
:* One nozzle heater
:* Two barrel heaters

* Hydraulic System
:* Twin injection cylinders
:* One carriage cylinder
:* Self contained hydraulic power unit features:
:* 5.4 gallon reservoir
:* 1725 RPM motor with 2 HP
:* 2.0 GPM gear pump immersed in the reservoir

* Control System
:* Siemens PLC/HMI
::* Recipes
::* Packing Mode
::* Purge Cycle
:* Directional and control valves with plug-in connectors that control:
::* Screw speed
::* Injection speed
::* Screw back pressure read on oil filled gage
:* Manual and semi-automatic modes
:* Motor starter with thermal overloads and emergency stop button
:* Selectable de-compression feature
:* Carriage speed

* Additional Features
:* Aluminum material hopper with shut off and dump tube
:* Moving parts covered by safety shroud
:* Heat shield on barrel
:* Greaseless bushings used in screw unit mechanism
:* Provision for cooling feed throat

===Maintenance===
====Greasing Grease Fittings====
For your convenience, here's what it says about greasing the grease fittings: "The machine requires very little in the way of lubrication, as the injection plate and thrust housing bushings are a composite semi-greaseless type that require lubrication once every 6 months to a year. The thrust housing has two linear bushings; one accessible from the front, one from the rear. The injection cylinder plate also has two bushings with staggered access. Use a lithium-based grease and inject only enough grease to force the old grease out. This removes any dirt accumulated in the bushings. Wipe the old grease off of the guide rods."

File:Mini-Jector-Model-55P.png

2021-09-13T23:49:33Z

PatrickL: Mini-Jector Model #55P © Miniature Plastic Molding

== Summary ==
Mini-Jector Model #55P © Miniature Plastic Molding

Injection Molding Machine

2021-09-13T23:35:18Z

PatrickL: Created page with "An injection molding machine (also spelled as injection moulding machine in BrE), also known as an injection press, is a machine for manufacturing plastic products by the inje..."

An injection molding machine (also spelled as injection moulding machine in BrE), also known as an injection press, is a machine for manufacturing plastic products by the injection molding process. It consists of two main parts, an injection unit and a clamping unit. See [https://en.wikipedia.org/wiki/Injection_molding_machine Injection Molding Machine] and [https://en.wikipedia.org/wiki/Hobby_injection_molding Hobby Injection Molding] on Wikipedia.

==Our Machine==
Maker Nexus has a [https://www.minijector.com/mini-jector-model-55p/ Mini-Jector Model 55P] injection molding machine. It is (insert dimensions here) and weighs (insert approximate weight here). It is able to provide (insert clamping force here) of clamping force for aluminum molds and can produce (insert number of pulls per hour) "pulls" per hour.

* Heating System
:* One nozzle heater
:* Two barrel heaters

* Hydraulic System
:* Twin injection cylinders
:* One carriage cylinder
:* Self contained hydraulic power unit features:
:* 5.4 gallon reservoir
:* 1725 RPM motor with 2 HP
:* 2.0 GPM gear pump immersed in the reservoir

* Control System
:* Siemens PLC/HMI
::* Recipes
::* Packing Mode
::* Purge Cycle
:* Directional and control valves with plug-in connectors that control:
::* Screw speed
::* Injection speed
::* Screw back pressure read on oil filled gage
:* Manual and semi-automatic modes
:* Motor starter with thermal overloads and emergency stop button
:* Selectable de-compression feature
:* Carriage speed

* Additional Features
:* Aluminum material hopper with shut off and dump tube
:* Moving parts covered by safety shroud
:* Heat shield on barrel
:* Greaseless bushings used in screw unit mechanism
:* Provision for cooling feed throat

===Maintenance===
====Greasing Grease Fittings====
For your convenience, here's what it says about greasing the grease fittings: "The machine requires very little in the way of lubrication, as the injection plate and thrust housing bushings are a composite semi-greaseless type that require lubrication once every 6 months to a year. The thrust housing has two linear bushings; one accessible from the front, one from the rear. The injection cylinder plate also has two bushings with staggered access. Use a lithium-based grease and inject only enough grease to force the old grease out. This removes any dirt accumulated in the bushings. Wipe the old grease off of the guide rods."

MN Collaboration tools

2021-09-12T19:12:11Z

PatrickL:

Maker Nexus uses a variety of tools to facilitate communication, collaboration, and dissemination of information inside and outside the organization. Some of these are self-hosted and administered by members (e.g. this wiki and our badge system), while others are provided to Maker Nexus as a hosted service (e.g. #Slack and #Google Workspace). Although tools, techniques, and technologies are always changing, the following list is what we currently rely on, and encourage members to use as well. If you are interested in testing out new software tools, you can create a [[committees|committee]] and pitch the idea on Slack.

===[http://makernexus.org Website]===
The Maker Nexus homepage is the public-facing entry portal to our organization. It has the most current information about the Maker Nexus organization. Website content is overseen and managed by the [[Executive Director]]. We are working to create a [[Communication Committee]] to manage the website for the ED.

===[[Slack]]===
[https://slack.com/ Slack] is a popular, proprietary group chat platform used by many enterprises and organizations. Discussions are organized into "channels" based on topic and function like many other online chat systems such as [https://matrix.org/|Matrix], [https://discord.com/|Discord], or [https://en.wikipedia.org/wiki/Internet_Relay_Chat|IRC]. Slack is the primary way to engage in low-latency, ephemeral communication with other members and staff and is great for things such as arranging for training, asking questions about machines, suggesting ideas, and sharing pictures of project progress or your pets.

===Google Workspace===
[[Google workplace]] provides a large collection of the tools that we use regularly, including email, documents, spreadsheets, calendars, manage documents, and time.

====Team Drives in Google Drive====

* MN Members: Where the vast majority of documents live. You must access this using your @makernexus.org Google account.

* Steering Committee: A group of people who volunteer a significant amount of time to keep the makerspace running. The few docs here are about making id badges, policies under discussion but don't have agreement from the steering committee yet, draft versions of the monthly report to members, etc.

* Donation Processing: Our donor's personal information is kept private. This team drive supports those few people in the organization who are working on donation programs.

* Finance: A few people who work on accounting tasks have access to this.

* Operations: A few documents pertaining to the operations staff at MN. Things like personnel scheduling, vacations, etc.

* Board of Directors: Only available to official board members. Being an open organization, we try to keep very few documents here. However, some information must be tightly held. For example, personnel docs, contracts with strict NDAs, working documents that the board has not gotten to the point of sharing the proposal with others, etc. If you want to know what's here, ask a board member.

===[[Main Page|Wiki]]===
This wiki is a repository of public information. Here we try to document more factual things, after they have been hammered out by a group. This wiki is public. Anyone can read what is here. Anyone can contribute. You can sign up for a wiki account in the upper right corner of this screen. This wiki contains information about Maker Nexus. It also serves as a knowledge base for the larger community of makers around the world - you can see that on the home page of the wiki.

===Email===
info@makernexus.org Someone from the steering committee monitors this email daily. If you need something or have some question, don't hesitate to send in an email. Please try to put something descriptive in the subject line.

===EZ Facility===
Our CRM

===Public Share===

Documents in the Public Share are available for the world to view. They often have a link to them from a page in this wiki.

Anyone can view this share drive: https://drive.google.com/drive/folders/1OVtDCs4H-r3UAqqseN0YeRGuM22ZraeF?usp=sharing

===An Example===

As an example of how these all might work... Someone thinks we need a privacy statement (good idea!). On Slack the start a new #privacystmt channel and posts in the #general channel their interest and ask people to join them in the new channel. After some lively discussion the group realizes that this is going to take some group work and longer term focus. They chat in Slack and decide to create a new folder in our GDrive to capture their ideas. They gather some existing privacy statements from other places on the web. They create a new Google Doc and begin assembling a privacy statement. They involve the steering committee, since this policy will need executive approval. Eventually we have a privacy statement we can all support. It's added to this wiki to document it. That new wiki page is locked to prevent random editing. A link to the wiki page is added to the website. The folder on the GDrive is Archived.

All that could have been done in a day by one person without any of these tools. However, if the issue is contentious or very complex, the tools help the team converge on a solution.

==Tools We Are Testing==

===Trello===

We have a few people using Trello for To-Do list management. Ask and you can be added to the group.

==Tools We Do Not Use==

We specifically avoid the use of desktop files that are emailed to each other. If you've ever done this before, and who hasn't, you know how easy it is for those to get out of sync and suddenly no one knows who has the latest version - and sometimes the document forks and you have a mess on your hands.

===BaseCamp===

We tried BaseCamp but found that it did not add a lot of value. It had poor integration with G-Drive. It hid too much information from users.

===Asana===

It is only free for 10 users. We need tools that can be used by the entire organization for free - or very, very, very low cost.

===One Drive===

We want to limit our toolset and One Drive duplicates GDrive.

===Drop Box===

We want to limit our toolset and Drop Box duplicates GDrive.

===Microsoft Office===

We have GSuite from Google for free to all members. We want all our documents in native GDoc formats for easy collaboration. If you originate a document in a Microsoft format, please import it to a native GDoc format when you add it to our GDrive.

Talk:MN Collaboration tools

2021-09-12T18:56:42Z

PatrickL: /* Tools We Don't Use */

== Tools We Don't Use ==
I think this is an important section. If we've tested a tool and decided it didn't work, then we should discourage members from starting up with the same tool unless the tool has changed in a way that overcomes the objections we found. For instance, BaseCamp didn't work for us after quite a bit of live testing; a member who wants the organization to use BaseCamp should be aware of our previous testing experience. [[User:Jschrempp|Jschrempp]] ([[User talk:Jschrempp|talk]])
:Ok I understand a bit better what this section is trying to say now. I take issue more with the name of the section more than anything. In the set of all tools, the subset of all the tools we don't use is very large and to only list a small section of them is confusing to me. I'd like to change it to something like Evaluated Tools Not Recommended for Use. My opinion on tooling and collaboration is more of a pragmatic approach, and that members can use whatever tools tickle their fancy for their projects. That obviously doesn't means MN will pay for their use or deploy them across the community, but they shouldn't be restricted or discouraged from the tools that allow them to collaborate and be productive. For example, I'm sure a lot of members use Dropbox for sharing files, and if they have files they would like to share or get feedback on, telling them or suggesting to them that "No, we don't use that here. We're a GDrive shop!" is counterproductive to the goal of easy collaboration. I want members to be empowered to test any tool to find what works best for them, and if they come up with a system of collaboration that wasn't thought up and tested by the steering committee or some other top-down decision process, we should all be able to benefit from their experience. [[User:PatrickL|PatrickL]] ([[User talk:PatrickL|talk]])

== Communication Committee ==
I see this as a new addition to the organization but don't see it defined yet. We need to know what it is if this page relies on it. [[User:Jschrempp|Jschrempp]] ([[User talk:Jschrempp|talk]])
:The section previously said Communication Team. That wasn't defined in the wiki but I think it already exists in some form (since the website does get updated). Since the concept of a committee already exists in the organization through groups like "steering committee", I made the wording more consistent. I have a draft of the committee page to more formally define what those can look like. [[User:PatrickL|PatrickL]] ([[User talk:PatrickL|talk]])

Talk:MN Collaboration tools

2021-09-12T18:55:53Z

PatrickL: /* Tools We Don't Use */

== Tools We Don't Use ==
I think this is an important section. If we've tested a tool and decided it didn't work, then we should discourage members from starting up with the same tool unless the tool has changed in a way that overcomes the objections we found. For instance, BaseCamp didn't work for us after quite a bit of live testing; a member who wants the organization to use BaseCamp should be aware of our previous testing experience. [[User:Jschrempp|Jschrempp]] ([[User talk:Jschrempp|talk]])
:Ok I understand a bit better what this section is trying to say now. I take issue more with the name of the section than anything. In the set of all tools, the subset of all the tools we don't use is very large and to only list a small list of couple is confusing to me. I'd like to change it to something like Evaluated Tools Use. My opinion on tooling and collaboration is more of a pragmatic approach, and that members can use whatever tools tickle their fancy for their projects. That obviously doesn't means MN will pay for their use or deploy them across the community, but they shouldn't be restricted or discouraged from the tools that allow them to collaborate and be productive. For example, I'm sure a lot of members use Dropbox for sharing files, and if they have files they would like to share or get feedback on, telling them or suggesting to them that "No, we don't use that here. We're a GDrive shop!" is counterproductive to the goal of easy collaboration. I want members to be empowered to test any tool to find what works best for them, and if they come up with a system of collaboration that wasn't thought up and tested by the steering committee or some other top-down decision process, we should all be able to benefit from their experience. [[User:PatrickL|PatrickL]] ([[User talk:PatrickL|talk]])

== Communication Committee ==
I see this as a new addition to the organization but don't see it defined yet. We need to know what it is if this page relies on it. [[User:Jschrempp|Jschrempp]] ([[User talk:Jschrempp|talk]])
:The section previously said Communication Team. That wasn't defined in the wiki but I think it already exists in some form (since the website does get updated). Since the concept of a committee already exists in the organization through groups like "steering committee", I made the wording more consistent. I have a draft of the committee page to more formally define what those can look like. [[User:PatrickL|PatrickL]] ([[User talk:PatrickL|talk]])

Talk:MN Collaboration tools

2021-09-12T18:30:36Z

PatrickL: /* Communication Committee */

Talk:MN Collaboration tools

2021-09-12T18:29:28Z

PatrickL: /* Communication Committee */

Google Workspace

2021-09-12T18:18:58Z

PatrickL: Created page with "* GMail - Every paying member of Maker Nexus will receive an email account in our domain. This email account will be the primary login for other member services and give them..."

* GMail - Every paying member of Maker Nexus will receive an email account in our domain. This email account will be the primary login for other member services and give them access to our team share.
* Docs -
* Sheet
* Present
* Calendar
*

Accounting

2021-09-12T06:37:17Z

PatrickL:

'''DRAFT: Comments in the Discussion page'''
== Title: Accounting ==
''or accountant, financial director, bookkeeper or other title determined''

Reports to the [[General_Manager]]Shop Director; dotted line reports to the [[Board of Directors]].
Ensures financial stability by managing the flow of funds, and providing appropriate transparency and reporting on the financial status of the organization.

Estimated Hours per Week: ?

== General Responsibilities ==
Responsible for keeping the accounting books for the organization, preparing payments for bills, depositing receipts.
Insuring that all deadlines are kept with relation to payments and * vreports, taxes.

== Job Responsibilities ==

* Prepares yearly tax returns.
* Primary interface with payroll organization.
* Weekly deposits checks into bank account.
* Weekly prepares checks to pay bills.
* Prepare weekly payroll.
* Reconciles monthly bank statements.
* Prepares reports for the [[Board_of_Directors#Board_Treasurer Treasurer]]
* Prepares asset, liability, and capital account entries by compiling and analyzing account information.
* Maintains accounting controls by preparing and recommending policies and procedures.
* Reconciles financial discrepancies by collecting and analyzing account information.
* Secures financial information by insuring and testing backups of the data.
* Maintains financial security by following internal controls.
* Complies with federal, state, and local financial legal accounting requirements.
* Maintains appropriate confidentiality and transparency of information.

== Qualifications ==

* 3 or more years of demonstrated experience in: Accounting and Corporate Finance
* Excellent Attention to Detail and Organizational Skills
* Strong Reporting and Documentation Skills
* Deadline-Oriented
* Experience in Reporting Research Results, SFAS Rules, Confidentiality
* Exhibits excellent Time Management, Data Entry, and General Math Skills

Slack

2021-09-12T06:28:28Z

PatrickL: Created page with "==About== From [https://en.wikipedia.org/wiki/Slack_(software) Wikipedia] <blockquote> Slack is a proprietary business communication platform developed by American software co..."

MN Collaboration tools

2021-09-12T04:44:49Z

PatrickL:

Maker Nexus uses a variety of tools to facilitate communication, collaboration, and dissemination of information inside and outside the organization. Some of these are self-hosted and administered by members (e.g. this wiki and our badge system), while others are provided to Maker Nexus as a hosted service (e.g. #Slack and #Google Workspace). Although tools, techniques, and technologies are always changing, the following list is what we currently rely on, and encourage members to use as well. If you are interested in testing out new software tools, you can create a [[committees|committee]] and pitch the idea on Slack.

===[http://makernexus.org Website]===
The Maker Nexus homepage is the public-facing entry portal to our organization. It has the most current information about the Maker Nexus organization. Website content is overseen and managed by the [[Communication Committee]].

===[[Slack]]===
[https://slack.com/|Slack] is a popular, proprietary group chat platform used by many enterprises and organizations. Discussions are organized into "channels" based on topic and function like many other online chat systems such as [https://matrix.org/|Matrix], [https://discord.com/|Discord], or [https://en.wikipedia.org/wiki/Internet_Relay_Chat|IRC]. Slack is the primary way to engage in low-latency, ephemeral communication with other members and staff and is great for things such as arranging for training, asking questions about machines, suggesting ideas, and sharing pictures of project progress or your pets.

===[[Google Workspace]]===
Google workplace provides a large collection of the tools that we use regularly, including email, documents, spreadsheets, calendars, :

manage documents, and time.

===[[Main Page|Wiki]]===
This wiki is a repository of public information. Here we try to document more factual things, after they have been hammered out by a group. This wiki is public. Anyone can read what is here. Anyone can contribute. You can sign up for a wiki account in the upper right corner of this screen. This wiki contains information about Maker Nexus. It also serves as a knowledge base for the larger community of makers around the world - you can see that on the home page of the wiki.

===Email===
info@makernexus.org Someone from the steering committee monitors this email daily. If you need something or have some question, don't hesitate to send in an email. Please try to put something descriptive in the subject line.

===EZ Facility===
Our CRM

===Team Drives in Google Drive===

* MN Members: Where the vast majority of documents live. You must access this using your @makernexus.org Google account.

* Steering Committee: A group of people who volunteer a significant amount of time to keep the makerspace running. The few docs here are about making id badges, policies under discussion but don't have agreement from the steering committee yet, draft versions of the monthly report to members, etc.

* Donation Processing: Our donor's personal information is kept private. This team drive supports those few people in the organization who are working on donation programs.

* Finance: A few people who work on accounting tasks have access to this.

* Operations: A few documents pertaining to the operations staff at MN. Things like personnel scheduling, vacations, etc.

* Board of Directors: Only available to official board members. Being an open organization, we try to keep very few documents here. However, some information must be tightly held. For example, personnel docs, contracts with strict NDAs, working documents that the board has not gotten to the point of sharing the proposal with others, etc. If you want to know what's here, ask a board member.

===Public Share===

Documents in the Public Share are available for the world to view. They often have a link to them from a page in this wiki.

Anyone can view this share drive: https://drive.google.com/drive/folders/1OVtDCs4H-r3UAqqseN0YeRGuM22ZraeF?usp=sharing

===An Example===

As an example of how these all might work... Someone thinks we need a privacy statement (good idea!). On Slack the start a new #privacystmt channel and posts in the #general channel their interest and ask people to join them in the new channel. After some lively discussion the group realizes that this is going to take some group work and longer term focus. They chat in Slack and decide to create a new folder in our GDrive to capture their ideas. They gather some existing privacy statements from other places on the web. They create a new Google Doc and begin assembling a privacy statement. They involve the steering committee, since this policy will need executive approval. Eventually we have a privacy statement we can all support. It's added to this wiki to document it. That new wiki page is locked to prevent random editing. A link to the wiki page is added to the website. The folder on the GDrive is Archived.

All that could have been done in a day by one person without any of these tools. However, if the issue is contentious or very complex, the tools help the team converge on a solution.

MN Collaboration tools

2021-09-12T04:44:07Z

PatrickL:

Maker Nexus uses a variety of tools to facilitate communication, collaboration, and dissemination of information inside and outside the organization. Some of these are self-hosted and administered by members (e.g. this wiki and our badge system), while others are provided to Maker Nexus as a hosted service (e.g. #Slack and #Google Workspace). Although tools, techniques, and technologies are always changing, the following list is what we currently rely on, and encourage members to use as well. If you are interested in testing out new software tools, you can create a [[committees|committee]] and pitch the idea on Slack.

===[[http://makernexus.org|Website]]===
The Maker Nexus homepage is the public-facing entry portal to our organization. It has the most current information about the Maker Nexus organization. Website content is overseen and managed by the [[Communication Committee]].

===[[Slack]]===
[https://slack.com/|Slack] is a popular, proprietary group chat platform used by many enterprises and organizations. Discussions are organized into "channels" based on topic and function like many other online chat systems such as [https://matrix.org/|Matrix], [https://discord.com/|Discord], or [https://en.wikipedia.org/wiki/Internet_Relay_Chat|IRC]. Slack is the primary way to engage in low-latency, ephemeral communication with other members and staff and is great for things such as arranging for training, asking questions about machines, suggesting ideas, and sharing pictures of project progress or your pets.

===[[Google Workspace]]===
Google workplace provides a large collection of the tools that we use regularly, including email, documents, spreadsheets, calendars, :

manage documents, and time.

===[[Main Page|Wiki]]===
This wiki is a repository of public information. Here we try to document more factual things, after they have been hammered out by a group. This wiki is public. Anyone can read what is here. Anyone can contribute. You can sign up for a wiki account in the upper right corner of this screen. This wiki contains information about Maker Nexus. It also serves as a knowledge base for the larger community of makers around the world - you can see that on the home page of the wiki.

===Email===
info@makernexus.org Someone from the steering committee monitors this email daily. If you need something or have some question, don't hesitate to send in an email. Please try to put something descriptive in the subject line.

===EZ Facility===
Our CRM

===Team Drives in Google Drive===

* MN Members: Where the vast majority of documents live. You must access this using your @makernexus.org Google account.

* Steering Committee: A group of people who volunteer a significant amount of time to keep the makerspace running. The few docs here are about making id badges, policies under discussion but don't have agreement from the steering committee yet, draft versions of the monthly report to members, etc.

* Donation Processing: Our donor's personal information is kept private. This team drive supports those few people in the organization who are working on donation programs.

* Finance: A few people who work on accounting tasks have access to this.

* Operations: A few documents pertaining to the operations staff at MN. Things like personnel scheduling, vacations, etc.

* Board of Directors: Only available to official board members. Being an open organization, we try to keep very few documents here. However, some information must be tightly held. For example, personnel docs, contracts with strict NDAs, working documents that the board has not gotten to the point of sharing the proposal with others, etc. If you want to know what's here, ask a board member.

===Public Share===

Documents in the Public Share are available for the world to view. They often have a link to them from a page in this wiki.

Anyone can view this share drive: https://drive.google.com/drive/folders/1OVtDCs4H-r3UAqqseN0YeRGuM22ZraeF?usp=sharing

===An Example===

As an example of how these all might work... Someone thinks we need a privacy statement (good idea!). On Slack the start a new #privacystmt channel and posts in the #general channel their interest and ask people to join them in the new channel. After some lively discussion the group realizes that this is going to take some group work and longer term focus. They chat in Slack and decide to create a new folder in our GDrive to capture their ideas. They gather some existing privacy statements from other places on the web. They create a new Google Doc and begin assembling a privacy statement. They involve the steering committee, since this policy will need executive approval. Eventually we have a privacy statement we can all support. It's added to this wiki to document it. That new wiki page is locked to prevent random editing. A link to the wiki page is added to the website. The folder on the GDrive is Archived.

All that could have been done in a day by one person without any of these tools. However, if the issue is contentious or very complex, the tools help the team converge on a solution.