Dear All,

Below are the minutes of the meeting from today's discussion:

Attendees: Canonizer Team, Talentelgia Team, Iffort Team, Code District Team
Meeting Date: 6th October 2021
Meeting Time: 6:00 pm IST to 06:48 pm IST
Agenda: Scrum call, 6th October Agenda items

Meeting points discussed

1. Ashish gave an update on the tickets Iffort team is working on.
2. Hamza gave an update on the tickets Code District team is working on.
3. Rohit gave an update on the tickets Talentelgia team is working on.
4. All the teams have to assign the tickets to themselves from the 23rd release items.
5. Ashutosh will check the Laravel upgrade issue and will share his findings.
6. Teams need to decide the best way to manage the email templates.
7. Different teams need to update their design under their sub camps for consensus under topic "Canonizer Website UI/UX Design"
8. Code district team will present an updated design on Friday.
9. Teams need to share the hours for the month of September to Kinnari.
10. Need to have a mechanism to report the posts on forms and the post will be automatically removed if gets reported by different users.
11. Meeting Recording Link: https://bit.ly/3FnFa6r

Thanks & Regards,

Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's discussion:

Attendees: Canonizer Team, Talentelgia Team, Iffort Team, Code District Team
Meeting Date: 5th October 2021
Meeting Time: 6:00pm IST to 07:16pm IST
Agenda: Scrum call, 5th October Agenda items
Meeting points discussed:

1. Each team gave an update on the tasks they have worked on.
2. For the issues regarding the Language update or Content text, developers need to tag Brent, Jim or Daksh.
3. Code District team presented the design of website.
4. We need to create different camps and sub camps under topic "Canonizer Website UI/UX Design" to submit designs related to different pages and get consensus on the designs.
5. Meeting Recording Link: https://bit.ly/3muUdmr

Thanks & Regards,

Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's discussion:

Attendees: Canonizer Team, Talentelgia Team, Iffort Team, Code District Team

Meeting Date: 4th October 2021

Meeting Time: 6:00pm IST to 07:16pm IST

Agenda: Scrum call, weekly Monday discussion, 4th October Agenda items

Meeting points discussed:

1. Each team gave an update on the tasks they have worked on.

2. Ashish discussed queries on ticket number #776 and Brent gave the solution as to how Private nickname logic is to be implemented.

3. Rupali shared the email template document she had prepared and it needs to be reviewed and if there is anything missing, it needs to be added to the Email template document.

4. Hamza discussed queries on ticket numbers #789, #759, #773 Rupali, Brent and Varun explained the solution for the same.

5. Rohit submitted the current website features list and created a topic: https://bit.ly/3a7gwIW

6. Rohit submitted the software coding standards and guidelines document and created a topic: https://bit.ly/3l5rmFQ

7. Meeting Recording Link: https://bit.ly/3uCJ0nk

Thanks & Regards,

Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's discussion:

Meeting Date: 1st October 2021

Meeting Time: 6:00pm IST to 07:04pm IST

Agenda: To discuss the development process of Canonizer 3.0 and daily standup call to discuss the tasks.

Meeting points discussed:

1. Each team gave an update on the tasks they have worked on.

2. Each team discussed the queries they has on the tasks.

3. Talentelgia team is working on creating the Feature Listing of the project and will submit it on Monday.

4. A new Topic is to be created for the feature listing and should be added to the High-level design camp.

5. Consensus design camp statement needs to be updated to "We are no longer using this camp" and add a link to Scalability Architecture topic and the content needs to be copied from Census Design statement to Scalability Architecture Design topic.

6. The score filter should always be 0.

7. We discussed that we need to create the sprint plan from the feature listing being prepared and should start creating the wireframes.

8. Technical architects from different teams need to have a meeting with the Canonizer development team to understand the algorithms so that they can provide a solution to optimize the Canonizer Tree.

9. Talentelgia team and Code district team can work on the design wireframes and consensus can be taken on the wireframes from different teams.

10. Meeting Recording Link: https://bit.ly/3A05P5q

Thanks & Regards,

Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's discussion:

Meeting Date: 30th September 2021

Meeting Time: 6:00pm IST to 6:53pm IST

Agenda: To discuss the development process of Canonizer 3.0 and daily standup call to discuss the tasks.

Meeting points discussed:

1. We discussed about creating 3 different repositories for different codebases (Web services, frontend, admin)

2. Sunny gave a presentation about the project development process.

3. We discussed about dividing the modules between different teams.

4. We have to create the complete feature listing document for Canonizer 3.0 based on Canonizer 2.0. We can add the new suggestions in the feature listing.

5. Meeting time need to be changed from tomorrow. Standup call will be first at 6:00 pm IST and after that, the design discussion meeting will start.

6. Software coding standard and guidelines document was shared in the Skype Group.

7. We have to save the documents of the projects on the Github wiki.

8. Current database of Canonizer 2.0 will be cloned for the Canonizer 3.0 and data will be copied periodically from the live db to Canonizer 3.0 database.

9. A new server will be launched for Canonizer 3.0

10. We will be using Jira for project management of Canonizer 3.0 and will keep using the Github board for Canonizer 2.0 tickets.

11. We discussed about the developers from the different teams working on the tickets.

