update

Reviewed files and MCL.md updated

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "writedown"]
+	path = writedown
+	url = https://github.com/dyne/writedown

MCL.md

@@ -18,92 +18,114 @@ The software community will be engaged mailnly with the use of public code repos
 
 Policymakers are the communities that have a remarkable negotiable power in terms of project outreach outside the MVPs lab environment. Thus, at the policymaking level, LEDGER MarCom strategy will target both individuals and groups who have a stake into the outcomes of the project. LEDGER will therefore encourage marketing, communication and dissemination activities to influence opinion and decision making processes within the policy domain by directly informing and attending to events promoted first and foremost by the Commission and relevant Directorates General, esp. those relevant to the implementation of solutions to problems affecting LEDGER’s verticals.
 
-### Business communities `aspra: I suggerst name change and shortening of this paragraph.`
+### Business Perspectives
-LEDGER success will be measured in terms of uptake of its MVPs by the market populated by citizens and consumers enabled to access business models that serve their needs while avoiding to ask anything in exchange without their previous knowledge and consent. As a result and thanks to FBA and BLM’s leading roles, consumers and business communities will be involved as a central dissemination and communication channel to promote and grow LEDGER’s values and value proposition. Both are structurlly interwoven, in that values cannot be framed independently of the value proposition underpinning them. This will in fact be the primary marketing and communication strategy for the project, because it is, to our knowledge, the aspect that mostly characterises LEDGER when compared to other in ether public or private endeavours in the decentralised data governance areas.
+LEDGER success will be measured in terms of uptake of its MVPs by the market populated by citizens and consumers enabled to access business models that serve their needs while avoiding to ask anything in exchange without their previous knowledge and consent. As a result and thanks to FBA and BLM’s leading roles, consumers and business communities will be involved as a central dissemination and communication channel to promote and grow LEDGER’s values and value proposition. Both are **structurally interwoven**, in that values cannot be framed independently of the value proposition underpinning them. This will in fact be the primary marketing and communication strategy for the project, because it is, to our knowledge, the aspect that mostly characterises LEDGER when compared to other in ether public or private endeavours in the decentralised data governance areas.
 
 Indeed, business communities are getting more and more aware about the topics and importance of the agenda that LEDGER is embodying. In turn, they are central for the uptake and upscaling of MVPs from LEDGER in that they can enjoy the adequate position and community outreach for large scale adoption of LEDGER’s venture builder solutions.
 
+To synthesize?
+
 
 ## 1. Editorial guidelines
 
-This editorial guidelines are here to provide all partners and involved participants with the essential information that needs to be distributed in all the stages of the duration of the LEDGER project as well as after the closing of the project in order to additionally provide with fulfilling the projects goals.
+These editorial guidelines are meant to provide all partners and involved participants with the essential information that needs to be distributed in all stages of the LEDGER project as well as after the closing of the project. In the following paragraphs, the content creation, internal validation, as well as the distribution and evaluation of the impact is analysed and exposed and the necessary workflow is drafted.
 
-Content Creation, internal validation, distribution and evaluation of impact is analysed and exposed and the necessary workflow drafted.
+All content developed for the project communication should attract participants to both Open Calls of the project. It should clearly express the characteristics, ethos and values of the Ledger project and it should be available for change, so that it can reflect the evolution of the project in all iterations during its 3 years duration. The MarCom of the project shall equally promote and document the development of the project through the sum of the participants work, the evolution of the technologies and the progress being made in each vertical.
 
-Content should attract participants for the first as well as the second Open Call of the project; express the characters of the ledger project through and within the single project highlights and results and be available to be changed to reflect the evolution of the project in his itearations during the 3 years. Communication and marketing of the project should equally promote and document the development of the project through the sum of the participants work, the evolution of the technologies and the progress being made in each vertical. Content distribution tactics and special needs are as well hinted.
+Editorial guidelines will also be visible to the participants. However, it is expected that close monitoring of the communication spaces and some re-iterations of editing will be necessary by the Dyne.org communication team and they will need to be validated through pair review between partners.
-
-The guidelines will be visible to the participants, however it is expected that close monitoring of the communication spaces and some hands-on editing will be necessary in time by the Dyne.org communication team and to be validated through pair review between partners.
-
-The following document will be in place to ensure best possible compliance with the guidelines:
-- LEDGER project consortium partners, will be informed specifically about the time in the project where they should provide with promotional material and other communications content
-- Consortium partners in charge of organizing events and bootcamps as previously agreed on, will be instructed to provide with ways (access) in order to create video documentation and other content both for external and internal communication and for general documentation .
-As part of the communication coordination meetings in LEDGER project producing and enabling production of communication, marketing and documentation material will be addressed accordingly.
 
