Week 10&11(3rd Aug —14th Aug): Team-Based assessment and Tech event.

Prakarsh Gupta
3 min readAug 18, 2023


Combining the summary of two weeks here, since there wasn’t a big change

After Week 9, I had a few tasks to work on:

  • Predefined Team groups: so that when the user wants to view a combination of teams in the heatmap, they can select one from some predefined groups.
  • Revise the logic for the Heatmap as follows: Instead of calculating the percentage done based on the visibility of a team divided by all teams, the new approach focuses solely on the teams that are visible.
  • A PR to merge the current changes from branch gsoc-2023 to master.
  • Fix a few bugs on the heatmap.

During these 2 weeks, I was able to do all these tasks and have pushed the code to the branch ‘feat/teamAssessment’.

Predefined team groups

The nomenclature “AB” corresponds to the inclusion of both Team A and Team B. This functionality operates based on a designated variable within the meta.yaml file. This variable takes the form of a hashmap, where the group name serves as the key, and an array of teams comprises the corresponding value. This design ensures seamless mapping between group labels and the teams they encompass.

Timo’s suggestion introduces the creation of a distinct file named ‘teams.yaml’ to host this variable. This approach enhances user clarity and organization. Furthermore, a valuable addition involves implementing a dedicated tab labeled ‘Teams.’ Within this tab, users can conveniently access an overview of team groupings and their corresponding teams, offering a more intuitive way to comprehend the relationship between team groups and the teams they encompass.

Team Filter

  1. In the current system, when the filter is in use and an activity is chosen, all teams linked to that task are displayed. However, a refinement is needed: the system should exclusively exhibit the teams that have been selected within the active filter, ensuring a more precise alignment between the filter settings and the displayed teams.
  2. The team filtering mechanism can be enhanced through a two-part division. The first part will encompass team groups, such as “All,” “AB,” “BC,” and so on. Meanwhile, the second part will involve individual teams. This setup enables a dynamic interaction: when a specific group is chosen, it not only serves to highlight that group but also brings attention to the individual teams associated with it.

Delivering a presentation at a tech event

I’ve had the privilege of introducing the latest enhancements to a handful of clients, and their positive feedback has bolstered my confidence to take the stage and share these advancements at a prominent tech event. Both Timo and Aryan have been incredibly supportive of this endeavor.

Currently, I’m in the process of actively seeking out opportunities to present on the topic of DevSecOps in the Delhi NCR region. Notably, I have my sights set on participating in the Open Security Summit (OSS) scheduled for October, as well as potentially contributing to the OWASP New Delhi Local Chapter event, also anticipated in October. The prospect of sharing insights and collaborating with fellow professionals in these settings is truly exciting.

Connect with me :)

dotCard | Twitter | LinkedIn | GitHub



Prakarsh Gupta

#buildinpublic GSoC'23 @OWASP || SDE 1 @ Expedia Group || NIT Kurukshetra