greenelab / greenelab/tribe-client
Have the client's access be able to be set as preferences by each user individually, for each client server/application.
Open
backlog
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Suggested by Casey and Alicja in #tribe channel for FunctionLab
This issue was imported from the old repository in bitbucket (https://bitbucket.org/greenelab/tribe-client/issues).
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing the Python client's handling of access and preferences, then confirm the intended per-user, per-client-server/application behavior with maintainers; done means that scope is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100