+Moreover, this document is in place to ensure the best possible compliance with timelines and guidlines; in particular:
+- The LEDGER project consortium partners will be informed specifically about the timelines in the project when they are expected to provide with promotional material and other communications content.
+- The Consortium partners in charge of organising events and bootcamps as previously agreed on, will be instructed to provide access to other partners and collaborators in order to facilitate the creation of video documentation and other produced content both for external and internal communication and documentation.
 
 ## 2. Structure of the materials and creation workflow
 
 Production of communication materials and the act of communicate follows this first diagram.
-Internally there are two main repository for shared materials: files, images, tempates, modules, temporary sharing, project folders etc. go on cloud.dyne.org, code and documentation and collectively written complex documents go on gitea.dyne.org.
+Internally there are two main repository for shared materials: files, images, templates, modules, temporary sharing, project folders etc. go on cloud.dyne.org, code and documentation and collectively written complex documents go on gitea.dyne.org.
 
 ![Workflow-simple.png](./images/Workflow-simple.png)
 ![Workflow-Distribution.png](./images/CommunicationWF.png)
-Folder structure for the communication cross partners and with participants is to be kept in git or in nextcloud to availability of the consortium and the perticipants. Structure is the one summarised in the following tree. Workflow and usage notes will be put in readme.md as it is custom with documentation.
 
-Follows the proposed taxonomy as a structure of folders
+Folder structure for the communication cross partners and with participants is to be kept in git or in nextcloud to availability of the consortium and the participants when necessary. Structure is the one summarised in the following tree.
+
+Workflow and use instructions will be put in readme.md in the appropriate folders as it is custom with documentation in FLOSS development creating a seamless and interchangeable workflow between documentation and other communication oriented production.
+
+What follows the proposed taxonomy replicated as a structure of folders
 
 ```
 
 Communication
-├── 1.Brand
+   1.Brand
-├── 2.Moodboards
+   2.Moodboards
-│   ├── 1.Health
+      1.Health
-│   ├── 2.Economy
+      2.Economy
-│   ├── 3.Mobility
+      3.Mobility
-│   ├── 4.Public-Services
+      4.Public-Services
-│   ├── 5.EnergyAndSustainability
+      5.EnergyAndSustainability
-│   └── 6.OpenInnovativeProjects
+      6.OpenInnovativeProjects
-├── 3.Texts
+   3.Texts
-│   ├── 1.Internal-EU
+      1.Internal-EU
-│   ├── 2.External
+      2.External
-│   └── 3.Divulgative
+      3.Divulgative
-├── 4.NGI-Identity
+   4.NGI-Identity
-├── 5.SoftwareDocumentation
+   5.SoftwareDocumentation
-├── 6.TV
+   6.TV
-├── 7.Gadgets
+   7.Gadgets
-├── 8.Other
+   8.Other
-├── 9.projects-firstround
+   9.projects-firstround
-│   ├── 1.Health
+      1.Health
-│   │   └── example-project-folder
+        - example-project-folder
-│   │       ├── press
+          - press
-│   │       └── promo
+		  - promo
-│   ├── 2.Economy
+      2.Economy
-│   ├── 3.Mobility
+      3.Mobility
-│   ├── 4.Public-Services
+      4.Public-Services
-│   ├── 5.EnergyAndSustainability
+      5.EnergyAndSustainability
-│   └── 6.OpenInnovativeProjects
+      6.OpenInnovativeProjects
-
 
 ```
-## 3. Materials (/Communication)
+
-General communication groups are represented in this diagram. Access is readable by contact.
+1. What is about the LEDGER-NGI Brand is collected in 1. Brand;
+2. Moodboards is the proposed way to collect emotional and visual contents at this stage, to be replicated with projects and kept as reference and documentation.
+3. is the vault for reference text, divided in tree registers, the internal and eu jargon text, the text made and meant for external communication and the outreach one, intended for general audiences. This should allow to make text easy to find and reusable.
+
+### 2.1 General communication groups
+
+Appartenence of all participants to a group is indicated in the following diagram. Sets are in different color and they overlap when is necessary, while the diameter of the circle gives an idea of the number of people involved in the group. We will use similar representation further on.
 
 ![Internalcommunications.png](./images/InternalCommunication.png)
 
