Timetable vs. Session Display protected content visibility
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 551
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 21
Description
``` yaml
# Ticket imported from Trac
```
While merging #1084, I've realized there are some details concerning visibility that we should sort out.
Namely, in "Session Display", what happens if a session is protected but there is a public contribution inside? Should it be displayed as the only thing inside the session? Should the whole session require authentication? (just like now?) And we need to make this behavior consistent with that of the timetable (it is not, as of now).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the protected-content behavior in Session Display with the timetable, focusing on how a protected session containing a public contribution is handled. The issue does not name files or tests, and work is complete only after the visibility behavior is decided and made consistent between both views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100