12. Each team gave an update on the tasks they have worked on.

13. Varun Gautam will review the tickets which are not assigned to anyone and will assign them to developers.

14. Meeting Recording Link: https://bit.ly/3meGoYZ

Thanks & Regards,

Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's (29th Sptember, 2021) discussion:

Meeting Date: 29th September 2021
Meeting Time: 6:00pm IST to 9:19pm IST
Agenda: To finalize the Technology Architecture to be used for the project
Meeting points discussed:
1. Discussed about Server-side rendering.
2. We discussed that we need to first document the features which need to be there in the minimum viable product.
3. Then based on the finalized features different teams can start working on Wire-framing, Web-service development.
4. In the stand-up call, all the teams gave the status update on the tickets and asked the queries they had.
5. We have to finalize the technology stack and all the representatives from different teams should give their support before tomorrow's meeting.
6. Sunny Jindal will be updating the mail camp statement with all the finalized technology stack.
7. Meeting Recording Links:
https://bit.ly/3A3gw7D
https://bit.ly/3Dbs0Ib

Thanks & Regards,
Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's discussion:

Meeting Date: 28th September 2021

Meeting Time: 7:00pm IST to 8:15pm IST

Agenda: To discuss the Technology Architecture to be used for the project

Meeting points discussed:

1. We discussed the web services framework to be used and Laravel Lumen was preferred for the web services and Laravel for admin.
2. We discussed the Authentication services to be used.
3. We discussed the Front-End Framework to be used. We need to build consensus on whether to use React js or Next js.
4. Server-Side rendering was discussed for SEO optimization.
5. We discussed the Design Framework to be used.
6. We discussed the Database to be used.
7. We discussed the Caching server to be used and we should wait to finalize it as we should first discuss how to optimize the current Tree calculations.
8. We discussed the Deployment process to be used.
9. We discussed the Testing framework to be used. For backend Laravel PHPUnit to be used, for React, Jest is to be used, and for QA Selenium web-driver with Python to be used.
10. We discussed the Issue Tracking Software to be used and Trello and Jira were to be added as competing camps.
11. Every team gave an update on the tasks they are working on.
12. Meeting Recording Links:

https://bit.ly/3ulqoIh
https://bit.ly/2WnBiB0

Thanks & Regards,
Rohit Gupta

Dear All,

Below are the minutes of the meeting from today's Design architecture discussion meeting:

Meeting Date: 27th September 2021

Meeting Time: 7:00pm IST to 7:30pm IST

Agenda: To discuss the Languages to be used for the project

Meeting points discussed:

1. We discussed the language to be used for the project.

2. We need to create separate topics for different topics and will have sub-camps under them for the language proposal.

3. Need to discuss if we need to have separate mobile apps using hybrid technology.

4. Discussed the tree snapshot caching.

5. Discussed if we should have the scores of the algorithms to be saved in the database for better performance.

6. Meeting Recording Link: https://bit.ly/3mkfrn5

Regards,

Rohit Gupta

Thanks Rohit, this is the greatest, and so needed.  I was sleeping, so nice to get caught up, thanks to your great effort.

And, I was able to see the question for me:

The public nick name is for someone willing to vote for something, publicly.  It is always my hope that it is very close to their real name.  As I am bad enough with real names, let alone having different nick names for me to keep track of and map between.  Evidently we need to explain this to people, so they can create better public nick names to increase publicly identifiable communication.

The "private" nick name is meant to be used, when someone wants to "vote" anonymously.  Of course, it is good to have this be different than your real name.

We need a security expert to design a system so, when required, we can canonize these anonymous IDs, yet keep them anonymous, and also, we don't want anyone else to be able to make the connection from the anonymous ID, and the actual identity of the person controlling it.  We want people to be able to trust canonizer with their anonymous identities, and any personal information they mark as wanting to be private.

Dear All,

I am sharing the minutes of the meeting below related to the Demo session we had today:

Agenda:

This meeting is held to give a demo of the project to different teams

Attendees:
    - Canonizer Development team (Varun, Rupali)
    - Talentelgia Team (Rohit, Sania)
    - Code District Team (Ali Ehsan, Hamza)
    - Iffort Team (Ashish)

Meeting Date: 25th September 2021
Start Time: 10:30 am IST
End Time: 11:30 am IST
Meeting Duration: 1 Hour
Meeting Medium: Skype

Meeting points discussed:

1. Basic overview of the project is discussed.
2. How the website is dependent on the Nick Name
3. Hierarchy of tree structure was discussed.
4. Different statuses of the topics, camps were discussed (Live, In Review, Objected, Old). We should create a document for these statuses.
5. Conditions related to the creation of topics and camps were discussed.
6. How the namespaces are being added to the system from admin was discussed.
7. All the queries asked by different teams were discussed.
8. Also, there will be another meeting required to discuss different algorithms.
9. All the teams will explore the system and will come up with the queries they have.
10. Meeting was recorded and here is the link to the video: https://bit.ly/3o7Ybnd

During the discussion, there was a query as mentioned below which needs clarity from Brent:

1. Need clarity on Public/Private nicknames as to what is the purpose of having a private nickname in the system, as currently, it is of no significance.

-- 
Thanks & Regards,

Rohit Gupta