Report contributions

[labra]

Report individual contributions made by each team member

[themrcesi]

Here I leave the main contributions (more or less in chronological order):

Documentation

• Documentation 0.1: in collaboration with @alvarezGarciaMarcos.
  • Sections 1, 1.1, 1.2, 1.3, 2, 12.
• Documentation 1.0:
  • Section 5: block view diagrams and explanations.
  • Section 6: sequence diagrams and explanations.
  • Section 8: domain model diagram.
  • Improvements in other sections: 3.2, 9, 10, 11.
• Documentation 1.1:
  • Minor improvements.

Implementation

• Developing a prototype with the main components of the application, in collaboration with @alvarezGarciaMarcos in this repository.
  • App
  • Dashboard, MyMap
  • NavBar, Login.
  • RouteList, RouteSummary.
• Integration of the above mentioned prototype into the main repository.
• Routing
• Displaying routes in the map.
• Redux components:
  • RouteActions, AuthActions, UserActions, LoadActions.
  • RouteReducer, Authreducer, UserReducer, LoadReducer, RootReducer.
• Parser of GPX files.
• Integration of the SOLID module functions into the application.
• Routes middleware.
• SOLID: permissions management, routes sharing, posting comments, groups creation with @alvarezGarciaMarcos (based on @InigoGutierrez previous work).

Testing

• Redux components:
  • RouteActions, AuthActions, UserActions, LoadActions, LocalesActions.
  • RouteReducer, Authreducer, UserReducer, LoadReducer, LocaleReducer.
• Other components: RouteSummary, MyMap, PageNotFound, Settings, Footer, Dashboard, Notifications, NotificationsList, Notification.
• Utils/functions.

General

• Solving general application bugs.
• Readme elaboration.
• General coordination of the team.
• Presentation (my part).

[alvarezGarciaMarcos]

Implementation

• Develop prototype with the main views of the application in this repo in collaboration with @themrcesi
• Integration of the above mentioned prototype in the main repository in collaboration with @themrcesi
  • Dashboard, MyMap
  • Navbar, Login
  • RouteList, RouteSummary
  • App
• Creation of a SlideShow component
• Creation of the rdf-query library.
• Implementing two middlewares: one for logging information in a good way to see everything tidied up, and other for asyncrhonous fetching of resources related to the profile of the user (asyncProfileFetch)
• Creation of a modal component that is used accross the application to interact with the user
• Creation of CSS files of the whole application
• Solid (in collaboration with @themrcesi, based on previous work made by @InigoGutierrez)
  • Permissions management
  • Route sharing
  • Posting comment (React components)
  • Route creation

Testing

• The following components:

  • Slideshow
  • RouteDetails
  • UploadButton
  • UploadRoute
  • ShareRoute
  • FriendList
  • Navbar

• Load tests with artillery

Documentation

• Documentation 0.1 - Sections 1, 1.1, 1.2, 1.3, 2, and 12 in collaboration with @themrcesi
• Documentation 1.0
  • Section 5. Explanation about middlewares
  • Improvements in sections 3.2, 9, 11 in collaboration with @themrcesi

General

• Creation of Slack workspace
• All minute writing and uploading (both to Slack and the Wiki)
• Fixing application bugs
• General coordination of the team
• Creation of the presentation template
• Creation of Dockerfile

[lamasumas]

Implementation

• Components
  • Profile
  • FriendList
  • Comment (GUI)
  • Setting
  • Internationalization ( with English and Spanish locales)
  • Footer
• External manual: External page where the user will be teach, in the case he needs some help, in how to use our application. Also, in here we answer some frequently ask questions that the user might have, like "What is Solid?" or "Why should I care about descentralized technologies?"
• Dev team page: External page that show who we are and which is our githubs accounts, so in case someone wants to contact us, his able to do it.
• Redux:
  • LocaleReducer
  • LocaleAction
• Solid:
  • Profile info
  • List of friends

Testing

• Profile component
• Footer
• Comment

Documentation

• Documentation 0.1: Sections (including diagrams) : 5, 5.1, 11, 3 in collaboration with @InigoGutierrez
• Documentation 1.0: Sections (including diagrams) 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7 and 9.4.

General

• Solving several bugs
• Solving a ton of codacy issues
• Presentation (my part)
• Reviewing and accepting pull requests

[InigoGutierrez]

Documentation

• 3.1, Business context:
  • Made flow of information consistent.
  • Added arrow meanings to the legend.
• 3.2, Technical context:
  • Added Maps API interface.
  • Added 3.2.1 about interaction with external APIs.
• 3.2, Decisions:
  • Redacted disadvantages of TDD and Codacy.
• 5, Building block view:
  • Made initial diagram, which would later suffer many updates.
  • Added information about the routes module and the way it was tested.
• In general:
  • Corrected the grammar of the documentation before deliveries.
  • Participated in the discussion of some parts, mainly domain concepts and security.

Sections 3 and 5 where written with @lamasumas for the first delivery.

Implementation

• Initially created and developed the module for routes functionality regarding Solid (creating, reading, updating, sharing and deleting routes and comments), which final problems were solved by @themrcesi and @alvarezGarciaMarcos.
• Explored libraries to interact with pods, manipulating information and files, researched and used solid-acl-utils and solid-file-client.
• Made the javascript source file from which routes for unit tests are taken.

Testing

• Researched methods of local pod testing for unit tests; found about, explored and used solid-local-pod.
• Tested the solid routes functionality; tests for all functionality regarding routes.
• Refactored several tests to avoid code duplication problems.

General

• Investigated how to and deployed a pod locally to try and create my user pod there, but finally switched to Inrupt because of its lack of UI.
• Investigated Solid functionality:
  • How information is stored in pods
  • How to deal with permissions (what is an .acl file, its dangers, how to create and manipulate them)
• Made efforts in the specification repository to get a common specification and explained its minutiae to my group.

[garciaAlvarezPelayo]

Documentation

Documentation 0.1

• Section 3.1 Business Context

• Section 3.2 Tecnical Context

• Section 4 Solution Strategy

• Section 7 Deployment View

all of them in collaboration with @alvarogarinf

• Section 10 Quality Requirements

Documentation 1.0

• Section 8 Cross-cutting Concepts

Documentation 1.1

• Minor improvements

Implementation

Components

• MyRoutes
• RouteDetails
• ShareRoute

Modals: using the fully adaptable ViadeModal component, created by @alvarezGarciaMarcos

General

• Minor modification in tests for adapting them to the new implementation

• Presentation (my part)

• Use of Lighthouse and My Web Audit, Google applications, to test

[alvarogarinf]

Documentation

Documentation 0.1: in collaboration with @garciaAlvarezPelayo .

• Section 3.1 Business Context
• Section 3.2 Tecnical Context
• Section 4 Solution Strategy
• Section 7 Deployment View

Documentation 1.0:

• Improvements and corrections in sections 3, 4.1 and 11

Implementation

• Added the component UploadRoutes and therefore the logic to upload the route file using the gpx parser and the images (except the solid part)
• Fix other components to make the implementations work

Testing

• RouteList
• Comments, Comment and CommentList
• Cucumber tests

General

• Solving general application bugs
• Presentation (my part).