<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://noolaham.foundation/wiki/index.php?action=history&amp;feed=atom&amp;title=Internal_Communications_Flow</id>
	<title>Internal Communications Flow - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://noolaham.foundation/wiki/index.php?action=history&amp;feed=atom&amp;title=Internal_Communications_Flow"/>
	<link rel="alternate" type="text/html" href="http://noolaham.foundation/wiki/index.php?title=Internal_Communications_Flow&amp;action=history"/>
	<updated>2026-10-25T18:25:32Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.34.1</generator>
	<entry>
		<id>http://noolaham.foundation/wiki/index.php?title=Internal_Communications_Flow&amp;diff=10301&amp;oldid=prev</id>
		<title>Natkeeran: Created page with &quot;Noolaham Foundations seeks to build an open, positive, collaborative, respectful atmosphere for all staff and volunteers.  Noolaham Foundation seeks to be a self-archiving, le...&quot;</title>
		<link rel="alternate" type="text/html" href="http://noolaham.foundation/wiki/index.php?title=Internal_Communications_Flow&amp;diff=10301&amp;oldid=prev"/>
		<updated>2020-06-27T12:19:16Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Noolaham Foundations seeks to build an open, positive, collaborative, respectful atmosphere for all staff and volunteers.  Noolaham Foundation seeks to be a self-archiving, le...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Noolaham Foundations seeks to build an open, positive, collaborative, respectful atmosphere for all staff and volunteers.  Noolaham Foundation seeks to be a self-archiving, learning organization.  Open communication and transparency are key to these goals.&lt;br /&gt;
&lt;br /&gt;
All of Noolaham Foundation meetings must be pre-announced on respective process or project email threads, with reasonable notice period.&lt;br /&gt;
Summary of all meetings should be shared via email or slack.&lt;br /&gt;
&lt;br /&gt;
Sector Lead/Project Co-Ordinator and/or their Department Manager, and/or Chief Operating Officer must always be present at the meeting.&lt;br /&gt;
The Chief Operating Officer must be present in all meetings where a job assignment/change or a priority establishment/change is needed.&lt;br /&gt;
It is not mandatory for COO to attend technical advisory process/project meetings.  However, the sector lead and/or department manager must be there and notify the summary of discussions in the slack thread or via email.&lt;br /&gt;
&lt;br /&gt;
Use official channels for internal communications: Process/Project email threads, slack channels, wiki, document management system (Google Docs), website, and GitHub repository. &lt;br /&gt;
&lt;br /&gt;
Do not use WhatsApp, use Slack instead.  Avoid creating email threads outside of processes and project email threads.&lt;br /&gt;
It is recommended that regular policy discussions happen face to face during the Governance Board meetings, rather than through drawn out email thread discussions.  Staff can prepare background information.&lt;br /&gt;
&lt;br /&gt;
For work related matters, volunteers should avoid communicating with staff outside of the following official meetings.&lt;/div&gt;</summary>
		<author><name>Natkeeran</name></author>
		
	</entry>
</feed>