Imported from 1485762012291.html

Author: progcodepreston

README.md

@@ -0,0 +1,109 @@
+# ProgCode Staffers Policy & Guidelines {#progcode-staffers-policy-guidelines}
+
+ProgCode Staffers Policy and Guidelines
+
+All the things you need to know to get started on becoming a conduit for technological progressive change
+
+TABLE OF CONTENTS
+
+[Abstract](export/abstract.md)
+
+[Mission, Objective, Goals](export/mission,_objective,_goals.md)
+
+[Agenda](export/agenda.md)
+
+[Values](export/values/README.md)
+
+[Ownership](export/values/ownership.md)
+
+[Autonomy](export/values/autonomy.md)
+
+[Collaboration](export/values/collaboration.md)
+
+[Members to Projects](export/values/collaboration.md#members-to-projects)
+
+[Projects to other projects](export/values/collaboration.md#projects-to-other-projects)
+
+[Projects and the network outside](export/values/collaboration.md#projects-and-the-network-outside)
+
+[Non-Hierarchy](export/values/non-hierarchy.md)
+
+[Decentralization](export/values/decentralization.md)
+
+[Push and be Pulled](export/values/push_and_be_pulled.md)
+
+[Personal Relationships](export/slack_forces/stimulus.md#personal-relationships)
+
+[Transparency](export/values/transparency.md)
+
+[Accountability](export/values/accountability.md)
+
+[Ego Check](export/ego_check/README.md)
+
+[1\. Perceived Position of Power](export/ego_check/1_perceived_position_of_power.md)
+
+[2\. Perception of a Dominating Force](export/ego_check/2_perception_of_a_dominating_force.md)
+
+[3\. Connections as Platform to empower the network](export/ego_check/3_connections_as_platform_to_empower_the_network.md)
+
+[Slack Forces](export/slack_forces/README.md)
+
+[Chaos](export/slack_forces/chaos.md)
+
+[Ideation](export/slack_forces/ideation.md)
+
+[Channel Dynamics](export/slack_forces/channel_dynamics.md)
+
+[Stimulus](export/slack_forces/stimulus.md)
+
+[Volunteers](export/slack_forces/stimulus.md#volunteers)
+
+[Network Effects](export/slack_forces/stimulus.md#network-effects)
+
+[Personal Relationships](export/slack_forces/stimulus.md#personal-relationships)
+
+[Archiving](export/slack_forces/archiving.md)
+
+[Github Forces](export/github_forces/README.md)
+
+[Order](export/github_forces/order.md)
+
+[Pilot Program](export/github_forces/pilot_program.md)
+
+[Project Lists](export/github_forces/project_lists.md)
+
+[Documentation](export/facilitation_norms/key_items_in_every_project.md#documentation)
+
+[Facilitation Norms](export/facilitation_norms/README.md)
+
+[Respect Ideas Members and Staffers](export/facilitation_norms/respect_the_ideas_of_members.md)
+
+[Attitudes on Projects](export/facilitation_norms/attitudes_on_projects.md)
+
+[Interacting with app creators](export/facilitation_norms/interacting_with_app_creators.md)
+
+[Do not make an ask, come in with an offer](export/facilitation_norms/do_not_make_an_ask,_come_in_with_an_offer.md)
+
+[Key items in every project](export/facilitation_norms/key_items_in_every_project.md)
+
+[Project Channel](export/facilitation_norms/key_items_in_every_project.md#project-channel)
+
+[Documentation](export/facilitation_norms/key_items_in_every_project.md#documentation)
+
+[Facilitation / Interaction](export/facilitation_norms/key_items_in_every_project.md#facilitation-interaction)
+
+[Parts of the House](export/parts_of_the_house/README.md)
+
+[Partner Dynamics](export/parts_of_the_house/partner_dynamics.md)
+
+[Member Dynamics](export/parts_of_the_house/member_dynamics.md)
+
+[Tools and Other Assets](export/parts_of_the_house/tools_and_other_assets.md)
+
+[Content](export/parts_of_the_house/content.md)
+
+[Staff Removal](export/staff_removal.md)
+
+[Conflict Resolutions](export/conflict_resolutions.md)
+
+[Conclusion](export/conclusion.md)

SUMMARY.md

@@ -0,0 +1,45 @@
+# Summary
+
+* [ProgCode Staffers Policy & Guidelines](README.md)
+* [Abstract](abstract.md)
+* [Mission, Objective, Goals](mission,_objective,_goals.md)
+* [Agenda](agenda.md)
+* [Values](values/README.md)
+  * [Ownership](values/ownership.md)
+  * [Autonomy](values/autonomy.md)
+  * [Collaboration](values/collaboration.md)
+  * [Non-Hierarchy](values/non-hierarchy.md)
+  * [Decentralization](values/decentralization.md)
+  * [Push and be Pulled](values/push_and_be_pulled.md)
+  * [Personal Relationships](values/personal_relationships.md)
+  * [Transparency](values/transparency.md)
+  * [Accountability](values/accountability.md)
+* [Ego Check](ego_check/README.md)
+  * [1. Perceived Position of Power](ego_check/1_perceived_position_of_power.md)
+  * [2. Perception of a Dominating Force](ego_check/2_perception_of_a_dominating_force.md)
+  * [3. Connections as Platform to empower the network](ego_check/3_connections_as_platform_to_empower_the_network.md)
+* [Slack Forces](slack_forces/README.md)
+  * [Chaos](slack_forces/chaos.md)
+  * [Ideation](slack_forces/ideation.md)
+  * [Channel Dynamics](slack_forces/channel_dynamics.md)
+  * [Stimulus](slack_forces/stimulus.md)
+  * [Archiving](slack_forces/archiving.md)
+* [Github Forces](github_forces/README.md)
+  * [Order](github_forces/order.md)
+  * [Pilot Program](github_forces/pilot_program.md)
+  * [Project Lists](github_forces/project_lists.md)
+  * [Documentation](github_forces/documentation.md)
+* [Facilitation Norms](facilitation_norms/README.md)
+  * [Respect the ideas of members ](facilitation_norms/respect_the_ideas_of_members.md)
+  * [Attitudes on projects](facilitation_norms/attitudes_on_projects.md)
+  * [Interacting with app creators](facilitation_norms/interacting_with_app_creators.md)
+  * [Do not make an ask, come in with an offer](facilitation_norms/do_not_make_an_ask,_come_in_with_an_offer.md)
+  * [Key items in every project](facilitation_norms/key_items_in_every_project.md)
+* [Parts of the House](parts_of_the_house/README.md)
+  * [Partner Dynamics](parts_of_the_house/partner_dynamics.md)
+  * [Member Dynamics](parts_of_the_house/member_dynamics.md)
+  * [Tools and Other Assets](parts_of_the_house/tools_and_other_assets.md)
+  * [Content](parts_of_the_house/content.md)
+* [Staff Removal](staff_removal.md)
+* [Conflict Resolutions](conflict_resolutions.md)
+* [Conclusion](conclusion.md)

abstract.md

@@ -0,0 +1,23 @@
+# Abstract {#abstract}
+
+The Progressive Coders Network is – as the name says – a network. And for one to understand how to be part of the ProgCode staff, one must fully understand the dynamics and forces surrounding networks.
+
+This document lays out research-driven best practices within networks as well as acquired knowledge throughout the formation of ProgCode.
+
+The organization of this document is as follows:
+
+Core Objectives
+
+ describe the reason of our existence and our mission. We also discuss the Agenda and [Values](values/README.md) that drive the culture of the community. After that, we will talk about the [Ego Check](ego_check/README.md), something that staffers have to continuously be mindful about as we move forward and interact with the community. Slack Forces and [Facilitation Norms](facilitation_norms/README.md) cover the basics on how we use slack, and how slack coincides with the culture we are forming. [Github Forces](github_forces/README.md) will provide us with an overlook on how we try to make sense of the chaos from Slack. And finally – the
+
+Parts of the House
+
+ – a discussion on the parts that make up the #operations channel.
+
+You will be exposed to the dynamics we have with various entities in the network. As an entity ourselves, ProgCode can be considered one of the applications in the network, with the key goal         of becoming conduits of collaboration between these applications.
+
+For a deeper dive on what a network is all about, I strongly urge you to read [Jon Kleinberg](https://www.google.com/url?q=http://www.cs.cornell.edu/home/kleinber/networks-book/&sa=D&ust=1485764357442000&usg=AFQjCNH6JEnFp47ylh8Rlay-U0_TvU8wrw) (highly recommend), [Mark Granovetter](https://www.google.com/url?q=https://www.unc.edu/~fbaum/teaching/articles/Lohmann_WP_1994.pdf&sa=D&ust=1485764357443000&usg=AFQjCNGvaNcB4lMlV5m-mdkWx3dONqo6kw), and [Malcolm Gladwell](https://www.google.com/url?q=https://www.amazon.com/Tipping-Point-Little-Things-Difference/dp/0316346624&sa=D&ust=1485764357443000&usg=AFQjCNFWHg4FaR3Gt9KysowL7CYFd0aqqw). Furthermore, resources by Robert Putnam and [Jane Franklin](https://www.google.com/url?q=https://www.lsbu.ac.uk/__data/assets/pdf_file/0007/9439/women-social-capital-families-research-working-paper.pdf&sa=D&ust=1485764357444000&usg=AFQjCNFCditbGUrj9hcgbHwhRvUTpusJOw) provides a deeper understanding on [social capital](https://www.google.com/url?q=https://en.wikipedia.org/wiki/Social_capital&sa=D&ust=1485764357445000&usg=AFQjCNFi9myMgDvLHiD9O1nLmEE_O4zw5Q), a network force/currency that we are trying to maximize and leverage inside and outside the network.
+
+For further info, @joepbreslin (operations coordinator) and I (@rapi) are more than happy to go on one-on-ones and learn more about your thoughts and ideas.
+
+This document will be ratified by the community on Monday, Jan 30, 2017 and will be the source of truth on anything related to staffers.

agenda.md

@@ -0,0 +1,7 @@
+# Agenda {#agenda}
+
+As a framework of support, we have no agenda other than providing support to the applications within the network and providing a service that will lead to the success of the projects and organizations that have chosen to be part of our network. Their success is our success, and the success of the progressive tech movement as a whole.
+
+Any ulterior agenda – self-promotion, self-branding – is not part of our service as it provides the impetus for the organization to exist because of itself (something that the core objective is in complete opposition to). The idea is that these projects chose to stay with us and they are free to leave us whenever they want. However, if they choose to stay with us, it is in our best interest – our agenda – to make it as worthwhile as possible, with only their success at heart.
+
+To put it succinctly, the only agenda we have is the fact that these projects can and will remove the influence of big money in politics, and fully empower the progressive grassroots movement. As such, it is in our interest to provide service to the applications in the network.

conclusion.md

@@ -0,0 +1,5 @@
+# Conclusion {#conclusion}
+
+This document will be ratified by the community on Monday, Jan 30, 2017 and will be the source of truth on anything related to staffers.
+
+These are the core ideas behind becoming an effective staffer. If you are up for it, please consider reaching out at #operations ! @joepbreslin and @rapi are more than happy to go on one-on-ones and learn more about your thoughts and ideas.

conflict_resolutions.md

@@ -0,0 +1,3 @@
+# Conflict Resolutions {#conflict-resolutions}
+
+For information on conflict resolution, please refer to our [Conflict Resolution policy & guidelines](https://www.google.com/url?q=https://docs.google.com/document/d/1wlf0s-Ibwj7CCwxf59TA7zNi8Y3x3CCakPdO60WpAy0/edit?usp%3Dsharing&sa=D&ust=1485764357525000&usg=AFQjCNGByjdCsCQzqzG2sCrG_E4R_Sek4g)

ego_check/1_perceived_position_of_power.md

@@ -0,0 +1,3 @@
+## 1\. Perceived Position of Power {#1-perceived-position-of-power}
+
+As staffers we are perceived as someone who is in a position of power. We have to be mindful of that and make an effort to come from a place of service. Staffers should also be mindful and making it a point to let people understand that they are working from a position of service, not granted power.

ego_check/2_perception_of_a_dominating_force.md

@@ -0,0 +1,3 @@
+## 2\. Perception of a Dominating Force {#2-perception-of-a-dominating-force}
+
+As someone who is perceived as someone who is in a position of power, we have to be mindful about the fact that we can be perceived as a dominating force. We have to make an effort to switch that idea to become a resource and entity of support.

ego_check/3_connections_as_platform_to_empower_the_network.md

@@ -0,0 +1,5 @@
+## 3\. Connections as Platform to empower the network {#3-connections-as-platform-to-empower-the-network}
+
+As someone who will be connected to a lot of project leaders, progressive movers, you have to be mindful that our connections, the relationships we develop should bring everyone up along with us. As people who will become more connected as we are the one who will interface with a lot of people, we have to strongly consider to use these connections, to use the network we have formed to serve the applications we support. We have to bring the whole organization up with us.
+
+With these in mind, we will bring forward a progressive collaboration at the front of our priorities. These ego checks, if we are constantly mindful about it, will inevitably make the progressive tech movement all the more sustainable and stronger.

ego_check/README.md

@@ -0,0 +1,9 @@
+# Ego Check {#ego-check}
+
+This is a flat structured community, meaning, the network is sustained because of a very distributed form of leadership. The network is sustained because of the idea of social capital, where leadership is and should be formed through the good works, contributions, good relationships, and value one has provided to the community – not because you have declared yourself a leader.
+
+The leadership is decentralized on applications and its app creators, which makes for the idea that the applications are autonomous, have their own governance and decision making, and their own cultures. ProgCode can be considered one of the applications in the network, with the key goal of becoming conduits of collaboration between these applications.
+
+Having said that, we as staffers – simply because of the term or becoming staffers/coordinators – will inevitably be seen as perceived leaders within the community. Our role as staffers inevitably puts the perception of a dominating figure within the community, and because of that we need to setup an ego check to be able for us to be mindful about our position in the community.
+
+Here are the following ego checks for you to consider as you engage with the community.

facilitation_norms/README.md

@@ -0,0 +1,3 @@
+# Facilitation Norms {#facilitation-norms}
+
+The following items provide a policy guide on how we as staffers interact with the community and its leaders.

facilitation_norms/attitudes_on_projects.md

@@ -0,0 +1,3 @@
+## Attitudes on projects {#attitudes-on-projects}
+
+Projects are ideas, realized. However, these are still subjected to the fact that a project will be able to become the best applicaton ever created – or – an undone project. However, this does not change our commitment on becoming a framework of support to any of the projects within ProgCode. A project in our community is in itself a way for members to take ownership of the community, and as we provide service to them, we send out signals that we are in-fact coming from a place of service.

facilitation_norms/do_not_make_an_ask,_come_in_with_an_offer.md

@@ -0,0 +1,3 @@
+## Do not make an ask, come in with an offer {#do-not-make-an-ask-come-in-with-an-offer}
+
+In starting a relationship with creators or members, always always come from a place of service. We do not and will not be able to create relationships without an offer of service coming from us. The ask will only have the possibility of happening once trust and camaraderie has been established. You are encouraged to provide continuous service. Failure to establish rapport will result to the supposed partner being repulsed and not join the network.

facilitation_norms/interacting_with_app_creators.md

@@ -0,0 +1,3 @@
+## Interacting with app creators {#interacting-with-app-creators}
+
+Please be mindful about creating or starting a relationship with application leaders. As much as possible, try to find a way to be introduced, and not approach them up-front. From the ego-check, we will be seen as a dominating entity, as such we ought to always be mindful about the way we present ourselves.

facilitation_norms/key_items_in_every_project.md

@@ -0,0 +1,21 @@
+## Key items in every project {#key-items-in-every-project}
+
+The following are important aspects any project in the community has got to have in order to drive development into their respective projects. ProgCode staffers can facilitate any of these if requested or has the go signal of the app creator.
+
+### Project Channel {#project-channel}
+
+The main venue and meeting point for partners to join the conversation and discuss the project goals, and the problem it is trying to solve. Again, the mere act of entry to a channel is – in itself – an act of putting stake into a project. Discussion deepens this idea and if driven well enough, will develop into ownership. Conversation is a key aspect in the whole process and having an area for which this is possible will be helpful.
+
+The creation of a channel is also the first act of ownership the app creator does for the community. The mere act of creating a channel is central to starting a conversation between the creator and the community.
+
+This will also allow us to drive members and partners into the project.
+
+### Documentation {#documentation}
+
+A clear and concise definition of the problem is necessary for a clean and sustainable onboarding and re-onboarding process. It will provide a fuller context of what the project is about, making it easier for members to jump on board the idea and contribute further. This opens up a great conversation about the nature of the problem, and allows the deepening of the members’ sense of ownership toward the project.
+
+To be clear, any form or act of engagement towards a specific project can be considered as an act of putting stake onto the project. Any interaction one initiates to a project provides ways for a member to build a sense of ownership, so the more avenues and the more ways a person can interact with a project, the better and faster it is to cultivate ownership and acts of collaboration.
+
+### Facilitation / Interaction {#facilitation-interaction}
+
+New members of a channel ought to have someone who is dedicated to welcoming them and guiding them through the process of getting onboarded to the project. It is hard to join a project when no one is talking to you, and there is no further development of ownership if right after you have joined a project no one bothers to interact with the newcomer. So facilitation / introduction / interaction are key to creating a very sustainable relationship with members.

facilitation_norms/respect_the_ideas_of_members.md

@@ -0,0 +1,3 @@
+## Respect the ideas of members {#respect-the-ideas-of-members}
+
+Ideation is such an integral part of Progressive Coders Network that the mere act of creating and building an idea to the community becomes a form of taking ownership to the community as a whole. We must respect these ideas and allow it to bloom or to reach its natural demise without negativity and with respect. For more information on our stance on ideas, please check out this [Medium post](https://www.google.com/url?q=https://medium.com/progressive-coders-network/a-volunteer-culture-powered-by-ideas-723544bedfa6&sa=D&ust=1485764357506000&usg=AFQjCNFSIZACQmQgmr4rp7yhBvpFwY_oyg).

github_forces/README.md

@@ -0,0 +1,3 @@
+# Github Forces {#github-forces}
+
+We have repurposed slack as the command center of how we go about things in the operations side of things. The main purpose of github is to have a central place for information about the operations and applications within the network.

github_forces/documentation.md

@@ -0,0 +1,3 @@
+## Documentation {#documentation}
+
+We use the GitHub wiki for all the knowledge and information we want stored in a more permanent place. This will allow any new folks to peruse everything about the community at their own leisure, driving transparency forward.

github_forces/order.md

@@ -0,0 +1,3 @@
+## Order {#order}
+
+The main purpose of GitHub is to make sense of everything that is happening in the ProgCode slack. To bring order to the chaos that Slack has presented. As such, we bring forth important information / updates from Slack to Github, to make the onboarding and even re-onboarding process as smoothly as possible.