Skip to content

Commit

Permalink
Merge pull request #22 from SebastianJames55/feature/meeting_minutes
Browse files Browse the repository at this point in the history
Feature/meeting minutes
  • Loading branch information
SebastianJames55 authored Aug 30, 2023
2 parents de5ea09 + 9c70c60 commit 9726d5e
Show file tree
Hide file tree
Showing 13 changed files with 977 additions and 0 deletions.
Binary file added high_level_diagram.drawio.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
65 changes: 65 additions & 0 deletions meeting_minutes/11th_July.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@

---

**Meeting Details:**

- Date: 11th July 2023, Tuesday
- Time: 1400 WAT

**Agenda Review:**

- Finalize our idea
- define our goal
- research on practicability
- confirm with mindsdb team
- Register for the hackathon
- Plan the project
- define milestones, assign deadlines, roles
- tech stack
- coding guidelines: naming conventions
- Discuss how to start with the project
- reach out to community for help
- possibility of mentors

**Meeting Summary:**

- Goal is to help console people who are going through tough times mentally
- Practicable, refer Build a Twitter Chatbot with OpenAI GPT in mindsdb learning hub
- We need to research & find the better engine & model which is specific to our use case
- Registered for the hackathon
- Prepared a high level diagram
- Defining milestones requires better understanding of the tasks to be done underneath.
So we are going to work on the action items & define them by 22nd July 1400 WAT.
- Front-end: TypeScript, ReactJS
Back-end: Python
- Coding guidelines draft will be prepared & later updated


**Action Items:**

- Reach out to MindsDB community to know if the idea is practicable by Seb
- how to get started
- reach out for help
- check if we would get mentors
- Research on working of mindsdb (refer chatbot examples), chatbot in general by Penn & Seb
- Preparing coding guidelines by Penn on 16th July


**Decisions and Resolutions:**

- Finalized idea: Chatbot for mental health
- Should revisit ideation in case it's not practicable


