Regular meeting time: 21:30, April 12, Host: Hu Binbin
Time for next regular meeting: 12:30, April 14th, Moderator: Shan Yanbo
1. Work report
| personnel | Completed the task yesterday | Tasks to be completed tomorrow |
|---|---|---|
| Qiao Xihua | Main page of personal center, navigation bar https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Frontend/issues/11 |
Empty classroom query page, integrate existing code |
| Zhang Yixuan | Front page of welcome page and login page https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Frontend/issues/2 |
Perform front-end and back-end interactions, and the timetable query part |
| Shan Yanbo | Preliminary design of results query page https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Frontend/issues/4 |
Complete the results query page |
| Hu Binbin | Login and empty classroom (not interacting with front end and crawler) https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/4 |
Complete another function and have time to interact with the front end and the crawler |
| Li Jiacheng | Timetable query interface (not interacting with front end and crawler) https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/1 |
Results query function |
| Du Bowei | VPN login function is perfect, you can enter the course center and teaching affairs https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/7 |
Perform score inquiry, empty classroom inquiry |
| Guo Jun | Uploaded 5 meeting minutes and processed blog comments https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/20 |
Build a database on the server |
Second, the meeting screenshot
3. Difficulties encountered at work
-
The code uploaded to Git should be backed up.
-
Considering that the late crawler process may bring burden to the server, the crawler will establish a message queue mechanism. In terms of interaction, the crawler does not directly interact with the backend, the crawler crawls to the data and directly enters the database, and the backend extracts the data directly from the database.
4. Burndown chart
5. Code or document check-in records
-
Front end Pull Request:
-
Pull Request:
-
Reptile commit record:
