Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Design and implement metadata matching system #501

Open
arkid15r opened this issue Jan 16, 2025 · 6 comments · May be fixed by #913
Open

Design and implement metadata matching system #501

arkid15r opened this issue Jan 16, 2025 · 6 comments · May be fixed by #913
Assignees
@Rajgupta36
Labels
backend

Comments

@arkid15r
Copy link
Collaborator

arkid15r commented Jan 16, 2025 •
edited
Loading

Design and implement a way to match community users to project leaders. For leaders we typically have first name and last names (sometimes just partial full name with some comment) so the workflow might need a manual involvement in some cases. But it seems we can easily match exact match cases while keeping "unsure" mappings as suggestions for further human processing.

The owasp app models should be modified to include leaders m2m relations to github.user. The command/job should suggest/populate chapter/committee/project leaders based on a certainty level.

Another area that the system should cover is entity / Slack channel mapping. Same functionality just in a different context.
For this we'll need to create a new model in slack app (probably, Channel)

I believe in order to achieve the best results the system should suggest matches that need to be verified/approved manually.

This is just an abstract problem description to start a discussion regarding the implementation.

          it's good idea but We don't have any links in the project index, and we can't identify a specific user from name.

Originally posted by @Rajgupta36 in #470 (comment)
@github-project-automation github-project-automation bot moved this to Backlog in Project Nest Jan 16, 2025
@KatalKavya96
Copy link

KatalKavya96 commented Jan 16, 2025 •
edited
Loading

@arkid15r I think i can resolve this issue,Kindly assign me this issue

@Raghavg18
Copy link
Contributor

@arkid15r Can u assign me this issue ?

@Rajgupta36
Copy link
Collaborator

@arkid15r can i work on it ?

@arkid15r arkid15r moved this from Backlog to In progress in Project Nest Jan 16, 2025
@arkid15r
Copy link
Collaborator Author

arkid15r commented Jan 16, 2025 •
edited
Loading

@KatalKavya96 @Raghavg18 I suggest starting with "good first issue" labeled issues and less complex tasks. The gradual task difficulty increment approach helps mentors to make sure tasks assigned to a right contributor.

upd: e.g. #502

@arkid15r arkid15r changed the title Design and implement leaders/community user matching Design and implement metadata matching system Jan 17, 2025
@harsh3dev
Copy link
Collaborator

Hi, @Rajgupta36 is this WIP? I would like to discuss more about how we can solve this problem.
I am interested to tackle it if its not been worked upon.

@Rajgupta36
Copy link
Collaborator

Hi, @Rajgupta36 is this WIP? I would like to discuss more about how we can solve this problem.
I am interested to tackle it if its not been worked upon.

Hii @harsh3dev . It's WIP . I created matching model now I am working on slack model

@Rajgupta36 Rajgupta36 linked a pull request Feb 22, 2025 that will close this issue
Draft
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rajgupta36 Rajgupta36

Labels
backend
Projects
Project Nest
Status: In progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

implemented matching leader model Rajgupta36/Nest-n
5 participants
@arkid15r @harsh3dev @Rajgupta36 @KatalKavya96 @Raghavg18