**Additional Notes:** (not specific to agenda items)
- [WeMakeDevs blogging challenge on hashnode](https://wemakedevs.org/events/hashnode)
- Hashnode hackathons


**Next Meeting:**

- Date: 15th July
- Time: 1400 WAT
- Expected End Time: 1500 WAT

---
39 changes: 39 additions & 0 deletions meeting_minutes/16th_July.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@

---

**Meeting Details:**

- Date: 16th July 2023, Sunday
- Time: 1400 WAT

**Agenda Review:**

- Plan the project
- breakdown the project into tasks

**Meeting Summary:**

- Broke down the project into tasks in terms of front-end, back-end by referring to Snoopstein chatbot example in detail.

**Action Items:**

- Design & implementing UI by Penn by 21st July
- Linking front-end to back-end by Penn
- Deciding the engine & model for the use case by Seb by 19th July
- Pass request (name, chat text) to mindsdb by Seb by 22nd July
- Python coding guidelines by Seb

**Decisions and Resolutions:**
- Tasks defined & assigned, along with deadlines
- Review progress, & keep each other in check

**Additional Notes:** (not specific to agenda items)
- few others are working on similar idea, saw it in questions channel

**Next Meeting:**

- Date: 19th July
- Time: 1400 WAT
- Expected End Time: 1500 WAT

---
43 changes: 43 additions & 0 deletions meeting_minutes/23rd_July.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@

---
**Submission deadline: 19th Aug**

**Meeting Details:**

- Date: 23rd July 2023, Sunday
- Time: 1400 WAT

**Agenda Review:**

- Progress wrt action items & tasks assigned
- Code structure: monolithic arch - front-end & back-end in same codebase
- Develop & release faster with deadline in view

**Meeting Summary:**

- Penn has designed & implemented basic UI. Penn will be checking on how to link front-end to back-end.
- Seb researched on engine & model. Privacy is a concern when it comes to openai & gpt. Future scope: explore on open source projects which respects privacy. Coding guidelines have been updated. Seb will be implementing the connection between back-end & mindsdb using python sdk provided by mindsdb.

**Action Items:**

- Deploy front-end for demo by Penn
- Linking front-end to back-end by Penn
- How to approach deploying front-end & back-end: research on best practices on use of multiple github accounts by Seb
- DB schema design: input & output tables by Seb

**Decisions and Resolutions:**

- Penn will be creating a repo for front-end in his github.
- Use of vercel (front-end) & render (back-end) for deploying

**Additional Notes:** (not specific to agenda items)

-

**Next Meeting:**

- Date: 30th July
- Time: 1400 WAT
- Expected End Time: 1500 WAT

---
46 changes: 46 additions & 0 deletions meeting_minutes/30th_July.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@

---
**Submission deadline: 19th Aug**

**Meeting Details:**

- Date: 30th July 2023, Sunday
- Time: 1300 - 1330 WAT

**Agenda Review:**

- Progress wrt tasks
- front-end deployment
- back-end connection to mindsdb
- Importance of automating backend
- Reviewing code & documentation, and merging into dev for reference

**Meeting Summary:**

- Penn facing minor issue with front-end deployment
- Seb facing import error for mindsdb-python-sdk
- Going forward the focus will be on getting more work done towards having a project for submission with proper documentation.

**Action Items:**

- Penn will finish up the minimal front-end & connection to back-end
- Penn will take up tasks for back-end based on github issues
- Seb will connect back-end to mindsdb & get a basic flow working
- Seb will create github issues

**Decisions and Resolutions:**

- Github issues will be used to create, define tasks with steps & resources
- Penn & Seb will work towards a working submission

**Additional Notes:** (not specific to agenda items)

- Meeting preponed as per Penn's suggestion

**Next Meeting:**

- Date: 4th August
- Time: 1400 WAT
- Expected End Time: 1500 WAT

---
36 changes: 36 additions & 0 deletions meeting_minutes/4th_Aug.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@

---
**Submission deadline: 19th Aug**

**Meeting Details:**

- Date: 4th Aug 2023, Friday
- Time: 1400 - WAT

**Agenda Review:**

- Urgency to focus on back-end tasks

**Meeting Summary:**

-

**Action Items:**

-

**Decisions and Resolutions:**

-

**Additional Notes:** (not specific to agenda items)

-

**Next Meeting:**

- Date: August
- Time: 1400 WAT
- Expected End Time: 1500 WAT

---
54 changes: 54 additions & 0 deletions meeting_minutes/9th_July.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
---

**Meeting Details:**

- Date: 9th July 2023, Sunday
- Time: 1300 WAT

**Attendees:**

- Penn - Front-end
- Sebastian - Back-end

**Agenda Review:**

- Self-introduction
- Sharing ideas

**Meeting Summary:**

- Self-introduction:
- Address each other's names, shared details such as country, timezone, language, current tech stacks and areas of experience
- Ideas Shared:
- Chatbot for mental health by Sebastian
- Chatbot for coding assistance by Penn

**Action Items:**

- Prepare meeting minutes format - Assigned to Seb - Deadline: 11th July
- Research for more ideas - Assigned to Penn - Deadline: 11th July

**Decisions and Resolutions:**

- Fix ideas, & start with the project by next meeting mentioned below

**Additional Notes:** (not specific to agenda items)

- [Kunal Kushwaha](https://www.youtube.com/c/kunalkushwaha)
- [WeMakeDevs](https://wemakedevs.org/)
- [Hashnode](https://hashnode.com/)
- [Rix](https://hashnode.com/rix?source=nav)

**Next Meeting and Adjournment:**

- Date: 11th July
- Time: 1400 WAT
- Expected End Time: 1500 WAT

**Review and Distribution:**

- Please review the minutes for accuracy and clarity.

**Archive:**

- Store the minutes in the designated archive folder.
72 changes: 72 additions & 0 deletions meeting_minutes/format.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@

---

**Meeting Details:**

- Date: [Insert Date]
- Time: [Insert Time]

**Attendees:**

- [Insert Attendee 1 Name] - [Insert Attendee 1 Role]
- [Insert Attendee 2 Name] - [Insert Attendee 2 Role]
- [Insert Attendee 3 Name] - [Insert Attendee 3 Role]
- ...

**Absentees:** (include when anyone else has been invited).

- [Insert Absent Member 1 Name]
- [Insert Absent Member 2 Name]
- ...

**Agenda Review:**

- [Insert Agenda Item 1]
- [Insert Agenda Item 2]
- ...

**Meeting Summary:**

- [Insert Agenda Item 1 Summary]
- [Important Point/Idea/Decision 1]
- [Important Point/Idea/Decision 2]
- ...

- [Insert Agenda Item 2 Summary]
- [Important Point/Idea/Decision 1]
- [Important Point/Idea/Decision 2]
- ...

**Action Items:**

- [Task 1] - Assigned to [Assigned Person/Team] - Deadline: [Insert Deadline]
- [Task 2] - Assigned to [Assigned Person/Team] - Deadline: [Insert Deadline]
- ...

**Decisions and Resolutions:**

- [Insert Decision 1]
- [Insert Decision 2]
- ...

**Additional Notes:** (not specific to agenda items)
eg: suggestions, recommendations

- [Insert Additional Note 1]
- [Insert Additional Note 2]
- ...

**Next Meeting and Adjournment:**

- Date: [Insert Next Meeting Date]
- Time: [Insert Next Meeting Time]
- Expected End Time: [Insert Expected End Time]

**Review and Distribution:**

- Please review the minutes for accuracy and clarity.

**Archive:**
- Store the minutes in the designated archive folder.

---
Loading

0 comments on commit 9726d5e

Please sign in to comment.