Reviewing Mentorship Proposals through LFX Portal could be improved for mentors
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 816
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 8
Description
## Few problems on top of my head
- Search could be simpler and intuitive.
- ctrl + click on search results should open in new tab.
- search should prefer new and open projects than projects that are completed two years ago.
- direct association of mentee LFX profile to github username should be mandatory to avoid confusion.
- LFX mentee profile creation should ask for mentee slack id in cncf/k8s slack channels. (advise to use this as same as github username).
- mentee selection should be done in the lfx portal rather in google forms.
## features maybe in future
- a tab showing how much potential candidates are involved in the project with information sourced from devstats would be good
- better filtering of mentee list in lfx portal - not just filter by tasks completed by mentee but also be able to filter by mentees who were active in organisation's github.
Contributor guide
Research direction
Start by reviewing the LFX Portal mentor workflow, especially project search and mentee selection, and compare it with the current Google Forms process. Check how GitHub activity, Devstats data, and Slack or GitHub identity details are currently represented. No repository files, tests, or single acceptance criterion are named, so the scope and definition of done need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- developer-experience, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100