Labels
Clear labels
bug
documentation
duplicate
enhancement
help wanted
invalid
question
wontfix
Kind/Bug
Kind/Enhancement
Kind/Feature
Kind/Question
Kind/Security
Kind/Testing
Status/Confirmed
Something is not working
issues with documentation purpose
This issue or pull request already exists
New feature
Need some help
Something is wrong
More information is needed
This won't be fixed
Something is not working
Improve existing functionality
New functionality
A question
This is security issue
Issue or pull request related to testing
This is indeed a bug/issue
Complexity
Easy
The complexity is low
Complexity
Hard
The complexity is high
Complexity
Medium
The complexity is medium
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Doing
Somebody is working on this
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Status
Review needed
Needs a reveiw
No labels
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lfk/org#7
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One part of the project that we'll have to implment right after the runner management by admins is the runner selfservice.
What runner selfservice?
We need a registration self service (registration form) for company runners (register for a company w/ a special link) an runners from the public (register with email confirmation.
This selfservice should also include a "about me" page, where the runner can view his registration status (and maybe later his distance, donations etc).
My first idea for this would be the following api endpoints:
/runners/register -> Register as a runner
/runners/register/:jwt -> Register as a runner for a company
/runners/me/:jwt -> View information about your registration
The specifics can of course vary - it's just my first idea for this.
The registration is implemented.
I'd reccomend starting planning and development on the selfservice frontend eary febraury after lfk/frontend has a first production-ready release.
Selfservice-UI is implemented over here: https://git.odit.services/lfk/selfservice