Here are the following pages that are still not implemented in Angular.
<list of available pages goes here>

Here is a list of possible issues we will encounter:
- If one or more team members happen to work on the same section, we will encounter huge problems in the merging phase;
- Knowledge about v6 is indeed available, but Kris will have to do the following: install JDEV, someone has to create a SVN account for him, so he can checkout the latest version of the project, setup his SVN with proper data, which I myself have no idea what it is, afterwards we would have to do multiple sessions where I have to explain the whole structure in JDEV, where the logic/sql/backend/frontend go, and that will require a lot of time in my opinion + ADF is significantly different than Angular;
- Functionalities within the pages are done in ADF, and we can't always follow the principle of simple rewriting code from Java to typescript and here are several reasons why:
	1. Mario wants everyone to write clean code, and I agree, but the code in ADF, for the most part is utter garbage, so good luck optimizing that code;
	2. There are scenarios which are not covered in Angular (e.g. calling stored procedures/functions from the DB, manipulating triple state checkboxes in a grid). We haven't done that and I think noone has an idea of how to do it properly;
	3. As a fresh example I am going to provide the checkin screen, which was practically done mid February, but was put on hold, since nobody knew what to expect from that screen and we ended up doing something extremely simplified, because we were ALL waiting on info from RV. Things are NOT clear from the beginning, since nobody knows the full picture;
- We don't have an established AND fully functional MAP implementation, which is present in at least 5 screens and not to mention the tied logic for the MAPS section;
- Without a proper organization from SOMEONE, people can decide what to work on at any time and the probability of merge conflicts skyrockets;
- You CANNOT expect to fully develop 100% working pages, since the way we do things in the project has changed 3 times since we started working on it, there are even cases, both complex and simple,  where NOBODY has an idea how to be done and we simply "LEAVE IT FOR LATER";
- Functioning as a team at this stage seems impossible, since exchanging information and/or solutions make us "TOO DEPENDENT" on eachother, which benefits absolutely nobody. We CANNOT work the same way, since we have differences in knowledge and if we deny help/knowledge nothing good will come out of it.
- We still do not have the necessary base of scenarios to cover all aspects of new developments, so that we can simply look it up rather than "depending too much" on other team members.


Things that are worth mentioning (for the 100th time):
- What is the purpose of calling ourselves a team if we do nothing that resembles team effort?
- I completely understand how everyone is "SUPER SUPER BUSY", but don't tell me you can't spare 20-30min on an issue that will help the other person progress, because at the end of it, we get blamed for "NOT BEING EFFICIENT". "Teamwork makes the dreamwork", am I right?;
- We don't have the organization/project manager/testers/resources, and you expect each of to be able to fulfill multiple roles at once, that is just tough. We can't test all the posibilities, we can't possibly know all the angles and we can't predict issues that can be cause by the customers themselves (e.g. How can I predict that the team from another company loaded TRASH data and causes our app to explode);

Impressions from last visit:
- It leaves quite an impression that we get no feedback whatsoever, just get presented with a lost client and a 5-minute quick lesson on why we are underperforming without addressing the obvious reasons, which have been existing for years.