ES2C Meeting's Minutes - Arquisoft/viade_es2c GitHub Wiki

3rd February 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Iván Álvarez López
  • Ana María García Sánchez

Summary

We first agreed on writing our documentation, issues and commits in English because our professor used that language in the documentation he gave us at the beginning.

Then, we observed our initial project so we could begin with the organization and implementation ideas.

After that, we decided that we are going to show our doubts, problems, work distribution and information searching by using issues and we are going to use the kanban’s functionality available in our git repository so we could be more organized and show our work.

We created different branches from the develop’s branch too. We called them “frontend”, “backend” and “documentation” so we could structure our project and we can create our personal branches from them (depending on the work we are doing) in the future.

And finally, we created different kanban’s boards, one for each new branch created during this meeting, and we added our first issue (it is about writing our names in our “Readme” file).

10th February 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Iván Álvarez López
  • Ana María García Sánchez

Summary

At first, we have commented on the different information obtained on React and Solid and we have accorded the distribution of the distinct parts of the documentation. Iván and Diego are the responsible of "Introduction and goals", Ana will take care of "Constraints" and Elmer and Jaime will carry out "Context and scope". These parts will be made in different branches that will start from the documentation:

  • feature_arc42_01introduction
  • feature_arc42_02contsraints
  • feature_arc42_03context

The next point has been to clarify the characteristics of the application and the different libraries that we will use to simplify development- The characteristics are the following:

  • The system will be based on a decentralized architecture where data storage is separated from the app.
  • Users can store their routes in their own pods.
  • Users can view the routes stored on a map.
  • The app will allow a user to share pictures, videos or information about a route with other friends.
  • A user can get notifications when some friend shares a route with him.
  • Users can have groups of friends with whom they may want to share a route
  • It should be possible to view routes loaded by users that are using a different app, so interoperability with other route management systems should be taken into account.
  • Ease of use by non-technical people.
  • Responsiveness of the application.
  • Online independence: no central control of data.
  • Security and privacy: no vulnerability points.
  • Aesthetics and friendliness of the application.
  • The originality of the solution.
  • Usability of technical documentation.
  • Interoperability with similar Solid apps.

In order to solve possible style problems, we are going to use bootstrap and we are going to investigate the differences between React and React Native because we want to offer support to mobile devices.

17th February 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Iván Álvarez López
  • Ana María García Sánchez

Summary

First, we have distributed the documentation as follows:

  • Solution strategy: Ana.
  • Building Block View: Iván y Diego.
  • Runtime View: Jaime y Elmer.

Each of the remaining points will be distributed among each of the members:

  • Deployment View: Elmer.
  • Cross-cutting Concepts: Iván.
  • Design decisions: Jaime.
  • Quality Requirements: Diego.
  • Risks and Technical debts: Ana.

Secondly, we have commented on the libraries and documentation found on React, Solid ...

9th March 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Iván Álvarez López
  • Ana María García Sánchez

Summary

We already have a login page and the most part of the routes' logic, so we distributed the other parts that we want to have for the next deadline (it's in a week).

So we decided that we will have the logic for save and load the information in the POD's (but we will use files instead of POD's for the demo), create a list of friends and maybe try to do the logic to be able to share images, routes, etc and finish the basics of the routes' logic.

We are going to try to stay as simple as possible so we can deliver a good demo and have a good base to create a well-made app.

16th March 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Ana María García Sánchez

Summary

Today we presented our first demo and saw the things that needed more time and work. In general, we are happy with our work because we are a few people right now and our demo is going in the direction that we wanted.

We decided to distribute the work for the future weeks:

  • Fix gh-pages
  • Fix codecov
  • Create a specific page for every route
  • Improve the creation of the route
  • Fix the RDF
  • take the routes from the PODs
  • Learn about gpx
  • Do more tests
  • Fix internationalization
  • See how to connect the route's data and the views
  • Delete the extra code
  • Fix the friend's list

And at the same time, we want to update the documentation and continue having meetings.

23th March 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Ana María García Sánchez

Summary

After the revision, we talked about our work. We have fixed some important issues and learned how to fix the rest of the problems that we were having, so we expect to have all the basic functionality done by the next meeting and start to improve some parts and add extra requirements.

