Skip to content

Discussion on how to raise weekly meeting topic and Discussion on Java OOP Rule

Meeting Info

Date 2022-08-18
Topic Discussion on how to raise weekly meeting topic and Discussion on Java OOP Rule
Attendee Calvin Yan, Rocky Chi, Daniel Zhou, Ted Zhao, Jackson Liu, Kevin Qian, Selly Huang
Note Taker Kevin Qian
Timer Daniel Zhou
Duration 60 minutes

Meeting Agenda

  1. Discussion on how to raise weekly meeting topic (5 min)
  2. Discussion on Java OOP Rule - (35 min)

Meeting Minutes / Action Items

Discussion on how to raise weekly meeting topic

  • Discussion: whether HEA team uses BOT to notify events and messages
  • Discussion: the topic of the weekly regular meeting needs to be added together or alternatively
  • Discussion: whether a new process needs to be added in the weekly meeting, and determine the topic of the next meeting

Discussion on Java OOP Rule

  • Java OOP Rule survey result:

java-oop-result

  • Results for controversial rules:
Rule Name Result Comments
[Mandatory] Using a deprecated class or method is prohibited Mandatory
[Mandatory] The toString method must be implemented in a POJO class Mandatory It is not allowed to submit without toString method. It is not recommended to use Lombok plug-in, which is easy to form dependency
[Recommended] For a setter method, the argument name should be the same as the field name Recommended

Action output

  1. Add a new link to the weekly meeting to decide the topic of the next meeting.
  2. HEA members can add topics at any time, and the priority can be discussed and sorted.
  3. Daily tip needs to let everyone in mctteam participate better. The sharing should be carried out in a modular manner, and more scene descriptions need to be added for better understanding.
  4. Daily tip, the prioritization:Git Process, RESTful naming convention, Frontend rules.
  5. The team needs to strengthen internal learning and understanding of rules, land on the project, and strengthen project code constraints through ide plug-ins and code reviews.