Decision making logs from previous semester: link hosted on Confluence

Index Week Rationale Decision Agreed by Catelogue
1 1 Confluence is too expensive given the current budget. Making a website on GitHub using templates is not too time-consuming. Use GitHub to make our landing page this semester. All team members.  
2 1 Reflecting on the collaboration last semester, not setting a fixed time for group meetings has caused trouble for some team members. Setting a fixed time to meet twice a week. All team members.  
3 1 Reflecting on our experience from last semester, we think that client meetings should not require all team members to attend, especially given the consideration that all team members have done this project for 1 semester and we all have a better idea of what the clients want now. Only the project manager meets with clients 1-2 times a week. All team members and clients.  
4 1 Due to the complex nature of physical components that OptoFab is manufacturing, the order placing process is highly dynamic. Since the IT department of RSPhys did not allow us to use React, the website development, especially debugging, is excruciating and the maintenance in the future is going to be hard for the IT department of RSPhys as well. Any tiny change of the UI or functionalities would require coding in multiple similar but different HTML files and create a hassle for the JavaScript part as well. Need to talk to IT department of RSPhys asap about using React. Inform clients about the importance of giving all requirements at once and make as little change to the functionalities as possible. All team members.  
5 1 The IT department of RSPhys allowed us to use React. The changes(new requirements) need to be made in so many places that the developers think rewriting the entire website with React is quicker and neater than editing the old one. Clients agreed. Refactor the website using React. All team members, clients, IT department of RSPhys.  
6 2 Reflecting on feedback from the audits last semester, making PowerPoint presentations might be unnecessary work that might even distract us from refining the landing page. Very carefully refine landing page for audit. Use the landing page to show our progress instead of PowerPoints. All team members.  
7 4 Database is just a part of the backend of one of the web applications that we are developing. Calling the customer portal the website and the order management system the database is not very clear. Specify the current two products as the Customer Portal and the Local Order Management System. All team members.  
8 4 Reflecting on feedback from Audit 1, our peers and tutor this semester want to make sure that everyone’s voice is heard by letting everyone participate in the tutorials and audits more. We will adjust our approach in the coming tutorials and audits.
1. The project manager will only be engaging in the Q&A session. Other team members will be in charge of presenting the Audits.
2. A reflection log will be created. All team members are going to write down some reflections when appropriate.
3. Strongly encourage all team members to communicate with the shadow team and Greg on tutorials.
All team members.  
9 4 Reflecting on feedback from Audit 1, The course convenor, our tutor, and our shadow team all think that we should create a reflection log in Audit 1. We will actively listen to other people’s advice and improve our documentation by adding a reflection log. All team members.  
10 5 Reflecting on feedback from Audit 1, many stakeholders think that more members should present the Audits. Ruoqian, Hengrui, Ruiqiao will prepare for Audit 2. Yaoyi, Phillip, Guoyu will prepare for Audit 3. All team members.  
11 5 Considering the time frame, we can not afford to develop the Remove functionality to a full extend, as in removing any components regardless of their position in a list of components. After negotiating with OptoFab, we compromise to only developing the Remove functionality for the last component in a list of components. Develop the Remove functionality for the last component in a list of components, such as Layer, Side, Spec. All team members and clients.  
12 5 Our current logs page contains four documentation types, meeting minutes, reflection log, work records, and decision making. From audit 1 feedback, we found our logs page is too long and hard to read. Our members also reflect it is hard to edit since the document is too long. Split Logs entry in the Navbar into four entries: Decision Making, Meeting Minutes, Reflection Log, and Work Records. Each entry link to the corresponding document only. All team members.  
13 Teaching break Visual effects of the web portal should be distinct from optofab-act site. Redesign the color scheme and page layout Website team members and client. Design
14 Teaching break For better customer experience, improve legibility and reduce the possibility of user mishandling on our website Add background opacity for texts; get rid of footer links; try non-linear background color schemes; Website team members and client. Design
15 Teaching break We need to find a way to limit file upload types for in different places so that we can avoid hackers uploading virus. Meanwhile, we have to handle some very uncommon types of files such as winlens files. We decided to check the file types based on the file extensions. Website team members. Technical
16 Teaching break We need to find a way to validate users are actual humans and prevent DDOS attacks. Google RECAPTCHA V2 is the most popular and stable tool available. We decided to use Google RECAPTCHA to implement validation. Website team members. Technical
17 7 As we all agreed in the Statement of work in the beginning of this semester, our team will start to wrap up the coding process and start to write the handover documents. According to our clients, we need to write handover documents in detail for OptoFab, for the future Techlauncher team, and for the maintainer in RSPhy We decided to 3 separate handover documents. A user guide for OptoFab and their customers on how to use the Customer Portal, one technical handover document for each of the product we have made - the Customer Portal and the Order Management System. All team members and client. Project Management
18 8 The backend of the Customer Portal is having trouble to be launched to the ANU server. OptoFab thinks the handover document has higher priority during our Monday regular meeting. They confirmed that our team need to work on the handover documents instead of researching more on resolving the technical issues. We decided to pause all coding activities and focus on the handover documents, the video, and Audit 3. All team members and client. Project Management