diff --git a/opensym2017/TO-DO.txt b/opensym2017/TO-DO.txt
new file mode 100644
index 0000000..b4abaac
--- /dev/null
+++ b/opensym2017/TO-DO.txt
@@ -0,0 +1,75 @@
+(TODO 1 - Kanashiro) We could refine this section by reducing the explanation about
+Colab and the discussion about our choice of Gitlab as Git repository manager.
+However, we believe that further reductions may impact on the reader
+understanding on the platform.
+
+(TODO 2 - Paulo/Melissa/Siqueira) 4.2* We also have included some additional
+academic literature used in this study:
+
+[1] Mockus et al. Two case studies of open source software development: Apache and Mozilla.
+[2] G. DeKoenigsberg. How successful open source projects work, and how and why to introduce students to the open source world.
+[3] Kon et al. Free and Open Source Software Development and Research: Opportunities for Software Engineering.
+[4] Ducheneaut, N. Socialization in an open source software community: A socio-technical analysis. 
+[5] Fagerholm et al. The role of mentoring and project characteristics for on boarding in open source software projects.
+[6] Fagerholm et al. On-boarding in open source software projects: A preliminary analysis.
+[7] Harzl, A. Can FOSS projects benefit from integrating Kanban: a case study.
+[8] Steghöfer el al. Teaching Agile - Addressing the Conflict between Project Delivery and Application of Agile Methods.
+[9] Booch et al. Collaborative Development Environments.
+[10] J. Chao. Student Project Collaboration Using Wikis. 
+[11] Tosi et al. Surveying the Adoption of FLOSS by Public Administration Local Organizations.
+[12] Freitas et al. FLOSS in an Open World: best practices from Brazil.
+[13] Ghosh et al. Study on the effect on the development of the information society of European public bodies making their own software available as open source.
+
+(TODO 3 - Paulo)To discuss these works we re-organized the section "REQUIREMENTS
+AND RELATED PROJECTS" in two different sections: "REQUIREMENTS" and another one
+named "RELATED WORK AND PROJECTS"
+
+(TODO 4 - Melissa) Conclusion
+
+** This project resulted in an important case to prove that it
+is possible to conciliate studies and professional training in universities, as
+long as the institution can provide a healthy and challenging environment to
+its students. After the end of the project, some students successfully embraced
+opportunities in public and private sectos, within national borders and abroad.
+Some others went further and started their own companies.
+
+** With some adaptations/"translation processes" it is possible
+to conciliate agile methodologies and FOSS practices to develop software to
+governmental organizations with functional hierarchical structures that use
+traditional development paradigm.
+
+(TODO 5 - Siqueira) Deixar um gancho para uma análise "post mortem" do projeto para o
+artigo do ICSE
+
+(TODO 6- Melissa/Siqueira) 7* We tried to refine our text in order to avoid "not
+very informative" expressions, as mentioned by reviewers.
+
+TODO 7 - Paulo) ** In the redefined section named "REQUIREMENTS", we will add a
+figure which shows how the requirements lead to the architecture and include a
+diagram of this process, as the reviewers suggested.
+
+- http://www.participa.br/softwarepublico/processo-de-evolucao-do-portal-do-software-publico-brasileiro
+
+
+(TODO 8 - Paulo/Melissa/Siqueira) ** After the redefined section called "RELATED
+WORK AND PROJECTS", we will add a new section to present and discuss our
+research design to answer the following research questions:
+
+(TODO 9 - Paulo/Melissa) ** Questions
+
+- Which strategy could be used to integrate several existing FOSS tools to
+promote the collaborative software development? 
+
+- How to introduce the FOSS collaborative and agile practices to governmental
+development process?
+
+- How to involve undergraduate students in real-world projects, interacting
+with real customers from a Government?
+
+(TODO 10 - Apresentação)
+1- Melissa vai (dividindo custos com Paulo)
+2- Gabriel vai e também apresenta o artigo do SPB (via UnB), mas alguém do artigo tem que se inscrever
+3- Paulo se inscrever, avisa que não, e produzimos um vídeo (e pedimos apoio ao José/Portugues da OSS)
+
+(TODO 11 - Paulo) mandar email para o Gerosa marcando uma revisão do nosso formulário.
+
--
libgit2 0.21.2