-`In this diagram I dont see where the participants actually are. Also the color assigned to them is not present in diagram`
+
+## 3. Materials (/Communication)
+
+Let's go to give a close look to the communication materials gathered so far and to their organisation.
+Chapter 3 refers to the materials for communication, were they are stored, how they need to be used.
 
 ### 3.1. Brand (/Communication/1.Brand)
-LEDGER project has to be integrated into NGI brand guidelines `ref??` and has to be divagated in the contexts created by NGI. At the same time the communication aim of LEDGER wants to outreach to communities of FLOSS developers and more marginal communities that might be alienated by the language, both visual and in other ways narrative of a traditional campaign. This document aims to be a guide that includes this perspective.
+LEDGER project has to be integrated into NGI brand guidelines and has to be divagated in the contexts created by NGI. At the same time the communication aim of LEDGER wants to outreach to communities of FLOSS developers and more marginal communities that might be alienated by the language, both visual and in other ways narrative of a traditional campaign. This document aims to be a guide that includes this perspective.
 
 ####	3.1.1. brand book for LEDGER project
-A Brand book is a very good tool for general communication. It can evolve from the coordinate communication already studied for Ledger Project.
+A Brand book is a very good tool for general communication (1). It can evolve from the coordinate communication already studied for Ledger Project.
 It includes though some simplified answers to generic questions that allow to present the project properly to any of the people involved.
 It includes as well a general visual guideline.
 The book is a living doc that includes synonyms and explanations for key concepts.
 
+(1) You can find as an example the brand book on NGI here:- https://www.ngi.eu/resources/promo-materials/
+
+Another excellent tool for expressing the narrative of the project is questions and answers. In FLOSS development this often took the form of FAQ. **Always Collect good questions!**
+
+Questions have to be gathered and answered and then a list of frequently recurring ones can be assembled.
+
+For the first phase of the project we refer to questions and answer that help internally to all participants to answer to anyone asking to the basic questions regarding the project giving as such a good answer to a generic audience.
+
 #####  Examples of Questions and Answers:
+ - Q: What are you busy with?
  - Q: What is LEDGER
  - Q: Why is it different/better/interesting?
 
+this tool will be elaborated by partners and included in the communication material as soon as it will be available.
+
+
 
 ####	3.1.2. general guidelines
 
@@ -116,8 +138,13 @@ The book is a living doc that includes synonyms and explanations for key concept
 
 Some Examples of the textual material that will be compiled for the many editing purposes necessary to the consortium communication.
 