This is the list of the work we have done from the list of the previous meeting:

  • Fix gh-pages
  • Fix codecov
  • Fix the RDF
  • take the routes from the PODs (But we still need to improve this)
  • See how to connect the route's data and the views

So for the next meeting, we want to:

  • Improve the I/O functionality
  • Try to get all the routes from a folder
  • Try to fix internationalization
  • Build a global array of routes
  • Pass parameters by URL
  • Charge the routes using the parameters
  • Fix the friend's list
  • Fix some links in the login page
  • Learn about tests

30th March 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Ana María García Sánchez

Summary

In this meeting, we tried to fix some errors and talked a little about our work. Now we have some parsers on the project, fixed the turtle's format so the POD can recognize it and treat it how it should be treated. Apart from that, this is the list of the work we have done from the previous meeting:

  • Try to get all the routes from a folder
  • Build a global array of routes
  • Pass parameters by URL
  • Charge the routes using the parameters
  • Quit some excess of code

So for the next meeting, we want to:

  • Improve the I/O functionality
  • Try to fix internationalization
  • Fix the friend's list
  • Fix some links in the login page
  • Learn about tests
  • Build some tests
  • Try to use LDFlex
  • Fix some problems about asynchronous methods
  • More parsers
  • Some documentation
  • Quit mode excess of code

13th April 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Ana María García Sánchez

Summary

In this meeting, we talked about our revision and the things we wanted to improve and add to Viade for the final deadline. Here you can see what we did from the last meeting and what we want to do for the final deadline: We did:

  • Quit some excess of code
  • Improve the I/O functionality (some parts)
  • Try to fix internationalization
  • Fix the friend's list
  • Fix some links in the login page
  • Learn about tests
  • Build some tests
  • Fix some problems about asynchronous methods
  • More parsers
  • Some documentation

We want to do:

  • Improve the I/O functionality (The rest)
  • Quit some buttons from the notifications that create errors
  • More parsers
  • Some documentation
  • Quit mode excess of code
  • Add comments
  • Comment the code
  • Create groups of friends
  • Improve the interface
  • Add security
  • Improve the friends' page
  • More options to upload routes from outside
  • Let the user choose where he want to store routes
  • Let the user write a link to a route in his POD
  • Separate the user's routes from the ones that his friends shared with him
  • Create a popup with the list of friends that the user can share a route with
  • Delete the routes delay so it goes faster
  • Write more descriptive errors
  • Force Viade to ask the user for permissions in every log in

20th April 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Ana María García Sánchez

Summary

In this meeting, we talked about our work progress and talked about some improvements. Here you can see what we did from the last meeting and what we want to do for the final deadline: We did:

  • Improve the I/O functionality (The rest)
  • Quit some buttons from the notifications that create errors
  • More parsers
  • Improve the friends' page

We want to do:

  • Some documentation
  • Quit mode excess of code
  • Add comments
  • Comment the code
  • Create groups of friends
  • Improve the interface
  • Add security
  • Improve the friends' page
  • More options to upload routes from outside
  • Separate the user's routes from the ones that his friends shared with him
  • Create a popup with the list of friends that the user can share a route with
  • Delete the routes delay so it goes faster
  • Write more descriptive errors
  • Force Viade to ask the user for permissions in every log in

27th April 2020:

Attendance

  • Elmer José Cortez Sanjínez
  • Jaime López Montero
  • Diego Santos Neila
  • Ana María García Sánchez

Summary

In this meeting, we talked about our work progress and talked about the last things we are gonna do in the project. We don't have much time left so we won't be able to accomplish all our objectives, so we will do the last necessary things and prepare our presentation. We did:

  • Quit mode excess of code
  • Add comments
  • Improve the interface
  • Improve the friends' page
  • More options to upload routes from outside
  • Create a popup with the list of friends that the user can share a route with
  • Separate the user's routes from the ones that his friends shared with him ( with the name of the author)

We want to do:

  • Some documentation
  • Create groups of friends
  • Improve the interface
  • Add security
  • Improve the friends' page
  • Create a popup with the list of friends that the user can share a route with
  • Create a presentation

We won't do:

  • Comment the code
  • Write more descriptive errors
  • Delete the routes delay so it goes faster
  • Force Viade to ask the user for permissions in every log in