Meeting:2021.07.26/Ben,Kevin

Start time	2021-07-26T08:00:00.000Z
End time	2021-07-26T08:30:00.000Z
Attendees	@BenKoo, @KevinTung
Context	Jared has stress at home and was not able to participate regularly
Goal	Check that PKC Workflow has reached the criteria of time management and project management., Alignment on future direction., Resolve participants' conflicts.
Criteria	Decide whether the criteria is reached, Conclusion of previous progress, Consensus of future actions, The conflict has been resolved, Decide future meeting frequency, Decide the criteria and way of communication.
Meeting URL	https://zoom.us/j/91612656130?pwd=SEdjMnJzdURqLzkySnBISkQ2eUhrdz09

Agenda

Conclusion of previous progress (5)

• Written the Logic Models (PKC Workflow, Jenkins, TLA+, Docker) on PKC Workflow
  • Criteria to be verified:

Time management statements

• Predictive plans
• Assign regular time to meet.
• Need a schedule (timetable)) to make verifiable progress
• Need a sign which shows mutual agreement
  • Any group decision needs to be decided group-wise and there must be a confirmation action whether officially or conventionally.
• Participants need to work on the same time schedule and create a full set of documentation so that others can replicate the work from scratch.
• Inform each other before events happen, and in case you had to postpone certain meetings, inform others ahead of time.
• Use one Public instance of PKC, in this case, thewiki.us as a platform to share progress, and you guys can have private instances of PKCs to manage your test cases.
• Be aware of other people's schedules, and making MEETINGS predicable, PREDICABLE TIME TABLE for things that must happen in the near future

Time management statements

Statement	Has Reached	Note
Predictive plans	Partially	PKC Project is planned but meeting wasn't planned.
Assign regular time to meet.	No	We were not able to communicate regularly at the beginning as there were a lot of things like project specification to figure out. Recently the communication were broken among the three of us. I think now I am able to lead regular meetings among 3 of us or between 2 of us.
Need a schedule (timetable)) to make verifiable progress	Yes(80%)	Including Meetings, Daily Documents, Project plan estimated time, Activities. * Ben emphasized FUTURE events but I emphasized on recording current and previous events. So a table to emphasize future events is required.
Need a sign which shows mutual agreement of future events.	Partially	Any group decision needs to be decided group-wise and there must be a confirmation action whether officially or conventionally.
Participants need to work on the same time schedule and create a full set of documentation so that others can replicate the work from scratch.	No	Kevin created the time schedule and invite others to use but there isn't confirmation yet. Kevin will lead the confirmation.
Inform each other before events happen, and in case you had to postpone certain meetings, inform others ahead of time.	Partially
Use one Public instance of PKC, in this case, thewiki.us as a platform to share progress, and you guys can have private instances of PKCs to manage your test cases.	Partially	We used thewiki.us but haven't confirmed a way to share progress.
Be aware of other people's schedules, and making MEETINGS predicable, PREDICABLE TIME TABLE for things that must happen in the near future	No	We haven't shared our schedule. Kevin will lead the confirmation to share schedule.

All Statements of Ben in Wechat

• However, I was expecting the two of you to update me on your regular plans. We need a schedule to move things forward. If we just ignore the schedule, we will remain to be an interest group that does things for fun. The results will not be predictable and no trustworthiness.
• THE TWO OF you still did not assign a regular time to meet so that we can have some predictable interaction pattern. This is becoming a pretty serious violation of the rule of engagement. Especially after I explicitly stated the requirement for?time management. and clearly the two of you just choose to ignore this instruction.
• Is there a process and a sign showing that everyone agrees yet?
• Any group decision needs to be decided group-wise and there must be a confirmation action whether officially or conventionally.
• The meeting agenda should be proposed in PKC.
• We don't even need to have meetings, as long as something is confirmed and new actions are being scheduled that will be all there is to it.

• Please don't upload any video or audio files to wikis, we will find a way to do that more systematically later. A way to manage digital resources is what PKC is all about.
• The whole point of using PKC is to leverage its powers in managing Namespaces. And you guys have been selfishly defining namespaces in ways that are most imminent in your own localized contexts, without thinking about Namespaces must be put in a "Single Source of Truth", such as a single wiki, to ensure the consistency and reusability of the chosen names.
• You guys need a schedule (timetable)) to make verifiable progress.
• Yes, but you need to work on the same time schedule with Kevin and create a full set of documentation so that others can replicate the work from scratch.
• As you develop content and code, you need to think about how others can read the wiki and right away do what you did.
• If there is no project timetable, there should be no more meetings in the future.
• The point is not about being frustrated or not, but the ability to be aware of each other's minimalistic commitment. The main common denominator in this project is PKC, and the process of backing and restoring data.
• The structure of relations in all actions, and all resources, should and must be connected using "Category" tags, and this insight was already very well stated in earlier conversations. Category Tree provides a way to manage the hierarchy of concepts. I also explicitly stated that all Inputs and Outputs are resources, and I even documented a list of resources in the Logic Model's Template Links.
• If a thing is not a resource, then, it is not relevant to a Logic Model's operational context, and therefore, shouldn't be mentioned. All the documents you have passed around in WeChat have demonstrated your lack of willingness to digest the EXPLICIT STATEMENTS I had already told you in two three days of consecutive meetings.
• All your statements still remain in adjectives and generic directions.
• The specific set of resources, in terms of using Jenkins (this Jared did mention today), and the specific sets of Formal Verification Tools (Cog, TLA+, K-Framework), and how they can or cannot be included in the ongoing work, is not even remotely hinted.
• The point is to use one Public instance of PKC, in this case, thewiki.us as a platform to share progress, and you guys can have private instances of PKCs to manage your test cases.
• the use of these tools to help clean up the content of MediaWiki. Since some of these tools are already been packed as Dockerized Images so that they can be tested and validated to see if they fit into our project.
• All these discussions should have been automatically, or manually transcribed into the Discussion Page of TimeLine so that we can see why and how these simple statements have not penetrated our thick skulls.
• All data dictionaries must follow the ideal of being Sound, Precise, and Terminable.
• A "Process" in the context of Logic Model, is a Multi-Input/Multi-Output Function. Therefore, providing the mappings between various Input entries and Output entries can be captured in a Matrix-Like or multiple matrices for their causal relations. For visualizing the "Function", a Matrix or a Railway diagram, like the one shown by Artemis.im website, can be employed.
• During the Pandemic, the most foundational courtesy of informing each other before events happen, and in case you had to postpone certain meetings, inform others ahead of time is the least I am expecting from both of you.
• Both of you had demonstrated a form of irregularity, and also very little attention and thoughts to other people's time schedule.
• Be aware of other people's schedules, and making MEETINGS predicable, PREDICABLE TIME TABLE for things that must happen in the near future