Skip to content

Commit

Permalink
Correct missing markup and cut text
Browse files Browse the repository at this point in the history
  • Loading branch information
Pelayori committed Feb 18, 2024
1 parent fa76f13 commit eff0c82
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/src/09_architecture_decisions.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -36,5 +36,5 @@ There you will find links and examples about ADR.

The purpose of this section is to create an ordered list of architectural decisions that we will make as we develop the project. This list will be ordered according to the importance of the decision.

1. *Protection of the master branch: This decision was made at the beginning of the first team meeting. Without a doubt, this is the most important architectural decision, as it will mean not being able to modify the master branch without all members having previously reviewed the modifications, so that nothing is added that could affect the functioning of the main branch. In addition to this, a develop branch was also created, which will function as a main2.0 branch for adding progress as it is made. To add to this branch also requires the approval of some members of the team.
2. *Switch from JavaScript to Java with Spring: This is a decision we made on Tuesday, February 6th, after the second session. So far in the project, it is one of the most important decisions so far, as it will mean not using the base project and starting another application in another programming language. We have come to this decision because we consider it much more accessible to use the Java language, as it has been taught from the beginning of the course. Moreover, with what we learn in the subject SDI we can apply it all to web development, using the Spring framework. We have also found a
1. *Protection of the master branch*: This decision was made at the beginning of the first team meeting. Without a doubt, this is the most important architectural decision, as it will mean not being able to modify the master branch without all members having previously reviewed the modifications, so that nothing is added that could affect the functioning of the main branch. In addition to this, a develop branch was also created, which will function as a main2.0 branch for adding progress as it is made. To add to this branch also requires the approval of some members of the team.
2. *Switch from JavaScript to Java with Spring*: This is a decision we took on Tuesday 6 February, after the second session. So far this project is one of the most important decisions so far, as it will mean not using the base project and starting another application in another programming language. We have come to this decision because we consider it much more accessible to use the Java language, as it has been taught from the beginning of the course. Moreover, with what we learn in the subject SDI (Distributed Systems and Internet) we can apply it all to web development, using the Spring framework. We have also found a Java library with which we can use Wikidata very easily. It was a unanimous decision that will make it easier for us to work smoothly in the long run.

0 comments on commit eff0c82

Please sign in to comment.