-####	3.3.1. Internal-EU language register
+####	3.3.1. Internal-EU language register (Communication/3.Texts/1.Internal-EU/)
-##### Basic information and main goals of the LEDGER project
+
+[I include here below the text we already have in this register, I will decouple it from the file later on.]
+
+NOTE: In the mean time NGI has changed completely the logo and the brand guidelines (may 2019) compliance is requested before September 2019
+
+##### Basic information and main goals of the LEDGER project as implied by the Verticals
 
 LEDGER - Decentralised Data Governance for the Next Generation Internet - is a project funded by the European Commission (GA 825268 - http://ledgerproject.eu/). Between 2019 and 2021, the LEDGER project has the mandate to distribute financial support to third parties in a cascade funding framework named Venture Builder Programme.
 
@@ -172,41 +199,62 @@ Expected Impact:
 - Strengthening and diversifying the offer of the LEDGER ecosystem of tools for decentralised data governance.
 - Contribute to the diffusion of solutions that are not contemplated in the five verticals analysed in previous sections of the work programme.
 
-####	3.3.2. External
+####	3.3.2. External (Communication/3.Texts/2.External/)
-[fill with examples]
 
-####	3.3.3. Divulgative
+[Has to be compiled]
-[fill with examples]
+
+####	3.3.3. Divulgative (Communication/3.Texts/3.Divulgative/)
+
+[Has to be compiled]
 
 ### 3.4. FLOSS Based Economies
 
 The evaluation of projects will focus on authentic feedback provided by communities of participants as well as their impact according to quantitative and financial indicators. The aspect of shared gains for the entire ecosystem impacted by projects will be regarded as an added value and a positive aspect of the proposed projects.
 
-The successful project will be characterized by the interference of the four different concepts:
+The successful project will be characterised by the interference of the four different concepts:
 - Creation is the inception and realisation of ideas.
 - Appropriation is the adaptation of ideas to a specific context.
 - Sharing is the circulation of ideas, open to study by others.
 - Distribution is the packaging and documentation of ideas.
 
-The envisioned concepts should relate in a way introduced by the Free Culture Movement and F/OSS based economies:
+The envisioned concepts should relate in a way introduced by the Free Culture Movement and F/OSS based economies.
 
 
-### 3.4.1 Virtuose creation
+#### 3.4.1 Virtuos creation
 
-Semiotic square of virtuose creation
+Semiotic square of virtuos creation
 
 > image should be remade to fit brand identity
 
 The circularity suggests that any moment represented can be a starting point for agencies that focus on the process rather than a final result. The Distribution moment here acquires the form of a free and open market where interactions can be structured, traced and categorised: brilliant examples for such distribution models are on-line platforms like Soundcloud for musicians or Github for programmers, whose popularity and sustainability is noticeable despite the apparent lack of a “business model” and even the absence for monetisation through advertisements. Appropriation thus becomes not a moment for the restriction and management of author rights, but brings us back to the meaning of “Appropriate Technology” and includes the contextual and distributed agency for translations, adaptations, customisations and user experience improvements within certain communities. Creation follows Appropriation and indicates that the moment of authorship is closely bound to that of appropriated education as an intelligible passage of values between a concrete instance of knowledge and the individual. The individual or collective moment of Creation is less isolated from other moments and, rather than representing the enclosing act of immaterial property (often and wrongly referred to as intellectual property, it highlights that creation by individual or collectives depends on how vibrant is the context of Sharing and how effective is the Appropriation of value circulation within the language and schemes that form practitioners.
 
 ### 3.5. NGI-Identity (/Communication/4.NGI-Identity)
-We are requested to fit as well some requirements of the founding program NGI
+
-[Fill here the necessary guidelines]
+We are requested to fit as well some requirements of the founding program NGI. NGI program branding guidelines are accessible through the NGI site (www.ngi.eu).
+
+- https://www.ngi.eu
+- https://www.ngi.eu/vision/
+- https://www.ngi.eu/resources/promo-materials/
+
+- https://ec.europa.eu/europeaid/sites/devco/files/communication_and_visibility_manual_en_0.pdf
+
+NGI has a set of wide area communication tools in place we are request to contribute: a blog, a newsletter, a page on open calls, a page of other events and a map.
+[does anyone has ideas on what is the best way to bridge between ledger communication and distribution to NGI one?]
+
 
 ### 3.6. Software Documentation (/Communication/5.SoftwareDocumentation)
 > Fill in guidelines for acceptable and good documentation, role of public and private GIT etc
+> standard guidelines for github are ok
+
+### 3.7. TV and Web integration Materials (/Communication/6.TV-Web)
+
+LEDGER web site is reachable at: ledgerproject.eu
+The type of work that this document is analysing is a multiplatform, multiple partner media communication exchange, were the media can be verified in the process and used on many publishing platforms, that can be accessed by the right target audience in the most immediate and appropriate way.
+
+So far we will not concentrate too much on the website, more on the storage and production of the material that will populate the website and that is thought to be able to travel in all sectors of communication envisioned.
+
+#### ledger-TV
 
-### 3.7. TV (/Communication/6.TV)
 Events, pitches of teams at events, presentation and webseminars, tutorials and other type of material for communication takes the form of visual. We call it here TV.
 We are available to procure a professional WEB TV studio and a crew to assemble high quality interviews. The following description is to facilitate and integrate the production process of video material to be shared via social media, in streaming or for public projection or reference.
 
@@ -223,7 +271,7 @@ We are available to procure a professional WEB TV studio and a crew to assemble
 - example work: packhuijs de zwijger for decode night
 - extra; Social media to screen (+1 person)
 
-#### INTERVIEW
+#### INTERVIEWS
 - On location, light and construction of the set, make up artist, two cameras, interviewer/producer, sound and editing
 - People: 3 people: cameraman, producer and editor
 - Necessary: Internet connection, power, signal out of mixer desk for audio
@@ -239,12 +287,28 @@ We are available to procure a professional WEB TV studio and a crew to assemble
 - Stickers
 
 all we might come up with; the design will be kept here.
+NB: some stuff has been sent over by ngi
 
 ### 3.9. Other (/Communication/8.Others)
+To say to Andres if he please replicate communication folder on google docs here were appropriate.
+- Whitepapers templates
+- Roll-up
+NB: fredd:One Ledger Rollup is now with dyne.org
+- Poster
+- Vision Poster
+- Presentation templates
+- Press Release templates
 
 ### 3.10. Projects-firstround (/Communication/9.projects-firstround)
 
-## 2. KPIs
+Part of the incubation process of each project is to train them to keep an eye on their narrative and coordinated image.
+In each vertical will be set up the material produced to represent the projects in that vertical.
+These insights, and the material produced with this intent and the supervision of the tutors is to be shared and organised in a similar fashion and intent. Here will be kept only the actual material, to be used if necessary as it is at the state of the art.
+We will review in time the necessity of using other types of system to keep this material up-to-date.
+Is not our intention to stress too much the taxonomy of projects into the verticals at this stage, so we do not deem necessary to build and develop a-priori a narrative per vertical. This might change if the need arises from the content.
+
+## 4. KPI of the LEDGER project (not sure is a good title)
+
 LEDGER aims to support European internet innovators such as teams of minimum 3 people among developers and researchers to design and implement their projects as Minimum Viable Products.
 
 We want to share some important performance indicators upfront with all participants:
@@ -254,73 +318,40 @@ We want to share some important performance indicators upfront with all particip
 - Early stage to delivery: The teams might be composed by individuals, but also by employees from small or medium enterprises, in which cases the group will be closely evaluated for their human-centric approach and the will to collaborate with the rest of the LEDGER community.
 
 
-## 3. Criteria
+## 6. Participants
+How we will treat Participants
 
-General Criteria of evaluation: the community of participants
+### 6.1. Contributors
-The evaluation of projects will focus on authentic feedback provided by communities of participants as well as their impact according to quantitative and financial indicators. The aspect of shared gains for the entire ecosystem impacted by projects will be regarded as an added value and a positive aspect of the proposed projects.
-
-The successful project will be characterized by the interference of the four different concepts delined in 3.4.1:
-- Creation is the inception and realisation of ideas.
-- Appropriation is the adaptation of ideas to a specific context.
-- Sharing is the circulation of ideas, open to study by others.
-- Distribution is the packaging and documentation of ideas.
-
-## 4. Verticals
-
-In this paragraph we repeat and collect the specific needs for communication of the verticals, in particular with regard of the projects selected.
-
-###### Health
-A state of complete physical, mental and social wellbeing, and not merely the absence of disease or infirmity.1  Because of the diffusion of wearables and mobile apps, a convergence of medical data coupled with an increasing quantity of non-medical and healthy lifestyle related data, there are new opportunities in terms of operators’ engagement and patient self-management.
-
-###### Economy
-There is an urgency for technological innovation aimed at simplifying the life of consumers and offering improved services by industry players. Because of the lack of communication between legacy software systems there is a lack of transparency at almost all levels and compartments: from the complexity of terms of services to a built in discretion in the governance dynamics of the industry. In this context, market complexity, data leaks and threatened consumer rights require innovative solutions for the qualitative technical enhancement of digital railways to process financial transactions, operate spending reviews and apply regulations in a transparent and accountable way.
-
-###### Mobility
-LEDGER  looks for new models to address societal and environmental challenges in a vast sector of the economy that is under a huge transformation by virtue of fast innovation.  New collaborative and mobility-as-a-service business models are generating new economic value in this industry. By leveraging innovations coming from ICT, the sector is moving towards a more open ecosystem.
-
-###### Public Services
-Social services have been organised by endorsing the factory model resulting in a commodified model of citizenship. This has lead to extreme privatisation of public services, facilities and utilities and a pervasive approach to citizens control resulting in potential lack of European technological and digital sovereignty, sovereignty deficit when it comes to technology, algorithms and data management in public sector. As a result, challenges in the public services sector vary from the inherent complexity to execute procurement, to concretely and sustainably upscale innovative services, or still to create algorithms that are reusable in different circumstances and adaptable to different needs in different cities.
-
-###### Energy and Sustainability
-In the next few years, the energy market is expected to  experience deep changes caused by planned policy reforms in the European Union with its 20-20-20 climate & energy package agreed in 2010.2 The energy sector is dominated by legacy, public-private national energy distribution companies where producers drain data and value from consumers on the main AC-Grid still relying on fossil fuels and an obsolete proprietary distribution system.  The producers and consumers of renewable energy (the prosumers) are the same passive actors that produce energy and simply give it back to the main grid which in turn increases its profits by leveraging Big Data related to users.
-
-
-###### Open Innovative Projects
-Vertical reserved for further societal challenges that need to be addressed.
-Expected Impact:
-- Contributing to address topics related to Sustainable Development Goals not addressed in the other verticals.
-- Strengthening and diversifying the offer of the LEDGER ecosystem of tools for decentralised data governance.
-- Contribute to the diffusion of solutions that are not contemplated in the five verticals analysed in previous sections of the work programme.
-
-
-## 6. Contributors
 Here will be collected names and affiliation in a cross checked way for the compilation of credit lists, quoting etc.
 
 In particular credits lists are to be kept very carefully to avoid mistakes, spelling error or omissions.
 
-### 6.1. Partners
+If necessity of a particular credit to be given to exerns for some type of content a file with the necessary text named credits.md will be added to the folder. It is always referring to the content of the folder (and subfolders). If visual elements have to be added to this file references can be put in a subfolder.
+
+### 6.2. Partners
+This will have to correspond to a "who are we" page on the web site. Should be something we are able to identify peopel by role, face and name.
+
+In the image following there is a first representation of the need to know and groups of partners identified so far.
 
 ![people-groups.png](./images/people-groups.png)
 
-### 6.2. Teams and Projects (/Communication/9.projects-firstround)
+### 6.3. Teams and Projects (/Communication/9.projects-firstround)
 Here a selection of the materials of the participants: names and logos, short pitch, picture of team, picture of idea, last video-pitch
 
-### 6.3. The Mentors
+### 6.4. The Mentors
 - list of mentors with cv, short pitch
-
+### 6.5. Board and Jury
-### 6.4. Board and Jury
 - all informations necessary to identify the board and jury
 
-## 7. Distributors
+## 7. Distribution of contents
-- Web site
+
-- Founding Box Community
+- Web site (Funding Box)
-- Dyne.org community (???)
+- Funding Box Community (Funding box community platform)
-- Social
+- Social (dyne.org network, public space)
 
 ### 7.1. Sharers and influencers
-- Dyne.org community (???)
+- Funding Box Community [to paste a description here]
-- Founding Box Community
+- Influencer List (special list?)
-- Influencer List (special list)
 - Internal mailinglist
 - External Mailing list
 
@@ -331,8 +362,8 @@ How to treat press in events, in press releases, modules and templates
 Overview and guidelines
 `missing content`
 
-### 7.4. FoundingBox social network and communities
+### 7.4. FundingBox social network and communities
-In dept guideline for partners on how to use FoundingBox app
+In dept guideline for partners on how to use FundingBox app
 `missing content`
 
 ### 7.5. Social Media

README.md

@@ -1,10 +1,13 @@
-Content is at the moment as follows:
+Revision 3 16 July 2019
+by fredd
 
-- Marcom.md document is the contribution of Radium, as on pad 17 jan 8:20 with small typos corrected
+- MCL.md is the main document
-- layout.md contains the contribution of Elena and Fredd and is a practical documents
+- live doc is on gitea to be monitored with git
 
-my first merge of the docs is in MCL.md that therefore is the one to read to give compartments
 
-the index of the doc has been worked up on pad https://pad.dyne.org/code/#/1/edit/1vtinoUpsmYruHjDHiW+Ng/CrTbI64coYYuDY72TIheqOkW/
 
-Structures of folders has to be kept aligned with doc!
+
+NB:
+- Structures of folders has to be kept aligned with doc!
+- Careful with the extra files that are due for the use of writedown, do not delete anything. Ref: writedown.dyne.org
+- obsolete documents have been moved under the old/ folder

config.zsh

@@ -0,0 +1,34 @@
+# Writedown
+# generic configuration defaults for rendered files
+
+WRITEDOWN_TITLE="LEDGER Communication Plan"
+WRITEDOWN_AUTHOR="Dyne.org"
+WRITEDOWN_AFFILIATION="Dyne.org Foundation"
+WRITEDOWN_DATE="Wednesday 18 October 2017"
+WRITEDOWN_TAGS="[communication, growth, hacking, community, development]"
+
+# number for each section
+WRITEDOWN_NRSEC=yes
+# table of contents
+WRITEDOWN_TOC=yes
+# bibliographic citation style (see writedown/citstyle)
+WRITEDOWN_CITSTYLE=harvard-kings-college-london
+# font size
+WRITEDOWN_FONTSIZE=14pt
+# bibtex file for bibliographic sources
+# WRITEDOWN_BIB=./views/references.bib
+# latex template (header and footer)
+#WRITEDOWN_LATEX_TEMPLATE=/usr/share/pandoc/data/templates/latex.tex
+
+# different formats as supported by pandoc.
+# to activate uncomment and fill, then use dash (-) as first argument
+# i.e: ./writedown/render -
+# WRITEDOWN_OUTPUT_FORMAT=epub
+# WRITEDOWN_OUTPUT_EXTENSION=epub
+
+# default pandoc base command
+# WRITEDOWN_PANDOC="pandoc --smart --standalone -f markdown
+
+# Experimental features are commented below
+
+# WRITEDOWN_ZOTERO="no"

views/index.txt

@@ -0,0 +1 @@
+MCL.md

views/template.tex

@@ -0,0 +1,179 @@
+\documentclass[a4paper]{extarticle}
+\usepackage{lmodern}
+$if(fontsize)$
+\usepackage[$fontsize$]{extsizes}
+$endif$
+\usepackage{fullpage}
+\usepackage{longtable}
+\usepackage{booktabs}
+\usepackage{amssymb,amsmath}
+\usepackage{ifxetex,ifluatex}
+\usepackage{fixltx2e} % provides \textsubscript
+\ifnum 0\ifxetex 1\fi\ifluatex 1\fi=0 % if pdftex
+  \usepackage[T1]{fontenc}
+  \usepackage[utf8x]{inputenc}
+\else % if luatex or xelatex
+  \ifxetex
+    \usepackage{mathspec}
+  \else
+    \usepackage{fontspec}
+  \fi
+  \defaultfontfeatures{Ligatures=TeX,Scale=MatchLowercase}
+\fi
+% use upquote if available, for straight quotes in verbatim environments
+\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
+% use microtype if available
+\IfFileExists{microtype.sty}{%
+\usepackage{microtype}
+\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
+}{}
+\usepackage{hyperref}
+\hypersetup{unicode=true,
+            pdftitle={$title$},
+            pdfauthor={$author$},
+            $if(keywords)$
+            pdfkeywords={$for(keywords)$$keywords$$sep$; $endfor$},
+            $endif$
+            pdfborder={0 0 0},
+            breaklinks=true}
+\urlstyle{same}  % don't use monospace font for urls
+\usepackage{xcolor}
+$if(listings)$
+\usepackage{listings}
+\lstset{
+    basicstyle=\ttfamily,
+%    numbers=left,
+    numberstyle=\footnotesize,
+    stepnumber=2,
+    numbersep=5pt,
+    backgroundcolor=\color{black!10},
+    showspaces=false,
+    showstringspaces=false,
+    showtabs=false,
+    tabsize=2,
+    captionpos=b,
+    breaklines=true,
+    breakatwhitespace=true,
+    breakautoindent=true,
+    linewidth=\textwidth
+}
+$endif$
+\usepackage{color}
+\usepackage{fancyvrb}
+\newcommand{\VerbBar}{|}
+\newcommand{\VERB}{\Verb[commandchars=\\\{\}]}
+\DefineVerbatimEnvironment{Highlighting}{Verbatim}{commandchars=\\\{\}}
+% Add ',fontsize=\small' for more characters per line
+\newenvironment{Shaded}{}{}
+\newcommand{\KeywordTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{\textbf{{#1}}}}
+\newcommand{\DataTypeTok}[1]{\textcolor[rgb]{0.56,0.13,0.00}{{#1}}}
+\newcommand{\DecValTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{{#1}}}
+\newcommand{\BaseNTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{{#1}}}
+\newcommand{\FloatTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{{#1}}}
+\newcommand{\ConstantTok}[1]{\textcolor[rgb]{0.53,0.00,0.00}{{#1}}}
+\newcommand{\CharTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
+\newcommand{\SpecialCharTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
+\newcommand{\StringTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
+\newcommand{\VerbatimStringTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
+\newcommand{\SpecialStringTok}[1]{\textcolor[rgb]{0.73,0.40,0.53}{{#1}}}
+\newcommand{\ImportTok}[1]{{#1}}
+\newcommand{\CommentTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textit{{#1}}}}
+\newcommand{\DocumentationTok}[1]{\textcolor[rgb]{0.73,0.13,0.13}{\textit{{#1}}}}
+\newcommand{\AnnotationTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
+\newcommand{\CommentVarTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
+\newcommand{\OtherTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{{#1}}}
+\newcommand{\FunctionTok}[1]{\textcolor[rgb]{0.02,0.16,0.49}{{#1}}}
+\newcommand{\VariableTok}[1]{\textcolor[rgb]{0.10,0.09,0.49}{{#1}}}
+\newcommand{\ControlFlowTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{\textbf{{#1}}}}
+\newcommand{\OperatorTok}[1]{\textcolor[rgb]{0.40,0.40,0.40}{{#1}}}
+\newcommand{\BuiltInTok}[1]{{#1}}
+\newcommand{\ExtensionTok}[1]{{#1}}
+\newcommand{\PreprocessorTok}[1]{\textcolor[rgb]{0.74,0.48,0.00}{{#1}}}
+\newcommand{\AttributeTok}[1]{\textcolor[rgb]{0.49,0.56,0.16}{{#1}}}
+\newcommand{\RegionMarkerTok}[1]{{#1}}
+\newcommand{\InformationTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
+\newcommand{\WarningTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
+\newcommand{\AlertTok}[1]{\textcolor[rgb]{1.00,0.00,0.00}{\textbf{{#1}}}}
+\newcommand{\ErrorTok}[1]{\textcolor[rgb]{1.00,0.00,0.00}{\textbf{{#1}}}}
+\newcommand{\NormalTok}[1]{{#1}}
+\usepackage{graphicx,grffile}
+\makeatletter
+\def\maxwidth{\ifdim\Gin@nat@width>\linewidth\linewidth\else\Gin@nat@width\fi}
+\def\maxheight{\ifdim\Gin@nat@height>\textheight\textheight\else\Gin@nat@height\fi}
+\makeatother
+% Scale images if necessary, so that they will not overflow the page
+% margins by default, and it is still possible to overwrite the defaults
+% using explicit options in \includegraphics[width, height, ...]{}
+\setkeys{Gin}{width=\maxwidth,height=\maxheight,keepaspectratio}
+\IfFileExists{parskip.sty}{%
+\usepackage{parskip}
+}{% else
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{6pt plus 2pt minus 1pt}
+}
+
+% previously included by writedown in options.sty
+\setlength{\parindent}{1.25em}
+\setlength{\parskip}{.2em}
+\usepackage{etoolbox}
+\AtBeginEnvironment{quote}{\parskip 1em}
+
+\setlength{\emergencystretch}{3em}  % prevent overfull lines
+\providecommand{\tightlist}{%
+  \setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
+\setcounter{secnumdepth}{0}
+% Redefines (sub)paragraphs to behave more like sections
+\ifx\paragraph\undefined\else
+\let\oldparagraph\paragraph
+\renewcommand{\paragraph}[1]{\oldparagraph{#1}\mbox{}}
+\fi
+\ifx\subparagraph\undefined\else
+\let\oldsubparagraph\subparagraph
+\renewcommand{\subparagraph}[1]{\oldsubparagraph{#1}\mbox{}}
+\fi
+% END OF CONFIG    ------------------------------------------
+
+% START OF CONTENT ------------------------------------------
+
+\title{$title$}
+$if(subtitle)$
+\providecommand{\subtitle}[1]{}
+\subtitle{$subtitle$}
+$endif$
+$if(author)$
+\author{$for(author)$$author$$sep$ \and $endfor$}
+$endif$
+$if(institute)$
+\providecommand{\institute}[1]{}
+\institute{$for(institute)$$institute$$sep$ \and $endfor$}
+$endif$
+\date{$date$}
+$if(logo)$
+\logo{\includegraphics{$logo$}}
+$endif$
+
+\newcommand{\passthrough}[1]{\lstset{mathescape=false}#1\lstset{mathescape=true}}
+
+\begin{document}
+
+\maketitle
+
+\begin{abstract}
+$abstract$
+\end{abstract}
+
+\providecommand{\keywords}[1]{\textbf{\textit{Keywords---}} #1}
+$if(keywords)$
+    \keywords{$for(keywords)$$keywords$$sep$; $endfor$}
+$endif$
+
+\pagebreak[4]
+{
+\setcounter{tocdepth}{3}
+\tableofcontents
+}
+\pagebreak[4]
+
+$body$
+
+\end{document}

writedown

@@ -0,0 +1 @@
+Subproject commit e56a5c17417a4e6101d9abfeeab055af72a2571c