milestone 1 completed

deliveries/TogetherCrew_Community_health_check_milestone1.md

@@ -0,0 +1,22 @@
+# Milestone Delivery :mailbox:
+
+**The [invoice form :pencil:](https://docs.google.com/forms/d/e/1FAIpQLSfmNYaoCgrxyhzgoKQ0ynQvnNRoTmgApz9NrMp-hd8mhIiO0A/viewform) has been filled out correctly for this milestone and the delivery is according to the official [milestone delivery guidelines](https://github.com/w3f/Grants-Program/blob/master/docs/Support%20Docs/milestone-deliverables-guidelines.md).**  
+
+
+* **Application Document:** https://github.com/w3f/Grants-Program/blob/master/applications/community-health-check.md
+* **Milestone Number:** 1
+
+**Context** (optional)
+The goal was to describe how we will build a network using Twitter data to measure the health ("vibes") of Twitter communities. 
+
+**Deliverables**
+
+| Number | Deliverable | Link | Notes|  
+| -----: | ----------- | ------------- |
+| 0a. | License | https://github.com/RnDAO/tc-Documentation/blob/master/Twitter-vibes/LICENSE.md | Apache 2.0  |
+| 0e. | Article| https://github.com/RnDAO/tc-Documentation/blob/master/Twitter-vibes/Twitter_Community_Vibes.md | We will publish an article (technical document) describing the metrics, the insights (so-what), and limitations. This article will also explain how the Twitter community is build (e.g., who are nodes, when there is an edge between two people, who is excluded/included and why). We will build a directed network, where nodes are always Twitter users. From a network assembly perspective, we will not differentiate between accounts representing people and those representing communities or organizations. The edges between an user profiles are either a reply, quote, mention, retweets, or likes. Thus, a tie from user A to user B exists if (1) user A replies to user B, user A quotes user B, user A mentions user B, user A retweets user B, or user A likes user B's tweet. At this moment, we will created weighted edges, not making a conceptual difference between the interaction type (reply, quote, mention, retweets and likes).The article will not be behind a paywall. The article will be written for an audience comfortable with data analysis. | 
+
+
+
+**Additional Information**
+no further information