Commit e2c47cb394fe8c83326bbd53178b1f59682fb94c

Authored by Paulo Meireles
1 parent ca5aac74

Adding TO-DO list to work on OpenSym final version

Showing 1 changed file with 75 additions and 0 deletions   Show diff stats
opensym2017/TO-DO.txt 0 → 100644
... ... @@ -0,0 +1,75 @@
  1 +(TODO 1 - Kanashiro) We could refine this section by reducing the explanation about
  2 +Colab and the discussion about our choice of Gitlab as Git repository manager.
  3 +However, we believe that further reductions may impact on the reader
  4 +understanding on the platform.
  5 +
  6 +(TODO 2 - Paulo/Melissa/Siqueira) 4.2* We also have included some additional
  7 +academic literature used in this study:
  8 +
  9 +[1] Mockus et al. Two case studies of open source software development: Apache and Mozilla.
  10 +[2] G. DeKoenigsberg. How successful open source projects work, and how and why to introduce students to the open source world.
  11 +[3] Kon et al. Free and Open Source Software Development and Research: Opportunities for Software Engineering.
  12 +[4] Ducheneaut, N. Socialization in an open source software community: A socio-technical analysis.
  13 +[5] Fagerholm et al. The role of mentoring and project characteristics for on boarding in open source software projects.
  14 +[6] Fagerholm et al. On-boarding in open source software projects: A preliminary analysis.
  15 +[7] Harzl, A. Can FOSS projects benefit from integrating Kanban: a case study.
  16 +[8] Steghöfer el al. Teaching Agile - Addressing the Conflict between Project Delivery and Application of Agile Methods.
  17 +[9] Booch et al. Collaborative Development Environments.
  18 +[10] J. Chao. Student Project Collaboration Using Wikis.
  19 +[11] Tosi et al. Surveying the Adoption of FLOSS by Public Administration Local Organizations.
  20 +[12] Freitas et al. FLOSS in an Open World: best practices from Brazil.
  21 +[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.
  22 +
  23 +(TODO 3 - Paulo)To discuss these works we re-organized the section "REQUIREMENTS
  24 +AND RELATED PROJECTS" in two different sections: "REQUIREMENTS" and another one
  25 +named "RELATED WORK AND PROJECTS"
  26 +
  27 +(TODO 4 - Melissa) Conclusion
  28 +
  29 +** This project resulted in an important case to prove that it
  30 +is possible to conciliate studies and professional training in universities, as
  31 +long as the institution can provide a healthy and challenging environment to
  32 +its students. After the end of the project, some students successfully embraced
  33 +opportunities in public and private sectos, within national borders and abroad.
  34 +Some others went further and started their own companies.
  35 +
  36 +** With some adaptations/"translation processes" it is possible
  37 +to conciliate agile methodologies and FOSS practices to develop software to
  38 +governmental organizations with functional hierarchical structures that use
  39 +traditional development paradigm.
  40 +
  41 +(TODO 5 - Siqueira) Deixar um gancho para uma análise "post mortem" do projeto para o
  42 +artigo do ICSE
  43 +
  44 +(TODO 6- Melissa/Siqueira) 7* We tried to refine our text in order to avoid "not
  45 +very informative" expressions, as mentioned by reviewers.
  46 +
  47 +TODO 7 - Paulo) ** In the redefined section named "REQUIREMENTS", we will add a
  48 +figure which shows how the requirements lead to the architecture and include a
  49 +diagram of this process, as the reviewers suggested.
  50 +
  51 +- http://www.participa.br/softwarepublico/processo-de-evolucao-do-portal-do-software-publico-brasileiro
  52 +
  53 +
  54 +(TODO 8 - Paulo/Melissa/Siqueira) ** After the redefined section called "RELATED
  55 +WORK AND PROJECTS", we will add a new section to present and discuss our
  56 +research design to answer the following research questions:
  57 +
  58 +(TODO 9 - Paulo/Melissa) ** Questions
  59 +
  60 +- Which strategy could be used to integrate several existing FOSS tools to
  61 +promote the collaborative software development?
  62 +
  63 +- How to introduce the FOSS collaborative and agile practices to governmental
  64 +development process?
  65 +
  66 +- How to involve undergraduate students in real-world projects, interacting
  67 +with real customers from a Government?
  68 +
  69 +(TODO 10 - Apresentação)
  70 +1- Melissa vai (dividindo custos com Paulo)
  71 +2- Gabriel vai e também apresenta o artigo do SPB (via UnB), mas alguém do artigo tem que se inscrever
  72 +3- Paulo se inscrever, avisa que não, e produzimos um vídeo (e pedimos apoio ao José/Portugues da OSS)
  73 +
  74 +(TODO 11 - Paulo) mandar email para o Gerosa marcando uma revisão do nosso formulário.
  75 +
... ...