Skip to content
This repository has been archived by the owner on Mar 26, 2022. It is now read-only.

Meetings Resolutions

Samuel Cifuentes García edited this page Feb 24, 2019 · 3 revisions

Introduction

In this page we will write down the decisions we are taking in each weekly meeting. Goal is transparency in our organizational process.

28th January Week

Beginning of the project, we have to get acquaintance with a lot of techs that are completely new to us such as:

  • SOLID
  • Decentralization
  • Linked Data
  • Node.js
  • Angular

Therefore this week will solely be destined to learning as much as possible about this techs, reading documentation and doing tutorials whenever its needed. This learning process will carry on during the whole project, obviously.

4th February week

This week we introduce two more goals

  • Gitflow, we will start using Github's capabilities to handle our organizational needs
  • Documentation, we kick off the start of the documenting process, as it is important to define the domain of the problem without tackling the code itself.

This will be parallel to our formation in the techs involved. We will start looking at other projects made in SOLID like @pheyvaer chess: https://github.com/pheyvaer/solid-chess, displayed in 6th's February Solid World

12th February week

Members who have been present:

  • All

Content

We started a discussion about the application modules (login, chat, contacts...) with a brainstorm.

On the one hand, we decided that when the application starts, the init frame will be a login where the users introduce their PODs to identify themselves. Also we discussed about the different application funcionalities(start a chat, add contacts, list their contacts list...).

On the other hand, we decided to use an agile method (SCRUM) using Project from github funcionalities as backlog. We decided to start coding the login and implementing the funcionalities of list, add and remove contacts from user's contact list. Finally, we will improve the documentation and improve our Angular knowledge.

18th February week

Members who have been present:

  • All

Content

We took an important decision this week. We decided to drop Angular in favour of working in Node.js There are a bunch of reasons to do so. First we already have a strong knowledge deficit. Javascript is not our forte tho we can defend ourselves on it, but we only started doing backend this past month, which is quite different from making toy client side websites. We also have to add learning how to handle SOLID to the equation, which is no easy task as well. Therefore we considered that learning a huge framework such as Angular on top of that is unrealistic for a 4 month constraint. Nonetheless, our project fits better within Node.js, using Angular would be overkill and all in all, it wouldn't provide enough benefits for it to be a sane choice.